How to uitlise full potential of Spring Framework

[Kishor Joshi]

Hi there
I am designing a web application using Spring Framework.I have learn a lot about Spring Framework.
I will use following Spring Advantages.

1)Spring Dependency Injections
2)Application Context.
3)Constructor Injection,Invoking Objects.
4)Autowiring,and many annotations of Spring Frameworks.
5)AOP(Aspect Oriented Programming) concepts.
6)Bean defination Inheritence.
7)Pointcuts and Wildcards.
8)Inner beans,Aliases.
9)Spring+Hibernate.


Those topics that I learned so far from Spring Frameworks.

Is there any other Spring Framework Features that I can use for better designing of my projects.?


Thanks

[Ulf Dittmer]

I think you're going about it the wrong way. You should choose a framework based on what you want it to do for you, not choose a framework first and then figure out what it can do for you. For any given task there may be other frameworks out there that are better suited. Or you may not want to use any framework for some particular task.

[Kishor Joshi]

You are write ulf

But so far That I have explored both Struts and Spring.

So I decided to use (Spring+Hibernate+Oracle+Front End Technologies)


for my tasks.

So Is there any thing in Spring that i can use better way.

The Online documentation is not vary effetcive to learn for a beginner..

So anything else in this framework?


Thanks

[Ulf Dittmer]

I think you missed the point I was trying to make. Spring can do tons of things, but that doesn't mean it makes sense to use them in any particular project. So again: define what you need done, and then make a decision on which framework (Spring, or some other, or none at all) to use.

What do you mean by "better" - better than what?

What do you mean by "anything else" - other than what?

[Kishor Joshi]

Ok so far the requirement I have will be satisfied by these framework later let you know.If there is something that Spring Can't do?

[Ulf Dittmer]

Tons of stuff. Making ice cream, for example. Spring is a bunch of frameworks, nothing more, nothing less - it is not the be-all-and-end-all of software development. Sooner or later you will run into things it can't do, and which you need to implement yourself, or use some other library for. But it seems this discussion is converging with the other one you started in https://coderanch.com/t/636867/Spring/frameworks.

[Jayesh A Lalwani]

Spring really is a collection of 20+ projects. The overall Spring architecture is represented by this diagram



This is not complete, but gives you an idea of where things lie.

If you want to learn Spring, it is essential to learn AOP, Aspects, everything in the Core Container and the Tests layer. Learning these things gives you the grounding to learn everything else. You should then make yourself familiar with all the other 20+ projects. You should know what each project does and where you can apply them. You don;t need to learn them in detail. You only need to learn them in enough detail so you can decide that where the project will be useful. You should only learn the projects that you really need to. It's very difficult to learn all the Spring projects in great detail.

I bet there are some Spring Gods who know all the Spring projects in detail. I haven't met any of those Gods. Personally, I learn what I need when I need it.