2.0 FileConnector question

[Steve Olson]

I had a file connextor based flow that worked fine in RC2, although FileConnector itself had a couple bugs related to how it was doing archiving when moveTo is in use, as I was doing.  I saw that those were fixed in RC3 and 2.0.0 gold, so tested my flow on those using the 2.0.0 release code.  The unchanged flow configuration runs under 2.0.0, but when it sees a file, is now throwing the same exception that is in Mule-3055.  Mule-3055 shows it's fixed in RC3 but only applies to an example, so I'm unsure if it is the exact same issue or something similar.

I'm gonna start digging into the cause of this, but if anyone is already familiar with whatever was in 3055, I'd appreciate any tips/info.  Here's my sample config snippits that worked fine in 2.0RC2 but break in 2.0.0 (I've changed some names to generic names and doen other editing). The component class below is expecting a String and has a method that the 2.0RC2 entry point resolver found just fine. But on 2.0.0 code it's almost like my file to string transformer isn't happening or something.

<file:file-to-string-transformer name="FileToString"/>
<file:connector name="fileconn1" autoDelete="false"
createMultipleTransactedReceivers="false"
fileAge="5000" moveToDirectory="${mypath}/Archive"
pollingFrequency="10000" >
        <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
        </custom-exception-strategy>
</file:connector>

<model name="Flow1">
<service name="service1">
    <inbound><inbound-endpoint address="file://${mypath}"
        transformer-refs="FileToString"
    connector-ref="fileconn1">
    </inbound-endpoint>
    </inbound>
    <component>
    <spring-object bean="controller1">
        </spring-object>
    </component>
    <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
    </custom-exception-strategy>
</service>
</model>

Thanks in advance for any help!

[Dirk Olmes]

Steve Olson wrote:

> I had a file connextor based flow that worked fine in RC2, although
> FileConnector itself had a couple bugs related to how it was doing archiving
> when moveTo is in use, as I was doing.  I saw that those were fixed in RC3
> and 2.0.0 gold, so tested my flow on those using the 2.0.0 release code.
> The unchanged flow configuration runs under 2.0.0, but when it sees a file,
> is now throwing the same exception that is in Mule-3055.  Mule-3055 shows
> it's fixed in RC3 but only applies to an example, so I'm unsure if it is the
> exact same issue or something
>
> I'm gonna start digging into the cause of this, but if anyone is already
> familiar with whatever was in 3055, I'd appreciate any tips/info.

IIRC that had something to do with the internal handling of
transformers. Dan should know ...

-dirk

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Daniel Feist]

Hi,

As you may have noticed streaming is now used by default for the file  
transport in 2.0.  There were some issued related to this  move/delete  
implementation which were fixed.

The bug reported in MULE-3055 was due to a transformer which with the  
new streaming default was no longer being run due to not have an  
InputStream as supported source type.

We created http://mule.mulesource.org/jira/browse/MULE-3065 to review  
all transformers and ensure this wasn't a problem elsewhere, but it  
seems the FileToString transformer must have slipped through, sorry...

I'll reopen the issue.

Dan

On 10 Apr 2008, at 11:55, Steve Olson wrote:

>
> I had a file connextor based flow that worked fine in RC2, although
> FileConnector itself had a couple bugs related to how it was doing  
> archiving
> when moveTo is in use, as I was doing.  I saw that those were fixed  
> in RC3
> and 2.0.0 gold, so tested my flow on those using the 2.0.0 release  
> code.
> The unchanged flow configuration runs under 2.0.0, but when it sees  
> a file,
> is now throwing the same exception that is in Mule-3055.  Mule-3055  
> shows
> it's fixed in RC3 but only applies to an example, so I'm unsure if  
> it is the
> exact same issue or something similar.
>
> I'm gonna start digging into the cause of this, but if anyone is  
> already
> familiar with whatever was in 3055, I'd appreciate any tips/info.  
> Here's my
> sample config snippits that worked fine in 2.0RC2 but break in 2.0.0  
> (I've
> changed some names to generic names and doen other editing). The  
> component
> class below is expecting a String and has a method that the 2.0RC2  
> entry
> point resolver found just fine. But on 2.0.0 code it's almost like  
> my file
> to string transformer isn't happening or something.
>
> <file:file-to-string-transformer name="FileToString"/>
> <file:connector name="fileconn1" autoDelete="false"
> createMultipleTransactedReceivers="false"
> fileAge="5000" moveToDirectory="${mypath}/Archive"
> pollingFrequency="10000" >
> <custom-exception-strategy
> class="com.ameren.esb.mule.EventServiceExceptionStrategy">
>               .. content skipped...
> </custom-exception-strategy>
> </file:connector>
>
> <model name="Flow1">
> <service name="service1">
>    <inbound><inbound-endpoint address="file://${mypath}"
> transformer-refs="FileToString"
>     connector-ref="fileconn1">
>    </inbound-endpoint>
>    </inbound>
>    <component>
>     <spring-object bean="controller1">
> </spring-object>
>    </component>
>    <custom-exception-strategy
> class="com.ameren.esb.mule.EventServiceExceptionStrategy">
>               .. content skipped...
>    </custom-exception-strategy>
> </service>
> </model>
>
> Thanks in advance for any help!
> --
> View this message in context: http://www.nabble.com/2.0-FileConnector-question-tp16609060p16609060.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Steve Olson]

