[
https://issues.apache.org/jira/browse/TAP5-1582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1582:
---------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated about 1.5 years ago, has no assignee, affects
an old version of Tapestry that is not actively developed anymore, and is
therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-6, which is available from Maven Central), please update it
as soon as possible. In the case of a feature request, please discuss it with
the Tapestry developer community on the [email protected] mailing list
first.
> IOC doesn't like tomcat multi-level contexts
> --------------------------------------------
>
> Key: TAP5-1582
> URL: https://issues.apache.org/jira/browse/TAP5-1582
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.2
> Reporter: Richard Guest
> Labels: bulk-close-candidate
>
> Deploying a multi-level context webapp to tomcat.
> According to
> http://tomcat.apache.org/tomcat-6.0-doc/config/host.html#Automatic_Application_Deployment
> the war should be named foo#bar.war, tomcat unpacks the war to
> webapps/foo#bar and serve the webapp from http://hostname:port/foo/bar
> However, tapestry IOC fails when attempting to use simple binding
> expressions, e.g. for "message:some-key":
> org.apache.tapestry5.ioc.internal.util.TapestryException: Could not convert
> 'message:some-key' into a component parameter binding: URI has a fragment
> component [at classpath:....]
>
> org.apache.tapestry5.internal.services.BindingSourceImpl.newBinding(BindingSourceImpl.java:82)
> ...
> java.lang.IllegalArgumentException: URI has a fragment component
> java.io.File.<init>(File.java:370)
>
> org.apache.tapestry5.ioc.services.ClassFabUtils.toFileFromFileProtocolURL(ClassFabUtils.java:340)
> ...
> It appears that java.net.URI considers #bar/WEB-INF/app.properties a
> "fragment" and that java.io.File(URI uri) barfs when fragment is set.
> Help...?
> I don't think I'm the only person who has experienced this -
> http://tapestry.1045711.n5.nabble.com/Multiple-level-context-path-not-working-in-tomcat-td2635336.html
> Let me know if there is any further information I can provide to clarify the
> issue.
> -- Rich
--
This message was sent by Atlassian JIRA
(v6.2#6252)
