October 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3957) Upgrade spring-oxm to 3.2.4.RELEASE

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3957: ------------------------------------- Summary: Upgrade spring-oxm to 3.2.4.RELEASE Key: JBESB-3957 URL: https://issues.jboss.org/browse/JBESB-3957 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.12 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.11 CP3 Upgrade spring oxm to 3.2.4.RELEASE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3957) Upgrade spring-oxm to 3.2.4.RELEASE

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3957?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3957. ----------------------------------- Resolution: Done > Upgrade spring-oxm to 3.2.4.RELEASE > ----------------------------------- > > Key: JBESB-3957 > URL: https://issues.jboss.org/browse/JBESB-3957 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.12 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > Upgrade spring oxm to 3.2.4.RELEASE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3957) Upgrade spring-oxm to 3.2.4.RELEASE

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3957?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3957. --------------------------------- > Upgrade spring-oxm to 3.2.4.RELEASE > ----------------------------------- > > Key: JBESB-3957 > URL: https://issues.jboss.org/browse/JBESB-3957 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.12 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > Upgrade spring oxm to 3.2.4.RELEASE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3954: ------------------------------------------------ tcunning(a)redhat.com changed the Status of [bug 1014959|https://bugzilla.redhat.com/show_bug.cgi?id=1014959] from NEW to MODIFIED > HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages > ------------------------------------------------------------------------ > > Key: JBESB-3954 > URL: https://issues.jboss.org/browse/JBESB-3954 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.12 > Reporter: Tadayoshi Sato > Assignee: Tadayoshi Sato > Fix For: 4.11 CP3 > > Attachments: reproducer.zip > > > The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint: > {code} > 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService has thrown exception, unwinding now > org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader. > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:230) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111) > at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) > at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431) > at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) > at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442) > at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<' > at [row,col {unknown-source}]: [1,1] > at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648) > at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047) > at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1095) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:122) > ... 15 more > {code} > While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3954. --------------------------------- > HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages > ------------------------------------------------------------------------ > > Key: JBESB-3954 > URL: https://issues.jboss.org/browse/JBESB-3954 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.12 > Reporter: Tadayoshi Sato > Assignee: Tadayoshi Sato > Fix For: 4.11 CP3 > > Attachments: reproducer.zip > > > The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint: > {code} > 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService has thrown exception, unwinding now > org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader. > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:230) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111) > at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) > at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431) > at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) > at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442) > at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<' > at [row,col {unknown-source}]: [1,1] > at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648) > at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047) > at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1095) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:122) > ... 15 more > {code} > While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3954) HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3954?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3954. ----------------------------------- Fix Version/s: 4.11 CP3 Resolution: Done Committed to 4.11CP2 branch. > HTTP Gateway and SOAPProcessor combination fails to handle MTOM messages > ------------------------------------------------------------------------ > > Key: JBESB-3954 > URL: https://issues.jboss.org/browse/JBESB-3954 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.12 > Reporter: Tadayoshi Sato > Assignee: Tadayoshi Sato > Fix For: 4.11 CP3 > > Attachments: reproducer.zip > > > The combination of JBR Gateway and SOAPProcessor can handle MTOM messages well as demonstrated by the {{webservice_mtom}} quickstart. However, if you substitute the JBR Gateway ({{<jbr-listener>}}) with HTTP Gateway ({{<http-gateway>}}), it fails to handle MTOM with the following error thrown from the target web service endpoint: > {code} > 2013-10-01 18:25:16,174 WARNING [org.apache.cxf.phase.PhaseInterceptorChain] (pool-25-thread-1) Interceptor for {http://ws.esb.samples.redhat.com/}MTOMService has thrown exception, unwinding now > org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader. > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:230) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60) > at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:243) > at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:111) > at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:99) > at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:431) > at org.jboss.wsf.stack.cxf.ServletControllerExt.invoke(ServletControllerExt.java:173) > at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:61) > at org.jboss.soa.esb.actions.soap.SOAPProcessor.process(SOAPProcessor.java:212) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:667) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:614) > at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:442) > at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:724) > Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<' > at [row,col {unknown-source}]: [1,1] > at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:648) > at com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2047) > at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > at com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1095) > at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:122) > ... 15 more > {code} > While the above error stacktrace is specific to JBossWS-CXF, the same issue can be reproduced on JBossWS-Native, too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3951) Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3951?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3951. --------------------------------- > Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging. > ----------------------------------------------------------------------------------------- > > Key: JBESB-3951 > URL: https://issues.jboss.org/browse/JBESB-3951 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transports > Affects Versions: 4.12 > Environment: All JBossESB. > Reporter: Rick Wagner > Assignee: Tom Cunningham > Priority: Minor > Fix For: 4.11 CP3 > > > org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters. > The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB. > 1) The constructor needs to pass along JMS credentials to it's parent. > 2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names). > These can be implemented with the following code snippets: > >>> In the class declarations <<< > private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString(); > >>> Replace the 'short' constructor with this longer one <<< > super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential()); > >>> Implement 'replyDestinationName' with conditional <<< > private static String replyDestinationName(JMSEpr toEpr) > throws URISyntaxException > { > if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE")){ > return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString(); > }else{ > return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString(); > } > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3951) Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging.

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3951?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3951. ----------------------------------- Assignee: Tom Cunningham Fix Version/s: 4.11 CP3 Resolution: Done > Please make DefaultJmsReplyToEpr more compatible with industry conventions for Messaging. > ----------------------------------------------------------------------------------------- > > Key: JBESB-3951 > URL: https://issues.jboss.org/browse/JBESB-3951 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transports > Affects Versions: 4.12 > Environment: All JBossESB. > Reporter: Rick Wagner > Assignee: Tom Cunningham > Priority: Minor > Fix For: 4.11 CP3 > > > org.jboss.internal.soa.esb.addressing.eprs.DefaultJmsReplyToEpr does not allow the user to choose a queue name that includes uppercase letters. > The most widespread messaging system in the field is most often used with uppercase queue names. This forces administrators to break conventions for JBossESB. > 1) The constructor needs to pass along JMS credentials to it's parent. > 2) An option should be added so WSMQ users can comply with IBM queue naming standards (upper case names). > These can be implemented with the following code snippets: > >>> In the class declarations <<< > private static final String ackMode = AcknowledgeMode.AUTO_ACKNOWLEDGE.toString(); > >>> Replace the 'short' constructor with this longer one <<< > super(epr.getVersion(), epr.getDestinationType(), replyDestinationName(epr), epr.getConnectionFactory(), epr.getJndiEnvironment(), replySelector(epr), epr.getPersistent(), ackMode, epr.getJMSSecurityPrincipal(), epr.getJMSSecurityCredential()); > >>> Implement 'replyDestinationName' with conditional <<< > private static String replyDestinationName(JMSEpr toEpr) > throws URISyntaxException > { > if ("UPPERCASE" == System.getProperty("REPLY_TO_SUFFIX_CASE")){ > return new StringBuilder().append(toEpr.getDestinationName()).append("_REPLY").toString(); > }else{ > return new StringBuilder().append(toEpr.getDestinationName()).append("_reply").toString(); > } > } -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3956) Make JBoss ESB buildable by JDK 1.7

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3956?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3956. ----------------------------------- Resolution: Done > Make JBoss ESB buildable by JDK 1.7 > ----------------------------------- > > Key: JBESB-3956 > URL: https://issues.jboss.org/browse/JBESB-3956 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > The newest OS X version, OS X Mavericks, has eliminated JDK 1.6 from its list of VMs. Need to make ESB buildable by a JAVA_HOME that points to JDK1.7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3956) Make JBoss ESB buildable by JDK 1.7

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3956?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3956. --------------------------------- > Make JBoss ESB buildable by JDK 1.7 > ----------------------------------- > > Key: JBESB-3956 > URL: https://issues.jboss.org/browse/JBESB-3956 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build and Release > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > The newest OS X version, OS X Mavericks, has eliminated JDK 1.6 from its list of VMs. Need to make ESB buildable by a JAVA_HOME that points to JDK1.7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2013