This content has been marked as final.
Show 3 replies
-
1. Re: Page action pain, new stateless component instance?
grettke_spdr Jul 2, 2007 12:51 PM (in response to grettke_spdr)To clarify, when I set up the flow in this manner, the two properties get lost. I suppose that the hashCode doesn't matter, I just want my stateless component.
As an aside, when I set this up using two stateless components a "form" and then the "action", everything works correctly.
Here is a log from this flow:2007-07-02 11:49:24,707 DEBUG [com.churchmutual.rms.action.impl.InspectionReques tActionImpl] Set account number: 0000415-02-1024 2007-07-02 11:49:25,629 DEBUG [com.churchmutual.rms.action.impl.InspectionReques tActionImpl] Hashcode: 32053749 2007-07-02 11:49:35,207 DEBUG [com.churchmutual.rms.action.impl.InspectionReques tActionImpl] Set user profile: JohnDoe 2007-07-02 11:49:35,707 DEBUG [com.churchmutual.rms.action.impl.InspectionReques tActionImpl] Hashcode: 5658787 2007-07-02 11:50:13,831 DEBUG [com.churchmutual.rms.action.impl.InspectionReque tActionImpl] Prepare page 2007-07-02 11:50:13,831 DEBUG [com.churchmutual.rms.action.impl.InspectionReque tActionImpl] Hashcode: 21178698
-
2. Re: Page action pain, new stateless component instance?
pmuir Jul 2, 2007 1:03 PM (in response to grettke_spdr)A stateless bean has no guarantee of holding state between method requests. Try putting it in the EVENT scope.
-
3. Re: Page action pain, new stateless component instance?
grettke_spdr Jul 2, 2007 1:04 PM (in response to grettke_spdr)"pete.muir@jboss.org" wrote:
A stateless bean has no guarantee of holding state between method requests. Try putting it in the EVENT scope.
Hi Pete, I'm really having a day over here. I can't believe I even posted this. I thought that it had been cut over to a stateful component already. I even posted about it being stateless. Thanks for listening I hope you don't charge standard therapist fees on this stuff.