Re: SV: Making SFTP transport working in Mule 2.2

Häggkvist, Lennart wrote:

Hi,

I'm also working on upgrading the SFTP transport to 2.2 (and I got it to work).

Beside the upgrade I have also added support for identity files (ie. use public/private
keys for authentication instead of passwords) and some other small changes.

How do I submit a patch for the above so that it will be included in the official release
Of the transport? The "Contribute" link on http://www.mulesource.org/display/SFTP/Home points
To http://www.mulesource.org/display/MULEFORGE/Contribute - but that is a Mule "core" info page?
Are there any differences between a transport and "core"?

Thanks,
 Lennart
 

-----Ursprungligt meddelande-----
Från: Pascal Alma [mailto:mule.user.relay@mulesource.com]
Skickat: den 1 juli 2009 08:31
Till: user@mule.codehaus.org
Ämne: [mule-user] Making SFTP transport working in Mule 2.2

Hi,

I am trying to get the sftp transport to work in Mule version 2.2. However I am stuck at the part the Mule has to find the xsd for the sftp transport. I keep getting the following error when trying to run the unit test 'SftpLargeReceiveFunctionalTestCase':
cvc-complex-type.2.4.a: Invalid content was found starting with element 'sftp:connector'. One of '{"http://www.mulesource.org/schema/mule/core/2.2":description, "http://www.springframework.org/schema/beans":beans, "http://www.springframework.org/schema/beans":bean, "http://www.springframework.org/schema/context":property-placeholder, "http://www.mulesource.org/schema/mule/core/2.2":global-property, "http://www.mulesource.org/schema/mule/core/2.2":configuration, "http://www.mulesource.org/schema/mule/core/2.2":notifications, "http://www.mulesource.org/schema/mule/core/2.2":abstract-extension, "http://www.mulesource.org/schema/mule/core/2.2":abstract-security-manager, "http://www.mulesource.org/schema/mule/core/2.2":abstract-transaction-manager, "http://www.mulesource.org/schema/mule/core/2.2":abstract-connector, "http://www.mulesource.org/schema/mule/core/2.2":abstract-global-endpoint, "http://www.mulesource.org/schema/mule/core/2.2":abstract-transformer, "http://www.mulesource.org/schema/mule/core/2.2":abstract-filter, "http://www.mulesource.org/schema/mule/core/2.2":abstract-model, "http://www.mulesource.org/schema/mule/core/2.2":abstract-interceptor-stack}' is expected.

So the real question for now is how do I refer to the 'local' location of the xsd in my mule-config file. I have edited the XSD so the namespace match 'http://www.mulesource.org/schema/mule/sftp/2.2'. I hoped that adding it to the classpath would be sufficient but unfortunately that is not the case. Any help is welcome!

Here is part of my 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:sftp="http://www.mulesource.org/schema/mule/sftp/2.2"
        xmlns:vm="http://www.mulesource.org/schema/mule/vm/2.2"
        xsi:schemaLocation="
               http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
               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/sftp/2.2  file///mule-sftp.xsd
               http://www.mulesource.org/schema/mule/vm/2.2 http://www.mulesource.org/schema/mule/vm/2.2/mule-vm.xsd">

        <sftp:connector name="sftp" pollingFrequency="20000" autoDelete="true">
                <custom-exception-strategy
                        class="org.mule.tck.functional.QuietExceptionStrategy" />
        </sftp:connector>
 ....
</mule>

---------------------------------------------------------------------
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