November 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-454) Allow no inputSuffix on the FileGateway

by Kurt Stam (JIRA)

Allow no inputSuffix on the FileGateway --------------------------------------- Key: JBESB-454 URL: http://jira.jboss.com/jira/browse/JBESB-454 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Environment: any Reporter: Kurt Stam Assigned To: Mark Little Make the suffix on input Files optional so that it simply picks up all the files in the directory. Check to see that in this case the output directory is not the same as the input directory. -- 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

18 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBESB-1344) Not all gateways are using ServiceInvoker

by Jiri Pechanec (JIRA)

Not all gateways are using ServiceInvoker ----------------------------------------- Key: JBESB-1344 URL: http://jira.jboss.com/jira/browse/JBESB-1344 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Reporter: Jiri Pechanec Priority: Critical Few gateways do not use Service Invoker. It means that they do not provide load balancing facility right now. This needs to be documented and fixed later. The guilty gateways are JmsGatewayListener.java HibernateInterceptor.java SqlTableGatewayListener.java -- 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

18 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-1110) Need a two-servers-on-one-machine quickstart

by Tom Cunningham (JIRA)

Need a two-servers-on-one-machine quickstart -------------------------------------------- Key: JBESB-1110 URL: http://jira.jboss.com/jira/browse/JBESB-1110 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Reporter: Tom Cunningham Assigned To: Tom Cunningham We need a quickstart that involves sending messages from one ESB on a single machine to another. Such a quickstart would demonstrate the servicebindings capabilities and other issues with running multiple ESB's on the same machine. -- 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

18 years, 1 month

3
6
0 / 0

[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

18 years, 1 month

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

18 years, 1 month

3
6
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

18 years, 2 months

2
5
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

18 years, 3 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

18 years, 3 months

2
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

18 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1154) Integrate remaining QSes into the Ci system

by Kevin Conner (JIRA)

Integrate remaining QSes into the Ci system ------------------------------------------- Key: JBESB-1154 URL: http://jira.jboss.com/jira/browse/JBESB-1154 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 IR1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2.1 Some of the QSes are now integrated into the CI system. We need to look at the remaining ones and integrate those as well. -- 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

18 years, 3 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues November 2007