December 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1424) transform_CSV2XML quickstart does not handle multiple rows in input

by Daniel Bevenius (JIRA)

transform_CSV2XML quickstart does not handle multiple rows in input ------------------------------------------------------------------- Key: JBESB-1424 URL: http://jira.jboss.com/jira/browse/JBESB-1424 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1, 4.2.1 CP1 Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Fix For: 4.2.1 CP1, 4.3 The xslt for-each statment in incorrect and only the first entry(row) in the CSV file will be transformed into xml. Correct the smooks-res.xml -- 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-1421) helloworld_sql_action missing attributes

by Tom Cunningham (JIRA)

helloworld_sql_action missing attributes ---------------------------------------- Key: JBESB-1421 URL: http://jira.jboss.com/jira/browse/JBESB-1421 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP1 00:52:31,198 INFO [JBoss4ESBDeployer] create esb service, Quickstart_helloworld_SQL_action.esb 00:52:31,212 INFO [DatabaseInitializer] java:/QuickstartDB datasource is already initialized 00:52:31,242 ERROR [XmlValidatorImpl] 1-ERROR-null-6:cvc-complex-type.4: Attribute 'message-column' must appear on element 'sql-message-filter'. 00:52:31,243 ERROR [XmlValidatorImpl] 2-ERROR-null-6:cvc-complex-type.4: Attribute 'insert-timestamp-column' must appear on element 'sql-message-filter'. 00:52:31,245 WARN [ServiceController] Problem starting service jboss.esb:deployment=Quickstart_helloworld_SQL_action.esb java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had validation errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:132) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(JBoss4ESBDeployment.java:82) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy44.start(Unknown Source) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployer.start(JBoss4ESBDeployer.java:432) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: java.lang.IllegalStateException: ESB file had validation errors. at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration.java:126) ... 46 more 00:52:31,281 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.esb:deployment=Quickstart_helloworld_SQL_action.esb State: FAILED Reason: java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had validation errors. I Depend On: jboss.esb:deployment=jbossesb.esb --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.esb:deployment=Quickstart_helloworld_SQL_action.esb State: FAILED Reason: java.lang.RuntimeException: java.lang.IllegalStateException: ESB file had validation errors. I Depend On: jboss.esb:deployment=jbossesb.esb -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-1388) Add a retry-count for rolledback/failed SQLCourier messages

by Tom Fennelly (JIRA)

Add a retry-count for rolledback/failed SQLCourier messages ----------------------------------------------------------- Key: JBESB-1388 URL: http://jira.jboss.com/jira/browse/JBESB-1388 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Fix For: 4.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

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1387) SQLCourier: Add "backoff" capability for rolledback rows

by Tom Fennelly (JIRA)

SQLCourier: Add "backoff" capability for rolledback rows -------------------------------------------------------- Key: JBESB-1387 URL: http://jira.jboss.com/jira/browse/JBESB-1387 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 Reporter: Tom Fennelly Assigned To: Tom Fennelly 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

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1405) It is possible to store message to message store with null classification but it is not possible to remove it

by Jiri Pechanec (JIRA)

It is possible to store message to message store with null classification but it is not possible to remove it ------------------------------------------------------------------------------------------------------------- Key: JBESB-1405 URL: http://jira.jboss.com/jira/browse/JBESB-1405 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store Affects Versions: 4.2.1 Reporter: Jiri Pechanec It either should not be allowd to store unclassified messages or the delete sql statement "delete from "+tableName+" where uuid=? and classification=?" hast to be reconsidered as it does not work for null values -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-1420) HelloWorld QS config not updated when sql schema changed

by Mark Little (JIRA)

HelloWorld QS config not updated when sql schema changed -------------------------------------------------------- Key: JBESB-1420 URL: http://jira.jboss.com/jira/browse/JBESB-1420 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor 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-1407) Changing a WS needs server restart

by Jaroslaw Kijanowski (JIRA)

Changing a WS needs server restart ---------------------------------- Key: JBESB-1407 URL: http://jira.jboss.com/jira/browse/JBESB-1407 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski Assigned To: Tom Cunningham I have annotated a POJO to expose a WS ( getCustomer() ). Then I deploy it as an ESB archive and check the WSDL. Next I change the WS, let's say the method name ( to getustomer() ), change jboss-esb.xml to invoke the new command, redeploy the esb archive, check the WSDL, it's fine - new method name is shown. But when I try to use the SOAPClient to consume the WS I get: javax.management.RuntimeMBeanException at org.jboss.mx.interceptor.ReflectedDispatcher.handleInvocationExceptions(ReflectedDispatcher.java:176) . . . Caused by: java.lang.UnsupportedOperationException: Operation 'getustomer' not supported by WSDL 'http://localhost:8080/Quickstart_webservice_drools_ext_intg/MyPOJOWS?wsdl'. at org.jboss.soa.esb.services.soapui.SoapUIClientService.getOperation(SoapUIClientService.java:148) at org.jboss.soa.esb.services.soapui.SoapUIClientService.buildRequest(SoapUIClientService.java:102) I need to restart the server to be able to consume the changed WS again. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBESB-1168) Test some of the 4.2GA Quickstarts against the 4.2.1 codebase

by Tom Fennelly (JIRA)

Test some of the 4.2GA Quickstarts against the 4.2.1 codebase ------------------------------------------------------------- Key: JBESB-1168 URL: http://jira.jboss.com/jira/browse/JBESB-1168 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 -- 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
6
0 / 0

[JBoss JIRA] Created: (JBESB-1416) Deployment.txt is out of date

by Mark Little (JIRA)

Deployment.txt is out of date ----------------------------- Key: JBESB-1416 URL: http://jira.jboss.com/jira/browse/JBESB-1416 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor 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-1408) webservice_consumer1 QS bugs

by Jaroslaw Kijanowski (JIRA)

webservice_consumer1 QS bugs ---------------------------- Key: JBESB-1408 URL: http://jira.jboss.com/jira/browse/JBESB-1408 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski The webservice_consumer1 QS is broken in several places: 1. jboss-esb.xml contains an unused SOAPClient's "operation" property 2. the MyResponseAction action class awaits the message under "helloworld-response", but the SOAPClient puts the response under the default location - missing SOAPClient property: <property name="set-payload-location" value="helloworld-response" /> 3. deploy the QS and run the sendjms task: 11:43:04,824 ERROR [STDERR] [Fatal Error] :1:1: Content is not allowed in prolog. 11:43:04,825 ERROR [JmsComposer] Object in JMS message has invalid XML org.xml.sax.SAXParseException: Content is not allowed in prolog. at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:98) at org.jboss.soa.esb.util.Util.deserialize(Util.java:223) 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) Adding a gateway to the listeners would be one possible solution... -- 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
5
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