June 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3822) Invalid logical operator used within MessageAwareListener

by Kevin Conner (JIRA)

Kevin Conner created JBESB-3822: ----------------------------------- Summary: Invalid logical operator used within MessageAwareListener Key: JBESB-3822 URL: https://issues.jboss.org/browse/JBESB-3822 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Reporter: Kevin Conner There is a test for rolling back all exceptions, currently enabled by default, however this code has an issue. It currently reads problem = rollbackOnPipelineFaults && !pipeline.process(_pipelineMessage); which means that the pipeline will only be executed if rollbackOnPipelineFaults is true. The line *should* read problem = rollbackOnPipelineFaults & !pipeline.process(_pipelineMessage); (note use of & rather than &&) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] (JBESB-3824) Provide public constructors for FtpImpl / SecureFtpImpl using ConfigTree

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3824: ------------------------------------- Summary: Provide public constructors for FtpImpl / SecureFtpImpl using ConfigTree Key: JBESB-3824 URL: https://issues.jboss.org/browse/JBESB-3824 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Tom Cunningham -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
3
0 / 0

[JBoss JIRA] (JBESB-3813) ESB Web Service Action should support attachments

by Adam Kovari (JIRA)

Adam Kovari created JBESB-3813: ---------------------------------- Summary: ESB Web Service Action should support attachments Key: JBESB-3813 URL: https://issues.jboss.org/browse/JBESB-3813 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 Environment: JBoss Enterprise SOA Platform 5.2.0 Reporter: Adam Kovari Priority: Minor SOAP Request looking like this for example: {code}------=_Part_0_1525155906.1338820621274 Content-Type: text/xml; charset=utf-8 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><chap:getAuthors xmlns:chap="http://chapter8.samples.esb.soa.jboss.org/"/></SOAP-ENV:Body></SOAP-ENV:Envelope> ------=_Part_0_1525155906.1338820621274 Content-Type: text/plain Content-ID: helloAttachment Hello World ------=_Part_0_1525155906.1338820621274--{code} will cause following exception on JBoss SOA-P server: {code} 16:29:05,781 WARNING [PhaseInterceptorChain] Interceptor for {http://soa.jboss.org/FirstESBSample}FirstESBServiceService 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.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:185) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:179) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractHTTPServlet.java:103) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(AbstractHTTPServlet.java:159) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) 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:183) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95) 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:599) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451) at java.lang.Thread.run(Thread.java:679) 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) ... 32 more {code} If the attachments are not used, no exception is thrown and response is returned properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
10
0 / 0

[JBoss JIRA] (JBESB-3821) Camel gateway classes are not loaded by deployer after VFS cache expiration

by Robert Balent (JIRA)

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3821) Classes are not loaded by deployer after VFS cache expiration

by Robert Balent (JIRA)

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3821) Classes are not loaded by deployer after VFS cache expiration

by Robert Balent (JIRA)

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3820) Improving SOAPProxy classpath protocol logging messages

by Vinicius Martinez (JIRA)

13 years, 6 months

1
2
0 / 0

[JBoss JIRA] (JBESB-3809) SOAPClient fails to send message with <xs:any> data type

by Sato Tadayoshi (JIRA)

Sato Tadayoshi created JBESB-3809: ------------------------------------- Summary: SOAPClient fails to send message with <xs:any> data type Key: JBESB-3809 URL: https://issues.jboss.org/browse/JBESB-3809 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.10 CP1 Reporter: Sato Tadayoshi The soapUI SOAPClient cannot map a request Map to a SOAP message template using OGNL and thus fails to send it if the message is defined with <xs:any> data type in the WSDL. An example WSDL looks like this: {code:xml} ... <types> <xs:schema targetNamespace="http://www.acme.com/ws/" xmlns:tns="http://www.acme.com/ws/" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="MyRequest"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" ref="tns:myRequestDetails"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="myRequestDetails"> <xs:complexType> <xs:sequence> <xs:any namespace="##other" processContents="lax"/> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> </types> <message name="MyWebServicePort_MyRequest"> <part element="tns:MyRequest" name="MyRequest"/> </message> ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
14
0 / 0

[JBoss JIRA] (JBESB-3819) HTTP content type is not returned from pipeline with SOAPProcessor

by Rick Wagner (JIRA)

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (JBESB-3818) Add support for full Camel pipeline configuration

by Brian Blasko (JIRA)

Brian Blasko created JBESB-3818: ----------------------------------- Summary: Add support for full Camel pipeline configuration Key: JBESB-3818 URL: https://issues.jboss.org/browse/JBESB-3818 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.11 Environment: All Reporter: Brian Blasko The current Camel gateway generates the DSL as a set of froms from the configuration and a single to to the service pipeline. It would be useful to be able to use the complete Camel DSL including it's pipeline processor. To do this, I suggest an alternate configuration that simply takes a complete DSL specification either as embedded or as an external configuration file. One implementation question would be should you still automatically add the To to route to the service pipeline. The initial thread is https://community.jboss.org/message/740841 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2012