geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine if there are WebServices to be deployed
Date Tue, 01 Aug 2006 17:28:14 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]

David Jencks updated GERONIMO-2030:
-----------------------------------

    Fix Version/s: 1.2

I've applied a slightly modifed version of this patch to 1.1.1 in g. rev 427654 and openejb
rev 2834.  The change is to use the isEJB parameter to look for WEB-INF/webservices.xml or
META-INF/webservices.xml rather than looking in both locations.

Chris, do you have changes you wish to make to this patch or should I reassign to myself and
apply to trunk?

> Allow WebServiceBuilder determine if there are WebServices to be deployed
> -------------------------------------------------------------------------
>
>                 Key: GERONIMO-2030
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2030
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: Conrad O'Dea
>         Assigned To: Chris Cardona
>             Fix For: 1.1.1, 1.2
>
>         Attachments: find-web-services.patch, geronimo_ws_builder_change.patch
>
>
> Each J2EE module deployer (EJB, Tomcat, Jetty) must decide if the module being deployed
has a WebService endpoint.  Currently, this requires the deployer to check for the presence
of a webservices.xml file.  This makes it awkward to add support for JAXWS style web services
to Geronimo.  
> A better solution is to push the WS endpoint check into the webservice deployer.  This
simplifies the logic of webservice deployment and also allows for more flexible options (such
as introducing a module that use JSE 5 features without polluting the existing deployers).
> A patch for this attached.

-- 
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

        

Mime
View raw message