You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by bu...@apache.org on 2004/03/09 15:55:57 UTC
DO NOT REPLY [Bug 21683] -
misinterpreted component-type specification-path in application specification
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=21683>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=21683
misinterpreted component-type specification-path in application specification
------- Additional Comments From hlship@apache.org 2004-03-09 14:55 -------
Basically, the failing here is that there's no way to add a prefix to a path
to indicate its type. I would like to see a "context:" prefix for paths within
the web application context (i.e., like a <context-asset>) and a "classpath:"
prefix for paths within the classpath (like <private-asset>).
There are a few kludges already in place; a couple of locations where a
leading slash in a path indicates a classpath resource. That's ugly and should
be fixed. However, I don't see this as a show-stopper for 3.0.
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org