Michael Horwitz wrote:
Matt is right - it definitely should work. I'm pretty sure I have done this in the past without issue.
Do you use spring1.x or spring2 ? I keep thinking my problem has to be in applicationContext-service.xml, and I was looking for other (working) files to compare mine against...
In terms of transaction/session handling the OpenSessionInViewFilter should take care of making sure the session is opened/closed once per request. The tx advice interceptors on the manager methods should open and close transactions on the same session - so you should definitely not have lazy loading issues. And by default transactions should be propogated.
Yes--I would claim that the most annoying problems with software in general are when something "should" work, but doesn't. :-)
One thing to check - everything is thread based. I'm assuming you are not spawning another thread to call the second manager?
Nothing strange going on thread-wise in this action or in the business logic in question. (Elsewhere in the webapp I do have an action that uses execAndWait for a long-running task, and does a dance to get the session to stay open until that spawned thread is complete, and that works like a charm.)
Any other suggestions? -Dale --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
