December 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1414) Valid JMSMessageID not parsed correctly

by Misel Lukic (JIRA)

Valid JMSMessageID not parsed correctly --------------------------------------- Key: JBESB-1414 URL: http://jira.jboss.com/jira/browse/JBESB-1414 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Misel Lukic DefaultESBPropertiesSetter throws exception according to java.net.URISyntaxException: Illegal character in opaque part at index 3: ID:<987123> at java.net.URI$Parser.fail(URI.java:2809) at java.net.URI$Parser.checkChars(URI.java:2982) at java.net.URI$Parser.parse(URI.java:3019) at java.net.URI.<init>(URI.java:578) at se.test.Test.doIt(Test.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.junit.internal.runners.TestMethodRunner.executeMethodBody(TestMethodRunner.java:99) at org.junit.internal.runners.TestMethodRunner.runUnprotected(TestMethodRunner.java:81) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestMethodRunner.runMethod(TestMethodRunner.java:75) at org.junit.internal.runners.TestMethodRunner.run(TestMethodRunner.java:45) at org.junit.internal.runners.TestClassMethodsRunner.invokeTestMethod(TestClassMethodsRunner.ja va:71) at org.junit.internal.runners.TestClassMethodsRunner.run(TestClassMethodsRunner.java:35) at org.junit.internal.runners.TestClassRunner$1.runUnprotected(TestClassRunner.java:42) at org.junit.internal.runners.BeforeAndAfterRunner.runProtected(BeforeAndAfterRunner.java:34) at org.junit.internal.runners.TestClassRunner.run(TestClassRunner.java:52) at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:38) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) if a valid JMSMessageId id passed. The spec only says the id should start with "ID:", so e.g " ID:<987123>" should be a valid id? Cheers, ml -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1413) jBPM to ESB issues with Quickstarts

by Jeff DeLong (JIRA)

jBPM to ESB issues with Quickstarts ----------------------------------- Key: JBESB-1413 URL: http://jira.jboss.com/jira/browse/JBESB-1413 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 CP1 Reporter: Jeff DeLong In bpm_orchestration4 qiuckstart he Ship It node causes an NPE on line 92 of ESBActionHandler: EPR replyTo = createReplyTo(esbToBpmVars.asXML(), globalProcessScope, executionContext); It appears this is because esbToBpmVars is null. <node name="Ship It"> <action name="esbAction" class="org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler"> <esbCategoryName>BPM_Orchestration4</esbCategoryName> <esbServiceName>ShippingService</esbServiceName> <bpmToEsbVars><mapping bpm="entireCustomerAsObject" esb="customer" /> <mapping bpm="entireOrderAsObject" esb="orderHeader" /> <mapping bpm="entireOrderAsXML" esb="entireOrderAsXML" /> </bpmToEsbVars> </action> <transition name="" to="end"></transition> Since it is probably legitimate to not specify esbToBpmVars , I suspect the code needs fixing. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1252) Message Serializer fails on attachments

by Kurt Stam (JIRA)

Message Serializer fails on attachments --------------------------------------- Key: JBESB-1252 URL: http://jira.jboss.com/jira/browse/JBESB-1252 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Kurt Stam Assigned To: Mark Little Fix For: 4.2.1 triage I got the following stack trace while running the aggregator quickstart. 10:14:52,078 WARN [MessageImpl] MessageImpl.fromXML caught unexpected exception: java.lang.NullPointerException at org.jboss.internal.soa.esb.message.format.xml.AttachmentImpl.listFromXml(AttachmentImpl.java:210) at org.jboss.internal.soa.esb.message.format.xml.AttachmentImpl.fromXML(AttachmentImpl.java:195) at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.fromXML(MessageImpl.java:209) at org.jboss.soa.esb.util.Util.deserialize(Util.java:226) at org.jboss.internal.soa.esb.couriers.helpers.JmsComposer.compose(JmsComposer.java:74) at org.jboss.internal.soa.esb.couriers.JmsCourier.pickup(JmsCourier.java:393) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:223) at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.pickup(TwoWayCourierImpl.java:205) at org.jboss.soa.esb.listeners.message.MessageAwareListener.waitForEventAndProcess(MessageAwareListener.java:269) at org.jboss.soa.esb.listeners.message.MessageAwareListener.doRun(MessageAwareListener.java:253) at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115) at java.lang.Thread.run(Thread.java:595) 10:14:52,140 ERROR [JmsComposer] Object in JMS message is not a Serializeable -- 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

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1403) Trim down set of xsd files installed into the standalone server

