January 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2972) ESB deployments don't see classes in the lib dir of the.esb archive

by Aaron Pestel (JIRA)

ESB deployments don't see classes in the lib dir of the.esb archive ------------------------------------------------------------------- Key: JBESB-2972 URL: https://jira.jboss.org/jira/browse/JBESB-2972 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Aaron Pestel It appears that the default folder in .esb archives for picking up dependent jars has changed from "lib" to "jars". This is does not map to the default JBDS ESB project which creates a "lib" directory and will break existing deployments of .esb files that have jars in the /lib directory of the .esb archive. This was created as a result of: https://jira.jboss.org/jira/browse/SOA-1588 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBESB-3129) File name to be referenced in Messages created by FTP and FILE listeners

by Edward Pilipczuk (JIRA)

File name to be referenced in Messages created by FTP and FILE listeners ------------------------------------------------------------------------ Key: JBESB-3129 URL: https://jira.jboss.org/jira/browse/JBESB-3129 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Adapters Affects Versions: 4.7 Environment: ESB4.7+JBossAS5.1 Reporter: Edward Pilipczuk Please consider providing the possibility of adding the reference to file processed by the FTP and FILE Gateway Listeners. The reference name can be added to Header->Call->RelatesTo field similarly how JMS Listeners passes JMS Correlation ID to the message. I think that above listeners shall have additional configuration parameter named passFileNameReference, which can have the following values: NONE (default for backward compatibility) SIMPLE (the simple name without path is passed to RelatesTo field) FULL (the fully qualified pathname to file is passed to RelatesTo field) Edward -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3127) JON plugin version not updated in xml config

by Kevin Conner (JIRA)

JON plugin version not updated in xml config -------------------------------------------- Key: JBESB-3127 URL: https://jira.jboss.org/jira/browse/JBESB-3127 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 The plugin version is not updated by the build process, it is currently set to 2.0. This should be updated automatically. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3126) Deploying through admin console not possible

by Kevin Conner (JIRA)

Deploying through admin console not possible -------------------------------------------- Key: JBESB-3126 URL: https://jira.jboss.org/jira/browse/JBESB-3126 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP1 My bad, will fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3124) Typo in example data/Smooks config in transform_XML2POJO2 example

by Jiri Pechanec (JIRA)

Typo in example data/Smooks config in transform_XML2POJO2 example ----------------------------------------------------------------- Key: JBESB-3124 URL: https://jira.jboss.org/jira/browse/JBESB-3124 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Jiri Pechanec Priority: Minor SamplePetsOrder.xml file contains username="j2ee" but in transforms/from-petstore.xml there is <jb:value property="userName" data="order/@userName" />. Not the difference in lower/uppercase N in username attribute name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3123) Incosistent use of message profile property in transform_XML2POJO2

by Jiri Pechanec (JIRA)

Incosistent use of message profile property in transform_XML2POJO2 ------------------------------------------------------------------ Key: JBESB-3123 URL: https://jira.jboss.org/jira/browse/JBESB-3123 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Jiri Pechanec Priority: Minor In scripts/check-origin.groovy the code sets Properties.MESSAGE_PROFILE property on message but reads property 'from'. The values are in fact different. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-3121) milyn-scribe-core missing

by Kevin Conner (JIRA)

milyn-scribe-core missing ------------------------- Key: JBESB-3121 URL: https://jira.jboss.org/jira/browse/JBESB-3121 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-3120) Description displays "--" when the description in jboss-esb.xml is empty.

by Kevin Conner (JIRA)

Description displays "--" when the description in jboss-esb.xml is empty. ------------------------------------------------------------------------- Key: JBESB-3120 URL: https://jira.jboss.org/jira/browse/JBESB-3120 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3099) spring_jpetstore quickstart sample - missing run scripts in hsqldb directory

by Kevin Conner (JIRA)

spring_jpetstore quickstart sample - missing run scripts in hsqldb directory ---------------------------------------------------------------------------- Key: JBESB-3099 URL: https://jira.jboss.org/jira/browse/JBESB-3099 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.7 Reporter: Kevin Conner Fix For: 4.7 CP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
13
0 / 0

[JBoss JIRA] Created: (JBESB-3117) Merge JBESB-3083: Wise SOAPClient action is unable to invoke oneway methods on the endpoints

by Tom Fennelly (JIRA)

Merge JBESB-3083: Wise SOAPClient action is unable to invoke oneway methods on the endpoints -------------------------------------------------------------------------------------------- Key: JBESB-3117 URL: https://jira.jboss.org/jira/browse/JBESB-3117 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Critical Fix For: 4.7 CP1 Wise SOAPClient action is unable to invoke oneway methods (methods annotated with javax.jws.Oneway annotation) on WS endpoints. It looks like webservice WSDL is parsed correctly, but after that no statements from oneway method body are executed. We tested this with very simple webservice (see attached file) containing one oneway method with System.out.println() statement. After WSDL was parsed, there was no further output from webservice method. Invocation of twoway methods on WS endpoint is working correctly (without any problems/exceptions and with expected results). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2010