> My webservices consists of apache axis and a bean (non ejb) that
> advertises one method as
> a webservice.
Using j2ee webservices means only ejb's (stateless session and message
driven bean) and servlet's (servlets and jaxm servlets) can be
webservices endpoints.
> Is a new class created for every thread that access the webservice? If
> so this would mean
> that class variables would be thread safe?
in case of servlet synchronize your service method
> For example using the PageContext or ConfigContext within my bean to
> retrieve startup variables from the container and then store them.
in case of servlet use this, for ejb's use static variables but be
carefull with this because all instance access the same values
hope it helps
regards,
stefan
jasonsig - 29 May 2006 16:00 GMT
Using j2ee webservices means only ejb's (stateless session and message
driven bean) and servlet's (servlets and jaxm servlets) can be
webservices endpoints.
I am confused with your statement I found many examples of using
regular class methods as webservice end points.
Below is what endpoint possiblilites i found, my case it would be the
second one.
A method of a stateless session EJB
A method of a Java class
A JMS method consumer
Stefan Theusner - 02 Jun 2006 23:00 GMT
> Below is what endpoint possiblilites i found, my case it would be the
> second one.
> A method of a stateless session EJB
> A method of a Java class
> A JMS method consumer
Thats right. I ownly written the possibilities for j2ee.
With normal java classes and jms i haven't work so far.