Issue 40 in tapestry5-cayenne: Doesn't work with Tapestry 5.3.2

10 views
Skip to first unread message

tapestry...@googlecode.com

unread,
Mar 15, 2012, 5:59:27 PM3/15/12
to tapestry5-caye...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 40 by rfrov...@gmail.com: Doesn't work with Tapestry 5.3.2
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=40

I'm not having luck with having 0.4 work with Tapestry 5.3.2. I'm using the
same jars I used with 5.2.6.

When starting with Jetty, I get the following:

2012-03-15 16:55:36.344:WARN::failed app: java.lang.RuntimeException:
Exception loading module(s) from manifest
jar:file:/home/rfrovarp/.m2/repository/com/googlecode/tapestry5-cayenne/tapestry5-cayenne-server/0.4/tapestry5-cayenne-server-0.4.jar!/META-INF/MANIFEST.MF:
Failure loading Tapestry IoC module class
com.googlecode.tapestry5cayenne.services.TapestryCayenneModule: Error
invoking service binder method
com.googlecode.tapestry5cayenne.services.TapestryCayenneCoreModule.bind(ServiceBinder)
(at TapestryCayenneCoreModule.java:93):
org/apache/tapestry5/PrimaryKeyEncoder
2012-03-15 16:55:36.345:WARN::Failed startup of context
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext@10ce397{/test,/home/rfrovarp/test/test/src/main/webapp}
java.lang.RuntimeException: Exception loading module(s) from manifest
jar:file:/home/rfrovarp/.m2/repository/com/googlecode/tapestry5-cayenne/tapestry5-cayenne-server/0.4/tapestry5-cayenne-server-0.4.jar!/META-INF/MANIFEST.MF:
Failure loading Tapestry IoC module class
com.googlecode.tapestry5cayenne.services.TapestryCayenneModule: Error
invoking service binder method
com.googlecode.tapestry5cayenne.services.TapestryCayenneCoreModule.bind(ServiceBinder)
(at TapestryCayenneCoreModule.java:93):
org/apache/tapestry5/PrimaryKeyEncoder
at
org.apache.tapestry5.ioc.IOCUtilities.addModulesInManifest(IOCUtilities.java:123)
at
org.apache.tapestry5.ioc.IOCUtilities.addDefaultModules(IOCUtilities.java:77)
at
org.apache.tapestry5.internal.TapestryAppInitializer.<init>(TapestryAppInitializer.java:124)
at org.apache.tapestry5.TapestryFilter.init(TapestryFilter.java:103)
at
org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
...

tapestry...@googlecode.com

unread,
Mar 15, 2012, 6:59:24 PM3/15/12
to tapestry5-caye...@googlegroups.com

Comment #1 on issue 40 by rfrov...@gmail.com: Doesn't work with Tapestry
5.3.2
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=40

My attached patch (against trunk) passes all of the tests when ran against
5.3.2. It was due to the PrimaryKeyEncoder being removed. In addition, the
tests ran into problems when going against servlet 2.4, so I bumped that
version. It also appears that one of the test pages is rendered a bit
differently, and appends _0 onto the select item that was being tested. I
updated the test to look for the correct element id.

Attachments:
tapestry-5.3.2.patch 2.8 KB

tapestry...@googlecode.com

unread,
Mar 16, 2012, 6:14:36 PM3/16/12
to tapestry5-caye...@googlegroups.com

Comment #2 on issue 40 by rfrov...@gmail.com: Doesn't work with Tapestry
5.3.2
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=40

Commit after doesn't work with the patch. If I have time, I'll try to
figure it out over the weekend.

tapestry...@googlecode.com

unread,
Mar 17, 2012, 12:10:53 AM3/17/12
to tapestry5-caye...@googlegroups.com
Updates:
Status: Accepted

Comment #3 on issue 40 by robert.z...@gmail.com: Doesn't work with Tapestry
5.3.2
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=40

If you're willing to use cayenne 3.1M3... you can try 0.5-SNAPSHOT (build
from source). I have it working with 5.3.2. I'll check your patch this
weekend if I get a chance.

tapestry...@googlecode.com

unread,
Mar 19, 2012, 11:43:42 AM3/19/12
to tapestry5-caye...@googlegroups.com

Comment #4 on issue 40 by rfrov...@gmail.com: Doesn't work with Tapestry
5.3.2
http://code.google.com/p/tapestry5-cayenne/issues/detail?id=40

I would prefer to not use Cayenne 3.1M3. I'd rather wait for 3.1 to be
fully released.

Also, checking out trunk and running the integration tests, that too has
problems with CommitAfter.

Reply all
Reply to author
Forward
0 new messages