[ https://issues.apache.org/jira/browse/TAP5-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Drobiazko closed TAP5-576. ------------------------------- Resolution: Won't Fix Fix Version/s: 5.1.0.2 Sorry, but tapestry-ioc is not the proper place for that code. The service ClasspathURLConverter was introduced to solve such issues. Just override it in you application and that's it. I'm also overriding this service in my OSGi apps because in Equinox all classes have the protocol bundelresource. > Add support for JBoss 5.x > ------------------------- > > Key: TAP5-576 > URL: https://issues.apache.org/jira/browse/TAP5-576 > Project: Tapestry 5 > Issue Type: Bug > Components: tapestry-ioc > Affects Versions: 5.0.18 > Reporter: Benjamin Bentmann > Fix For: 5.1.0.2 > > Attachments: TAP5-576.patch > > > The class loaders of JBoss 5.x use URLs like > {noformat} > 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/ > {noformat} > 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?|http://www.mail-archive.com/us...@tapestry.apache.org/msg31403.html] > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.