I think the 2nd way with "<set-object>" way does not work because "SessionNumbers" isn´t a property of the ApplicationStateManager itself. I think thes ASOs are held in some kind of internal collection and this collection would be the ASOs property.
The first way should be the way to go but unfortunatly I don´t know how. The only hints that I have are: - is the StateObject referenced correctly (full qualified HiveMind name) - maybe you can contribute some translator/provider to tapestry that is able to help you inject your SessionNumbers object --- i just thought that there is a convenient way to push my visit-object to the EngineService... --- Why not getRequestCycle().getEngine().getVisit() ??? -----Ursprüngliche Nachricht----- Von: Peter Schröder [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 14:03 An: Tapestry users Betreff: AW: T4 aso in service hi holger, i tried it that way, but i could not figure out, how to access the state-object as a value. SessionNumbers is my state-object. i tried stuff like: <set property="numbers" value="SessionNumbers" /> -->Unable to translate 'SessionNumbers' to type de.freenet.pos.klarmobilBusiness.beans.SessionNumbers: No property editor for de.freenet.pos.klarmobilBusiness.beans.SessionNumbers. <set-object property="numbers" value="service-property:tapestry.state.ApplicationStateManager:SessionNumbers" /> -->Class $ApplicationStateManager_111e5aa0536 does not contain a property named 'SessionNumbers'. i just thought that there is a convenient way to push my visit-object to the EngineService... -----Ursprüngliche Nachricht----- Von: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 12:21 An: Tapestry users Betreff: AW: T4 aso in service I think when you have a getter and setter for "yourObject", then you can set the object via hivemind in your service declaration, something like that: <service-point id="ServiceID" interface="com.company.Interface"> <invoke-factory> <construct class="com.company.ServiceImpl"> <set property="yourObject" value="value"/> </construct> </invoke-factory> </service-point> Have a look a this: http://hivemind.apache.org/hivemind1/hivemind/BuilderFactory.html -----Ursprüngliche Nachricht----- Von: Peter Schröder [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 12:03 An: Tapestry users Betreff: AW: T4 aso in service i get the ASM bye tapestrys autowiring. so there is no way to inject the object directly? i thought there would be, cause hivemind knows all state-objects from hivemodule... -----Ursprüngliche Nachricht----- Von: Holger Stolzenberg [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 11:45 An: Tapestry users Betreff: AW: T4 aso in service We are going this way: public void service( IRequestCycle cycle ) { ApplicationStateManager manager = cycle.getInfraStructure().getApplicationStateManager(); YourObject o = (YourObject)manager.get( "HiveMindASOKey" ); } -----Ursprüngliche Nachricht----- Von: Peter Schröder [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 10:55 An: Tapestry users Betreff: T4 aso in service hi, i want to access some state-object in an engine-service. currently i am doing that by injecting the ApplicationStateManager and getting the object from it. is there a more elegant way to do that (via hivemind?)? kind regards, peter -----Ursprüngliche Nachricht----- Von: Andreas Pardeike [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 12. April 2007 09:42 An: Tapestry users Betreff: Tapestry 5 Redirects On 12 apr 2007, at 03.29, Howard Lewis Ship wrote: > Every request is a page redirect in T5. Check the URLs in the browser > as you work through the application. Is that clever design? I can think of several reasons why this could be a bad idea. What's the reasoning behind this? Andreas Pardeike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
