[JBoss JIRA] Created: (JBESB-3083) Wise SOAPClient action is unable to invoke oneway methods on the endpoints
by Boris Belovic (JIRA)
Wise SOAPClient action is unable to invoke oneway methods on the endpoints
--------------------------------------------------------------------------
Key: JBESB-3083
URL: https://jira.jboss.org/jira/browse/JBESB-3083
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.7
Reporter: Boris Belovic
Priority: Critical
Attachments: wise_oneway.tar.bz2
Wise SOAPClient action is unable to invoke oneway methods (methods annotated with javax.jws.Oneway annotation) on WS endpoints. It looks like webservice WSDL is parsed correctly, but after that no statements from oneway method body are executed. We tested this with very simple webservice (see attached file) containing one oneway method with System.out.println() statement. After WSDL was parsed, there was no further output from webservice method.
Invocation of twoway methods on WS endpoint is working correctly (without any problems/exceptions and with expected results).
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBESB-2912) No re-deployment of an altered package
by Lukáš Petrovický (JIRA)
No re-deployment of an altered package
--------------------------------------
Key: JBESB-2912
URL: https://jira.jboss.org/jira/browse/JBESB-2912
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment
Affects Versions: 4.7
Reporter: Lukáš Petrovický
When deploying an ESB archive of a webservice_consumer1 QS, everything goes well. However, when I update the ESB archive by deleting WEB-INF/jboss-web.xml in the WAR inside and then overwrite the already deployed ESB with this new one, the deployer doesn't pick it up and re-deployment never happens.
I also tried updating the index.jsp inside the WAR inside the ESB archive, and the re-deployment didn't happen as well. When I delete the whole WAR from inside the ESB, the re-deployment does happen. (And fails, which is expected.)
>From these experiments I conclude that the re-deployment doesn't happen when you only alter the WAR file inside the ESB archive and nothing else.
If necessary, I can attach both the original and altered ESB archives - didn't do so, because they're both very easy to create.
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBESB-3029) JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
by Kevin Conner (JIRA)
JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
----------------------------------------------------------------------------------
Key: JBESB-3029
URL: https://jira.jboss.org/jira/browse/JBESB-3029
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.6
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.8
Jeff DeLong reported this issue to me. Thanks Jeff!
When deploying a .esb archive exploded the schema imports/includes do not work. This is because the getSchemas() method in JBoss4ESBDeployer cannot handle a deployment that is a '-esb.xml' file but instead currently only handles directory or a zip archived ending with '.esb'.
We need to add support for deployments of exploded archives where the deployment deployment file is a '-esb.xml' file.
This can be seen by running the publish_as_webservice quickstart:
ant -Ddeploy.exploded.requested=true deploy
As a solution we could for example add the following to getSchemas() in JBoss4ESBDeployer:
final String fileName = file.getName();
if (fileName.endsWith(".esb"))
return getSchemasFromArchive(file);
if (fileName.endsWith("-esb.xml"))
{
final File metaInf = file.getParentFile();
final File deploymentRoot = metaInf.getParentFile();
return getSchemasFromDirectory(deploymentRoot);
}
--
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
16 years, 3 months
[JBoss JIRA] Created: (JBESB-3027) JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
by Daniel Bevenius (JIRA)
JBoss4ESBDeployer: does not support schema imports/includes for exploded archives.
----------------------------------------------------------------------------------
Key: JBESB-3027
URL: https://jira.jboss.org/jira/browse/JBESB-3027
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.7, 4.6
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.8
Jeff DeLong reported this issue to me. Thanks Jeff!
When deploying a .esb archive exploded the schema imports/includes do not work. This is because the getSchemas() method in JBoss4ESBDeployer cannot handle a deployment that is a '-esb.xml' file but instead currently only handles directory or a zip archived ending with '.esb'.
We need to add support for deployments of exploded archives where the deployment deployment file is a '-esb.xml' file.
This can be seen by running the publish_as_webservice quickstart:
ant -Ddeploy.exploded.requested=true deploy
As a solution we could for example add the following to getSchemas() in JBoss4ESBDeployer:
final String fileName = file.getName();
if (fileName.endsWith(".esb"))
return getSchemasFromArchive(file);
if (fileName.endsWith("-esb.xml"))
{
final File metaInf = file.getParentFile();
final File deploymentRoot = metaInf.getParentFile();
return getSchemasFromDirectory(deploymentRoot);
}
--
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
16 years, 4 months