June 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1946) Soapclient ognl soapenc:array support

by Joakim Sandström (JIRA)

Soapclient ognl soapenc:array support ------------------------------------- Key: JBESB-1946 URL: https://jira.jboss.org/jira/browse/JBESB-1946 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.4 Reporter: Joakim Sandström The current ognl implementation doesn't handle the following response correctly. Only the last findBySomethingReturn item is returned. i.e. <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <ns1:findBySomethingResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://mydomain"> <findBySomethingReturn soapenc:arrayType="ns2:customer[2]" xsi:type="soapenc:Array" xmlns:ns2="urn:sys" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">1</id> <name xsi:type="xsd:string">one</name> </findBySomethingReturn> <findBySomethingReturn xsi:type="ns2:customer"> <id xsi:type="xsd:int">2</id> <name xsi:type="xsd:string">two</name> </findBySomethingReturn> </findBySomethingReturn> </ns1:findBySomethingResponse> </soapenv:Body> </soapenv:Envelope> -- 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, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3347) JbpmPersistenceException in RetryExecutor with high number of due jobs

by Kevin Conner (JIRA)

JbpmPersistenceException in RetryExecutor with high number of due jobs ---------------------------------------------------------------------- Key: JBESB-3347 URL: https://jira.jboss.org/browse/JBESB-3347 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3348) JbpmPersistenceException in RetryExecutor with high number of due jobs

by Kevin Conner (JIRA)

JbpmPersistenceException in RetryExecutor with high number of due jobs ---------------------------------------------------------------------- Key: JBESB-3348 URL: https://jira.jboss.org/browse/JBESB-3348 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2556) Character corruption using SOAPClient (SOAPUI)

by Theodore S (JIRA)

Character corruption using SOAPClient (SOAPUI) ---------------------------------------------- Key: JBESB-2556 URL: https://jira.jboss.org/jira/browse/JBESB-2556 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.5 Environment: any Reporter: Theodore S When using SOAPUI using International characters can lead to character corruption. How to reproduce: Send chinese characters in the WS request to a webservice endpoint using the SOAPUI integration in JBossESB. Fix: In class org.jboss.soa.esb.actions.soap.SOAPClient change line 462: post.setRequestEntity(new StringRequestEntity(request)); to StringRequestEntity requestEntity = new StringRequestEntity(request,"text/xml","UTF-8"); post.setRequestEntity(requestEntity); -- 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, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3337) Error running webservice_proxy_security.

by Marek Baluch (JIRA)

Error running webservice_proxy_security. ---------------------------------------- Key: JBESB-3337 URL: https://jira.jboss.org/browse/JBESB-3337 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web Services Affects Versions: 4.7 CP2 Reporter: Marek Baluch When running webservice_proxy_security QS the following exception is thrown on the client side: runinternal: [java] **** REQUEST URL: https://localhost:8443/Quickstart_webservice_proxy_security/http/ProxyWS [java] **** REQUEST BODY: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hello="http://webservice_proxy_security/helloworld"><soapenv:Header/><soapenv:Body><hello:sayHello><toWhom>mbaluch</toWhom></hello:sayHello></soapenv:Body></soapenv:Envelope> [java] 14:12:09,151 DEBUG [main][header] >> "POST /Quickstart_webservice_proxy_security/http/ProxyWS HTTP/1.1[\r][\n]" [java] 14:12:09,170 DEBUG [main][header] >> "Content-Type: text/xml;charset=UTF-8[\r][\n]" [java] 14:12:09,170 DEBUG [main][header] >> "Authorization: Basic a2VybWl0OnRoZWZyb2c=[\r][\n]" [java] 14:12:09,170 DEBUG [main][header] >> "SOAPAction: ""[\r][\n]" [java] 14:12:09,170 DEBUG [main][header] >> "User-Agent: Jakarta Commons-HttpClient/3.0.1[\r][\n]" [java] 14:12:09,171 DEBUG [main][header] >> "Host: localhost:8443[\r][\n]" [java] 14:12:09,171 DEBUG [main][header] >> "Content-Length: 256[\r][\n]" [java] 14:12:09,171 DEBUG [main][header] >> "[\r][\n]" [java] 14:12:09,171 DEBUG [main][content] >> "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:hello="http://webservice_proxy_security/helloworld"><soapenv:Header/><soapenv:Body><hello:sayHello><toWhom>mbaluch</toWhom></hello:sayHello></soapenv:Body></soapenv:Envelope>" [java] Exception in thread "main" javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [java] at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174) [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1611) [java] at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:187) [java] at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:181) [java] at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1035) [java] at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:124) [java] at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:516) [java] at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:454) [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:884) [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1112) [java] at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:623) [java] at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) [java] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) [java] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) [java] at java.io.FilterOutputStream.flush(FilterOutputStream.java:123) [java] at org.apache.commons.httpclient.methods.StringRequestEntity.writeRequest(StringRequestEntity.java:150) [java] at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:495) [java] at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:1973) [java] at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:993) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:397) [java] at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396) [java] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324) [java] at org.jboss.soa.esb.samples.quickstart.webservice_proxy_security.test.SendWSMessage.main(SendWSMessage.java:89) [java] Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [java] at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285) [java] at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191) [java] at sun.security.validator.Validator.validate(Validator.java:218) [java] at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126) [java] at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209) [java] at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249) [java] at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1014) [java] ... 19 more [java] Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target [java] at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174) [java] at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238) [java] at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280) [java] ... 25 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3345) Security context should contain domain information

