so what exactly are you doing? obviously you cant really share an app across
actual contexts because they are supposed to be isolated.
so what do you do? you have a single application object, but you map two
filters with two different paths and share the single instance of
application object via custom applicationfactory?
-igor
On 8/15/07, David Leangen <[EMAIL PROTECTED]> wrote:
>
>
> Hmmm...
>
> Very nasty things are happening in my forms. Because it's not resolving
> the URLs properly, wicket thinks that my pages are expired.
>
> Does this mean that I have no choice but to re-instantiate a new wicket
> for each context?
>
>
> In other words, is what I'm trying to do too much to ask of wicket
> without some major changes?
>
> Or is there a relatively simple way I could get this to work?
>
>
>
>
>
> On Wed, 2007-08-15 at 12:57 +0900, David Leangen wrote:
> > I'm attempting to mount one instance of wicket on more than one context
> > path. However, something is not working as I expect it to from within
> > Wicket, due to some kind of caching going on.
> >
> >
> > Essentially, I have my servlet container setup so that both of the
> > following get routed to the same instance of wicket:
> >
> > www.example.com/cxt1/
> > www.example.com/cxt2/
> >
> > On the first run, both work as expected.
> >
> > If I try to access directly either one of:
> >
> > www.example.com/cxt1/somePage
> > www.example.com/cxt2/somePage
> >
> > also no problem.
> >
> > However, if I first access cxt1, then later try to access:
> >
> > www.example.com/cxt2{/}
> >
> > Wicket is forwarding me back to:
> >
> > www.example.com/cxt1
> >
> > And vice-versa when I first access cxt2 and later try to access cxt1
> > without a path.
> >
> > Also, none of my links are working as expected. Once cxt1 is cached, all
> > my links now point to that context, which messes up what I'm trying to
> > do.
> >
> >
> > Is this a bug? If so, where should I look to fix this?
> >
> >
> > Thanks!
> > 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]
>
>
