September 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2861) Quickstarts: webservice_bpel compatibility issues

by Boris Belovic (JIRA)

Quickstarts: webservice_bpel compatibility issues ------------------------------------------------- Key: JBESB-2861 URL: https://jira.jboss.org/jira/browse/JBESB-2861 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.4 CP2 Reporter: Boris Belovic Priority: Minor Webservice_bpel quickstart can not be run in CP02 due to compatibility issues. These issues come from Activevos (creator of BPEL engine) and does not come from JBoss side. Activevos should first solve these issues and then this QS can be run again. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2858) Fix namespace in mappers110 tests

by Kevin Conner (JIRA)

Fix namespace in mappers110 tests --------------------------------- Key: JBESB-2858 URL: https://jira.jboss.org/jira/browse/JBESB-2858 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 Some configurations still refer to the 1.0.1 schema -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2583) Add support for XPath routing

by Kevin Conner (JIRA)

Add support for XPath routing ----------------------------- Key: JBESB-2583 URL: https://jira.jboss.org/jira/browse/JBESB-2583 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 -- 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

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2857) ESBContractGeneratorUnitTest test disabled

by Kevin Conner (JIRA)

ESBContractGeneratorUnitTest test disabled ------------------------------------------ Key: JBESB-2857 URL: https://jira.jboss.org/jira/browse/JBESB-2857 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 The testWSAExtensions110 test has been disabled at some point, re-enable it. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1879) JMS provider transactional support cannot be enabled

by Jiri Pechanec (JIRA)

JMS provider transactional support cannot be enabled ---------------------------------------------------- Key: JBESB-1879 URL: https://jira.jboss.org/jira/browse/JBESB-1879 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.2.1 CP3 Reporter: Jiri Pechanec Assignee: Kevin Conner Fix For: 4.2.1 CP4 It was told that plain jms-provider now supports JTA transactions and according to code it could but there is no transacted attribute available for jms-provider-type in XML schema for jboss-esb.xml file. -- 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

15 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-2856) WSDL unavailable for deployed web service in AS5.1/ESB4.6

by Gary Brown (JIRA)

WSDL unavailable for deployed web service in AS5.1/ESB4.6 --------------------------------------------------------- Key: JBESB-2856 URL: https://jira.jboss.org/jira/browse/JBESB-2856 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.6 Reporter: Gary Brown In the RiftSaw project, we have an example demonstrating the integration of RiftSaw into the ESB. This is a modified version of the Quickstart_webservice_bpel to run on ODE instead of AE. Attached is a cut down version of the example, with the bpel stripped out, and also some of the jbossesb/deployment configuration modified to enable the example to be deployed to both JBossAS4.2.3/ESB4.5 and JBossAS5.1/ESB4.6. When deployed in AS4.2.3/ESB4.5, there are two web services created (although I will focus on the shipping service). From the http://localhost:8080/jbossws/services console window, it shows the endpoint address as http://127.0.0.1:8080/Quickstart_webservice_bpel/ABI_Shipping?wsdl and when this link is navigated it shows valid WSDL. When the same ESB bundle is deployed to AS5.1/ESB4.6, the JBossWS console shows the endpoint address as http://127.0.0.1:8080/Quickstart_webservice_bpel-Quickstart_webservice_bp... which navigates to a 'resouce is not available' error page. If I try the AS4.2.3/ESB4.5 URL with this server I get the following stack trace: 12:00:09,463 ERROR [[/Quickstart_webservice_bpel]] StandardWrapper.Throwable javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/Quickstart_webservice_bpel,endpoint=ABI_Shipping at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) 12:00:09,464 ERROR [[ABI_Shipping]] Allocate exception for servlet ABI_Shipping javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/Quickstart_webservice_bpel,endpoint=ABI_Shipping at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) [ Show » ] Gary Brown - 28/Sep/09 07:00 AM When deploying just the Quickstart_webservice_esb_bpel.esb to a AS4.2.3 environment (slightly modified to ensure it deployed), the jbossws console showed the wsdl at: http://127.0.0.1:8080/Quickstart_webservice_bpel/ABI_Shipping?wsdl Navigating this link showed a valid WSDL definition. However, when deploying the same ESB bundle to AS5.1/ESB4.6, it shows the endpoint address in the JBossWS/Services console as: http://127.0.0.1:8080/Quickstart_webservice_bpel-Quickstart_webservice_bp... This is the address that shows the "requested resource is not available" error page. If we use the same URL as in 4.2.3, then it gets the following stack trace: 12:00:09,463 ERROR [[/Quickstart_webservice_bpel]] StandardWrapper.Throwable javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/Quickstart_webservice_bpel,endpoint=ABI_Shipping at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) 12:00:09,464 ERROR [[ABI_Shipping]] Allocate exception for servlet ABI_Shipping javax.xml.ws.WebServiceException: Cannot obtain endpoint for: jboss.ws:context=/Quickstart_webservice_bpel,endpoint=ABI_Shipping at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initEndpoint(AbstractEndpointServlet.java:153) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.initServiceEndpoint(AbstractEndpointServlet.java:124) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.init(AbstractEndpointServlet.java:72) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1048) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:777) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) -- 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

15 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2850) Fix javadoc generation

by Kevin Conner (JIRA)

Fix javadoc generation ---------------------- Key: JBESB-2850 URL: https://jira.jboss.org/jira/browse/JBESB-2850 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 1.2 xsd configuration and some errors. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2833) Remove XMLUnit from codebase

by Kevin Conner (JIRA)

Remove XMLUnit from codebase ---------------------------- Key: JBESB-2833 URL: https://jira.jboss.org/jira/browse/JBESB-2833 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 XMLUnit has been introduced, even though we already have other means of checking XML, and is now leaked into the core codebase through ESBContractGenerator. We need to remove this dependency. -- 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

15 years, 1 month

3
12
0 / 0

[JBoss JIRA] Created: (JBESB-2854) Add load-on-startup configurability to servlet-based gateways

by David Ward (JIRA)

Add load-on-startup configurability to servlet-based gateways ------------------------------------------------------------- Key: JBESB-2854 URL: https://jira.jboss.org/jira/browse/JBESB-2854 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.7 Reporter: David Ward Assignee: David Ward Priority: Trivial Fix For: 4.7 This is a trivial next-to-zero risk addition that was intentionally done to support eager loading of the HttpGatewayServlet so it would register an EPR for this item: JBESB-2824 . Although that item was rejected, this could still be a useful addition, and since it's risk is next-to-zero, I'd rather not lose the capability. Created this separate jira item so the svn commit could be tracked with it. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2824) HttpGatewayServlet doesn't register an HTTPEpr

by David Ward (JIRA)

HttpGatewayServlet doesn't register an HTTPEpr ---------------------------------------------- Key: JBESB-2824 URL: https://jira.jboss.org/jira/browse/JBESB-2824 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 It should register an HTTPEpr in init() and unregister it in destroy(). -- 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

15 years, 1 month

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues September 2009