You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Brian Fitzgerald (Created) (JIRA)" <ji...@apache.org> on 2012/01/16 06:47:40 UTC
[jira] [Created] (AMQ-3661) Managed File Transfer over ActiveMQ
Managed File Transfer over ActiveMQ
-----------------------------------
Key: AMQ-3661
URL: https://issues.apache.org/jira/browse/AMQ-3661
Project: ActiveMQ
Issue Type: New Feature
Components: Broker, Connector
Affects Versions: NEEDS_REVIEWED
Reporter: Brian Fitzgerald
Priority: Minor
Many existing Websphere MQ users utilise it as a transport layer for a managed file transfer product - like WMQ V7 or PM4Data or enDI. These products provide a scheduled, polling, or XML driven, transfer of a file by splitting it into messages and then re-assembling on the target machine - with append/overwrite/ack capabilities etc. Extending the capabilities of AMQ to include something similar would make it even more attractive. Could possibly leverage the camel context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3661) Managed File Transfer over ActiveMQ
Posted by "Timothy Bish (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187292#comment-13187292 ]
Timothy Bish commented on AMQ-3661:
-----------------------------------
ActiveMQ provides BlobMessage for large file transfers. Otherwise this seems like something better suited to a Camel component and not built directly into the broker.
> Managed File Transfer over ActiveMQ
> -----------------------------------
>
> Key: AMQ-3661
> URL: https://issues.apache.org/jira/browse/AMQ-3661
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, Connector
> Affects Versions: NEEDS_REVIEWED
> Reporter: Brian Fitzgerald
> Priority: Minor
> Labels: activemq
>
> Many existing Websphere MQ users utilise it as a transport layer for a managed file transfer product - like WMQ V7 or PM4Data or enDI. These products provide a scheduled, polling, or XML driven, transfer of a file by splitting it into messages and then re-assembling on the target machine - with append/overwrite/ack capabilities etc. Extending the capabilities of AMQ to include something similar would make it even more attractive. Could possibly leverage the camel context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3661) Managed File Transfer over ActiveMQ
Posted by "Rob Davies (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-3661.
-----------------------------
Resolution: Won't Fix
Assignee: Rob Davies
Apache Camel provides all the features for scheduling, file splitting and re-assembly of messages.
> Managed File Transfer over ActiveMQ
> -----------------------------------
>
> Key: AMQ-3661
> URL: https://issues.apache.org/jira/browse/AMQ-3661
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, Connector
> Affects Versions: NEEDS_REVIEWED
> Reporter: Brian Fitzgerald
> Assignee: Rob Davies
> Priority: Minor
> Labels: activemq
>
> Many existing Websphere MQ users utilise it as a transport layer for a managed file transfer product - like WMQ V7 or PM4Data or enDI. These products provide a scheduled, polling, or XML driven, transfer of a file by splitting it into messages and then re-assembling on the target machine - with append/overwrite/ack capabilities etc. Extending the capabilities of AMQ to include something similar would make it even more attractive. Could possibly leverage the camel context.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira