-
1. Re: Deployment event hook?
Probably as part of Heiko's JAX-WS deployment process, as the initial deployment stages are dealing with the complete archive, which could have multiple BPEL processes/WSDL interfaces, so would require analysing the deployment descriptor to understand what to do.
If basing the UDDI publish on JAX-WS and annotations, then probably best to do it at the later stage when the individual WSDLs are being deployed to JBossWS - so Heiko will need to provide a pointer to where to look. -
2. Re: Deployment event hook?
Does it make sense to integrate UDDI deployment in
org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint?
--Kurt -
3. Re: Deployment event hook?
Is this an optional feature? Can the user disable it, for example, if they want to control the registry deployment?
-
4. Re: Deployment event hook?
I'm using the juddiv3 client code, which will read its configuration from a uddi.xml in the riftsaw.sar. If the file is not provided it will just fail with a short 'uddi.xml not found' INFO level log message, and no 'self-registration' will take place. For more details on the juddi-client see:
http://svn.apache.org/repos/asf/webservices/juddi/trunk/docs/jUDDI-UserGuide.pdf Chapter 7. The juddi-client should work with any UDDIv3 compliant registry. The functionality is similar to using UDDI annotations: http://apachejuddi.blogspot.com/2009/11/uddi-annotations-how-do-i-self-register.html. If deemed needed we can add a UDDI.registration on/off flag in the riftsaw (ODE) configuration.
--Kurt -
6. Re: Deployment event hook?
org.jboss.soa.bpel.runtime.ws.EndpointManager.createEndpoint?
This could be on place to hook into. Another would be jbossws itself.
IMO that later is probably more appropriate and JBossWS would benefit from it, as well as any other client doing WS deployment through JBossWS.
I would suggest you include the JBossWS team in that decision.