Just found the answer - evidently the default on the file connector for the streaming attribute has changed to true.  When I set it to default, my flow that worked under 2.0RC2 starts working again.

I don't know much about streaming, so will explore how to deal with that sometime later.

Steve Olson wrote:

I had a file connextor based flow that worked fine in RC2, although FileConnector itself had a couple bugs related to how it was doing archiving when moveTo is in use, as I was doing.  I saw that those were fixed in RC3 and 2.0.0 gold, so tested my flow on those using the 2.0.0 release code.  The unchanged flow configuration runs under 2.0.0, but when it sees a file, is now throwing the same exception that is in Mule-3055.  Mule-3055 shows it's fixed in RC3 but only applies to an example, so I'm unsure if it is the exact same issue or something similar.

I'm gonna start digging into the cause of this, but if anyone is already familiar with whatever was in 3055, I'd appreciate any tips/info.  Here's my sample config snippits that worked fine in 2.0RC2 but break in 2.0.0 (I've changed some names to generic names and doen other editing). The component class below is expecting a String and has a method that the 2.0RC2 entry point resolver found just fine. But on 2.0.0 code it's almost like my file to string transformer isn't happening or something.

<file:file-to-string-transformer name="FileToString"/>
<file:connector name="fileconn1" autoDelete="false"
createMultipleTransactedReceivers="false"
fileAge="5000" moveToDirectory="${mypath}/Archive"
pollingFrequency="10000" >
        <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
        </custom-exception-strategy>
</file:connector>

<model name="Flow1">
<service name="service1">
    <inbound><inbound-endpoint address="file://${mypath}"
        transformer-refs="FileToString"
    connector-ref="fileconn1">
    </inbound-endpoint>
    </inbound>
    <component>
    <spring-object bean="controller1">
        </spring-object>
    </component>
    <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
    </custom-exception-strategy>
</service>
</model>

Thanks in advance for any help!

[Steve Olson]

Sorry, the prior post should have said when I set streaming="false"


Just found the answer - evidently the default on the file connector for the streaming attribute has changed to true.  When I set it to default, my flow that worked under 2.0RC2 starts working again.

I don't know much about streaming, so will explore how to deal with that sometime later.

Steve Olson wrote:

I had a file connextor based flow that worked fine in RC2, although FileConnector itself had a couple bugs related to how it was doing archiving when moveTo is in use, as I was doing.  I saw that those were fixed in RC3 and 2.0.0 gold, so tested my flow on those using the 2.0.0 release code.  The unchanged flow configuration runs under 2.0.0, but when it sees a file, is now throwing the same exception that is in Mule-3055.  Mule-3055 shows it's fixed in RC3 but only applies to an example, so I'm unsure if it is the exact same issue or something similar.

I'm gonna start digging into the cause of this, but if anyone is already familiar with whatever was in 3055, I'd appreciate any tips/info.  Here's my sample config snippits that worked fine in 2.0RC2 but break in 2.0.0 (I've changed some names to generic names and doen other editing). The component class below is expecting a String and has a method that the 2.0RC2 entry point resolver found just fine. But on 2.0.0 code it's almost like my file to string transformer isn't happening or something.

<file:file-to-string-transformer name="FileToString"/>
<file:connector name="fileconn1" autoDelete="false"
createMultipleTransactedReceivers="false"
fileAge="5000" moveToDirectory="${mypath}/Archive"
pollingFrequency="10000" >
        <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
        </custom-exception-strategy>
</file:connector>

<model name="Flow1">
<service name="service1">
    <inbound><inbound-endpoint address="file://${mypath}"
        transformer-refs="FileToString"
    connector-ref="fileconn1">
    </inbound-endpoint>
    </inbound>
    <component>
    <spring-object bean="controller1">
        </spring-object>
    </component>
    <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
    </custom-exception-strategy>
</service>
</model>

Thanks in advance for any help!

[Daniel Feist]

Yes.

Seems what you found and my explanation (if you received it yet)  
match, which is a good sign.

To clarify streaming default changed to true for 2.0 but didn't change  
between RC releases.  What changed between RC releases is that  
initially file streaming was broken and then it got fixed :-)

Once the FileToString transformer is updated (in 2.0.1 i guess) you'll  
be able to use the default of streaming without a problem.

Dan

On 10 Apr 2008, at 13:23, Steve Olson wrote:

