AW: Tapestry 4.1, Problems when adding Service implementing IEngineService to hivemind.xml, Element service not allowed here

2008-02-20 Thread Stroeber, Andreas
to look at. Thanks so far. Andi -Ursprüngliche Nachricht- Von: Igor Drobiazko [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 19. Februar 2008 18:54 An: Tapestry users Betreff: Re: Tapestry 4.1, Problems when adding Service implementing IEngineService to hivemind.xml, Element service

Tapestry 4.1, Problems when adding Service implementing IEngineService to hivemind.xml, Element service not allowed here

2008-02-19 Thread Stroeber, Andreas
Hi users, It's driving me crazy. :o( The thing i want to accomplish is, adding a new service to my tapestry application. Relying on Enjoying Web Development with Tapestry, it can be done by writing a class implementing the interface IEngineService and furthermore adding some configuration to

Re: Tapestry 4.1, Problems when adding Service implementing IEngineService to hivemind.xml, Element service not allowed here

2008-02-19 Thread Alejandro Scandroli
Hi Andreas, I think you should use service-point instead of service (I'm not sure if this has changed between Tapestry versions) Try something like this: service-point id=pdf interface=rd.bird.colibri.tapservices.FileService invoke-factory

Re: Tapestry 4.1, Problems when adding Service implementing IEngineService to hivemind.xml, Element service not allowed here

2008-02-19 Thread Igor Drobiazko
Here is an example from a production application: service-point id=ChartEngine interface=org.apache.tapestry.engine.IEngineService invoke-factory model=threaded construct class=impl.ChartEngineServiceImpl set-object property=exceptionReporter