You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/09/21 23:56:22 UTC
[jira] Closed: (GERONIMO-2291) Allow WebServiceBuilder determine if
there are WebServices to be deployed
[ http://issues.apache.org/jira/browse/GERONIMO-2291?page=all ]
David Jencks closed GERONIMO-2291.
----------------------------------
Resolution: Fixed
Changes merged from GERONIMO-2030
g server/trunk rev 448705
openejb2 (incubator) rev 448706
g sandbox/javaee5 (jetty6 integration) rev 448707
> Allow WebServiceBuilder determine if there are WebServices to be deployed
> -------------------------------------------------------------------------
>
> Key: GERONIMO-2291
> URL: http://issues.apache.org/jira/browse/GERONIMO-2291
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 1.1
> Environment: all
> Reporter: Aaron Mulder
> Assigned To: David Jencks
> Fix For: 1.2
>
>
> 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