December 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1329) Collections (unbounded xs:elements) can't be first element in xs:sequence

by Per-Anders Backstrom (JIRA)

Collections (unbounded xs:elements) can't be first element in xs:sequence ------------------------------------------------------------------------- Key: JBESB-1329 URL: http://jira.jboss.com/jira/browse/JBESB-1329 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Environment: JBoss 4.2.GA Reporter: Per-Anders Backstrom Collections can't be the first element in a xs:sequence or else the OGNL-mapping will fail. I have narrowed the bug down to the org.jboss.internal.soa.esb.soap.OGNLUtils class and the getOGNLExpression() method. The bug is easily reproduced, in the soapui-client test-cases, in file orderprocessing/OrderProcessingSchema.xsd, just see to that the element name "lineItems" gets positioned first in complexType named "order". Btw, collections are asserted in OGNLUtils.java by checking for the first occurrence of a comment-string containing "1 or more repetitions" at the parent node of the actual element, but as far as I can see my collections are always commented with "Zero or more repetitions". If the first comment is rather "Optional", e.g the collection isn't first element in the parent node, this assertion would probably fail anyway? -- 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

16 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1072) JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger

by Mark Little (JIRA)

JCA code uses org.jboss.logging.Logger whereas everything else uses org.apache.log4j.Logger ------------------------------------------------------------------------------------------- Key: JBESB-1072 URL: http://jira.jboss.com/jira/browse/JBESB-1072 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor 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

16 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-1417) bpm_orchestration1 needs to be updated

by Jiri Pechanec (JIRA)

bpm_orchestration1 needs to be updated -------------------------------------- Key: JBESB-1417 URL: http://jira.jboss.com/jira/browse/JBESB-1417 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Process flow Affects Versions: 4.2.1 CP1 Reporter: Jiri Pechanec See warnings in log 2007-12-20 14:31:20,131 INFO [STDOUT] 1********** Begin Service 1 *********** 2007-12-20 14:31:20,196 INFO [STDOUT] In: Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] Out: Service 1 Start It Up 2007-12-20 14:31:20,196 INFO [STDOUT] ************ End Service 1 ************ 2007-12-20 14:31:20,406 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:20,644 INFO [STDOUT] 2********** Begin Service 2 *********** 2007-12-20 14:31:20,644 INFO [STDOUT] In: Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] Out: Service 2 Service 1 Start It Up 2007-12-20 14:31:20,645 INFO [STDOUT] ************ End Service 2 ************ 2007-12-20 14:31:20,789 INFO [org.jboss.soa.esb.services.jbpm.actionhandlers.EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead. 2007-12-20 14:31:21,020 INFO [STDOUT] 3********** Begin Service 3 *********** 2007-12-20 14:31:21,028 INFO [STDOUT] In: Service 2 Service 1 Start It Up 2007-12-20 14:31:21,028 INFO [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up 2007-12-20 14:31:21,029 INFO [STDOUT] ************ End Service 3 ************ 2007-12-20 14:31:21,184 INFO [STDOUT] Executed by the process, not by the 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

16 years, 10 months

5
8
0 / 0

[JBoss JIRA] Created: (JBESB-768) Quickstart that demos JMS custom_correlation

by Daniel Bevenius (JIRA)

Quickstart that demos JMS custom_correlation -------------------------------------------- Key: JBESB-768 URL: http://jira.jboss.com/jira/browse/JBESB-768 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Daniel Bevenius Priority: Optional Burr suggested that we add a quickstart that demos a custom correlation using jms. An example could be an application that creates a custom correlation id which it sets on the JMSMessage before posting to the ESB. It then needs to wait for a response and use a selector for that that specific correlation id. This would call for them to create a custom JMSRouter/JMSNotifier. -- 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

16 years, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-1401) Remove DeployProcessDefinition command from jBPM integration layer

by Kevin Conner (JIRA)

Remove DeployProcessDefinition command from jBPM integration layer ------------------------------------------------------------------ Key: JBESB-1401 URL: http://jira.jboss.com/jira/browse/JBESB-1401 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kurt Stam Fix For: 4.2.1 CP1 Support for the DeployProcessDefinition command is to be removed from the integration layer. This command will be replaced by the standard jBPM 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

16 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1409) webservice_consumer2 QS bugs

by Jaroslaw Kijanowski (JIRA)