>
> Sorry, the prior post should have said when I set streaming="false"
>
>
> Steve Olson wrote:
>>
>> Just found the answer - evidently the default on the file connector  
>> for
>> the streaming attribute has changed to true.  When I set it to  
>> default, my
>> flow that worked under 2.0RC2 starts working again.
>>
>> I don't know much about streaming, so will explore how to deal with  
>> that
>> sometime later.
>>
>>
>> Steve Olson wrote:
>>>
>>> I had a file connextor based flow that worked fine in RC2, although
>>> FileConnector itself had a couple bugs related to how it was doing
>>> archiving when moveTo is in use, as I was doing.  I saw that those  
>>> were
>>> fixed in RC3 and 2.0.0 gold, so tested my flow on those using the  
>>> 2.0.0
>>> release code.  The unchanged flow configuration runs under 2.0.0,  
>>> but
>>> when it sees a file, is now throwing the same exception that is in
>>> Mule-3055.  Mule-3055 shows it's fixed in RC3 but only applies to an
>>> example, so I'm unsure if it is the exact same issue or something
>>> similar.
>>>
>>> I'm gonna start digging into the cause of this, but if anyone is  
>>> already
>>> familiar with whatever was in 3055, I'd appreciate any tips/info.  
>>> Here's
>>> my sample config snippits that worked fine in 2.0RC2 but break in  
>>> 2.0.0
>>> (I've changed some names to generic names and doen other editing).  
>>> The
>>> component class below is expecting a String and has a method that  
>>> the
>>> 2.0RC2 entry point resolver found just fine. But on 2.0.0 code it's
>>> almost like my file to string transformer isn't happening or  
>>> something.
>>>
>>> <file:file-to-string-transformer name="FileToString"/>
>>> <file:connector name="fileconn1" autoDelete="false"
>>> createMultipleTransactedReceivers="false"
>>> fileAge="5000" moveToDirectory="${mypath}/Archive"
>>> pollingFrequency="10000" >
>>> <custom-exception-strategy
>>> class="com.ameren.esb.mule.EventServiceExceptionStrategy">
>>>               .. content skipped...
>>> </custom-exception-strategy>
>>> </file:connector>
>>>
>>> <model name="Flow1">
>>> <service name="service1">
>>>    <inbound><inbound-endpoint address="file://${mypath}"
>>> transformer-refs="FileToString"
>>>     connector-ref="fileconn1">
>>>    </inbound-endpoint>
>>>    </inbound>
>>>    <component>
>>>     <spring-object bean="controller1">
>>> </spring-object>
>>>    </component>
>>>    <custom-exception-strategy
>>> class="com.ameren.esb.mule.EventServiceExceptionStrategy">
>>>               .. content skipped...
>>>    </custom-exception-strategy>
>>> </service>
>>> </model>
>>>
>>> Thanks in advance for any help!
>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/2.0-FileConnector-question-tp16609060p16609892.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[mdemo]

A couple of days I came up to a problem with the file connector, because i need the file object instead of a stream. The stream functionality is a new one in mule 2, see: http://www.nabble.com/Mule-2-and-FileConnector-td16549768.html

According to the file connector there are discussions about message adapters:
http://www.nabble.com/Streaming-and-MessageAdaptor%27s-in-2.0-td16587734.html

only for information
regards markus


Sorry, the prior post should have said when I set streaming="false"

Steve Olson wrote:

Just found the answer - evidently the default on the file connector for the streaming attribute has changed to true.  When I set it to default, my flow that worked under 2.0RC2 starts working again.

I don't know much about streaming, so will explore how to deal with that sometime later.

Steve Olson wrote:

I had a file connextor based flow that worked fine in RC2, although FileConnector itself had a couple bugs related to how it was doing archiving when moveTo is in use, as I was doing.  I saw that those were fixed in RC3 and 2.0.0 gold, so tested my flow on those using the 2.0.0 release code.  The unchanged flow configuration runs under 2.0.0, but when it sees a file, is now throwing the same exception that is in Mule-3055.  Mule-3055 shows it's fixed in RC3 but only applies to an example, so I'm unsure if it is the exact same issue or something similar.

I'm gonna start digging into the cause of this, but if anyone is already familiar with whatever was in 3055, I'd appreciate any tips/info.  Here's my sample config snippits that worked fine in 2.0RC2 but break in 2.0.0 (I've changed some names to generic names and doen other editing). The component class below is expecting a String and has a method that the 2.0RC2 entry point resolver found just fine. But on 2.0.0 code it's almost like my file to string transformer isn't happening or something.

<file:file-to-string-transformer name="FileToString"/>
<file:connector name="fileconn1" autoDelete="false"
createMultipleTransactedReceivers="false"
fileAge="5000" moveToDirectory="${mypath}/Archive"
pollingFrequency="10000" >
        <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
        </custom-exception-strategy>
</file:connector>

<model name="Flow1">
<service name="service1">
    <inbound><inbound-endpoint address="file://${mypath}"
        transformer-refs="FileToString"
    connector-ref="fileconn1">
    </inbound-endpoint>
    </inbound>
    <component>
    <spring-object bean="controller1">
        </spring-object>
    </component>
    <custom-exception-strategy class="com.ameren.esb.mule.EventServiceExceptionStrategy">
               .. content skipped...
    </custom-exception-strategy>
</service>
</model>

Thanks in advance for any help!