From mvn jetty:run:
Here's request map: Full()Here's session map: Full()and finally
S.contextPath:
From jetty
Here's request map: Full(/mt)Here's session map: Full(/mt)and finally
S.contextPath: /mt
WTF?
My actor code is:
bind(f, defaultXml,
nakedHomeButton -
FWIW, my Jetty config I tried to make as simple as possible:
Set name=contextPath/mt/Set
Set name=warSystemProperty name=jetty.home default=.//
webapps/menutest-1.0-SNAPSHOT.war/Set
Set name=extractWARfalse/Set
Set name=copyWebDirfalse/Set
Set name=defaultsDescriptorSystemProperty name=jetty.home
So are you saying that if you run it via jetty:run it doesn't behave properly,
but it does if you run it from jetty outside of mvn?
Or that in both cases it does not behave? I'm not sure exactly what you mean by
from jetty so I think it might be important.
To set your context path from mvn
Ross: no, the opposite. in mvn jetty:run all is well since it is in
the root context. (?)
When I deploy the war to jetty and use the /mt context all the
ajaxButtons insist on going to the root.
PS - although i've had trouble before, 2.0-M1 seems *more* broken :(
On Feb 4, 3:37 pm, Ross Mellgren
I think David's analysis is exactly right: CometActors do not run in
the scope of any HTTP requests. I'm guessing that
the context path is not getting to the CometActor.
As the button text I put S.contextPath+/index and sure enough, it
shows /index - even though the above output shows that to
Yes very well could be. I was part of the email chain when Marius implemented
these changes and I thought that this was why LiftSession has a copy of the
contextPath. Taking a quick glance at the code it should work with that, but
Marius should definitely comment since he's most familiar with
