UDDI (was Re: Question)

[Guillaume Nodet <gu...@worldonline.fr>]

I think the easiest way to implement this would be to add such a feature 
in the servicemix-common
project that is used by the new jbi compliant components 
(servicemix-http and servicemix-jms for BC).
The main reason is that these binding components already accept wsdl 
deployments, so that the only
thing to do would be to configure a remote UDDI registry.  When an 
endpoint is activated by the component
(due to a service unit deployment), it could register the wsdl in the 
remote registry.  Periodically, it could
poll the registry for new wsdl (matching a given  protocol) and register 
create new endpoints for them.

This could lead to some interesting features, where the same binding 
components (on two different servicemix
instance) could share endpoints (an endpoint activated by a BC would be 
automatically discovered by
other servicemix instances), therefore achieving a simple network 
amongst the jbi containers.

Cheers,
Guillamue Nodet

Jonathan.Edwards@cexp.com wrote:

>I was thinking about starting off with a simple enhancement to the Http and
>Saaj components that would allow for simple UDDI interaction. Basically
>allow the BC to perform endpoint lookup with a non-host:port specific
>well-known name against a UDDI registry (but yeah, the protocols are not all
>that straight forward; a colleague of mine is researching interoperating
>with Systinet - we shouldn't have to use any vendor specific APIs). I'm
>still not sure where the best place do perform this lookup is - to your
>point about protocols (for example, if I update the SaajComponent to use
>UDDI, and the endpoint returned is jms://, what would I do?). 
>
>/jonathan
>
>  
>
>>-----Original Message-----
>>From: Guillaume Nodet [mailto:guillaume.nodet@worldonline.fr]
>>Sent: Friday, February 03, 2006 9:42 AM
>>To: servicemix-users@geronimo.apache.org
>>Subject: Re: Question
>>
>>
>>Registration of wsdl endpoints could be done with a 
>>ServiceMix service 
>>(same kind of thing than the JdbcAuditor).
>>Classes interested in receiving events on endpoints / 
>>components can use the
>>    JBIContainer.getRegistry().addComponentPacketListener method
>>It could register wsdl in the uddi registry whenever an 
>>endpoint with a 
>>wsdl is activated.
>>It would be better to do that at deployment / undeployment, but the 
>>callbacks are not implemented.
>>
>>The problem of querying UDDI registry for endpoint resolution 
>> is about 
>>the protocols to use.
>>I'm not an UDDI expert (never used it actually), so I may 
>>miss something.
>>The NMR can only access jbi endpoints , so that if you want 
>>to invoke a 
>>service over http+soap,
>>you would need to go though an http binding component (who's 
>>role is to 
>>talk http).
>>The NMR could look for the wsdl in the UDDI but it would not 
>>know how to 
>>send the exchange.
>>
>>Maybe a given BC could look in the UDDI and register 
>>endpoints for these 
>>services
>>(either real jbi endpoints, or external endpoints), but this 
>>could not 
>>occur dynamically.
>>I mean, the endpoints must have been registered before the 
>>exchange is sent.
>>Or, we could enhance the NMR so that when an endpoint can not be 
>>resolved, it asks the BCs
>>to look in the UDDI registry and register endpoints.
>>
>>Any thoughts ?
>>
>>Cheers,
>>Guillaume Nodet
>>
>>
>>Jonathan.Edwards@cexp.com wrote:
>>
>>    
>>
>>>And the other way round? So that SM can query UDDI to see 
>>>      
>>>
>>what other WS are
>>    
>>
>>>available (primarily for endpoint resolution).
>>>
>>> 
>>>
>>>      
>>>
>>>>-----Original Message-----
>>>>From: James Strachan [mailto:james.strachan@gmail.com]
>>>>Sent: Friday, February 03, 2006 3:24 AM
>>>>To: servicemix-users@geronimo.apache.org
>>>>Subject: Re: Question
>>>>
>>>>
>>>>
>>>>On 3 Feb 2006, at 10:13, Stefan Klinger wrote:
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>>>>This sounds like a good starting point to me. I also feel 
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>that some  
>>>>   
>>>>
>>>>        
>>>>
>>>>>kind of service monitor would be required as well. If I'm not  
>>>>>mistaken, the services register with the UDDI which can then be  
>>>>>used for lookup by the proxy. However, this does not tell me  
>>>>>whether the services are actually working and producing sensible  
>>>>>results. Do you think it might be worth investigating some of the  
>>>>>open-source monitoring tools and have them as optional plugins to  
>>>>>ServiceMix?
>>>>>     
>>>>>
>>>>>          
>>>>>
>>>>Definitely :)
>>>>
>>>>Also I think we could get ServiceMix to auto-register components/ 
>>>>endpoints into UDDI as they are activated/deactivated too; 
>>>>        
>>>>
>>so other  
>>    
>>
>>>>WS folks can query UDDI to see services running in ServiceMix
>>>>
>>>>James
>>>>-------
>>>>http://radio.weblogs.com/0112098/
>>>>
>>>>   
>>>>
>>>>        
>>>>
>>> 
>>>
>>>      
>>>
>
>
>  
>