You are viewing a plain text version of this content. The canonical link for it is here.
Posted to scout-dev@ws.apache.org by "Deepak Bhole (JIRA)" <sc...@ws.apache.org> on 2005/10/11 18:02:06 UTC
[jira] Created: (SCOUT-9) Separation of Apache Scout and jUDDI
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/ReadMsg?listName=juddi-dev@ws.apache.org&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: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
[jira] Resolved: (SCOUT-9) Separation of Apache Scout and jUDDI
Posted by "Kurt Stam (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam resolved SCOUT-9.
---------------------------
Resolution: Fixed
Fix Version/s: 1.0
This work is done, the code is checked in on the trunk. jUDDI is only used in the unittests.
> Separation of Apache Scout and jUDDI
> ------------------------------------
>
> Key: SCOUT-9
> URL: https://issues.apache.org/jira/browse/SCOUT-9
> Project: Scout
> Issue Type: Improvement
> Components: Scout - jUDDI Interface
> Environment: All
> Reporter: Deepak Bhole
> Assigned To: Anil Saldhana
> Priority: Minor
> Fix For: 1.0
>
>
> 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=juddi-dev@ws.apache.org&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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
[jira] Closed: (SCOUT-9) Separation of Apache Scout and jUDDI
Posted by "Kurt Stam (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam closed SCOUT-9.
-------------------------
Resolution: Fixed
Fix Version/s: (was: 1.0)
1.0rc1
> Separation of Apache Scout and jUDDI
> ------------------------------------
>
> Key: SCOUT-9
> URL: https://issues.apache.org/jira/browse/SCOUT-9
> Project: Scout
> Issue Type: Improvement
> Components: Scout - jUDDI Interface
> Environment: All
> Reporter: Deepak Bhole
> Assignee: Anil Saldhana
> Priority: Minor
> Fix For: 1.0rc1
>
>
> 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=juddi-dev@ws.apache.org&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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org
[jira] Reopened: (SCOUT-9) Separation of Apache Scout and jUDDI
Posted by "Kurt Stam (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt Stam reopened SCOUT-9:
---------------------------
Need to add the right Fix Version
> Separation of Apache Scout and jUDDI
> ------------------------------------
>
> Key: SCOUT-9
> URL: https://issues.apache.org/jira/browse/SCOUT-9
> Project: Scout
> Issue Type: Improvement
> Components: Scout - jUDDI Interface
> Environment: All
> Reporter: Deepak Bhole
> Assignee: Anil Saldhana
> Priority: Minor
> Fix For: 1.0rc1
>
>
> 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=juddi-dev@ws.apache.org&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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: scout-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: scout-dev-help@ws.apache.org