Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <20360298.1153033624353.JavaMail.jira@brutus>
Date: Sun, 16 Jul 2006 00:07:04 -0700 (PDT)
From: "Alan Cabrera (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Updated: (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=all ]

Alan Cabrera updated GERONIMO-2030:
-----------------------------------

    Fix Version/s: 1.1.x
                       (was: 1.1.1)

Moving unassigned issues over to the 1.1.x pool where they can be worked on for the, in all probability, 1.1.2 patch.

> Allow WebServiceBuilder determine if there are WebServices to be deployed
> -------------------------------------------------------------------------
>
>                 Key: GERONIMO-2030
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2030
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 1.1
>         Environment: all
>            Reporter: Conrad O'Dea
>             Fix For: 1.1.x
>
>         Attachments: find-web-services.patch, 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