webservice_consumer2 QS bugs ---------------------------- Key: JBESB-1409 URL: http://jira.jboss.com/jira/browse/JBESB-1409 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski 1. 'sendjms' ant task shouldn't be in build.xml 2. readme.txt: org.jboss.soa.esb.actions.soap.SOAPClient This class is used to make the call to the webservice. It will take the parameters that MyRequestAction set in "paramsLocation", call the webservice, then place the response in "responseLocation". This is zero Java code ESB wiring in jboss-esb.xml. This is not the case in this QS. The SOAPClient takes the WS params from the default lcoation, and puts the response also there. 2 properties would need to be added to the SOAPClient to have this behavior: <property name="get-payload-location" value="paramsLocation" /> <property name="set-payload-location" value="responseLocation" /> Also both action classes, MyRequestAction and MyResponseAction, would need to be changed to get/set the WS params from/to these locations. -- 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

16 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1334) responseXStreamConfig issue

by Jaroslaw Kijanowski (JIRA)

responseXStreamConfig issue --------------------------- Key: JBESB-1334 URL: http://jira.jboss.com/jira/browse/JBESB-1334 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Jaroslaw Kijanowski Attachments: webservice_drools_intg.tar To reproduce: download attached QS ant deploy ant runtest I have a webservice and try to consume it via SOAPClient. message.getBody().get() has following entry: <env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'><env:Header></env:Header><env:Body><ns2:getCustomerResponse xmlns:ns2="http://webservice_drools_intg/droolsws"><return><birthDate>1980</birthDate><group>0</group><license>3</license></return></ns2:getCustomerResponse></env:Body></env:Envelope> This webservice returns a POJO, so I tried to use the responseXStreamConfig property to populate a bean: <property name="responseXStreamConfig"> <alias name="return" class="org.jboss.soa.esb.samples.quickstart.webservice_drools_intg.Customer" namespace="http://webservice_drools_intg/droolsws" /> </property> Here's the output: com.thoughtworks.xstream.converters.ConversionException: return : No ClassLoaders found for: return ---- Debugging information ---- required-type : org.jboss.soa.esb.samples.quickstart.webservice_drools_intg.Customer cause-message : return : No ClassLoaders found for: return class : org.jboss.soa.esb.samples.quickstart.webservice_drools_intg.Customer message : return : No ClassLoaders found for: return line number : 1 path : /org.jboss.soa.esb.samples.quickstart.webservice_drools_intg.Customer/return cause-exception : com.thoughtworks.xstream.alias.CannotResolveClassException ------------------------------- at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:45) at com.thoughtworks.xstream.core.ReferenceByXPathUnmarshaller.convertAnother(ReferenceByXPathUnmarshaller.java:39) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:99) at com.thoughtworks.xstream.core.ReferenceByXPathMarshallingStrategy.unmarshal(ReferenceByXPathMarshallingStrategy.java:12) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:552) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:531) at org.jboss.soa.esb.actions.soap.SOAPClient.applyXStreamResponseDeserializer(SOAPClient.java:425) at org.jboss.soa.esb.actions.soap.SOAPClient.processResponse(SOAPClient.java:398) at org.jboss.soa.esb.actions.soap.SOAPClient.process(SOAPClient.java:341) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: com.thoughtworks.xstream.alias.CannotResolveClassException: return : No ClassLoaders found for: return at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:35) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.XmlFriendlyMapper.realClass(XmlFriendlyMapper.java:44) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:49) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:46) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:70) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:18) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:27) at com.thoughtworks.xstream.converters.reflection.ReflectionConverter.determineType(ReflectionConverter.java:179) at com.thoughtworks.xstream.converters.reflection.ReflectionConverter.unmarshal(ReflectionConverter.java:102) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:38) ... 13 more -- 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

16 years, 11 months

4
19
0 / 0

[JBoss JIRA] Created: (JBESB-1312) Add documentation on jBPM/JBESB

by Kurt Stam (JIRA)

Add documentation on jBPM/JBESB ------------------------------- Key: JBESB-1312 URL: http://jira.jboss.com/jira/browse/JBESB-1312 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kurt Stam Fix For: 4.2.1 CP1 We need documentation on how the integration works, best practices and limitations. -- 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

16 years, 11 months

2
7
0 / 0

[JBoss JIRA] Created: (JBESB-1418) SQLGateway duplicates

by Jiri Pechanec (JIRA)

SQLGateway duplicates ---------------------- Key: JBESB-1418 URL: http://jira.jboss.com/jira/browse/JBESB-1418 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jiri Pechanec -- 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

16 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1301) jBPM integration needs revisiting

by Mark Little (JIRA)

jBPM integration needs revisiting --------------------------------- Key: JBESB-1301 URL: http://jira.jboss.com/jira/browse/JBESB-1301 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Kurt Stam Priority: Blocker 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

16 years, 11 months

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