April 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3280) character encoding problem with WSDL contracts

by Kevin Conner (JIRA)

character encoding problem with WSDL contracts ---------------------------------------------- Key: JBESB-3280 URL: https://jira.jboss.org/jira/browse/JBESB-3280 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 A user posted an issue where Russian characters are getting marred by the contract JSP application, or WSDL getting chopped by the HttpGatewayServlet. (Please refer to the JBoss Forum Reference link associated with this issue.) In the original WSDL, (ItemService.wsdl), you see Russian characters like this: <s:documentation xml:lang="RU">Öåëü:Öåëü</s:documentation> If you front the ESB service with a JBR/HTTP gateway, the characters come out like this: <s:documentation xml:lang="RU">????:????</s:documentation> And if you front the ESB service with the HTTPGatewayServlet, the entire WSDL document gets chopped: XML Parsing Error: unclosed token Location: http://localhost:8080/contract_encoding/http/Examples/ItemService?wsdl Line Number 1558, Column 11: <s:element minO ----------^ We need to handle the character encoding properly in both cases. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3279) character encoding problem with WSDL contracts

by David Ward (JIRA)

character encoding problem with WSDL contracts ---------------------------------------------- Key: JBESB-3279 URL: https://jira.jboss.org/jira/browse/JBESB-3279 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 A user posted an issue where Russian characters are getting marred by the contract JSP application, or WSDL getting chopped by the HttpGatewayServlet. (Please refer to the JBoss Forum Reference link associated with this issue.) In the original WSDL, (ItemService.wsdl), you see Russian characters like this: <s:documentation xml:lang="RU">Öåëü:Öåëü</s:documentation> If you front the ESB service with a JBR/HTTP gateway, the characters come out like this: <s:documentation xml:lang="RU">????:????</s:documentation> And if you front the ESB service with the HTTPGatewayServlet, the entire WSDL document gets chopped: XML Parsing Error: unclosed token Location: http://localhost:8080/contract_encoding/http/Examples/ItemService?wsdl Line Number 1558, Column 11: <s:element minO ----------^ We need to handle the character encoding properly in both cases. -- 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, 5 months

1
14
0 / 0

[JBoss JIRA] Created: (JBESB-3165) war-security does not work for EBWS.

by Daniel Bevenius (JIRA)

war-security does not work for EBWS. ------------------------------------ Key: JBESB-3165 URL: https://jira.jboss.org/jira/browse/JBESB-3165 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Security, Web Services Affects Versions: 4.7 Reporter: Daniel Bevenius Fix For: 4.7 CP2 In EsbWebServiceDeployer only gateways in jboss-esb.xml are considered and services configured with EBWS are not in the deploy method: webModel.setAuthDomain(esbMetaData.getModel().getAuthDomain()); webModel.setAuthMethod(esbMetaData.getModel().getAuthMethod()); ModelUtil.updateWebModel(ModelUtil.getListenerGroups(esbMetaData.getModel()), webModel); The getListenerGroups method only looks for gateways and an EBWS is not considered to be one. So there will be no security constraints for the url to the EBWS. This is just from a quick look into the code base here and I need to look into this more closely. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3299) SOAPProxy breaks when WSDL elements have special characters

by Uday (JIRA)

SOAPProxy breaks when WSDL elements have special characters ----------------------------------------------------------- Key: JBESB-3299 URL: https://jira.jboss.org/jira/browse/JBESB-3299 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.8 Reporter: Uday Assignee: David Ward Fix For: 4.9 A user posted an issue where Russian characters are getting marred by the contract JSP application, or WSDL getting chopped by the HttpGatewayServlet. (Please refer to the JBoss Forum Reference link associated with this issue.) In the original WSDL, (ItemService.wsdl), you see Russian characters like this: <s:documentation xml:lang="RU">Öåëü:Öåëü</s:documentation> If you front the ESB service with a JBR/HTTP gateway, the characters come out like this: <s:documentation xml:lang="RU">????:????</s:documentation> And if you front the ESB service with the HTTPGatewayServlet, the entire WSDL document gets chopped: XML Parsing Error: unclosed token Location: http://localhost:8080/contract_encoding/http/Examples/ItemService?wsdl Line Number 1558, Column 11: <s:element minO ----------^ We need to handle the character encoding properly in both cases. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-3282) sql-listener not working correctly with transacted="true"

by Kevin Conner (JIRA)

sql-listener not working correctly with transacted="true" --------------------------------------------------------- Key: JBESB-3282 URL: https://jira.jboss.org/jira/browse/JBESB-3282 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3290) Schema validation: DocumentBuilder can be reused between messages

by Kevin Conner (JIRA)

Schema validation: DocumentBuilder can be reused between messages ----------------------------------------------------------------- Key: JBESB-3290 URL: https://jira.jboss.org/jira/browse/JBESB-3290 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 CP1 Reporter: Kevin Conner Priority: Minor 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3181) ESB plugin needs to be renamed

by Jaroslaw Kijanowski (JIRA)

ESB plugin needs to be renamed ------------------------------ Key: JBESB-3181 URL: https://jira.jboss.org/jira/browse/JBESB-3181 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Jaroslaw Kijanowski -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-3284) EsbDeployment stop/start mbean functions do not restart listeners

by Kevin Conner (JIRA)

EsbDeployment stop/start mbean functions do not restart listeners ----------------------------------------------------------------- Key: JBESB-3284 URL: https://jira.jboss.org/jira/browse/JBESB-3284 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.7 CP1 Reporter: 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3265) JmsConnectionPool performs JNDI lookup for connection factory every time it obtains a session

by Kevin Conner (JIRA)

JmsConnectionPool performs JNDI lookup for connection factory every time it obtains a session --------------------------------------------------------------------------------------------- Key: JBESB-3265 URL: https://jira.jboss.org/jira/browse/JBESB-3265 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Tom Fennelly Fix For: 4.8 -- 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, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBESB-3263) JmsConnectionPool searches for associated JmsSessionPool by sequentially iterating over JmsSessions

by Kevin Conner (JIRA)

JmsConnectionPool searches for associated JmsSessionPool by sequentially iterating over JmsSessions --------------------------------------------------------------------------------------------------- Key: JBESB-3263 URL: https://jira.jboss.org/jira/browse/JBESB-3263 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.8 -- 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, 6 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 April 2010