I just moved some of my application's assets into my source-tree.
Unfortunately, it appears that externalized assets aren't working
properly, at least as far as I can see.
This is the URL I get when I include some.file in my component (the two
files are in the same directory in the source tree, and are both
deployed properly):
http://localhost:8080/example/assets/[md5-sum]com/example/some.file
Notice the missing slash between [md5-sum] and the com/example/some.file.
I have no idea why this isn't working. I checked and double-checked my
friendly-URLs configuration, web.xml, and component specification - and
everything is at it should be:
hivemodule.xml:
<contribution configuration-id="tapestry.url.ServiceEncoders">
<asset-encoder id="asset" path="/assets"/>
</contribution>
web.xml:
<servlet-mapping>
<servlet-name>example</servlet-name>
<url-pattern>/assets/*</url-pattern>
</servlet-mapping>
Component.jwc:
<asset id="some" path="some.file" />
And still, I get a URL that does NOT serve my asset but instead yields
an ARE:
Failure to export classpath resource /example/some.file.
Session id : 90plsd6162v1
Exceptions:
org.apache.hivemind.ApplicationRuntimeException: Classpath resource
'/example/some.file' does not exist.
(The rest of the exception chain really isn't important here.)
Meanwhile, requesting the following works like a charm:
http://localhost:8080/example/assets/[md5-sum]/com/example/some.file
Notice the added slash between [md5-sum] and com/example/some.file.
So, what's all this about? Am I doing something wrong, or is there a bug
somewhere?
-Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
