If I'm understanding this correctly you simply want a set of images available on the same server that your wicket app is on. Just make an "images" folder at the same level as WEB-INF (that is, a sibling of).
If you are using wicket 1.2.x, you would have mounted your wicket app to some path under your context: for instance /app. A link to a wicket page mounted to /home would look like this: http://yourserver.com/yourcontext/app/home A link to an image would look like this: http://yourserver.com/yourcontext/images/myimage.jpg On Wicket 1.3, you use a filter instead, and the filter is smart enough to know what content to handle so technically you don't need the extra /app path you can reference your application and static images like so: http://yourserver.com/yourcontext/home http://yourserver.com/yourcontext/images/myimage.jpg (it's the same as before) Again, not sure if that's what you are asking, but hopefully it is! Craig. On 9/28/07, V. Jenks <[EMAIL PROTECTED]> wrote: > > Basically, yes. I wasn't sure if there was a Wicket solution to this problem > or not. I wasn't sure if there was a way to make a hard-coded reference to > a resource outside of the webroot, for the purposes of doing what I > explained. > > > Eelco Hillenius wrote: > > > >> 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. > > > > Oh, ok, I didn't understand what you meant. So you don't want to just > > put these images in a path than can be served by a web server? > > > > Eelco > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Displaying-images-remotely---HTML-email-tf4535313.html#a12944856 > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
