why also append the jsessionid in the post url?
or as an hidden field?
also just post to the right dynamic resource url and it should work fine.
(you have to do then everything yourself of course like parsing the input)
johan
On 5/9/07, JulianS [EMAIL PROTECTED] wrote:
We are building a
Johan Compagner wrote:
why also append the jsessionid in the post url?
or as an hidden field?
You are right, passing the jsessionid to the server is not a problem. The
problem is, how do we check that session id against what is in the wicket
session, since the DynamicWebResource doesn't
are you sure you cant do Session.get() in the resource?
-igor
On 5/9/07, JulianS [EMAIL PROTECTED] wrote:
Johan Compagner wrote:
why also append the jsessionid in the post url?
or as an hidden field?
You are right, passing the jsessionid to the server is not a problem. The
problem is,
igor.vaynberg wrote:
are you sure you cant do Session.get() in the resource?
That's the solution! Thanks very much. I said it was a newbie question :)
Julian
--
View this message in context:
http://www.nabble.com/Newbie-Qs-about-DynamicWebResource-tf3712534.html#a10398102
Sent from the
We are building a Wicket app that also needs to support applets. The applets
are modeless dialogs that live outside the browser.
Each applet communicates with the server by sending data to a URL and
receiving a text response. We can do this by creating a service that
subclasses
