Sounds like a clean solution to bundle dwr also inside component libs.
Just drop it in and use it! Nice.
Stephane Decleire schrieb:
I've come up with this idea :
String context = request.getContextPath();
renderSupport.addScriptLink(context + "/dwr/engine.js");
and the DWR servlet mapping could be passed as a parameter to my
component to be fully customized ...
I think you mean sth like:
renderSupport.addScriptLink(context + "/${dwrServletMapping}/engine.js");
What do you think about it ?
Stephane
Andy Pahne a écrit :
I don't know if that's possible.
You - as a library provider - and the consumer at least need to find a
convention about how the dwr servlet is mapped. /dwr/ is kind of
standard, but not granted. That's the first problem.
Next problem: Do the Tapestry facilities (@IncludeScriptLibrary...)
support your use case? I guess not.
When I integrated dwr, I did not even think that far, because I did
not have to bundle it as a component lib. So I ended up using the same
script-tags that you used.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
