Hi,

Sal proposed another solution to this problem, which is working quite well for me.
I'm now using a static cache for the ResourceHome, so 2 different instances are using the same Map that contains the Resources. It is very easy to apply, just create your own static m_resources and overwrite the find() method and dont use add().....


thx sal

stefan

Campana Jr., Salvatore J wrote:

Stefan,

You should be able to do a jndi lookup in your service classes to lookup
a home.  You may define homes in the jndi-config, but if you want the
same home for 2 different services, then use 1 services (service A) home
as your home for both...

So in the other service (service B) you'd lookup the home of service
A.....



-----Original Message-----
From: Stefan Lischke [mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 11:37 AM
To: [email protected]
Subject: Same instance of ResourceHome for 2 services


Hi guys,

i'm just struggling using one instance of a ResourceHome for 2 service. I can name the same class in both <resource name="home" type="ResourceHome"> but they get 2 different instances. So it is not
possible to share one resource with 2 or more services.


Is this a feature or a bug?

I need this for the following stuff: i have a Resource which is a
Subscription, but i need 2 different services for it. The first one gets
all notifications with usenotify=false (that means with no notify tag
around, so im using my own WSRFMsg Handler) the second one gets the
SubscriptionEnd Message.

any ideas?

stefan


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






--
My place : http://user.cs.tu-berlin.de/~lischke


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to