You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jeff Puro (JIRA)" <ji...@apache.org> on 2006/09/27 18:45:23 UTC
[jira] Created: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
--------------------------------------------------------------------------------------------------------------------------------------------
Key: SM-604
URL: https://issues.apache.org/activemq/browse/SM-604
Project: ServiceMix
Issue Type: Bug
Components: servicemix-http, servicemix-jsr181
Affects Versions: 3.0
Reporter: Jeff Puro
Fix For: 3.0.1
Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Guillaume Nodet resolved SM-604.
--------------------------------
Fix Version/s: 3.1
Resolution: Fixed
Author: gnodet
Date: Thu Oct 19 05:12:08 2006
New Revision: 465596
URL: http://svn.apache.org/viewvc?view=rev&rev=465596
Log:
SM-604: Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
Patch provided by Jeff Puro, thx !
Modified:
incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/HttpComponent.java
incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java
incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java
Author: gnodet
Date: Thu Oct 19 05:12:09 2006
New Revision: 465597
URL: http://svn.apache.org/viewvc?view=rev&rev=465597
Log:
SM-604: Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
Patch provided by Jeff Puro, thx !
Modified:
incubator/servicemix/branches/servicemix-3.0/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java
incubator/servicemix/branches/servicemix-3.0/servicemix-http/src/main/java/org/apache/servicemix/http/HttpLifeCycle.java
incubator/servicemix/branches/servicemix-3.0/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1, 3.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=comments#action_37236 ]
Jeff Puro commented on SM-604:
------------------------------
Currently the patch does not distinguish between http and https. It assumes everything is http. This should be an easy fix.
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Jeff Puro updated SM-604:
-------------------------
Attachment: servicemix-http-host-port.patch
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Jeff Puro updated SM-604:
-------------------------
Attachment: (was: servicemix-http-host-port.patch)
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Work on SM-604 started by Jeff Puro.
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Jeff Puro updated SM-604:
-------------------------
Attachment: servicemix-http-host-port.patch
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
> Attachments: servicemix-http-host-port.patch
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (SM-604) Allow servicemix-http managed mode to
dynamically determine the server, port, and context path it is running on
when generating jsr181 WSDLs
Posted by "Jeff Puro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-604?page=all ]
Jeff Puro reassigned SM-604:
----------------------------
Assignee: Jeff Puro
> Allow servicemix-http managed mode to dynamically determine the server, port, and context path it is running on when generating jsr181 WSDLs
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-604
> URL: https://issues.apache.org/activemq/browse/SM-604
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http, servicemix-jsr181
> Affects Versions: 3.0
> Reporter: Jeff Puro
> Assigned To: Jeff Puro
> Fix For: 3.0.1
>
>
> Currently when ServiceMix has an http endpoint that is running in "managed" mode and that endpoint has a target service of a jsr181 endpoint it generates WSDLs with a hardcoded value of "localhost". However, it should determine the server, port, and context path of the web container that it is running under and use this information to generate the service element in the WSDL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira