Hi Gabor, Thanks for your sincere reply, I can certainly understand the concept you suggested.
At present I am using the property file instead as a work around and showing the cross application urls by using the plane o Labels, it's working well. However, still I wondered that this might very well be a hidden core wicket functionality where a webpage knows by itself about the application it belongs to. I believe this functionality will be very useful if incorporated in case it is not present presently. Cheers, -J Gabor Szokoli wrote: > > On Dec 15, 2007 9:41 PM, chickabee <[EMAIL PROTECTED]> wrote: >> I have a tomcat webapp with two Wicket Applications, say A and B. >> >> Now, if I create a bookmarkable link in application A for a WebPage which >> actually belongs to application B then it balks out for obvious reasons. > > I'm not sure I understand 100%, but maybe this helps: > Register the bookmarkable page in application B, and use a > configuration parameter in applicaton A-s web.xml with B-s base URL. > Try to remember you did this the next time you deploy application B to > a different context root, or set up a reverse proxy. > > Or the two servlets could talk to each other and share the registered > bookmarkable URLs dynamically > >> I wonder if there is a way to make a WebPage application aware, so that >> it >> resolves it's owner application automatically. > > Application.get() ? > > > Gabor Szokoli, guessing > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/How-to-make-a-WebPage-Application-aware--tp14354922p14356035.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
