Yes, in fact in J2EE 1.4 only stateless session beans (not statefull ones) can expose their interface as web service. But, the quotation was not that implementation specific, it was "web service has to be state-less" and this is not true IMHO. I do maintain "global state" in my web service (just static variables right now) which could be accessed by any SLSB instance within the same JVM. Works for EJB way (SLSB) and JAX-RPC way.
 
cu
   Merten


From: Peter Smith [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 23, 2004 5:11 AM
To: [EMAIL PROTECTED]
Subject: Re: Web Service with state


Have read that web service has to be state-less. Why is that?
    

Where did you read that?
Maybe it's a hint which should be followed if possible, but nothing more
IMHO.
  

From J2EE1.4 web services point of view this is not a "hint" at all....

See "Web Services for J2EE, Version 1.0" (aka JSR-109 for J2EE1.4) [ref http://www.jcp.org/en/jsr/detail?id=109]

[section 5.3.2.1 EJB Container programming model] A Service implementation bean *must* be a stateless object

[section 5.3.2.2 Web Container programming model] A Service implementation *must* be a stateless object

and [section 1.4 document conventions] "MUST" meaning is from RFC 2119 [ref http://www.faqs.org/rfcs/rfc2119.html] meaning "absolute requirement of the specification"

Peter.

 

This is an email from Fujitsu Australia Software Technology Pty Ltd, ABN 27 003 693 481. It is confidential to the ordinary user of the email address to which it was addressed and may contain copyright and/or legally privileged information. No one else may read, print, store, copy or forward all or any of it or its attachments. If you receive this email in error, please return to sender. Thank you.

If you do not wish to receive commercial email messages from Fujitsu Australia Software Technology Pty Ltd, please email [EMAIL PROTECTED]

Reply via email to