[SCOUT-9] Separation of Apache Scout and jUDDI

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0rc1
• Component/s: Scout - jUDDI Interface
• Environment: All
• Assignee: Anil Saldhana
• Reporter: Deepak Bhole
• Created: 12/Oct/05 01:00
• Updated: 26/Jul/07 13:42
• Resolved: 26/Jul/07 13:42

Description

Currently, there is a heavy dependency between Scout and jUDDI, and the two projects need to be de-coupled.

The arguments for doing so have already been discussed on the developer mailing lists over here:
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=[e-mail]&msgNo=1575

The following are some of the major changes that need to be done to achieve this:
1. Some registry code from jUDDI needs to be copied over into scout (IRegistry, RegistryException, RegistryProxy and AbstractRegistry) and ported to use xmlbeans instead of jUDDI data types.
2. Some transport classes (AxisTransport and Transport) need to be copied over from jUDDI and modified as applicable.
3. All classes in Scout that rely on jUDDI data types, need to be changed to use autogenerated types, generated by xmlbeans instead.

I will be submitting a patch with the above changes within the next couple of days or so.