Hi Michael,
Michael Horwitz wrote:
The usual culprit here is in the naming of the manager class your are
using to do the save/edit. AppFuse ships with the following
definitions for the AOP transaction proxy:
<aop:config>
<aop:advisor id="userManagerTx"
advice-ref="userManagerTxAdvice" pointcut="execution(*
*..service.UserManager.*(..))" order="0"/>
<aop:advisor id="userManagerSecurity"
advice-ref="userSecurityAdvice" pointcut="execution(*
*..service.UserManager.saveUser(..))" order="1"/>
<aop:advisor id="managerTx" advice-ref="txAdvice"
pointcut="execution(* *..service.*Manager.*(..))" order="2"/>
</aop:config>
In short this says proxy all classes with names ending in 'Manager'
that are in package 'service'. In AppFuse this translates to proxying
all methods defined in the manager interface (it is the interface that
is proxied here, not the implementation).
Thanks for the reply, which was very educational. Unfortunately, I
don't believe that my Manager is the problem. The reason I believe that
is that my Manager is named DeliveryManager (and DeliveryManagerImpl)
which fits the pattern specified above. Also, when it is called by my
DeliveryAction class, I have no problems saving my form data.
Maybe I didn't explain the problem well enough.
If I take the following track:
DeliveryAction -> deliveryList.jsp -> DeliveryAction -> deliveryForm.jsp
-> DeliveryAction etc. it all works fine.
However, If I take this track:
DeliveryOverviewAction -> deliveryOverview.jsp -> DeliveryAction (via
post to delivery.html) -> deliveryForm.jsp ..., I get my error here as
soon as I post back to DeliveryAction.
Cheers,
Rob Hills
Waikiki, Western Australia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
