[jboss-dev-forums] [Design of JBoss ESB] - Re: Registry Design

[anil.saldhana@jboss.com]

Assuming you want to prototype and plan to use JAXR against jUDDI, here are some relevant details.

  | * Pick up Scout/juddi versions from jboss-4.0.4.GA
  | * Create a version of the juddi transport interface.  Scout will use this transport to communicate to juddi. So you can make a local call here (not use soap or any transport).
  | Eg:
  | http://viewcvs.labs.jboss.com/cgi-bin/viewcvs.cgi/jbosstest/build.xml?only_with_tag=Branch_4_0
  | 
  | * There is a bloated JUDDI Servlet that picks up the incoming soap message, parses the uddi op and then calls its internal infrastructure. So you will need to peek in and assume that you have the uddi op (as you are making a local call in the transport) and pick up the infrastructure call and plug it into the transport that you used in aforementioned step.
  | 
  | http://viewcvs.labs.jboss.com/cgi-bin/viewcvs.cgi/contrib/varia/src/main/org/jboss/jaxr/juddi/JUDDIServlet.java?only_with_tag=Branch_4_0
  | 
  | So basically you have removed the extra step of marshalling in the transport and unmarshalling in a servlet.  You have combined the scout and juddi via a local call in the transport.
  | 
  | Underneath, Scout uses juddi proxy to communicate and this transport interface is part of it.
  | 

This info is for Kurt.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3971351#3971351

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3971351