Re: incorrect xsd file generated

Asankha C. Perera Sat, 13 Oct 2007 10:03:51 -0700

Ok.. I think this is a bug we need to fix for 1.1... could you file aJIRA Balaji?

Upul could you take a look into this issue and find a solution? Isuspect something with Axis2, but we may be able to work around the issue...


asankha

balaji hari wrote:

The problem with the parameter useOriginalWsdl is if set to "true" then
synapse doesn't apply security policy to input and output message in wsdl.

If set to false then it changes the xsd files in a mysterious way. I think a
parameter to use original xsd file  in WSDL will help resolve this.

Another issue is if I set useOriginalWsdl to true, synapse doesn't modify
the xsd files, but its unable to retrieve original xsd file.

Hope this helps.

Balaji



pzfreo wrote:

Balaji

Thanks for pointing this nasty little bug out! Can you please raise a
JIRA.

Would it be enough to use the "useOriginalWSDL" option?

<definitions xmlns="http://ws.apache.org/ns/synapse";>
    <proxy name="StockQuoteProxy">
        <target>
            <endpoint>
                <address uri="
http://localhost:9000/soap/SimpleStockQuoteService"/>
            </endpoint>
<outSequence>
<send/>
</outSequence>
        </target>
        <publishWSDL
uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
<parameter name="useOriginalwsdl">true</parameter>
<parameter name="modifyUserWSDLPortAddress">false</parameter>
    </proxy>
</definitions>

You might want to use true instead in your case.

Paul

On 10/12/07, balaji hari <[EMAIL PROTECTED]> wrote:

When creating a proxy service using synapse, the xsd file is regenerated

in

an incorrect way.

I have attached the wsdl and xsd files. The original xsd file doesn't
have

namespace whereas the regenerated one has namespace prefix!

Original one:


<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:tns="http://eta.sddc.army.mil/xsd/raterankrequest";
targetNamespace="http://eta.sddc.army.mil/xsd/raterankrequest";>
        <xsd:import schemaLocation="raterankinput.xsd"/>
        <xsd:element name="RateRankRequest"

type="tns:RateRankRequestType"/>

        <xsd:complexType name="RateRankRequestType">
                <xsd:sequence>
                        <xsd:choice>
                                <xsd:element ref="DRO"/>
                                <xsd:element ref="MSG"/>
                        </xsd:choice>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

**Regenerated one

<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema attributeFormDefault="unqualified"
        elementFormDefault="unqualified"
targetNamespace="http://eta.sddc.army.mil/xsd/raterankrequest";>
        <xsd:import namespace=""

schemaLocation="RateRankServiceUserToken?xsd=xsd1"

/>
        <xsd:element name="RateRankRequest"
type="tns:RateRankRequestType"

/>

        <xsd:complexType name="RateRankRequestType">
                <xsd:sequence>
                        <xsd:choice>
                                <xsd:element ref="tns:DRO" />
                                <xsd:element ref="tns:MSG" />
                        </xsd:choice>
                </xsd:sequence>
        </xsd:complexType>
</xsd:schema>

http://www.nabble.com/file/p13183308/test.zip test.zip



Balaji
--
View this message in context:

http://www.nabble.com/incorrect-xsd-file-generated-tf4616122.html#a13183308

Sent from the Synapse - Dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

Re: incorrect xsd file generated

Reply via email to