W
whoopsy
I'm new to web services and am deciding whether or not to implement my
web service as a simple java class or a stateless session ejb. Reading
the weblogic documentation, one line confuses me "Implementing Web
Service by Java Class - write thread-safe code, because WebLogic
maintains only a single instance of a Java class that implements a Web
Service operation, and each invoke uses this same instance"
If two requests from different clients come in at the same time for the
same service, (1) is the second request blocked until the first
succeeds OR (2) are they both run concurrently, but you better take
care that they don't modify some shared resource without
synchronization?
forgive the newbie question, thanks for the help - Dan
web service as a simple java class or a stateless session ejb. Reading
the weblogic documentation, one line confuses me "Implementing Web
Service by Java Class - write thread-safe code, because WebLogic
maintains only a single instance of a Java class that implements a Web
Service operation, and each invoke uses this same instance"
If two requests from different clients come in at the same time for the
same service, (1) is the second request blocked until the first
succeeds OR (2) are they both run concurrently, but you better take
care that they don't modify some shared resource without
synchronization?
forgive the newbie question, thanks for the help - Dan