Hi Sebastian,
> Why do you think that something gows wrong on server side? If you deployed
yes, it works fine if i deploy the service with
<parameter name="scope" value="Session"/>
_and_ set maintainsession to true in the client code.
but imho, i expected to do _nothing_ at client side to get
sessions working if i deployed with session-scope.
just for my clearness:
what's the difference between
<parameter name="scope" value="Request"/>
and <parameter name="scope" value="Session"/>
if i do nothing at client-side?
klaus
ps: i've now found out, how to activate the sessions in
my .NET client-code 8-), so i can live with this fuzziness.
Am Dienstag, 17. Dezember 2002 08:46 schrieb
[EMAIL PROTECTED]:
[...]
> Why do you think that something gows wrong on server side? If you deployed
> your server with that line and you set the maintainsession to true, the
> Session should be working. I see this in my tcpmon, which shows me the
> current session-ID in the SOAP-header. What is it like at your
> architecture?
>
> For me it looks like this:
> I instantiate a ServiceLocator, set for this the maintainsession to true,
> build service from the locator and invoke methods. Together with the
> deploying on the server-side I can now see a line like:
> Cookie: JSESSIONID=........
>
> in my SOAP-Header. For every invoke this ID is equal so it indicates me,
> that the session is working. But since now I'm not able to append Objects
> to that session, because I always got a NullPointer, when I try. I will try
> to use the SimpleSessionHandler on client side to manage that problem and
> will tell how that works.
[...]
--
Klaus Thiele - Personal & Informatik AG
mailto:[EMAIL PROTECTED]
"There's got to be more to life than compile-and-go."
