I went to try the context thing..... that doesn't quite work for me yet, though god knows im trying.. <asset name="dojoSource" path="context:js/dojo_rrl/dojo.js" /> <asset name="dojoPath" path="context:js/dojo_rrl/"/> i also tried the same but with a leading /, so path = "context:/js/dojo_rrl/" etc
I made sure that by accessing [host]:8080/[context]/js/dojo_rrl/dojo.js i could bring up dojo.js and sure enought htere it was but the entire page was riddled with errors (ie, no dojo -- not just no images). Anyway, thanks again for your continued indulgence, Josh On 11/20/06, Josh Long <[EMAIL PROTECTED] > wrote:
eep.. ok, wait, whats the fix? Actually, err, I don't think it's (strictly) a jetty bug, either, as my test environment (tomcat) is dojo image-less as well. What was the indication it was a jetty bug for you? How'd you fix it or work around it? Josh On 11/19/06, Jesse Kuhnert < [EMAIL PROTECTED]> wrote: > > Just took a look at this myself and found that images not showing up are > a > jetty bug. At least for me. I could be totally wrong, but since I had to > add > relative resource css path support to the Tapestry asset service it was > easier to track down. > > The reason it works with the built in dojo version is because Tapestry > manages ~all~ resource access for those paths. > > -- > Jesse Kuhnert > Tapestry/Dojo/(and a dash of TestNG), team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > >
