mistapony wrote:
>
> Anyone have any idea on this. It is utterly annoying to have to hard code
> the Context in the page spec.
>
Well, you don't show how you're using the "msi" asset... You don't normally
see assets included in onlick handlers, so I'm guessing you're using OGNL to
get the value of the path and putting it into an @Any component that renders
the button? That's... uh, not ideal.
If you're going to do that, you might as well inject the context into your
basepage:
@InjectObject("infrastructure:request")
public abstract WebRequest getRequest();
Then you can use the ognl:request.contextPath instead of hard-coding the
URL.
--
View this message in context:
http://www.nabble.com/T-4.1-Strange-Asset-Context-problem-tp14176242p14357371.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