by Kevin Conner (JIRA)

Security context should contain domain information -------------------------------------------------- Key: JBESB-3345 URL: https://jira.jboss.org/browse/JBESB-3345 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: 4.7 CP1 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Critical The security context from an authentication request should check the domain and invalidate the information if the service is secured with a different security domain. At present the execution of a service with a different domain could result in the pipeline being executed differing credentials, one set from the first domain if the request is still valid, a second set from the second domain if it has expired. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3338) Unable to run load_generator QS.

by Marek Baluch (JIRA)

Unable to run load_generator QS. -------------------------------- Key: JBESB-3338 URL: https://jira.jboss.org/browse/JBESB-3338 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 CP2 Reporter: Marek Baluch "ant runtest" yields the following: BUILD FAILED /home/mbaluch/work/build/soa502cr1/jboss-as/samples/quickstarts/load_generator/build.xml:43: /home/mbaluch/work/build/soa502cr1/jboss-as/server/production/deploy/jbossesb.sar/lib not found. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-3339) two_servers QS build script doesn't configure the servers properly.

by Marek Baluch (JIRA)

two_servers QS build script doesn't configure the servers properly. ------------------------------------------------------------------- Key: JBESB-3339 URL: https://jira.jboss.org/browse/JBESB-3339 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Documentation, Examples Affects Versions: 4.7 CP2 Reporter: Marek Baluch Target setup-servers does not change the jboss.messaging.ServerPeerID. The target itself is not required to do this change but then the readme file should contain necessary steps to change the ID. e.g.: if AS 5.x: start the second application server (./run.sh -c second -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=20) Because of this the second server instance will not start. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-3281) EBWS: Add support for schemas that exist in jarsin

by Daniel Bevenius (JIRA)

EBWS: Add support for schemas that exist in jarsin -------------------------------------------------- Key: JBESB-3281 URL: https://jira.jboss.org/jira/browse/JBESB-3281 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Daniel Bevenius -- 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, 10 months

2
11
0 / 0

[JBoss JIRA] Created: (JBESB-3327) SOAPClient's OGNL util does not map collections properly from SOAP responses

by Magesh Kumar B (JIRA)

SOAPClient's OGNL util does not map collections properly from SOAP responses ---------------------------------------------------------------------------- Key: JBESB-3327 URL: https://jira.jboss.org/browse/JBESB-3327 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Web Services Affects Versions: 4.8 Reporter: Magesh Kumar B Assignee: Magesh Kumar B Fix For: 4.9 When SOAP responses contain collections like shown below they are not processed properly. Only the last value is retained in the resulting OGNL map. <OrderStatus> <id>1</id> <comment>order processed</comment> <returnCode>1</returnCode> <comments>Additional Comment1</comments> <comments>Additional Comment2</comments> <comments>Additional Comment3</comments> <comments>Additional Comment4</comments> </OrderStatus> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 10 months

1
9
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 2010