I was using just the root context of / but I have also tried a context of /app and the image uri get rendered properly as /app/images/edit.gif but still they don't render.
I will try making a war.
Cheers,
Adam.
----- Original Message ----- From: "Erik Hatcher" <[EMAIL PROTECTED]>
To: "Tapestry users" <[email protected]>
Sent: Friday, April 22, 2005 11:30 AM
Subject: Re: Images not serving (may be Jetty Launcher)
On Apr 22, 2005, at 5:31 AM, Adam Chesney wrote:I still have not fixed this issue.
I have tried using the assets as below and now when i view the source of the RENDERED pages the images look like this: <img src="/images/edit.gif" border="0" alt="Edit"/>But I still only see the ALT text and the images are not rendered.
What is the context path you're using? URL's should be prefixed with that, which is generally your webapp name. My hunch is you've not configured your Jetty setting properly. Can you get to the image by hacking the URL to include the context path?
One thing to try is build a WAR file out of your code, deploy it to the webapps directory of a full Jetty installation, then from the command-line at the root of the Jetty installation type "java -jar start.jar".
So, my question is:
As I am using Tapesty 3.03, shouldn't the assets have a check sum attached?
Only private assets that serve from the classpath use the checksum. Assets from the context do no need a checksum as they are directly accessible.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
