Here's what's confusing to me. I know you are right about the inject element. I think that goes in the component/page specification. As far as the hivemodule.xml, I'm very confused by the documentation. There is nothing in the docs showing a full example. I'm going to look at the examples that come with the tapestry download. Maybe I can find something there. The off thing is that we have that rare case where our webapp is deployed with 4 instances of the Tapestry servlet. The docs said something about having /WEB-INF/appContext/hivemodule.xml for each of the instances, based on the instance's appContext name. I'm not sure if I can share the visit aso across each of the apps (having one /meta-inf/hivemodule.xml), or if each needs it's own version (/WEB-INF/appContext/hivemodule.xml).
Thanks for the help... Frank Russo Senior Developer FX Alliance, LLC -----Original Message----- From: karthik G [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 07, 2005 10:14 AM To: Tapestry users Subject: Re: Basic 4.0 upgrade question I'm a beginner. But I thought I s'd make an attempt to answer this question. So I'm sorry if this is not what you are looking for. Are'nt session objects stored in META-INF/hivemodule.xml in tapestry4 and then injected into the page using <inject> element when using JDK < 1.5 ? --- hivemodule.xml -- <?xml version="1.0"?> <module id="com.your.package" version="1.0.0"> <contribution configuration-id="tapestry.state.ApplicationObjects"> <state-object name="visit" scope="session"> <create-instance class="com.YourClass"/> </state-object> </contribution> </module> and later in the page specification - <inject property="visit" type="state" object="visit"/> and in the page, public abstract YourClass getVisit(); regards karthik * * --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
