4:09 p.m.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract link
is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:19 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2822:
-------------------------------------
Hmmm... looking at the SOAPProxyWsdlContractPublisher... it makes a http lookup to load
the wsdl. What will happen here when the ws endpoint is running in the same container?
If the .esb is being deployed before the web container is "open for business"
and accepting requests, won't this wsdl lookup fail or hang?
I did test some of these SOAPProxy quickstarts, but might have deployed and undeployed the
quickstarts to a running server i.e. where the webcontainer is fully deployed and
accepting requests.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:26 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
It will indeed fail, but with an obvious exception. The webservice_proxy_* quickstarts
each purposely deploy the war holding the webservice first, then sleeps for 3 seconds,
then deploys the esb archive.
In the problem described above, there is no exception. Just a missing EPR, which means
the contract app won't show it. Everything *functions* properly, though. It's
just that the (possibly transformed) wsdl - which is a requirement to make available - is
unavailable.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:41 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2822:
-------------------------------------
It sounds as if this has to be fixed.
As Tom points out, bringing up a server which already contains these deployments may not
work because the HTTP request will be blocked by the local server (valves not opened until
server initialises).
As this is likely to happen on the main thread we will be in a catch-22 situation. Can we
at least try this out and see if the issue is as we suspect? Can we also take this to the
forums?
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
Well, bringing up a server with both deployments and having deployment order break pulling
the wsdl I think should be a different jira item, and I think that it is would make for a
good forum entry given is that a good use case for a *proxy*. I'll create the thread,
but it should be broken off from this jira.
I don't think we need a forum thread for this jira. The wsdl contract not showing up
I know is not due to deployment order, because while doing a tiny bit of debugging
yesterday, I hand-deployed the war containing the webservice *first*, then hand-deployed
the esb file containing the soapproxy. I also see INFO log4j output from the soapproxy
saying it has sucessfully parsed the wsdl.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
It has something to do with the new http-gateway. On trunk fronting a service with
soapproxy in it with http via *JBR* works fine, and again the old http-gateway worked fine
too.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2822:
-------------------------------------
Definitely different jira items, no disagreement. Forum reference was to the second,
pulling HTTP during config.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
HTTP pulling topic pulled off into this forum thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=161091 . I'll create
a jira for it and link to the forum thread once we decide what we want to do.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:28 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward reassigned JBESB-2822:
---------------------------------
Assignee: David Ward
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:40 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
Here is the jira for the deployment order issue: JBESB-2870
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:59 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-2822.
-----------------------------
Resolution: Done
Committed revision 29581. (trunk)
Tested on both AS4 and AS5.
Integration tests run clean.
Now, if you have an http-gateway endpoint of:
http://127.0.0.1:8080/Quickstart_webservice_proxy_basic/http/Proxy_Basic/...
, and it includes a SOAPProxy action, the (transformed) wsdl is now available here:
http://127.0.0.1:8080/Quickstart_webservice_proxy_basic/http/Proxy_Basic/...
, per convention.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:46 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-2822:
-----------------------------------
Just a minor tweak:
$ svn commit rosetta/src/org/jboss/soa/esb/http/HttpConfiguration.java
Sending rosetta/src/org/jboss/soa/esb/http/HttpConfiguration.java
Transmitting file data .
Committed revision 29582.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5510
days inactive
5543
days old
11 comments
3 participants
participants (3)
-
David Ward (JIRA) -
Kevin Conner (JIRA)
-
Tom Fennelly (JIRA)