geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine if there are WebServices to be deployed
Date Tue, 16 May 2006 14:44:07 GMT
    [ ] 

David Jencks commented on GERONIMO-2030:

Can you port this patch to 1.1?  That needs to happen before it will be applied: we are going
to merge trunk into 1.1 and proceed from there.

I've wanted this feature for quite a while: it should allow the ws builder to add the dependencies
on the ws library that will be used (i.e. add a dependency on axis for the axis integration).
 I was thinking that both the service reference builder and web services builder needed a
chance to add to the environment.

> Allow WebServiceBuilder determine if there are WebServices to be deployed
> -------------------------------------------------------------------------
>          Key: GERONIMO-2030
>          URL:
>      Project: Geronimo
>         Type: Improvement
>     Security: public(Regular issues) 
>   Components: webservices
>  Environment: all
>     Reporter: Conrad O'Dea
>  Attachments: 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:
For more information on JIRA, see:

View raw message