January 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1518) Removing the deployProcess command broke the QSs bpm_orchestration* tests

by Kurt Stam (JIRA)

Removing the deployProcess command broke the QSs bpm_orchestration* tests ------------------------------------------------------------------------- Key: JBESB-1518 URL: http://jira.jboss.com/jira/browse/JBESB-1518 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kurt Stam Assigned To: Kurt Stam 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-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

18 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-1517) Minor doc updates in CBR, MessageTransformation and Registry

by Mark Little (JIRA)

Minor doc updates in CBR, MessageTransformation and Registry ------------------------------------------------------------ Key: JBESB-1517 URL: http://jira.jboss.com/jira/browse/JBESB-1517 Project: JBoss ESB Issue Type: Bug 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 >From our intern. -- 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-1515) ESB does not close ResultSets in all situations

by Mark Little (JIRA)

ESB does not close ResultSets in all situations ----------------------------------------------- Key: JBESB-1515 URL: http://jira.jboss.com/jira/browse/JBESB-1515 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Rosetta, Transports Affects Versions: 4.2.1 Reporter: Mark Little Fix For: 4.2.1 CP1 Should always close ResultSets as soon as they are done with, even if the corresponding Statement is closed later which would implicitly close: to free up memory asasp. However, the ESB also did not catch some errors during processing which would mean that Statements and ResultSets did not get closed at all. -- 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-1512) Need a way of determining jbpmTokenId

by Tom Cunningham (JIRA)

Need a way of determining jbpmTokenId ------------------------------------- Key: JBESB-1512 URL: http://jira.jboss.com/jira/browse/JBESB-1512 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Reporter: Tom Cunningham Fix For: 4.2.1 CP1 Talked to Kurt about this one - the jbpmTokenId is required to signal a process, but it is hard to get. Currently, the only way to determine the jbpmTokenId is to use the jbpmConsole. Two options for improving this would be : 1. Have jBPM call back into a service so we can obtain the id that way or 2. Have the jBPM deploy command return the ID -- 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
2
0 / 0

[JBoss JIRA] Created: (JBESB-1505) bpm_orchestration2 documentation does not correspond to actual results

by Jiri Pechanec (JIRA)

bpm_orchestration2 documentation does not correspond to actual results ---------------------------------------------------------------------- Key: JBESB-1505 URL: http://jira.jboss.com/jira/browse/JBESB-1505 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Jiri Pechanec Assigned To: Kevin Conner Fix For: 4.2.1 CP1 Under old jbPM implementation even the paralel paths were executed one by one which means that the results were gathered to the message. Now the paths are executed in paralel which means that 1) Each path contains only name of its own city 2) The final resul cvonains only the name of city (path) executed as the last one The documentation should be changed and/or QS should be changed in that way that each patch records its results under separate key in the message. -- 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
4
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

18 years, 3 months

3
8
0 / 0

[JBoss JIRA] Created: (JBESB-1509) ESB mediated WSDLs have no xml preamble, which may cause issues for some clients

by Tom Fennelly (JIRA)

ESB mediated WSDLs have no xml preamble, which may cause issues for some clients -------------------------------------------------------------------------------- Key: JBESB-1509 URL: http://jira.jboss.com/jira/browse/JBESB-1509 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.2.1 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.2.1 CP1 Quote from Jeff Delong... "I finally had time to figure this out. The WSDL that is generated and accessible via the Contract web app is missing the ?xml tag at the beginning of the document: <?xml version="1.0" encoding="UTF-8"?> meaning it could not be read by a tool such as SoapUI. Once I saved the WSDL to a file and added the ?xml tag it could be read, and the service consumed, but SoapUI. It does invoke the web service correctly, through the jboss remoting http port, and proper ESB actions are invoked." I couldn't reproduce this error in my env, but we should add the preamble 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, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1510) Improvements to webservice_bpel quickstart Readme.txt

by Tom Fennelly (JIRA)

Improvements to webservice_bpel quickstart Readme.txt ----------------------------------------------------- Key: JBESB-1510 URL: http://jira.jboss.com/jira/browse/JBESB-1510 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples, Web Services 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

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1432) Error running bpm_orchestration3

by Jehudi Castro (JIRA)

Error running bpm_orchestration3 -------------------------------- Key: JBESB-1432 URL: http://jira.jboss.com/jira/browse/JBESB-1432 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBoss SOA Platform™ ESB Embedded ESB Server - Version 4.2.0.beta1 Reporter: Jehudi Castro Running this step of the quickstart: 3. In Window1, type 'ant startProcess -Dtoken=Demo1' I get "jbpmTokenId: null" This id is needed in order to continue with the quickstart. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2008