June 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2578) Update to smooks 1.2

by Kevin Conner (JIRA)

Update to smooks 1.2 -------------------- Key: JBESB-2578 URL: https://jira.jboss.org/jira/browse/JBESB-2578 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.5 Reporter: Kevin Conner Priority: Optional Fix For: 4.6 Optional task to upgrade to smooks 1.2 when released. -- 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

16 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-2651) Generated server no longer included samples

by Kevin Conner (JIRA)

Generated server no longer included samples ------------------------------------------- Key: JBESB-2651 URL: https://jira.jboss.org/jira/browse/JBESB-2651 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 The server created under product/build/jbossesb-server... no longer contains the samples directory. We need to identify what has changed and make sure that they are reinstated. -- 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

16 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2632) Remove smooks from ws security extractor

by Kevin Conner (JIRA)

Remove smooks from ws security extractor ---------------------------------------- Key: JBESB-2632 URL: https://jira.jboss.org/jira/browse/JBESB-2632 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The extractor uses smooks internally, creating an implicit dependency on the smooks jars. We now have jbossesb.sar depending on smooks.esb, which in turn has an indirect dependency on jbossesb.sar. This can cause problems during deployment. -- 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

16 years, 10 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-2524) RemoteGatewayListener ignores local FTP location

by George Gastaldi (JIRA)

RemoteGatewayListener ignores local FTP location ------------------------------------------------ Key: JBESB-2524 URL: https://jira.jboss.org/jira/browse/JBESB-2524 Project: JBoss ESB Issue Type: Patch Security Level: Public (Everyone can see) Affects Versions: 4.4 Reporter: George Gastaldi Priority: Trivial The class RemoteGatewayListener does an ugly checking for the temporary directory and ignores any attempt to define a local directory: This is the actual code : .. protected void checkMyParms() throws ConfigurationException, RegistryException, GatewayException { try { File temp = File.createTempFile("FTPdown", ".tmp"); temp.delete(); String localDir = temp.getParent(); if (null==localDir) localDir=new File("").getAbsolutePath(); config.setAttribute(RemoteFileSystem.PARMS_LOCAL_DIR, localDir); final String remoteDir = config.getAttribute(ListenerTagNames.FILE_INPUT_DIR_TAG) ; config.setAttribute(RemoteFileSystem.PARMS_REMOTE_DIR, remoteDir); EPR epr = ListenerUtil.assembleEpr(config); if (epr instanceof FTPEpr) { FTPEpr ftpEpr = (FTPEpr) epr; RemoteFileSystem rfs = RemoteFileSystemFactory.getRemoteFileSystem(ftpEpr, true); rfs.quit(); } else { throw new GatewayException("This Gateway only accepts FTP and SFTP."); } } catch (IOException ex) { throw new ConfigurationException(ex); } catch (RemoteFileSystemException ex) { throw new ConfigurationException(ex); } } ... The Listener should check first if a path has been defined before attempting to discover the local directory. BTW, the first lines could be replaced by System.getProperty("java.io.tmpdir"), instead of creating and deleting a file (expensive unnecessary operation). -- 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

16 years, 10 months

3
14
0 / 0

[JBoss JIRA] Created: (JBESB-2650) ConfigTree's getWholeText can throw NPE if child tree is empty

by Daniel Bevenius (JIRA)

ConfigTree's getWholeText can throw NPE if child tree is empty -------------------------------------------------------------- Key: JBESB-2650 URL: https://jira.jboss.org/jira/browse/JBESB-2650 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Reporter: Daniel Bevenius Assignee: Daniel Bevenius Priority: Minor Fix For: 4.6 Creating a ConfigTree with a child that is empty and calling getWholeText on the parent ConfigTree will cause a NPE to be thrown. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2648) RemoteGatewayListener should use System tmpdir for ftpLocalDir

by Tom Fennelly (JIRA)

RemoteGatewayListener should use System tmpdir for ftpLocalDir -------------------------------------------------------------- Key: JBESB-2648 URL: https://jira.jboss.org/jira/browse/JBESB-2648 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Tom Fennelly Assignee: Tom Fennelly Priority: Minor Fix For: 4.6 Currently, it's creating a tmpdir. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2608) Poor Exception Message "doesn't define a Message-Aware Listener"

by Kevin Conner (JIRA)

Poor Exception Message "doesn't define a Message-Aware Listener" ---------------------------------------------------------------- Key: JBESB-2608 URL: https://jira.jboss.org/jira/browse/JBESB-2608 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.4 Reporter: Burr Sutter Assignee: Kevin Conner Priority: Minor Fix For: 4.4 CP3 This message should also indicate that an InVM listener can also be used by adding invmScope="GLOBAL" to the service declaration. 12:31:43,355 WARN [ServiceController] Problem starting service jboss.esb:deploy ment=Quickstart_helloworld_http.esb java.lang.RuntimeException: org.jboss.soa.esb.ConfigurationException: Service co nfiguration for Service 'HelloWorld:HelloWorld_HTTP' doesn't define a Message-Aw are Listener (i.e. is-gateway='false'). at org.jboss.soa.esb.listeners.config.Configuration.create(Configuration .java:138) at org.jboss.soa.esb.listeners.config.JBoss4ESBDeployment.startService(J Boss4ESBDeployment.java:99) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS upport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB eanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch er.java:155) -- 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

16 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2646) Programmer guide incorrectly states inVM transport is not transactional

by Darrin Mison (JIRA)

Programmer guide incorrectly states inVM transport is not transactional ----------------------------------------------------------------------- Key: JBESB-2646 URL: https://jira.jboss.org/jira/browse/JBESB-2646 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Reporter: Darrin Mison The ESB Programmer Guide states that the inVM transport is not transactional. I assume this is a typo as the rest of the content of the Transaction Semantics section (P41) suggests that it is. -- 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

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2645) Setting required http-provider XML attribute fails the *.esb deployment

by Sindre Hamlander (JIRA)

Setting required http-provider XML attribute fails the *.esb deployment ----------------------------------------------------------------------- Key: JBESB-2645 URL: https://jira.jboss.org/jira/browse/JBESB-2645 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.4 FP1 Reporter: Sindre Hamlander "Attribute 'host' is not allowed to appear in element 'http-provider'" message appears in the server.log when trying to deploy a *.esb file that makes use of the new http-provider, done by Tom Fennelly. According to jbossesb-1.1.0.xsd the "host" attribute must be set on the "http-provider" tag in the jboss-esb.xml. Workaround: Do not try to the "host" attribute as underlying provider implementation does not require this value to be set. Although not required, you may want to remove the schemaLocation attribute from the jbossesb element in the jboss-esb.xml -- 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

16 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-2640) Provide alternative jBPM Message/Scheduler services

by Kevin Conner (JIRA)

Provide alternative jBPM Message/Scheduler services --------------------------------------------------- Key: JBESB-2640 URL: https://jira.jboss.org/jira/browse/JBESB-2640 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Fix For: 4.4 CP3 To include JMS inflow for MessageService (job, timer and command behaviour), JMS inflow for Scheduler (using JBossMessaging specific behaviour) and quartz for Scheduler. -- 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

16 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2009