8:03 a.m.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Adapters
Affects Versions: 4.2 Milestone Release 2
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2 Milestone Release 1
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true". This
would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
8:33 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Mark Little updated JBESB-533:
------------------------------
Fix Version/s: (was: 4.2 Milestone Release 1)
Affects Version/s: 4.0 Beta 1 Maintenance Pack 1
(was: 4.2 Milestone Release 2)
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
2:40 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Work on JBESB-533 started by Daniel Bevenius.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:34 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12361665 ]
Daniel Bevenius commented on JBESB-533:
---------------------------------------
I have added a strategy so that it is possible to specify different strategies for a
read-only ftp server (comments removed):
public interface RemoteFileSystemStrategy
{
void init( String configFile ) throws Exception;
File[] filterFileList( File[] files ) throws GatewayException;
boolean deleteFile( File file ) throws GatewayException;
boolean renameFile( File from, File to ) throws GatewayException;
File getWorkFileName( File file, String suffix );
}
The default implementation does the same as what the RemoteGatewayListener did before.
RemoteGatewayListener just delegates now.
This lets us specify different implementations in the esb configuration file.
Every time that RemoteGatewayListeners's getFileList method is called it calls the
strategies filterFileList method.
I have written an implementation (ReadOnlyRemoteFileSystemStrategy.class) that uses JBoss
Cache to cache the filenames, and replicate to other members in the current cache cluster.
This also has a cache loader configured so that the file list is persisted. The cache can
be configured so that the files are only stored in the cache for a certain amount of time
(jgroups configuration). In our case the files on the ftp server will be archived every
day.
Having such a solution will prevent the esb from working with the same file more then
once.
I think that may be others have similar situations and perhaps this is something that
should be checked in?
I have not yet changed the ftp-message-filter to have the property read-only. If read-only
is true the ReadOnlyRemoteFileSystemStrategy could be used, but this could also be
overrridden in the config file if a different impl is to be used. Should I add this
property?
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:38 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius updated JBESB-533:
----------------------------------
Attachment: ReadOnlyRemoteFileSystemStrategyTest.java
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: ReadOnlyRemoteFileSystemStrategyTest.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:40 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius updated JBESB-533:
----------------------------------
Attachment: RemoteFileSystemStrategy.java
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:40 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius updated JBESB-533:
----------------------------------
Attachment: ReadOnlyRemoteFileSystemStrategy.java
FtpFileCache.java
FtpFileCacheTest.java
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:42 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius updated JBESB-533:
----------------------------------
Attachment: ftpfile_cache_test.xml
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:48 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12361669 ]
Kevin Conner commented on JBESB-533:
------------------------------------
Hiya Daniel.
This would be a very good addition to the codebase as I am sure others will have the same
requirements as you. We should look at adding this as soon after the release as we can.
Kev
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
11:20 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12361792 ]
Daniel Bevenius commented on JBESB-533:
---------------------------------------
I have added this functionality to this workspace:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/dbevenius/
The helloworld_ftp_action quickstart has been updated and show what the configuration
looks like:
<ftp-provider name="FTPprovider" hostname="@FTP_HOSTNAME@" >
<ftp-bus busid="helloFTPChannel" >
<ftp-message-filter
username="@FTP_USERNAME@"
password="@FTP_PASSWORD@"
read-only="true"
passive="false"
directory="@FTP_DIRECTORY@"
input-suffix=".dat"
work-suffix=".esbWorking"
post-delete="false"
post-suffix=".COMPLETE"
error-delete="false"
error-suffix=".HAS_ERROR"
/>
</ftp-bus>
</ftp-provider>
So the only property that has been added is the read-only property. This is all that is
needed by default, but this configuration then expects a jboss cache configuration file
named ftpfile-cache-config.xml on the root of your classpath. This can be overridden be
specifying the file to configure like this:
<ftp-listener name="FtpGateway"
busidref="helloFTPChannel"
maxThreads="1"
is-gateway="true"
<property
name="pollLatencySeconds" value="5"/>
<!-- Example of how one can specify a different configuration file
for jboss cache -->
<property name="remoteFileSystemStrategy-configFile"
value="ftpfile_cache_test_config.xml"/>
</ftp-listener>
The value of remoteFileSystemStrategy-configFile can either be a file path on the file
system, or a path on the classpath. I implementation will look for the file on the file
system first and then look for it on the classpath.
It is also possible to specify a different implementation of the RemoteFileSystemStrategy
by using the following property:
<property name="remoteFileSystemStrategy-class"
value="some.class.that.implements.RemoteFileSystemStrategy"/>
Note that the cacheloader specified in the configuration uses hypersonics inmemory
database so if you close down all instances and restart them all files will be processes
again. But by configuring a "real" database this should not be an problem.
'ant run-readonly' will run the readonly version of the quickstart.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
10:34 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Mark Little updated JBESB-533:
------------------------------
Fix Version/s: 4.2
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
4:10 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12362419 ]
Daniel Bevenius commented on JBESB-533:
---------------------------------------
I've added the class DeleteOnEvictTreeCacheListener, which is a TreeCacheListener.
This listener will upon receiving a node evict event also remove the data from the node.
The use case for this is in our case that the files created on the ftpserver will be
archived once per day. So we could set the maxAgeSeconds (in ftpfile-cache-config.xml)
property to say two days. After two days the file names are removed from the cache.
There could also be a case when the files are archived on the ftpserver after a certain
number of files have been created. In this case one could set the maxNodes to the
appropriate amount.
Classes of interest:
DeleteOnEvictTreeCacheListener
DeleteOnEvictTreeCacheListenerTest
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
7:19 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12362431 ]
Daniel Bevenius commented on JBESB-533:
---------------------------------------
Added docs/Providers_and_ListenersGuide.odt which is a suggestion for documenting the
configuring options for providers and listeners (things like the configuration specified
above)
This will to some extends duplicate the documentation in the .xsd files but also add
information that is outside of the scope of the schema.
I'll attach this document in case anyone would like to take a look.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
ReadOnlyRemoteFileSystemStrategy.java, ReadOnlyRemoteFileSystemStrategyTest.java,
RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
7:21 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius updated JBESB-533:
----------------------------------
Attachment: Providers_and_ListenersGuide.odt
Example of docuementation for this Jira and perhaps for other providers/listeners. See
comments for more information
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
1:48 p.m.
New subject: [JBoss JIRA] Work stopped: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Work on JBESB-533 stopped by Daniel Bevenius.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
5:59 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12364006 ]
Mark Little commented on JBESB-533:
-----------------------------------
Daniel, if you're happy with this then just add it to the trunk so it's in the 4.2
release. Thanks.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
9:51 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12364020 ]
Mark Little commented on JBESB-533:
-----------------------------------
Oh and don't forget to update the manuals: this is sufficiently different from
what's already there to warrant some text about it.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
12:54 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=comments#action_12364315 ]
Daniel Bevenius commented on JBESB-533:
---------------------------------------
I'll check this in by the end of the week. I need to add a way to specify the
TreeCacheListener to be used.
I don't quite know where to put the documentation for this. Where do you think if
should put this?
Thanks,
Daniel
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
9:07 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Work on JBESB-533 started by Daniel Bevenius.
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
6:08 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Daniel Bevenius closed JBESB-533.
---------------------------------
Resolution: Done
Committed work: revision 12573
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
5:54 a.m.
New subject: [JBoss JIRA] Reopened: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Mark Little reopened JBESB-533:
-------------------------------
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2 Milestone Release 3
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
5:55 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Mark Little updated JBESB-533:
------------------------------
Fix Version/s: 4.2 Milestone Release 3
(was: 4.2)
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2 Milestone Release 3
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
5:56 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-533) FTP bus that is read-only (no rename, post-delete etc)
[ http://jira.jboss.com/jira/browse/JBESB-533?page=all ]
Mark Little closed JBESB-533.
-----------------------------
Resolution: Done
FTP bus that is read-only (no rename, post-delete etc)
------------------------------------------------------
Key: JBESB-533
URL: http://jira.jboss.com/jira/browse/JBESB-533
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Adapters
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Daniel Bevenius
Assigned To: Daniel Bevenius
Priority: Minor
Fix For: 4.2 Milestone Release 3
Attachments: ftpfile_cache_test.xml, FtpFileCache.java, FtpFileCacheTest.java,
Providers_and_ListenersGuide.odt, ReadOnlyRemoteFileSystemStrategy.java,
ReadOnlyRemoteFileSystemStrategyTest.java, RemoteFileSystemStrategy.java
I currently have a requirement to use the ftpbus to connect to an ftp server running on a
mainframe computer. The permissions that exists there are for the current file and it is
read only. This means that we cannot rename the file upon pickup and not move/delete after
processing it.
Proposed solutions:
1. Add a property to the ftp-message-filter, for example read-only="true".
This would probably make it more clear to the end user that the other properties like
post-delete, post-directory, work-suffix, post-delete, post-directory etc, are not valid
for this configuration. If the read-only value is true a subclass of RemoteGatewayListener
would be used. The current implementation sets the gatewayClass in the class
FtpListenerMapper line 80:
if(listener.getIsGateway()) {
listenerNode.setAttribute("gatewayClass",
RemoteGatewayListener.class.getName());
Is there another way to set the gatewayClass that I'm not aware of? I'll
investigate this and perhaps post a question to the design forum.
2. Add a strategy to the RemoteGatewayListener that handles delete and rename. The
default strategy would work like it does now but one would be able to specify a strategy
in the configuration to override it. The strategy to use would then be set in the
checkMyParams if the default strategy in not wanted.
I would appreciate any suggestions or comments.
I assigned this to myself only because I need to start on this as soon as possible.
--
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
6352
days inactive
6419
days old
22 comments
3 participants
participants (3)
-
Daniel Bevenius (JIRA) -
Kevin Conner (JIRA)
-
Mark Little (JIRA)