AW: AW: AW: AW: AW: AW: Deploying the client

2002-12-17 Thread Sebastian . Beyer
W: AW: Deploying the client thanks sebastian, as i see, it's the same in .NET. > ahhh thats your problem. In the documentation they say, that you have > to which documentation? i have only that one which comes with the distribution. klaus Am Dienstag, 17. Dezember 2002 10:08 schrieb

AW: AW: AW: AW: AW: AW: Deploying the client

2002-12-17 Thread Klaus Thiele
thanks sebastian, as i see, it's the same in .NET. > ahhh thats your problem. In the documentation they say, that you have to which documentation? i have only that one which comes with the distribution. klaus Am Dienstag, 17. Dezember 2002 10:08 schrieb [EMAIL PROTECTED]: > Hi Klaus, > > ahhh

AW: AW: AW: AW: AW: Deploying the client

2002-12-17 Thread Sebastian . Beyer
02 10:02 An: [EMAIL PROTECTED] Betreff: AW: AW: AW: AW: AW: Deploying the client Hi, yes, but with scope as "session" i get _also_ a new session object each time i request a method if i don't set maintainsession to true at client-code - thats why i'm irritated. (with scope as

AW: AW: AW: AW: AW: Deploying the client

2002-12-17 Thread Klaus Thiele
Hi, yes, but with scope as "session" i get _also_ a new session object each time i request a method if i don't set maintainsession to true at client-code - thats why i'm irritated. (with scope as "application" it works as expectet _without_ do anything at client-side - same object for each reques