[JBoss JIRA] Created: (JBESB-1863) ConfigTree creates children with meaningless names
by Mark Little (JIRA)
ConfigTree creates children with meaningless names
--------------------------------------------------
Key: JBESB-1863
URL: http://jira.jboss.com/jira/browse/JBESB-1863
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.2.1 CP3
Reporter: Mark Little
Priority: Minor
When checking for children, ConfigTree calls getNodeName on subelements and uses the returned string as the name of the entry. This means children end up with names like "property" (non-unique) or "el" (again, not unique). I think most users will be expecting more meaningful names, such as:
<action name="simplePropertyRouter" class="SimpleDynamicRouter" >
<property name="message.property.name" value="from" />
<property name="message.property.value" value="plus">
<service.name>PlusFileService</service.name>
<service.name>service99</service.name>
</property>
</action>
A child could be "message.property.name" rather than "property".
--
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
16 years, 5 months
[JBoss JIRA] Created: (JBESB-1792) JndiReadOnlyRemoteFileSystemStrategy
by Daniel Bevenius (JIRA)
JndiReadOnlyRemoteFileSystemStrategy
-------------------------------------
Key: JBESB-1792
URL: http://jira.jboss.com/jira/browse/JBESB-1792
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Reporter: Daniel Bevenius
Fix For: 4.4
>From Forum thread:
We should be able to configure the ftp listeners to use a global cache. right now, a new TreeCache is instanciated for every listener. Maybe an option would be to have a JndiReadOnlyRemoteFileSystemStrategy class which would use a jndi name property defined at the listener level. This would require changes in the ReadOnlyRemotegatewayListener which expects a config file attribute. Maybe the whole config tree could be sent to the strategy implementation in the init method so that the strategy uses what it needs.
--
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
16 years, 5 months
[JBoss JIRA] Created: (JBESB-1793) ReadOnlyRemoteFileSystemStrategy: add support for timestamps
by Daniel Bevenius (JIRA)
ReadOnlyRemoteFileSystemStrategy: add support for timestamps
------------------------------------------------------------
Key: JBESB-1793
URL: http://jira.jboss.com/jira/browse/JBESB-1793
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 4.4
Reporter: Daniel Bevenius
Fix For: 4.4
>From Forum thread:
Since only the filename is stored in the cache, new files on ftp gateway overwriting existing ones but with the same file name wont trigger the listener. The file timestamp on the ftp server should be used when querying the cache. But this requires quite a few changes (from RemoteFileSystem.getFileListFromRemoteDir which returns an array of String to the ftp client which should use listFiles instead of listNames)
--
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
16 years, 5 months