Hello Robert,
I've already implemented such a Spring-MessageReceiver that lookups
Services that are actualy Beans from its SpringConfiguration.
I only searching about a way to share some Object reference across
multiple Service-Calls.
Thanks,
Siamak Haschemi
robert lazarski schrieb:
I solved my problem by using a static variable, but it would be nice to
know if there exists a Context to put references in which has a lifetime
longer than a service-call.
Thanks a lot,
Siamak Haschemi
Siamak Haschemi schrieb:
Hello Robert,
I've already implemented such a
Hi Siamak;
Sorry for late reply.
You dont need to use static variable , context hierarchy is there to
provide those features for you. When you deploy a service in application
scope , then the associate ServiceGroupContext and serviceContext has
the life time of the system , so best way is to
Thank you for your hint.
I will give it a try.
I think that Axis2 needs much more examples for such little questions.
This will be a keypoint for the acceptance of the 3rd generation of this
Apache project.
Thank you very much,
Siamak Haschemi
Deepal Jayasinghe schrieb:
Hi Siamak;
Sorry
Hello to all.
I have two Services defnied. They need to share a reference to the
Spring-ApplicationContext. Now I need to know how the communication
between two Services in a ServiceGroup can be achieved. I know I can do
this with a Singleton, but I wonder if Axis2 has some mechanism for
Is what you're realy after is two services that are wired into Spring?
Spring-ApplicationContext already is a singleton - look at setting up a
BeanFactory.
The other way is as you show in services.xml - message recievers. I'm
actually coding one up a spring message receiver now. The idea is to
