Well said Alex, all good points;
- but if you want you sure can add JPA interceptor
annotations to the jUDDI model classes.
- Or, as another alternative, you can use the subscription API
which would call back to a service of your choice with updates.
Plenty of ways to go about it I guess..
Cheers,
--Kurt
On 4/24/13 9:55 PM, Alex O'Ree wrote:
I'm not sure I understand what you're asking you, so here's a few
interpretations.
1) If a service is already in the registry, you can retrieve the data
using the inquiry service, then use it for whatever you want.
2) If a service is not already in the registry, I'm assuming that you
have the relevant information already, so no action is required.
3) If you have a client and don't know where the service you want to
use is located, use the inquiry API to locate it and obtain the end
point (find_service, getServiceDetails, getBindingDetails, etc)
4) I wouldn't recommend a JPA interceptor. UDDI is a web service, use
it as such. The underlying data structures within the database are
subject to change. The UDDI specification is not.
On Wed, Apr 24, 2013 at 9:48 PM, Subash Chaturanga <[email protected]> wrote:
Hi all,
I am using JUDDI (v3.1.3) to store service metadata to UDDI registry. That
works perfectly fine as expected. My problem is:
i.e I am storing a service to UDDI registry. Meanwhile (after stored or
before) I want to use the same service meta data and do something else (i.e
an external service invocation).
Since JUDDI writes to uddi registry through JPA, I think I need something
like JPA interceptors. Is this the way to do this ? It would be great if
some one can give me any links/sample where something similar have done
before.
Thanks in Advance
--
Subash Chaturanga
Sri Lanka
Blog - http://subashsdm.blogspot.com/
Twitter - http://twitter.com/subash89
