June 2007 - esb-issues - Jboss List Archives

[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, 6 months

2
5
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, 6 months

2
3
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, 6 months

2
3
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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-627) The ActionProcessorMethodInfo does not correctly handle null responses.

by Kevin Conner (JIRA)

The ActionProcessorMethodInfo does not correctly handle null responses. ----------------------------------------------------------------------- Key: JBESB-627 URL: http://jira.jboss.com/jira/browse/JBESB-627 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The adapter should terminate if a null message is returned from one of the processor methods. -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-622) Add target server version of hibernate to quickstart exec classpath

by Kevin Conner (JIRA)

Add target server version of hibernate to quickstart exec classpath ------------------------------------------------------------------- Key: JBESB-622 URL: http://jira.jboss.com/jira/browse/JBESB-622 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The client for jbpm_simple1 receives serialised versions of hibernate classes, one of which is org.hibernate.collection.AbstractPersistentCollection. If the server version of hibernate is different to the local version then an InvalidClassException will be thrown on the client when the above class is deserialised. The server version of hibernate should be prefixed to the quickstart exec-classpath. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-625) ActionProcessingPipeline checks wrong message for replies

by Kevin Conner (JIRA)

ActionProcessingPipeline checks wrong message for replies --------------------------------------------------------- Key: JBESB-625 URL: http://jira.jboss.com/jira/browse/JBESB-625 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The ActionProcessingPipeline test for sending replies checks against the wrong message. It checks to see if the original message is non null instead of the current message. This leads to a NullPointerException if a null message is returned from the action processing pipeline. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-620) Remove scoping restriction for AS + JBoss Messaging deployments of quickstarts

by Kevin Conner (JIRA)

Remove scoping restriction for AS + JBoss Messaging deployments of quickstarts ------------------------------------------------------------------------------ Key: JBESB-620 URL: http://jira.jboss.com/jira/browse/JBESB-620 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Now that jboss messaging 1.3 can be deployed without scoping it is no longer necessary to restrict the quickstarts. -- 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, 6 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-605) MessageAwareListener may not shutdown executor

by Kevin Conner (JIRA)

MessageAwareListener may not shutdown executor ---------------------------------------------- Key: JBESB-605 URL: http://jira.jboss.com/jira/browse/JBESB-605 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The doRun method of the MessageAwareListener is not guaranteed to run if the lifecycle has been stopped prior to the execution of the thread. In this circumstance the MessageAwareListener will not have the opportunity to shutdown the executor, causing the doDestroy method to timeout while waiting for the executor to finish. The executor shutdown should be called in the doDestroy method once the lifecycle state has changed to STOPPED. -- 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, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-540) Trailblazer issues with 4.2.0 CR2

by Andr￩ Fernando (JIRA)

Trailblazer issues with 4.2.0 CR2 --------------------------------- Key: JBESB-540 URL: http://jira.jboss.com/jira/browse/JBESB-540 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Reporter: Andr￩ Fernando Assigned To: Mark Little -- 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, 6 months

4
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2007