July 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-663) Modify filters so they fire on gateways before input data is passed to couriers

by Mark Little (JIRA)

Modify filters so they fire on gateways before input data is passed to couriers ------------------------------------------------------------------------------- Key: JBESB-663 URL: http://jira.jboss.com/jira/browse/JBESB-663 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2 Milestone Release 3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-662) Expose class loading failures to caller

by Kevin Conner (JIRA)

Expose class loading failures to caller --------------------------------------- Key: JBESB-662 URL: http://jira.jboss.com/jira/browse/JBESB-662 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 2 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Milestone Release 3 Following a recent discussion on the forums we discovered that errors during classloading are being hidden from the caller. The specific incident involved deploying an esb which had been created using jdk1.6. No reasonable error message was displayed on the console (nor in the server.log) to indicate the cause of this failure. There are two locations which are responsible for this. The first location is ClassUtil as it currently treats all CNFE as equal. It should be checking to see if there is an associated exception and, if so, terminating the search at that point. The second location is ServicePublisher which is throwing a RuntimeException(!!!!) without associating the cause. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBESB-293) When performing a base listener mapping, make sure that the bus and provider are also base types.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-293?page=all ] Mark Little closed JBESB-293. ----------------------------- Fix Version/s: 4.2 Milestone Release 3 (was: 4.2) Resolution: Done > When performing a base listener mapping, make sure that the bus and provider are also base types. > ------------------------------------------------------------------------------------------------- > > Key: JBESB-293 > URL: http://jira.jboss.com/jira/browse/JBESB-293 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-293) When performing a base listener mapping, make sure that the bus and provider are also base types.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-293?page=all ] Mark Little reopened JBESB-293: ------------------------------- > When performing a base listener mapping, make sure that the bus and provider are also base types. > ------------------------------------------------------------------------------------------------- > > Key: JBESB-293 > URL: http://jira.jboss.com/jira/browse/JBESB-293 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 CR1 > Reporter: Tom Fennelly > Assigned To: Tom Fennelly > Fix For: 4.2 Milestone Release 3 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-637) Call RelatesTo serialisation is incorrect

by Kevin Conner (JIRA)

Call RelatesTo serialisation is incorrect ----------------------------------------- Key: JBESB-637 URL: http://jira.jboss.com/jira/browse/JBESB-637 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The consequence of this is a NullPointerException when the RelatesTo element is deserialised. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-636) Fault deserialisation fails

by Kevin Conner (JIRA)

Fault deserialisation fails --------------------------- Key: JBESB-636 URL: http://jira.jboss.com/jira/browse/JBESB-636 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Fault deserialisation fails with a ClassCastException -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-583) Investigate the classpath issue re StAX and inclusion of jboss-messaging-client.jar in the classpath

by Tom Fennelly (JIRA)

Investigate the classpath issue re StAX and inclusion of jboss-messaging-client.jar in the classpath ---------------------------------------------------------------------------------------------------- Key: JBESB-583 URL: http://jira.jboss.com/jira/browse/JBESB-583 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 2 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2 The SOAPClient supports using XStream to deserialize messages. In order to support namespaced messages, we have to use the StaxDriver for XStream. This means including a StAX impl in the classpath. We've included Woodstox. The StAX impl is picked up via a factory class that uses a System property. The System prop is set via services defs in the impl jar i.e. the woodstox jar set the impl via a services def. So the first problem is: When jboss-messaging-client.jar is on the classpath, the stax core is not able to find the impl via the System property. Remove jboss-messaging-client.jar from the classpath(and replace with jboss-remoting.jar) and all is fine for those tests. This however causes the following mysterious issue: The jboss-message-client.jar is removed from the classpath and replaced with jboss-remoting.jar, the JBossRemotingGatewayListener is unable to start because it can't find the "org.jboss.remoting.transport.coyote.CoyoteInvoker" (or something like that). This is totally bizarre because I've checked the classpath many times and the class is def there. It is picking up the jar because I can assert that other classes from the same jar are visible. I did a number of tests on this, all based on removing everything else from the classpath and only having the jboss-remoting.jar file. Need to get to the bottom of these classpath issues. I've gotten around it in the tests by running the unit tests twice in the build and modifying the classpath on both runs. Don't worry, I exclude and include so as we're not running the same tests twice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-624) Check action handlers for correct response processing

by Kevin Conner (JIRA)

Check action handlers for correct response processing ----------------------------------------------------- Key: JBESB-624 URL: http://jira.jboss.com/jira/browse/JBESB-624 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The StaticRouter action is incorrectly processing messages, others may be doing the same thing. The process method of the StaticRouter action forwards the message to a number of destinations but also returns a response to the originator. This response is returned by virtue of the ReplyTo settings on the incoming message. The action should be returning null so that further message processing is disabled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Closed: (JBESB-367) Spring integration example

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-367?page=all ] Mark Little closed JBESB-367. ----------------------------- Fix Version/s: 4.2 Milestone Release 3 (was: 4.2) Resolution: Done > Spring integration example > -------------------------- > > Key: JBESB-367 > URL: http://jira.jboss.com/jira/browse/JBESB-367 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: James Williams > Priority: Optional > Fix For: 4.2 Milestone Release 3 > > Time Spent: 1 day > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBESB-367) Spring integration example

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-367?page=all ] Mark Little reopened JBESB-367: ------------------------------- > Spring integration example > -------------------------- > > Key: JBESB-367 > URL: http://jira.jboss.com/jira/browse/JBESB-367 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR2 > Reporter: Mark Little > Assigned To: James Williams > Priority: Optional > Fix For: 4.2 Milestone Release 3 > > Time Spent: 1 day > Remaining Estimate: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 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 July 2007