Separation of Apache Scout and jUDDI
------------------------------------

         Key: SCOUT-9
         URL: http://issues.apache.org/jira/browse/SCOUT-9
     Project: Scout
        Type: Improvement
  Components: Scout - jUDDI Interface  
 Environment: All
    Reporter: Deepak Bhole
 Assigned to: Anil Saldhana 
    Priority: Minor


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/[EMAIL PROTECTED]&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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to