May 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3288) JMSRouter doesn't allow sending to topics

by Kevin Conner (JIRA)

JMSRouter doesn't allow sending to topics ----------------------------------------- Key: JBESB-3288 URL: https://jira.jboss.org/jira/browse/JBESB-3288 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.8 Reporter: Chad Hahn JMSRouter was changed from 24096 to 24944 to cast a JNDI lookup from a Destination to a Queue. This causes a ClassCastException when using a Topic. http://fisheye.jboss.org/browse/JBossESB/trunk/product/rosetta/src/org/jb... -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2768) Aggregator meta data in properties

by Kevin Conner (JIRA)

Aggregator meta data in properties ---------------------------------- Key: JBESB-2768 URL: https://jira.jboss.org/jira/browse/JBESB-2768 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.4 CP3 Reporter: Kevin Conner Fix For: 4.4 CP4 The MessageMulticaster creates an aggregation id and stores this value in message properties. Normally this does not prove to be an issue but when using invm transport it may cause issues. When the message is sent to multiple services, using pass by reference semantics, then all services will see the *same* properties and may, depending on timing, see the same aggregation id. The aggregation value should really be in the message context as this section is always duplicated when creating a reference, never shared. The problem we face is that users may already be referencing the property, especially if they are creating a fresh response message, so we need to think about handling this. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3305) cache session requested acknowledge mode.

by Kevin Conner (JIRA)

cache session requested acknowledge mode. ----------------------------------------- Key: JBESB-3305 URL: https://jira.jboss.org/jira/browse/JBESB-3305 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 CP3 Reporter: Kevin Conner -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3307) scout and juddiv2 performance enhancements

by Kevin Conner (JIRA)

scout and juddiv2 performance enhancements ------------------------------------------ Key: JBESB-3307 URL: https://jira.jboss.org/jira/browse/JBESB-3307 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Priority: Blocker Fix For: 4.4 CP4 -- 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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-3306) JAXRRegistryImpl performance enhancements

by Kevin Conner (JIRA)

JAXRRegistryImpl performance enhancements ----------------------------------------- Key: JBESB-3306 URL: https://jira.jboss.org/jira/browse/JBESB-3306 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.4 CP3 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP4 -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3304) CLONE -Add better description of SOAPProxy wsdl property URI schemes

by David Ward (JIRA)

CLONE -Add better description of SOAPProxy wsdl property URI schemes -------------------------------------------------------------------- Key: JBESB-3304 URL: https://jira.jboss.org/jira/browse/JBESB-3304 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Fix For: 4.9 The documentation here: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.0/html/Programmer... lists examples for the http://, https://, file://, classpath:// and internal:// schemes, but should give detail on when you would use which scheme. The internal:// scheme is the one that could be most confusing to readers. Additionally, there is a typo on the classpath:// example. classpath://META-INF/HelloWorldWS.wsdl should instead be classpath:///META-INF/HelloWorldWS.wsdl (with 3 slashes). The "classpath://" prefix is chopped off during parsing, and 1 more slash is needed for absolute classpath resource loading, otherwise relative classpath resource loading is employed. This is NOT a bug - it was intended to work that way - but the documentation should be updated. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3303) Add better description of SOAPProxy wsdl property URI schemes

by David Ward (JIRA)

Add better description of SOAPProxy wsdl property URI schemes ------------------------------------------------------------- Key: JBESB-3303 URL: https://jira.jboss.org/jira/browse/JBESB-3303 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.8 Reporter: David Ward Assignee: David Ward Priority: Minor Fix For: 4.9 The documentation here: http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/5.0.0/html/Programmer... lists examples for the http://, https://, file://, classpath:// and internal:// schemes, but should give detail on when you would use which scheme. The internal:// scheme is the one that could be most confusing to readers. Additionally, there is a typo on the classpath:// example. classpath://META-INF/HelloWorldWS.wsdl should instead be classpath:///META-INF/HelloWorldWS.wsdl (with 3 slashes). The "classpath://" prefix is chopped off during parsing, and 1 more slash is needed for absolute classpath resource loading, otherwise relative classpath resource loading is employed. This is NOT a bug - it was intended to work that way - but the documentation should be updated. -- 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, 8 months

1
5
0 / 0

[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

15 years, 8 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

15 years, 8 months

1
14
0 / 0

[JBoss JIRA] Commented: (JBESB-3172) SOAPProxy Service with unreachable proxy URL causes server to hang

by David Ward (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-3172?page=com.atlassian.jira.plu... ] David Ward commented on JBESB-3172: ----------------------------------- Update: There has been an active forum thread here, a lot of which has to do with service deployment haning: http://community.jboss.org/thread/105869 . I will be addressing that thread as part of resolution to this issue. > SOAPProxy Service with unreachable proxy URL causes server to hang > ------------------------------------------------------------------ > > Key: JBESB-3172 > URL: https://jira.jboss.org/jira/browse/JBESB-3172 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Web Services > Affects Versions: 4.7 > Reporter: David Ward > Assignee: David Ward > Fix For: 4.9 > > Attachments: AbstractHttpMethodFactory.java.diff, GETHttpMethodFactory.java.diff, POSTHttpMethodFactory.java.diff > > > Please read the description and comments in SOA-1928. -- 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, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2010