January 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3135) OneWay EBWS with WS-Addressing support enabled throws exception on invocation

by Jiri Pechanec (JIRA)

OneWay EBWS with WS-Addressing support enabled throws exception on invocation ----------------------------------------------------------------------------- Key: JBESB-3135 URL: https://jira.jboss.org/jira/browse/JBESB-3135 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.7 Reporter: Jiri Pechanec If EBWS is set to support WS-Addressing and accepts one-way invocation then server throws exception and returns status code 500. 15:39:15,798 ERROR [HandlerChainExecutor] Exception during handler processing javax.xml.ws.addressing.AddressingException: Required addressing property missing: {http://www.w3.org/2005/08/addressing}Action at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.appendRequiredHeader(SOAPAddressingPropertiesImpl.java:315) at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:265) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleResponseOrFault(WSAddressingServerHandler.java:174) at org.jboss.ws.extensions.addressing.jaxws.WSAddressingServerHandler.handleOutbound(WSAddressingServerHandler.java:110) at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:305) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:142) at org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS.callResponseHandlerChain(HandlerDelegateJAXWS.java:105) at org.jboss.ws.core.server.ServiceEndpointInvoker.callResponseHandlerChain(ServiceEndpointInvoker.java:129) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:269) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:468) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:293) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:203) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:129) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.internal.soa.esb.webservice.ESBResponseFilter.doFilter(ESBResponseFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) 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:636) If synchronous invocation is used then it works correctly. It may be cause by the upgrade of JBossWS implementation in ER7. -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3132) ERROR message shows up when deleting an already deleted esb in JON

by Kevin Conner (JIRA)

ERROR message shows up when deleting an already deleted esb in JON ------------------------------------------------------------------ Key: JBESB-3132 URL: https://jira.jboss.org/jira/browse/JBESB-3132 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3130) Update PicketLink to 1.0.1

by Daniel Bevenius (JIRA)

Update PicketLink to 1.0.1 -------------------------- Key: JBESB-3130 URL: https://jira.jboss.org/jira/browse/JBESB-3130 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Security Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 CP1 -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3136) udp_gateway contains unused groovy files

by Kevin Conner (JIRA)

udp_gateway contains unused groovy files ---------------------------------------- Key: JBESB-3136 URL: https://jira.jboss.org/jira/browse/JBESB-3136 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Minor Fix For: 4.7 CP1 -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3133) http_gateway quick start should work with ant runtest and not ant soap to be consistent with most other quickstarts

by Kevin Conner (JIRA)

http_gateway quick start should work with ant runtest and not ant soap to be consistent with most other quickstarts ------------------------------------------------------------------------------------------------------------------- Key: JBESB-3133 URL: https://jira.jboss.org/jira/browse/JBESB-3133 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3131) ruleReload for CBR router does not work

by Jiri Pechanec (JIRA)

ruleReload for CBR router does not work --------------------------------------- Key: JBESB-3131 URL: https://jira.jboss.org/jira/browse/JBESB-3131 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.7 Reporter: Jiri Pechanec Parameter ruleReload does not have any effect - rules are not reloaded. Use fun_cbr quickstart ant deploy ant runtestDrools Blue Team is printed into console Edit deploy/Quickstart_fun_cbr.esb/FunCBRRules-XPath.drl and modify the status codes (rotate them by one) and modify all the log messages ant runtestDrools Blue Team is printed into console -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3076) relative schema imports in WSDL unresolved when loaded by HttpSOAPProxyWsdlLoader

by David Ward (JIRA)

relative schema imports in WSDL unresolved when loaded by HttpSOAPProxyWsdlLoader --------------------------------------------------------------------------------- Key: JBESB-3076 URL: https://jira.jboss.org/jira/browse/JBESB-3076 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 Please read: http://community.jboss.org/thread/144706 -- 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

14 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2913) Only one JMS endpoint accessible when more available

by Lukáš Petrovický (JIRA)

Only one JMS endpoint accessible when more available ---------------------------------------------------- Key: JBESB-2913 URL: https://jira.jboss.org/jira/browse/JBESB-2913 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Lukáš Petrovický Using enhanced webservice_consumer1 QS (to be attached soon), we deploy an ESB service with two different JMS listeners: <jms-provider name="JBossMQ" connection-factory="ConnectionFactory"> ... <jms-bus busid="quickstartEsbChannel"> <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_webservice_consumer1_esb" /> </jms-bus> <jms-bus busid="quickstartEsbChannel2"> <jms-message-filter dest-type="QUEUE" dest-name="queue/quickstart_webservice_consumer1_esb2" /> </jms-bus> </jms-provider> ... <listeners> <jms-listener name="JMS-ESBListener" busidref="quickstartEsbChannel"/> <jms-listener name="JMS-ESBListener2" busidref="quickstartEsbChannel2"/> ... </listeners> Using JBoss ESB Service list (http://localhost:8080/contract/), we can see the service correctly with two endpoints (jms:localhost:1099#queue/quickstart_webservice_consumer1_esb, jms:localhost:1099#queue/quickstart_webservice_consumer1_esb2). However, both these endpoints share the same WSDL and that only contains a port for the first listener: ... <service name="HelloWorldWSService"> <port binding="tns:HelloWorldBinding" name="HelloWorldPort"> <soap:address location="jms:/#queue/quickstart_webservice_consumer1_esb"/> </port> </service> ... -- 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

14 years, 4 months

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-3092) SOAPProxy action: Port number is missing in the imported schema types URL

by Boris Belovic (JIRA)

SOAPProxy action: Port number is missing in the imported schema types URL ------------------------------------------------------------------------- Key: JBESB-3092 URL: https://jira.jboss.org/jira/browse/JBESB-3092 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Boris Belovic I have a simple ESB service with SOAPProxy action, the WSDL document for the webservice imports the schema types from external .xsd file. The ESB service fails on deployment with following exceptions: [JBossWSEntityResolver] Trying to resolve id as a non-file URL: http://localhost/Contract_publisher_soapproxy_ws/HelloWorldImport?wsdl&re... Caused by: java.lang.IllegalArgumentException: Cannot resolve imported resource: http://localhost/Contract_publisher_soapproxy_ws/HelloWorldImport?wsdl&re... at org.jboss.ws.tools.wsdl.WSDLLocatorImpl.getImportInputSource(WSDLLocatorImpl.java:139) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseImport(JBossWSDLReaderImpl.java:398) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.parseDefinitions(JBossWSDLReaderImpl.java:322) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2292) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2256) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2309) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2330) at org.jboss.ws.tools.wsdl.JBossWSDLReaderImpl.readWSDL(JBossWSDLReaderImpl.java:2362) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:128) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxyWsdlLoader.loadDefinitions(SOAPProxyWsdlLoader.java:102) at org.jboss.soa.esb.actions.soap.proxy.SOAPProxy.<init>(SOAPProxy.java:145) ... 66 more It looks like the port number (8080) is missing in the URL of the imported resource. This issue is new in ER6, when I tried to deploy the service on ER5, everything works fine (no exceptions during the deployment). -- 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

14 years, 4 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-3070) Implement workaround for SOA-1606

by Kevin Conner (JIRA)

Implement workaround for SOA-1606 --------------------------------- Key: JBESB-3070 URL: https://jira.jboss.org/jira/browse/JBESB-3070 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- 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

14 years, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2010