This is how I inject spring into my engine service:
<service-point id="LandingService"
interface="org.apache.tapestry.engine.IEngineService">
<invoke-factory>
<construct class="engine.LandingService">
<set-object property="responseRenderer"
value="infrastructure:responseRenderer"/>
<set-object property="linkFactory"
value="infrastructure:linkFactory"/>
<set-service property="request"
service-id="tapestry.globals.HttpServletRequest"/>
<set-service property="response"
service-id="tapestry.globals.HttpServletResponse"/>
<set-object property="pageService"
value="service:tapestry.services.Page"/>
<set-object property="homePageName"
value="app-property:org.apache.tapestry.home-page"/>
<set-object property="notFoundPageName"
value="app-property:org.apache.tapestry.notfound-page"/>
<set-object property="market" value="spring:personal.Market"/>
<set-service property="identity" service-id="Identity"/>
</construct>
</invoke-factory>
</service-point>
"Josh Long" <[EMAIL PROTECTED]> skrev i en meddelelse
news:[EMAIL PROTECTED]
>I was usuing tapestry 4.1.1-snapshot gleefully and one day it (maven
> and the snapshot with it) updated above and beyond
> 4.1.1-20060802.044417-5 (the particular snapshot iteration after which
> my build stop working around a week or two ago). I was receiving
> strange errors about classpath conflicts, etc.
>
> I pinned my snapshot iteration down and just now took another whack at
> resolving the issue. the errors were related to hivemodule.xml having
> a conflict with the class path of the tapestry framework jars
> hivemodule.xml.
>
> so, first question: where (if not webapp/WEB-INF/) does hivemodule.xml
> properly go? Right now i have hivemodule.xml named oldhivemodule.xmla
> nd everything works properly.. except all the things hivemodule.xml
> was responsible for (engine services, freindly-urls, a custom
> persistence mechanism...)
>
> And, while im on a hivemodule roll, would someone be kind enough to
> show me how i would inject a spring bean accessible through spring:foo
> into an engine service? Im not quite sure I get the
> factory/create-instance/lightweight initialization etc routine, and
> cant figure out for the live of me what i would need to get a tapestry
> service wired with a spring bean...
>
> Thanks again!
>
> Peace,
> Josh
>
> ---------------------------------------------------------------------
> 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]
