Ryan Nowak

I would second Herman's advice, turn logging on DEBUG and watch the logs. Does it begin a transaction? If not then something in your aop configuration is wrong.

I suggest starting with the some of the FAQ's and literature where they try to convince you to use it. Once you understand their philosophy, learning the concepts will be easy because you will already have a guess at how they implement a feature.

After this point you must learn about Beans, ApplicationContext and configuration. Most other topics will require a basic knowledge of loading and configuring beans. Head to the (excellent) documentation, browse that for some interesting sections. If there is an api in particular you want to learn within Spring, tackle that after you "get" bean configuration.

Beyond that, use some reflection, why do you want to learn Spring? What will you use it for? Find something cool and try it out.

If you try running with debugging on in your logger it will display the sql string that it generates, of the form :

? = call Schema.Package.Function(?, ?, ?)

Where using unnamed parameters (thats what StoredProcedure does), they are bound in order of declaration. So that's why the return parameter must go first. The reasoning seems totally reasonable to me, but this should be documented.

The isFunction boolean property determines whether there is a "? = " at the beginning. So without setting it to a function, you would just have "call Schema...."

Rashid,

Put the return parameter first in your declaration.

This was hard to find in the documentation, I struggled with it for a while.