I guess because you included a servicemix container definition in your xbean.xml
configuration file for your SU.
It should look like:
<beans>
<ftp:pollingEndpoint service="test:poller"
endpoint="endpoint"
targetService="test:receiver"
uri="ftp://servicemix:[EMAIL PROTECTED]/smx/test" />
</beans>
if you want to deploy a single ftp polling endpoint.
On 11/13/06, mart <[EMAIL PROTECTED]> wrote:
Yeah thanks just as in the service.xml, just noticed it after posting the
message so sorry for that.
But I cannot deploy FTP component I don't understand why it tries to launch
another smx instance when putting it in my deploy directory, resulting in an
error concerning rmi binding.
INFO - AutoDeploymentService - Directory: deploy: Archive changed:
processing ftpA.zip ...
DEBUG - AutoDeploymentService - Unpacked archive
D:\TEST\sm-31\deploy\ftpA.zip to D:\TEST\sm-31\data\smx\tmp\ftpA.0.tmp
DEBUG - JMSFlow - Called Flow suspend
DEBUG - AutoDeploymentService - SA dependencies: [servicemix-ftp]
DEBUG - DeploymentService - Moving
D:\TEST\sm-31\data\smx\tmp\ftpA.0.tmp to
D:\TEST\sm-31\data\smx\service-assemblies\myNewFT
install
DEBUG - DeploymentService - Unpack service unit archive
D:\TEST\sm-31\data\smx\service-assemblies\myNewFTP\version_2\install\
:\TEST\sm-31\data\smx\service-assemblies\myNewFTP\version_2\sus\servicemix-ftp\myFTP
DEBUG - FtpComponent - Deploying service unit
DEBUG - FtpComponent - Looking for
D:\TEST\sm-31\data\smx\service-assemblies\myNewFTP\version_2\sus\servicemix-ftp\myFTP
true
INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT
JBI Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations
please see: http://incubator.apache.org/servicemix/
WARN - ManagementContext - Failed to start rmi registry:
internal error: ObjID already in use
DEBUG - ManagementContext - Failed to start rmi registry
[...]
gnodet wrote:
>
> Like this:
>
> <file:endpoint service="test:service" endpoint="endpoint"
> directory="file:target/componentOutput">
> <file:marshaler>
> <bean class="xxx">
> xxx
> </bean>
> </file:marshaler>
> </file:endpoint>
>
>
> On 11/13/06, mart <[EMAIL PROTECTED]> wrote:
>>
>> In this syntax, how would I use a custom marshaler I have written myself?
>>
>>
>> gnodet wrote:
>> >
>> > Yes, both ftp and file use the same syntax.
>> > The documentation is currently very light and it should
>> > improve before 3.1 release.
>> >
>> > On 11/10/06, mart <[EMAIL PROTECTED]> wrote:
>> >>
>> >> Hello
>> >>
>> >> how to use custom marshaler with the new FTP and File components?
>> >>
>> >> I can see this but how I map this kind of config with a custom
>> Marshaler
>> >> on
>> >> a syntax point of view? does this work also for FTP?
>> >>
>> >> <file:endpoint service="test:service" endpoint="endpoint"
>> >> directory="file:target/componentOutput">
>> >> <file:marshaler>
>> >> <sm:defaultFileMarshaler>
>> >> <sm:fileName>
>> >> <!-- lets use a header from the message -->
>> >> <sm:xpathString xpath="concat($name, '.xml')"/>
>> >> </sm:fileName>
>> >> </sm:defaultFileMarshaler>
>> >> </file:marshaler>
>> >> </file:endpoint>
>> >>
>> >> Thank you!
>> >> --
>> >> View this message in context:
>> >>
>>
http://www.nabble.com/FTP-Component-%283.1%29-and-Marshalers-tf2606860s12049.html#a7274395
>> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>>
http://www.nabble.com/FTP-Component-%283.1%29-and-Marshalers-tf2606860s12049.html#a7317060
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context:
http://www.nabble.com/FTP-Component-%283.1%29-and-Marshalers-tf2606860s12049.html#a7319190
Sent from the ServiceMix - User mailing list archive at Nabble.com.
--
Cheers,
Guillaume Nodet
