[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=comments#action_12411987 ]
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: 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
