Eelco Hillenius wrote:
>
> Not sure if it is the answer you are looking for, but paths to shared
> resources (which packaged resources such as images are) are
> predictable. Basically:
>
> http://your.com/yourapp/resources/com.your.another.package.SomeClass/your_image_next_to_your_class.gif
>
> So there is /resources/ which is a reserved path for shared resources
> in Wicket. Then there is the name of the class you want to use to
> relatively reference your resource, and then there is the resource
> relative to that class. And that can be in a subdir, but you can't use
> '..' etc.
>
> Eelco
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
Interesting... This might work, however I don't understand what the class
would be? Would it be the Application class? The images reside in
C:\AppName\images, which is obviously outside of the app.
I suppose I don't quite understand how that would work?
--
View this message in context:
http://www.nabble.com/Displaying-images-remotely---HTML-email-tf4535313.html#a12943828
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
