File transport over Network (Non FTP)

[lekkie]

Hi Guys,

I am planning to move some files over the standard network using the famous \\ip-address\folder\redlof\ syntax and this is my config.

I have tried to search for posts related to network file transports but no luck.

The Mule sample doc says

file:////192.168.0.1/temp/ but Mule throws this exception

however if you change that to 192.168.0.1/temp/ it creates a folder 192.168.0.1/temp in the current directory.

Is there a special declaration needed to use network files?

kr,

Lekkie.

[Dirk Olmes]

lekkie wrote:

> Hi Guys,
>
> I am planning to move some files over the standard network using the famous
> \\ip-address\folder\redlof\ syntax and this is my config.
>
> I have tried to search for posts related to network file transports but no
> luck.
>
> The Mule sample doc says
>
> file:////192.168.0.1/temp/ but Mule throws this exception

Oops which sample doc is this?

This is plain wrong, the file transport can do local files only. If you
need remote files either use SMTP or the CIFS forge transport (currently
unmaintained but I'm glad for any contributions).

-dirk

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

    http://xircles.codehaus.org/manage_email

[lekkie]

here:

http://www.mulesoft.org/display/MULE2USER/File+Transport?showComments=true&showCommentArea=true#FileTransport-ExpressingFileEndpoints

To connect to a windows network drive:

file:////192.168.0.1/temp/

(sic)

Dirk Olmes wrote:

lekkie wrote:
> Hi Guys,
>
> I am planning to move some files over the standard network using the famous
> \\ip-address\folder\redlof\ syntax and this is my config.
>
> I have tried to search for posts related to network file transports but no
> luck.
>
> The Mule sample doc says
>
> file:////192.168.0.1/temp/ but Mule throws this exception

Oops which sample doc is this?

This is plain wrong, the file transport can do local files only. If you
need remote files either use SMTP or the CIFS forge transport (currently
unmaintained but I'm glad for any contributions).

-dirk

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

    http://xircles.codehaus.org/manage_email

[Dirk Olmes]

lekkie wrote:
> here:
>
> http://www.mulesoft.org/display/MULE2USER/File+Transport?showComments=true&showCommentArea=true#FileTransport-ExpressingFileEndpoints
>
> To connect to a windows network drive:
>
> file:////192.168.0.1/temp/

Thanks I have removed that from the docs as it's definitely wrong.

-dirk

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

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

Hold on a second, what exception does Mule throw? This was working just fine last time I remember.

Andrew

[Dirk Olmes]

Andrew Perepelytsya wrote:
> Hold on a second, what exception does Mule throw? This was working just
> fine last time I remember.

Really? How is this supposed to work? Does it work cross platform, i.e.
accessing a SMB drive from Linux? I really doubt that.

-dirk

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

    http://xircles.codehaus.org/manage_email

[Stephen Fenech-2]

Hi Guys,

This worked for me, both when I had a shared windows folder and even
when had a shared folder in Ubuntu. I had the Mule on Vista and could
write and read files on both XP and Ubuntu. The following is the config

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:spring="http://www.springframework.org/schema/beans"
       xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2"
       xmlns:file="http://www.mulesource.org/schema/mule/file/2.2"
       xsi:schemaLocation="
               http://www.mulesource.org/schema/mule/core/2.2 
http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
               http://www.mulesource.org/schema/mule/vm/2.2 
http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
               http://www.mulesource.org/schema/mule/file/2.2 
http://www.mulesource.org/schema/mule/file/2.2/mule-file.xsd">

    <file:connector name="fileConnector" streaming="false"
autoDelete="true"/>
    <vm:connector name="vmConnector" queueEvents="true"/>
   
    <file:file-to-string-transformer name="fileToString"/>
   
    <model>  
   
        <service name="fileWriter">
            <inbound>
                <vm:inbound-endpoint  path="fromTest"/>                
           
            </inbound>
            <log-component/>
            <outbound>
                <pass-through-router>
                    <file:outbound-endpoint
path="//192.168.11.4/Shared/muleFiles"/>
                </pass-through-router>
            </outbound>
        </service>
   
        <service name="fileReader">
            <inbound>
                <file:inbound-endpoint
path="//192.168.11.4/Shared/muleFiles"
transformer-refs="fileToString"/>                          
            </inbound>
            <log-component/>
            <outbound>
                <pass-through-router>
                    <vm:outbound-endpoint path="toTest"/>
                </pass-through-router>
            </outbound>
        </service>  
    </model>

</mule>

Hope this helps


Dirk Olmes wrote:

> Andrew Perepelytsya wrote:
>  
>> Hold on a second, what exception does Mule throw? This was working just
>> fine last time I remember.
>>    
>
> Really? How is this supposed to work? Does it work cross platform, i.e.
> accessing a SMB drive from Linux? I really doubt that.
>
> -dirk
>
> ---------------------------------------------------------------------
> 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

[Andrew Perepelytsya]

Right, it's time to bring those removed doc pieces back.

Andrew

On Oct 19, 2009 3:47 AM, "Stephen Fenech" <stephen.fenech@...> wrote:

Hi Guys,

This worked for me, both when I had a shared windows folder and even when had a shared folder in Ubuntu. I had the Mule on Vista and could write and read files on both XP and Ubuntu. The following is the config

<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns="http://www.mulesource.org/schema/mule/core/2.2"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:spring="http://www.springframework.org/schema/beans"
     xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2"
     xmlns:file="http://www.mulesource.org/schema/mule/file/2.2"
     xsi:schemaLocation="
             http://www.mulesource.org/schema/mule/core/2.2 http://www.mulesource.org/schema/mule/core/2.2/mule.xsd
             http://www.mulesource.org/schema/mule/vm/2.2 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd
             http://www.mulesource.org/schema/mule/file/2.2 http://www.mulesource.org/schema/mule/file/2.2/mule-file.xsd">

  <file:connector name="fileConnector" streaming="false" autoDelete="true"/>
  <vm:connector name="vmConnector" queueEvents="true"/>
    <file:file-to-string-transformer name="fileToString"/>
    <model>           <service name="fileWriter">
          <inbound>
              <vm:inbound-endpoint  path="fromTest"/>                                     </inbound>
          <log-component/>
          <outbound>
              <pass-through-router>
                  <file:outbound-endpoint path="//192.168.11.4/Shared/muleFiles"/>
              </pass-through-router>
          </outbound>
      </service>
        <service name="fileReader">
          <inbound>
              <file:inbound-endpoint path="//192.168.11.4/Shared/muleFiles" transformer-refs="fileToString"/>                                     </inbound>
          <log-component/>
          <outbound>
              <pass-through-router>
                  <vm:outbound-endpoint path="toTest"/>
              </pass-through-router>
          </outbound>
      </service>     </model>

</mule>

Hope this helps

Dirk Olmes wrote: > > Andrew Perepelytsya wrote: >   >> >> Hold on a second, what exception does ...