Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
5.0.18
-
None
-
None
Description
The class loaders of JBoss 5.x use URLs like
vfszip:/M:/jboss/jboss-5.0.1.GA/server/default/deploy/tapestry-test.war/WEB-INF/lib/tapestry-core-5.0.18.jar/org/apache/tapestry5/corelib/pages/
to point at class path resources. Tapestry is currently not capable of parsing these and as a result fails to find its own core components.
This is related to the mail thread JBoss5 and T5 configuration? a collegue of mine found. The approach outlined there yields URLs that point at non-existent files but served as an inspiration for our patch.
Attachments
Attachments
Issue Links
- relates to
-
TAP5-693 To document how to deploy Tapestry 5 on Jboss 5
- Closed