geronimo-dev mailing list archives

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

Conrad O'Dea commented on GERONIMO-2030:

I'll port it although it will probably be a couple of days before I get to it.

For this to be most useful I think that the plans for the deployers need to be refactored
a little to be similar to those on trunk.  Principally this means moving the WebServiceBuilder
GBean from the J2EE deployer out in to it's own config.  I don't know if this is planned work
or not. 


> 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