2:33 p.m.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.7 CP2
Reporter: David Ward
Assignee: David Ward
Fix For: 4.7 CP2
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
2:35 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3255:
------------------------------
Fix Version/s: 4.8
(was: 4.7 CP2)
Changing incorrect Fix Version to 4.8.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7 CP2
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:52 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3255:
-----------------------------------
What's interesting is why classloading of
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy" from XMLBeansModel.class works
fine during hot-deploys and re-deploys, but not during server re-starts.
I tried explicity defining this in the .esb archive's deployment.xml:
<depends>jboss.esb:deployment=soap.esb</depends>
, even though this line exists in actionArtifactMap.properties:
org.jboss.soa.esb.actions.soap.proxy.SOAPProxy=soap.esb
, with hopes that it would be a classloading workaround, but no dice.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7 CP2
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:39 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
Kevin Conner updated JBESB-3255:
--------------------------------
Affects Version/s: 4.7
(was: 4.7 CP2)
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:41 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3255:
-------------------------------------
This sounds like a more basic problem, can we have a log file attached to this issue
please?
Also, do you have an example which demonstrates the issue?
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
2 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3255:
-----------------------------------
There is nothing in the log. The WSDL just silently does not show up on server re-starts
(again, it does on hot deploys and re-deploys). The CNFE is silently
"swallowed" because otherwise the continous integration builds break (as the
classpath is not set up correctly for those). I can see that at least a log.warn(...)
would be nice in the future at least, and probably spending the time fixing the junit
classpath.
The basic problem is that XMLBeansModel is in rosetta.jar, and SOAPProxy is in soap.esb,
and whereas soap.esb is available to the classloader of XMLBeansModel during hot deploys
and re-deploys, it doesn't seem to be for server re-starts. Otherwise,
SOAPProxy.class would be found.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
5:20 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3255:
-------------------------------------
The log will show the sequence though, which is likely to be relevant.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
5:48 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3255:
------------------------------
Complexity: Medium (was: Low)
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
5:50 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward updated JBESB-3255:
------------------------------
Attachment: server.log
Attaching server.log, when starting the server fresh with webservice_proxy_basic.ejb
already in the deploy directory.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
Attachments: server.log
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:22 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3255:
-----------------------------------
Sequences are indeed different. Below are excerpts from 2 different server.logs, with the
timestamps stripped out (although order preserved!) and grepped for relevant lines.
server.log during a hot-deploy of quickstart:
----------------------------------------------------------
Here, you see that soap.esb goes through all it's deploment steps BEFORE
Quickstart_webservice_proxy_basic.esb even starts. Everything works well in this
scenario.
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/soap.esb/
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName soap.esb
with identity: ID-5
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service,
Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName
Quickstart_webservice_proxy_basic.esb with identity: ID-7
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Registering action class
org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Using normal action
pipeline processor for org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
server.log during a restart of jboss:
----------------------------------------------
Here, you see an inter-mingling of deploment steps between
Quickstart_webservice_proxy_basic.esb and soap.esb. In this scenario, the service
deploys, but the WSDL is not available due to a CNFE trying to find SOAPProxy.class (which
lives in a soap.esb jar).
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service,
Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] create esb service, soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer] Deploying:
file:/home/dward/repos/jbossesb/trunk/product/build/jbossesb-server-4.8/server/default/deploy/soap.esb/
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName soap.esb
with identity: ID-5
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Creating
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.lifecycle.LifecycleResourceManager] Associating deploymentName
Quickstart_webservice_proxy_basic.esb with identity: ID-6
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Created
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=soap.esb
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Starting
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Registering action class
org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Using normal action
pipeline processor for org.jboss.soa.esb.actions.soap.proxy.SOAPProxy
[org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment] Started
jboss.esb:deployment=Quickstart_webservice_proxy_basic.esb
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
Attachments: server.log
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:46 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-3255:
-------------------------------------
The problem is that the call to getServiceContracts() is occurring in
EsbWebServiceDeployer and that is called too early in the deployment process, at
POST_PARSE. The classloader for the deployment has not been created at this stage.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
Attachments: server.log
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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:44 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3255) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward closed JBESB-3255.
-----------------------------
Resolution: Done
[trunk]$ svn commit
Sending
product/rosetta/src/org/jboss/internal/soa/esb/publish/ContractProviderLifecycleResource.java
Sending product/rosetta/src/org/jboss/soa/esb/listeners/config/Configuration.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/config/JBoss4ESBDeployer.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/config/JBoss4ESBDeployment.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/config/mappers/XMLBeansModel.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/config/mappers110/XMLBeansModel.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/config/mappers120/XMLBeansModel.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/deployers/mc/EsbDeployer.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/deployers/mc/EsbDeployment.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/deployers/mc/EsbMetaData.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/deployers/mc/EsbWebServiceDeployer.java
Sending
product/rosetta/src/org/jboss/soa/esb/listeners/gateway/http/HttpGatewayServlet.java
Transmitting file data ............
Committed revision 32439.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL: https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
Attachments: server.log
When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL
shows up in the contract JSP application no problem. However, when re-starting the server
(and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still
functions. The problem is the missing WSDL.
The problem is in:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610.
The class it's looking for, of course, is
"org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.
--
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
5199
days inactive
5210
days old
11 comments
2 participants
participants (2)
-
David Ward (JIRA) -
Kevin Conner (JIRA)