October 2011 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3703) Patch around the removal of RemoteDeployer

by Tom Cunningham (Created) (JIRA)

Patch around the removal of RemoteDeployer ------------------------------------------ Key: JBESB-3703 URL: https://issues.jboss.org/browse/JBESB-3703 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.10 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 In the jbossas5 plugin, the RemoteDeployer class has been removed and has been replaced by ManagedComponentDeployer. If RemoteDeployer isn't found, try to use ManagedComponentDeployer. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] (JBESB-3702) AbstractFileGateway setFileWorking is destroying the exception information instead of showing it.

by Fabricio González (Created) (JIRA)

AbstractFileGateway setFileWorking is destroying the exception information instead of showing it. ------------------------------------------------------------------------------------------------- Key: JBESB-3702 URL: https://issues.jboss.org/browse/JBESB-3702 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.10, 4.9 Reporter: Fabricio González I was having some troubles while configuring an FTP listener and found out that the method setFileWorking in the class AbstractFileGateway is currently destroying the exception information and instead it only shows a standard message without telling us what was the original exception (Also, the message that it shows is wrong because it shows file.getAbsolutePath() and that shows a wrong path when working with FTP files, but this is not the main bug). Several classes down the path of the rename that setFileWorking is trying to do, add their custom information to the GatewayException that they throw so that developers can know what is falling. But setFileWorking is not displaying that information. I think that there should be an option to add that info if we want to see while developing, at least add a log.debug with the original exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3701) Upgrade mvel to 2.1.Beta6

by Tom Cunningham (Created) (JIRA)

Upgrade mvel to 2.1.Beta6 ------------------------- Key: JBESB-3701 URL: https://issues.jboss.org/browse/JBESB-3701 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Upgrade mvel to 2.1.Beta6 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-3647) Please document Smooks transformation with POJO input

by Tom Cunningham (JIRA)

Please document Smooks transformation with POJO input ----------------------------------------------------- Key: JBESB-3647 URL: https://issues.jboss.org/browse/JBESB-3647 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Fennelly Fix For: 4.10 CP1 The user had to rely on source code-reading to use Smooks with POJO input. This is a valid usage of Smooks and is alluded to several times in the documentation, but it is never spelled out how to accomplish it. (In particular, the beanId to use with FreeMarker is not spelled out.) Please add this information to Section 12.1.9.4 of the Programmer's Guide. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBESB-3696) Update jbpm jobexecutor configuration

by Kevin Conner (JIRA)

Update jbpm jobexecutor configuration ------------------------------------- Key: JBESB-3696 URL: https://issues.jboss.org/browse/JBESB-3696 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.10 Reporter: Kevin Conner Assignee: Tom Cunningham Priority: Minor Fix For: 4.10 CP1 The jobexecutor configuration is missing the retryInterval, causing problems should the job executor catch an exception and attempt to reschedule. Update the jbpm.job.executor bean configuration, within jbpm.esb/config/jobexecutor/jbpm.cfg.xml.config, so that it also contains the following property setting <property name="retryInterval"><int value="4000" /></property>  -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

7
8
0 / 0

[JBoss JIRA] (JBESB-3700) Upgrade jbpm to 3.2.11.SP2

by Tom Cunningham (Created) (JIRA)

Upgrade jbpm to 3.2.11.SP2 -------------------------- Key: JBESB-3700 URL: https://issues.jboss.org/browse/JBESB-3700 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Upgrade jbpm to 3.2.11.SP2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] (JBESB-3699) Add Sybase DDL to juddi-sql

by Tom Cunningham (Created) (JIRA)

Add Sybase DDL to juddi-sql --------------------------- Key: JBESB-3699 URL: https://issues.jboss.org/browse/JBESB-3699 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Add the Sybase DDL into juddi-sql. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBESB-3692) Make wise-core.properties configurable in SOAPClient action

by Shailesh Joshi (JIRA)

Make wise-core.properties configurable in SOAPClient action ----------------------------------------------------------- Key: JBESB-3692 URL: https://issues.jboss.org/browse/JBESB-3692 Project: JBoss ESB Issue Type: Enhancement Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.9 Reporter: Shailesh Joshi In WSDynamicClientFactory, the wise temporary directory is read as a property with no default value. File file = new File(wiseProperties.getProperty("wise.tmpDir"). this throws exception is the directory is not present or property file missing. Instead it would be good if we can pass these properties in SOAPClient config tree so that we can use System properties there. If config tree is missing then, we can fall back on wise-core.properties - if that is also missing use the DEFAULT properties with incremented package names (IDGenerator) for downloaded classes. similar to wise0.xml and wise1.xml etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

2
1
0 / 0

[JBoss JIRA] (JBESB-3698) BusinessRulesProcessor action needs better support for stateful CEP scenarios

by Tom Cunningham (Created) (JIRA)

BusinessRulesProcessor action needs better support for stateful CEP scenarios ----------------------------------------------------------------------------- Key: JBESB-3698 URL: https://issues.jboss.org/browse/JBESB-3698 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.10 Reporter: Tom Cunningham Fix For: 4.10 CP1 >From Kevin : It is possible to use CEP, without referencing DISPOSE/CONTINUE, by defining the "org.jboss.soa.esb.services.rules.continueState" property within jbossesb-properties.xml as "true". This will affect all references of stateful sessions as there is currently no way to specify this per action. See patch in related SOA issue (SOA-3417). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

4
3
0 / 0

[JBoss JIRA] (JBESB-3697) Remove references to base <provider>/<bus> configuration w/properties

by Tom Cunningham (Created) (JIRA)

Remove references to base <provider>/<bus> configuration w/properties --------------------------------------------------------------------- Key: JBESB-3697 URL: https://issues.jboss.org/browse/JBESB-3697 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.10 CP1 Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.10 CP1 Section 9.2 and 9.3 of the programmer's guide contain legacy configuration which references the use of base <provider/> and <bus/>. These references no longer work - they cause deployment errors. Additionally, without some of the properties defined in the <provider/> and <bus/> tags defined within the tag (and not child <property/>) you get more deployment errors. Upgrade the examples to standard quickstart <jms-provider/> / <jms-bus/> examples. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2011