Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <15337291.1147818966782.JavaMail.jira@brutus>
Date: Tue, 16 May 2006 22:36:06 +0000 (GMT+00:00)
From: "David Jencks (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
 if there are WebServices to be deployed
In-Reply-To: <24756538.1147767726142.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-2030?page=comments#action_12412067 ] 

David Jencks commented on GERONIMO-2030:
----------------------------------------

A couple of days is fine, I think I would rather wait till after 1.1 is frozen/branched to apply a patch of this impact.  

I think you may not have an up to date copy of 1.1?  The deployers have been split up into lots of plans similar to how they are in head for a couple of weeks now.  Please update and check again :-)

> 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