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:22:06 UTC
[jira] Created: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Sachin Patel (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Sachin Patel updated GERONIMO-2030:
-----------------------------------
Fix Version/s: 1.1.1
(was: 1.1.x)
Assignee: Matt Hogstrom
This jira is unassigned but contains a patch that needs to be reviewed for inclusion in 1.1.1.
> 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
> Assigned To: Matt Hogstrom
> Fix For: 1.1.1
>
> 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
[jira] Assigned: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Chris Cardona (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Chris Cardona reassigned GERONIMO-2030:
---------------------------------------
Assignee: Chris Cardona
> 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
> Assigned To: Chris Cardona
> Fix For: 1.1.1
>
> 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
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Conrad O'Dea (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=comments#action_12411989 ]
Conrad O'Dea commented on GERONIMO-2030:
----------------------------------------
I'll port it although it will probably be a couple of days before I get to it.
For this to be most useful I think that the plans for the deployers need to be refactored a little to be similar to those on trunk. Principally this means moving the WebServiceBuilder GBean from the J2EE deployer out in to it's own config. I don't know if this is planned work or not.
thanks
> 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Conrad O'Dea (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Conrad O'Dea updated GERONIMO-2030:
-----------------------------------
Attachment: geronimo_ws_builder_change.patch
patch to move webservice detection into WebServiceBuilder
> 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Alan Cabrera (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Sachin Patel (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Sachin Patel updated GERONIMO-2030:
-----------------------------------
Assignee: (was: Matt Hogstrom)
> 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.1
>
> 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
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Julian Squires (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Julian Squires updated GERONIMO-2030:
-------------------------------------
Attachment: find-web-services.patch
Here's an updated patch against branches/1.1, which passes all tests.
> 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: 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
[jira] Closed: (GERONIMO-2030) Allow WebServiceBuilder determine if
there are WebServices to be deployed
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Aaron Mulder closed GERONIMO-2030.
----------------------------------
Fix Version/s: (was: 1.2)
Resolution: Fixed
Closing this as applied to 1.1.1 -- copied the issue to track the status in trunk.
> 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
> Assigned To: David Jencks
> Fix For: 1.1.1
>
> 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
[jira] Assigned: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
David Jencks reassigned GERONIMO-2030:
--------------------------------------
Assignee: David Jencks
> 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
> Assigned To: David Jencks
> Fix For: 1.1.1, 1.2
>
> 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
[jira] Assigned: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Chris Cardona (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Chris Cardona reassigned GERONIMO-2030:
---------------------------------------
Assignee: (was: Chris Cardona)
> 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.1, 1.2
>
> 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Donald Woods updated GERONIMO-2030:
-----------------------------------
Fix Version: 1.2
Version: 1.1
> 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
> Versions: 1.1
> Environment: all
> Reporter: Conrad O'Dea
> Fix For: 1.2
> 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Donald Woods (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
Donald Woods updated GERONIMO-2030:
-----------------------------------
Fix Version: 1.1.1
(was: 1.2)
Moving to 1.1.1 since G1579 depends on this fix.
David J., can you either apply this patch or move it to 1.2 if you think its too much for a maintenance release?
> 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
> Versions: 1.1
> Environment: all
> Reporter: Conrad O'Dea
> Fix For: 1.1.1
> 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
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Chris Cardona (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=comments#action_12425053 ]
Chris Cardona commented on GERONIMO-2030:
-----------------------------------------
Hi David, go ahead assign it to yourself. I just started looking at it and I haven't done any significant work yet. Thanks.
> 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
> Assigned To: Chris Cardona
> Fix For: 1.1.1, 1.2
>
> 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
[jira] Updated: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2030?page=all ]
David Jencks updated GERONIMO-2030:
-----------------------------------
Fix Version/s: 1.2
I've applied a slightly modifed version of this patch to 1.1.1 in g. rev 427654 and openejb rev 2834. The change is to use the isEJB parameter to look for WEB-INF/webservices.xml or META-INF/webservices.xml rather than looking in both locations.
Chris, do you have changes you wish to make to this patch or should I reassign to myself and apply to trunk?
> 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
> Assigned To: Chris Cardona
> Fix For: 1.1.1, 1.2
>
> 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
[jira] Commented: (GERONIMO-2030) Allow WebServiceBuilder determine
if there are WebServices to be deployed
Posted by "Conrad O'Dea (JIRA)" <de...@geronimo.apache.org>.
[ 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