> By reusing the same code that I have been using to serve images inside of > the application, I can use to get a reference to the images w/ a full URL, > like so: > > http://myurl/MyApp/home/resources/wicket.Application/imageResource?file=C:\\assets\\newsletter\\my_photo.jpg > > ...which I was able to discover because of this line in my init() in my app > class: > > getSharedResources().add("imageResource", new ImageResource()); > > Eelco's post got me thinking of that and it works. Any reason I shouldn't > do it this way?
No, that's pretty much what I meant. The only thing still is that you might want to use logical paths (e.g. relative to a root dir) so that you'll have http://myurl/MyApp/home/resources/wicket.Application/imageResource?file=assets/newsletter/my_photo.jpg instead of exposing where on your server those images are exactly located. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