by Kevin Conner (JIRA)

Trim down set of xsd files installed into the standalone server --------------------------------------------------------------- Key: JBESB-1403 URL: http://jira.jboss.com/jira/browse/JBESB-1403 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1, 4.3 At present we are installing the complete contents of the xml directory but the only file that is actually used is jbossesb-1.0.1.xsd. We need to trim down the list for installation into the standalone server. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1364) Allow embedded quickstart deployments to reference any target server

by Kevin Conner (JIRA)

Allow embedded quickstart deployments to reference any target server -------------------------------------------------------------------- Key: JBESB-1364 URL: http://jira.jboss.com/jira/browse/JBESB-1364 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 CP1 The current embedded configuration allows the quickstarts to deploy into the production or default whereas within the jbossesb deployment they can target any server. We need to remove the restriction on the embedded deployment so that the QSes can target any server, while retaining the current default mechanism. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-1410) Call copy is shallow! Should have a copy constructor.

by Mark Little (JIRA)

Call copy is shallow! Should have a copy constructor. ----------------------------------------------------- Key: JBESB-1410 URL: http://jira.jboss.com/jira/browse/JBESB-1410 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 CP1 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1411) Smooks DOMVisitor that sends the Element object to an ESB Service

by Daniel Bevenius (JIRA)

Smooks DOMVisitor that sends the Element object to an ESB Service ----------------------------------------------------------------- Key: JBESB-1411 URL: http://jira.jboss.com/jira/browse/JBESB-1411 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Minor Fix For: 4.3 Add a Smooks visitor, DOMServiceDelegateVisitor, which wraps the element object in an ESB Message object and then sends the message to the configured ESB Service. This will enable an action to first transform a fragment and then send the fragment to the destination service in smaller messages and hopefully inprove throughput for large messages. As this use DOM there is still the cost of memory footprint, but when we upgrade to Smooks Version 1.0 we can add a SAXVisitor that does the same and then avoid the memory footprint. Add a quickstart that demonstrates the visitor. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1317) The jBPM must be configured by default to use JTA

by Jiri Pechanec (JIRA)

The jBPM must be configured by default to use JTA ------------------------------------------------- Key: JBESB-1317 URL: http://jira.jboss.com/jira/browse/JBESB-1317 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Process flow Affects Versions: 4.2.1 Reporter: Jiri Pechanec When using asynchronous invocation of jBPM process it needs to be executed inside JTA transaction. The jBPM thus should be configured to use JTA by default. -- 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

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-904) A number of QSes complain about message attribute not being set

by Kevin Conner (JIRA)

A number of QSes complain about message attribute not being set --------------------------------------------------------------- Key: JBESB-904 URL: http://jira.jboss.com/jira/browse/JBESB-904 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Priority: Minor Fix For: 4.2.1 This is coming from SystemPrintln, error message is "'message' attribute not set" -- 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
14
0 / 0

[JBoss JIRA] Created: (JBESB-1382) SQL Listener XSD definition assigning suspicious defaults

by Tom Fennelly (JIRA)

SQL Listener XSD definition assigning suspicious defaults --------------------------------------------------------- Key: JBESB-1382 URL: http://jira.jboss.com/jira/browse/JBESB-1382 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.2.1 CP1 It's assigning defaults to some of the column names. I'd have thought it shouldn't be defaulting these - they either exist and are configured and used... or they're not and the code should check for that and/or give an error because it allows code to continue on blindly thinking everything is cool. <xsd:attribute default="message_id" name="message-id-column" <xsd:attribute default="message" name="message-column" <xsd:attribute default="status" name="status-column" -- 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

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2007