Agree.
I think that, like for application servers, the project should provide a
karaf feature and maintain it.
It's the case of ServiceMix for instance.
Regards
JB
On 09/13/2010 06:24 PM, David Jencks wrote:
Perhaps we could encourage these other projects to maintain or at least host
the feature for their own project?
thanks
david jencks
On Sep 13, 2010, at 8:33 AM, Guillaume Nodet wrote:
Yeah, we could also provide features for James (smtp server),
directory (ldap), Open IM (jabber) etc...
I'm not 100% sure where to draw the line though ....
Maybe using a different feature repository would make things less tied
together ...
On Mon, Sep 13, 2010 at 17:24, Charles Moulliard<[email protected]> wrote:
Remark :
As we don't have any FTP server in camel like we have with Jetty for
camel-http, this project could be used for that purpose or to provide
a simple FTP server
On Mon, Sep 13, 2010 at 5:21 PM, Jean-Baptiste Onofré<[email protected]> wrote:
Hi Charles,
It's interesting. It's quite the same think that is provided by
servicemix-ftp component (used in an OSGi way).
Regards
JB
On 09/13/2010 05:17 PM, Charles Moulliard wrote:
Hi,
I would liketo suggest that we add in the feature file of SMX 4.x or
Karaf 2.x a new interesting feature --> Apache FTP Server
The project requires that we use the two following bundles :
osgi:install -s mvn:org.apache.ftpserver/ftplet-api/1.0-SNAPSHOT
osgi:install -s mvn:org.apache.ftpserver/ftplet-api/1.0-SNAPSHOT
and we add a config file spring-dm or blueprint like this one
<beans xmlns="http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:osgi="http://www.springframework.org/schema/osgi";
xmlns:ftp="http://mina.apache.org/ftpserver/spring/v1";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://mina.apache.org/ftpserver/spring/v1
http://mina.apache.org/ftpserver/ftpserver-1.0.xsd
">
<ftp:server id="server">
<ftp:listeners>
<ftp:nio-listener name="default" port="2222" />
</ftp:listeners>
<!--
<ftp:ftplets>
<ftp:ftplet name="ftplet1">
<ref bean="ftplet" />
</ftp:ftplet>
</ftp:ftplets>
-->
<ftp:file-user-manager
url="org/apache/ftpserver/example/osgiservice/users.properties" />
</ftp:server>
<osgi:service interface="org.apache.ftpserver.FtpServer"
ref="server">
</osgi:service>
<!--<osgi:reference id="ftplet"
interface="org.apache.ftpserver.ftplet.Ftplet" /> -->
<!-- Starts and stops the bean as the context is started and
stopped -->
<bean
class="org.apache.ftpserver.example.osgiservice.impl.FtpServerLifecycle"
init-method="init" destroy-method="destroy"
>
<property name="server" ref="server" />
</bean>
</beans>
Other options are available
What do you think about that ?
Regards,
Charles Moulliard
Senior Enterprise Architect (J2EE, .NET, SOA)
Apache Camel - Karaf - ServiceMix Committer
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Blog : http://cmoulliard.blogspot.com | Twitter :
http://twitter.com/cmoulliard
Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
