-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I can verify that the tap 4 jar is good. Looking at your stack trace (and yes, I looked at it all - boy... gotta love "detail"), is it possible you have either a) outdated dependencies or b) an improper tap 4 jar? Given the information you posted earlier, I tried to duplicate your environment (jar locs, hivemodule piece, etc) and still have no problems with getting the service encoder working properly.
As a side question... have you tried restarting Tomcat? I wouldn't expect this to cause any problems, but it's an unknown... so... Let me know if you still encounter issues. Brian Mitch Christow wrote: > At least nobody can complain about not seeing the nested exceptions :) > > On a different note though, anybody know if there is a problem with the > tapestry 4 jar, since it is complaining about the tapestry.request.xml file? > > Regards, > Mitch > > > -----Original Message----- >>>>>>> . . . >>>>>>> >>>>>>> <servlet-mapping> >>>>>>> >>>>>>> <servlet-name>myApp</servlet-name> >>>>>>> >>>>>>> <url-pattern>*.html</url-pattern> >>>>>>> >>>>>>> </servlet-mapping> >>>>>>> >>>>>>> . . . >>>>>>> >>>>>>> >>>>>>> >>>>>>> Furthermore I have added a hivemodule.xml file to my project with >>> the >>>>>>> following content: >>>>>>> >>>>>>> >>>>>>> >>>>>>> <?xml version="1.0"?> >>>>>>> >>>>>>> <module id="com.testApplication" version="1.0.0" package=" >>>>>>> com.testApplication "> >>>>>>> >>>>>>> <contribution configuration-id="tapestry.url.ServiceEncoders"> >>>>>>> >>>>>>> <page-service-encoder id="page" extension="html" >>>>>>> service="page"/> >>>>>>> >>>>>>> </contribution> >>>>>>> >>>>>>> </module> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFDybo6aCoPKRow/gARAlgnAKCNwchKvsrMb/RRGYWVVa+tLvMpXgCgxkmH bvQO2FhqSM54/YxMGn6EyVc= =DIOV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
