You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Kurt Stam (JIRA)" <ju...@ws.apache.org> on 2007/11/02 21:02:50 UTC

[jira] Created: (JUDDI-122) After Axis2 goes in go through a dependency check

After Axis2 goes in go  through a dependency check
--------------------------------------------------

                 Key: JUDDI-122
                 URL: https://issues.apache.org/jira/browse/JUDDI-122
             Project: jUDDI
          Issue Type: Task
            Reporter: Kurt Stam
            Assignee: Kurt T Stam
             Fix For: 2.0


We need to split out the dependencies, and fix them so we don't end up with jar dependencies against juddi-core we only need for the WS stack. The WS stack used should be pluggable, but we do need an out-of-the-box tomcat install which includes axis2.

-- 
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: juddi-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: juddi-dev-help@ws.apache.org


[jira] Updated: (JUDDI-122) After Axis2 goes in go through a dependency check

Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/JUDDI-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam updated JUDDI-122:
------------------------------

    Fix Version/s:     (was: 2.0)
                   3.0

> After Axis2 goes in go  through a dependency check
> --------------------------------------------------
>
>                 Key: JUDDI-122
>                 URL: https://issues.apache.org/jira/browse/JUDDI-122
>             Project: jUDDI
>          Issue Type: Task
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.0
>
>
> We need to split out the dependencies, and fix them so we don't end up with jar dependencies against juddi-core we only need for the WS stack. The WS stack used should be pluggable, but we do need an out-of-the-box tomcat install which includes axis2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (JUDDI-122) After Axis2 goes in go through a dependency check

Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
     [ https://issues.apache.org/jira/browse/JUDDI-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kurt T Stam closed JUDDI-122.
-----------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 3.0)
                   3.0alpha

We have created modules child modules to take care of these external dependencies:

juddi-cxf is module that packages up the juddi.war with a CXF (Celtics XFire) WS Stack
juddi-axis is module for using an AXIS2 WS Stack.

These modules are simply out-of-the box packaging options, and any WS stack that implements JAX-WS can be used.

> After Axis2 goes in go  through a dependency check
> --------------------------------------------------
>
>                 Key: JUDDI-122
>                 URL: https://issues.apache.org/jira/browse/JUDDI-122
>             Project: jUDDI
>          Issue Type: Task
>            Reporter: Kurt T Stam
>            Assignee: Kurt T Stam
>             Fix For: 3.0alpha
>
>
> We need to split out the dependencies, and fix them so we don't end up with jar dependencies against juddi-core we only need for the WS stack. The WS stack used should be pluggable, but we do need an out-of-the-box tomcat install which includes axis2.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.