i dont know, i might got the multi-wicket-app in the same webapp way, just like wicket-examples.
that way you dont have any of these goofy issues. every bundle provides its own application instance and registers its own url slice. -igor On Wed, Jun 25, 2008 at 10:59 PM, David Leangen <[EMAIL PROTECTED]> wrote: > >> > The thing is that I'm in an OSGi environment, and I have >> > a WicketService that provides my Wicket instance. I attach >> > "Applications" as bundles to the Wicket instance and "mount" >> > them on a certain path. >> >> >> so why are the /?wicket:interface urls interfering with that? > > He he... that goes back to the proxy issue. For what I'm doing, it's > important that the single Wicket instance be mounted on "/", which means > that "top" pages become inaccessible from outside of the firewall. > > The only way all this will work for me is if the url becomes something > like /app/?wicket:interface, (or even > better /app/pageName?wicket:interface) where "app" is the "mount > point" (not in the pure Wicket sense) of the Application bundle I attach > to the Wicket instance. > > This way: > - only one wicket instance mounted on "/" > - have a path accessible via proxying > - can determine the Application bundle based on the URL path > > Cheers, > David > > > > > --------------------------------------------------------------------- > 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]
