You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Aleksey Sushko (JIRA)" <ji...@apache.org> on 2011/04/07 23:18:06 UTC

[jira] [Created] (CAMEL-3845) New FTP component working with PROXY

New FTP component working with PROXY
------------------------------------

                 Key: CAMEL-3845
                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
             Project: Camel
          Issue Type: Improvement
          Components: camel-ftp
    Affects Versions: 2.7.0
            Reporter: Aleksey Sushko


FTP the component works well. He isn't able to go through proxy server.
Library FTP4J is able to go through different proxy servers.
Squid Server is used FTP over HTTP proxy.

I have developed component FTP of the client constructed on library FTP4J. 
FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
Has added storage of the last FTPReply.
Has added transfer of parameters connectTimeout and soTimeout.
Libraries FTP4J aren't present in central maven repository. The library no OSGi.

In camel the component has added parameter "proxy". 
It is a line url authorizations for proxy server. 
If the scheme http is specified, we put HTTPTunnelConnector. 
If the scheme ftp is specified, we put FTPProxyConnector. 
If the scheme socks5 is specified, we put SOCKS5Connector. 
If the scheme socks or socks4 is specified, we put SOCKS4Connector. 

If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 

Route example

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
  xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  default-activation="lazy">

  <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
    <cm:default-properties>
      <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
      <cm:property name="ftp.delay" value="100000"/>
      <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
    </cm:default-properties>
  </cm:property-placeholder>
    
  
  <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
    <route>
      <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
      <to uri="file://data/dict/inbox"/>
      <to uri="mock:log"/>
    </route>
  </camelContext>

</blueprint>



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-3845) New FTP component working with PROXY

Posted by "Richard Kettelerij (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018098#comment-13018098 ] 

Richard Kettelerij commented on CAMEL-3845:
-------------------------------------------

Note that FTP4J is LGPL licensed, so it should be hosted at Camel Extras.

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>             Fix For: Future
>
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-3845) New FTP component working with PROXY

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-3845:
-------------------------------

    Fix Version/s: Future
       Issue Type: New Feature  (was: Improvement)

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>             Fix For: Future
>
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CAMEL-3845) New FTP component working with PROXY

Posted by "Aleksey Sushko (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Sushko updated CAMEL-3845:
----------------------------------

    Attachment: camel-ftp4j.tar.gz

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (CAMEL-3845) New FTP component working with PROXY

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen closed CAMEL-3845.
------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: Future)
                   2.8.0
         Assignee: Claus Ibsen

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-3845) New FTP component working with PROXY

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018090#comment-13018090 ] 

Claus Ibsen commented on CAMEL-3845:
------------------------------------

When you attach files, you need to set a X in [x] for Grant license to Apache Software Foundation. If you do *not* do that we cannot use any patches from you.

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>             Fix For: Future
>
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CAMEL-3845) New FTP component working with PROXY

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CAMEL-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018237#comment-13018237 ] 

Claus Ibsen commented on CAMEL-3845:
------------------------------------

I would prefer we work with the existing FTP components and enhance those if they have issues.

The Camel ftp components is advanced and have many features and is re-using logic from camel-core (file component) so its frankly usually a lot of work to add a new FTP component.

People in the community is welcome to work on 3rd party components, but we have to pass on this contribution. 

> New FTP component working with PROXY
> ------------------------------------
>
>                 Key: CAMEL-3845
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3845
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-ftp
>    Affects Versions: 2.7.0
>            Reporter: Aleksey Sushko
>             Fix For: Future
>
>         Attachments: camel-ftp4j.tar.gz
>
>
> FTP the component works well. He isn't able to go through proxy server.
> Library FTP4J is able to go through different proxy servers.
> Squid Server is used FTP over HTTP proxy.
> I have developed component FTP of the client constructed on library FTP4J. 
> FTP4J Version 1.6 - 2011/01/07.  http://www.sauronsoftware.it/projects/ftp4j/ 
> Has added storage of the last FTPReply.
> Has added transfer of parameters connectTimeout and soTimeout.
> Libraries FTP4J aren't present in central maven repository. The library no OSGi.
> In camel the component has added parameter "proxy". 
> It is a line url authorizations for proxy server. 
> If the scheme http is specified, we put HTTPTunnelConnector. 
> If the scheme ftp is specified, we put FTPProxyConnector. 
> If the scheme socks5 is specified, we put SOCKS5Connector. 
> If the scheme socks or socks4 is specified, we put SOCKS4Connector. 
> If the parameter "proxy" isn't specified, there is a direct connection to FTP server. 
> Route example
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
>   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0"
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>   default-activation="lazy">
>   <cm:property-placeholder persistent-id="com.mycompany.route.bundle">
>     <cm:default-properties>
>       <cm:property name="ftp.url" value="ftp4j://ftp.mycompany.com/"/>
>       <cm:property name="ftp.delay" value="100000"/>
>       <cm:property name="ftp.proxy" value="&proxy=http://user:pwd@cache.mycompany.lan:3128/"/>
>     </cm:default-properties>
>   </cm:property-placeholder>
>     
>   
>   <camelContext xmlns="http://camel.apache.org/schema/blueprint">      
>     <route>
>       <from uri="{{ftp.url}}?delay={{ftp.delay}}&amp;noop=true&amp;binary=true{{ftp.proxy}}"/>
>       <to uri="file://data/dict/inbox"/>
>       <to uri="mock:log"/>
>     </route>
>   </camelContext>
> </blueprint>

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira