January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1506) "Back to Console" link doesn't work in SOA

by Tom Cunningham (JIRA)

"Back to Console" link doesn't work in SOA ------------------------------------------ Key: JBESB-1506 URL: http://jira.jboss.com/jira/browse/JBESB-1506 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Tooling Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP1 The "Back to Console" link doesn't work in SOA (see SOA-341). Need an ESB side bug to commit change for this. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1499) SQLGateway adds process column

by Jiri Pechanec (JIRA)

SQLGateway adds process column ------------------------------ Key: JBESB-1499 URL: http://jira.jboss.com/jira/browse/JBESB-1499 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Rosetta Affects Versions: 4.2.1 Environment: FC7/PostgreSQL Reporter: Jiri Pechanec Assigned To: Tom Cunningham Fix For: 4.2.1 CP1 Table was created create table GATEWAY_TABLE (UNIQUE_ID integer, DATA_COLUMN varchar(255), STATUS_COL varchar(255)) body: [ objects: {org.jboss.soa.esb.message.defaultEntry={DATA_COLUMN=Bye ESB World, STATUS_COL=P, UNIQUE_ID=5, unique_id=5, status_col=P, data_column=Bye ESB World}, org.jboss.soa.esb.message.defaultEntry-set-stack=Deferred serialized value: 3fa3586c} ] The issue is probably related to upper/lower case names of columns -- 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

3
9
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-1434) Caching service invokers in EsbNotifier/EsbActionHandler can require restart of server

by Jiri Pechanec (JIRA)

Caching service invokers in EsbNotifier/EsbActionHandler can require restart of server -------------------------------------------------------------------------------------- Key: JBESB-1434 URL: http://jira.jboss.com/jira/browse/JBESB-1434 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Reporter: Jiri Pechanec Assigned To: Kurt Stam Priority: Critical Fix For: 4.2.1 CP1 If you change the trnsport definition of service and redeploy application the cached service invoker can malfunction and server restart is required. -- 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

3
13
0 / 0

[JBoss JIRA] Created: (JBESB-1490) Error running webservice_bpel quickstart

by Jehudi Castro (JIRA)

Error running webservice_bpel quickstart ---------------------------------------- Key: JBESB-1490 URL: http://jira.jboss.com/jira/browse/JBESB-1490 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Environment: JBoss SOA Platform, ESB Embedded ESB Server - Version 4.2.0.beta1 Reporter: Jehudi Castro The section for the deployment of the ActiveBPEL components is not active in the build.xml file   -- 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
4
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-1503) bpm_orchestration1 quickstart does not deploy in beta2 build

by Mark Little (JIRA)

bpm_orchestration1 quickstart does not deploy in beta2 build ------------------------------------------------------------ Key: JBESB-1503 URL: http://jira.jboss.com/jira/browse/JBESB-1503 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 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

1
5
0 / 0

[JBoss JIRA] Created: (JBESB-1502) SqlTableGatewayListener does not cope with null datasource lookup

by Mark Little (JIRA)

SqlTableGatewayListener does not cope with null datasource lookup ----------------------------------------------------------------- Key: JBESB-1502 URL: http://jira.jboss.com/jira/browse/JBESB-1502 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Adapters, Transports 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1501) ServiceInvoker only refreshes cache once per send after total failure of cache

by Mark Little (JIRA)

ServiceInvoker only refreshes cache once per send after total failure of cache ------------------------------------------------------------------------------ Key: JBESB-1501 URL: http://jira.jboss.com/jira/browse/JBESB-1501 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 We need to check to see if this instance used up all of it's attempts to deliver in a previous deliver or we'll only refresh the cache once per subsequent send because we will have exhausted the EPRs in the cache, i.e., size==0. When the SI instance is originally created we do an initial cache fetch. Until this fix, that cache fetch was not being done again after a complete failure, which meant that only 1 cache update was being done per send, as opposed to two. -- 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

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1462) Automatic cleanup of dead EPRs from registry

by Mark Little (JIRA)

Automatic cleanup of dead EPRs from registry -------------------------------------------- Key: JBESB-1462 URL: http://jira.jboss.com/jira/browse/JBESB-1462 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2.1 Reporter: Mark Little 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

18 years, 3 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008