You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Conrad O'Dea (JIRA)" <de...@geronimo.apache.org> on 2006/05/16 10:24:06 UTC
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=comments#action_12411922 ]
Conrad O'Dea commented on GERONIMO-2030:
----------------------------------------
BTW, this patch has been deveoped against trunk. The structure of the plans for the deployers and WebServiceBuilders is much more flexible here.
> Allow WebServiceBuilder determine if there are WebServices to be deployed
> -------------------------------------------------------------------------
>
> Key: GERONIMO-2030
> URL: http://issues.apache.org/jira/browse/GERONIMO-2030
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira