[mule-user] FtpConnector and filenameParser property
Bambitroll_
View this message in context: FtpConnector and filenameParser property
Sent from the Mule - User mailing list archive at Nabble.com.
Bambitroll_
Kynan Fraser
Hi,
Have you tried moving the parser declaration to the endpoint? eg.
<endpoint address="..." connector="FTPConnector">
<properties>
<property name="filenameParser"
value="org.mule.providers.file.SimpleFilenameParser" />
<property name="outputPattern"
value="n_${COUNT}.txt" />
</properties>
</endpoint>
Regards,
Kynan
Bambitroll_ wrote:
>
> Hello,
>
> First of all, here is my setup: Mule 1.4.3 running on Ubuntu 7.04 on JRE
> 1.6.0_03.
>
> I am experiencing a problem with the FtpConnector and more specifically
> the property called filenameParser. I am trying to get Mule to use a home
> made class to handle the filename generation (since the default options
> are not good enough for me). But when I try to set the filenameParser
> property, I get an error. So I tried with the default class, and I also
> get an error (like if Mule did not have a setter for filenameParser, which
> according to the API it has!).
> Here is how it looks in my config file:
> <connector name="tsp-ftpConnector"
> className="org.mule.providers.ftp.FtpConnector">
> <properties>
> <property name="pollingFrequency" value="5000" />
> <property name="filenameParser"
> value="org.mule.providers.file.SimpleFilenameParser" />
> <property name="outputPattern" value="n_${COUNT}.txt" />
> <property name="validateConnections" value="true" />
> </properties>
> </connector>
--
View this message in context: http://www.nabble.com/FtpConnector-and-filenameParser-property-tf4626800.html#a13224665
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
Bambitroll_
Thanks Kynan for your input!
It works better this way indeed, even if I don't quite understand why my way
of doing it does not.
Do you have any explanation why I cant' set the filenameParser property
directly when I define the connector?
So I moved on from there and tried to replace SimpleFileNameParser with my
own class.
So now my config file looks like this:
<endpoint name="MyFtp"
address="ftp://user:pwd@ftpserver/appl/test/"
connector="tsp-ftpConnector" transformers="TSPObjectToFTPFile" >
<properties>
<property name="filenameParser"
value="org.XXX.YYY.providers.ftp.MyFilenameParser" />
<property name="outputPattern" value="n_${UUID}.ctl" />
</properties>
</endpoint>
But I see that MyFilenameParser (which implements FilenameParser interface)
is never called! SimpleFilenameParser is still the one used!
Any idea why that is?
Thanks a bunch!
Kynan Fraser wrote:
>
> Hi,
>
> Have you tried moving the parser declaration to the endpoint? eg.
>
> <endpoint address="..." connector="FTPConnector">
> <properties>
> <property name="filenameParser"
>
> value="org.mule.providers.file.SimpleFilenameParser" />
> <property name="outputPattern"
> value="n_${COUNT}.txt" />
> </properties>
> </endpoint>
>
> Regards,
> Kynan
>
>
-----
BT.
--
View this message in context: http://www.nabble.com/FtpConnector-and-filenameParser-property-tf4626800.html#a13229035
Bambitroll_
I think I found out why the filenameParser property does not work...
Indeed, if you have a look here
(http://mule.mulesource.org/display/MULE/Ftp+Provider) and go the the
Property Overrides section, you will see the list of what can be overridden,
and filenameParser is not one of them.
And I guess that mule does not complain about it (like it does if I define
filenameParser in the connector tag) because somehow it simply ignores it.
And the conclusion of all this is that we still don't know why setting the
filenameParser property in the connector tag causes an error.
Could this be a bug?
BT.
-----
Rgrds,
BT.
--
View this message in context: http://www.nabble.com/FtpConnector-and-filenameParser-property-tf4626800.html#a13229301
Andrew Perepelytsya
Andrew