You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by alexandre_garino <al...@experian-scorex.mc> on 2008/04/09 17:58:32 UTC

WSDL Generation

Hi,

I built synapse from the rev 646352. I set up a new proxy from this xml
fragement.

    <proxy name="KpsProxy" transports="http" startOnLoad="true">
        <target>
            <inSequence>
                <send>
                    <endpoint>
                        <address uri="https://www.xxxxx.xxx/kps.asmx">
                            <enableAddressing/>
                            <enableSec policy="policy.kps"/>
                        </address>
                    </endpoint>
                </send>
            </inSequence>
            <outSequence>
                <send/>
            </outSequence>
        </target>
        <publishWSDL uri="https://www.xxxxx.xxx/kps.asmx?wsdl"/>
    </proxy>

When I retrieve the WSDL through synapse (e.g.
http://10.130.30.202:8080/soap/KpsProxy?wsdl) I noticed that the service
element is not properly updated. Location attributes remain unchanged.

<wsdl:service name="KpsProxy"> 
<wsdl:port name="KPSSoap" binding="tns:KPSSoap">
<soap:address location="https://www.xxxxx.xxx/kps.asmx" />
</wsdl:port>
<wsdl:port name="KPSSoap12" binding="tns:KPSSoap12">
<soap12:address location="https://www.xxxxx.xxx/kps.asmx" />
</wsdl:port>
</wsdl:service>

I guess this is a regression because that works fine with synapse 1.1.1
release.

Regards,
Alexandre

-- 
View this message in context: http://www.nabble.com/WSDL-Generation-tp16588436p16588436.html
Sent from the Synapse - User mailing list archive at Nabble.com.


Re: WSDL Generation

Posted by Ruwan Linton <ru...@gmail.com>.
Asankha,

As I told, since there was a conceptual change in axis2, the fault was on
our side.

In detail the change is that, axis2 now reflects the exact WSDL as it is
over the generated WSDL in WSDL bindings and WSDL ports. So if there are 2
bindings in the wsdl that we used to generate the service, axis2 will only
add those two and nothing else and WSDL ports are the same. We need the
vice-versa and need to change the bindings and the WSDL ports according to
our transports.

So I had to clear the bindings (AxisEndpoints map) from the generated
service so that axis2 adds all the bindings from all the transports and the
WSDL ports.

Adding a unit test for this is pretty hard but should be able to do because
we can keep a wsdl to generate a service and a copy of the WSDL of the
generated service, so that we can do an XML comparison of the WSDL with the
one we store. I will try to come up with a unit test for this.

Thanks,
Ruwan

On Tue, Apr 15, 2008 at 1:45 PM, Asankha C. Perera <as...@wso2.com> wrote:

> Ruwan
>
> Was the fault on our side or on Axis2? Anyway would be good if we could
> write a unit test for this scenario if at all possible..
>
>
>  I guess this is a regression because that works fine with synapse 1.1.1
> > > > release.
> > > >
> > > >
> > > asankha
>



-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Re: WSDL Generation

Posted by "Asankha C. Perera" <as...@wso2.com>.
Ruwan

Was the fault on our side or on Axis2? Anyway would be good if we could 
write a unit test for this scenario if at all possible..

>>> I guess this is a regression because that works fine with synapse 1.1.1 release.
>>>       
asankha

Re: WSDL Generation

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Alexandre,

The issue with WSDL generation has been fixed, if you could build Synapse
from the trunk you should be able to see this working. Also please follow
the comments on the JIRA [1] on configuring the service. You will need to
exclude the unconfigured transports by providing the set of transports on
which the service is exposed as follows;

<proxy name="test" transports="http https">.......</proxy>

or you will have to configure all the transports by providing the necessary
parameters.

[1] - https://issues.apache.org/jira/browse/SYNAPSE-267

Thanks,
Ruwan

On Wed, Apr 9, 2008 at 11:11 PM, Ruwan Linton <ru...@gmail.com>
wrote:

> Hi Alexandre,
>
> It seems like an issue which has been introduced by the migration of the
> axis2 version from 1.4 to SNAPSHOT. Can you please raise a JIRA for this. We
> will fix this ASAP....
>
> Thanks,
> Ruwan
>
>
> On Wed, Apr 9, 2008 at 9:28 PM, alexandre_garino <
> alexandre.garino@experian-scorex.mc> wrote:
>
> >
> > Hi,
> >
> > I built synapse from the rev 646352. I set up a new proxy from this xml
> > fragement.
> >
> >    <proxy name="KpsProxy" transports="http" startOnLoad="true">
> >        <target>
> >            <inSequence>
> >                <send>
> >                    <endpoint>
> >                        <address uri="https://www.xxxxx.xxx/kps.asmx">
> >                            <enableAddressing/>
> >                            <enableSec policy="policy.kps"/>
> >                        </address>
> >                    </endpoint>
> >                </send>
> >            </inSequence>
> >            <outSequence>
> >                <send/>
> >            </outSequence>
> >        </target>
> >        <publishWSDL uri="https://www.xxxxx.xxx/kps.asmx?wsdl"/>
> >    </proxy>
> >
> > When I retrieve the WSDL through synapse (e.g.
> > http://10.130.30.202:8080/soap/KpsProxy?wsdl) I noticed that the service
> > element is not properly updated. Location attributes remain unchanged.
> >
> > <wsdl:service name="KpsProxy">
> > <wsdl:port name="KPSSoap" binding="tns:KPSSoap">
> > <soap:address location="https://www.xxxxx.xxx/kps.asmx" />
> > </wsdl:port>
> > <wsdl:port name="KPSSoap12" binding="tns:KPSSoap12">
> > <soap12:address location="https://www.xxxxx.xxx/kps.asmx" />
> > </wsdl:port>
> > </wsdl:service>
> >
> > I guess this is a regression because that works fine with synapse 1.1.1
> > release.
> >
> > Regards,
> > Alexandre
> >
> > --
> > View this message in context:
> > http://www.nabble.com/WSDL-Generation-tp16588436p16588436.html
> > Sent from the Synapse - User mailing list archive at Nabble.com.
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"




-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Re: WSDL Generation

Posted by Ruwan Linton <ru...@gmail.com>.
Hi Alexandre,

It seems like an issue which has been introduced by the migration of the
axis2 version from 1.4 to SNAPSHOT. Can you please raise a JIRA for this. We
will fix this ASAP....

Thanks,
Ruwan

On Wed, Apr 9, 2008 at 9:28 PM, alexandre_garino <
alexandre.garino@experian-scorex.mc> wrote:

>
> Hi,
>
> I built synapse from the rev 646352. I set up a new proxy from this xml
> fragement.
>
>    <proxy name="KpsProxy" transports="http" startOnLoad="true">
>        <target>
>            <inSequence>
>                <send>
>                    <endpoint>
>                        <address uri="https://www.xxxxx.xxx/kps.asmx">
>                            <enableAddressing/>
>                            <enableSec policy="policy.kps"/>
>                        </address>
>                    </endpoint>
>                </send>
>            </inSequence>
>            <outSequence>
>                <send/>
>            </outSequence>
>        </target>
>        <publishWSDL uri="https://www.xxxxx.xxx/kps.asmx?wsdl"/>
>    </proxy>
>
> When I retrieve the WSDL through synapse (e.g.
> http://10.130.30.202:8080/soap/KpsProxy?wsdl) I noticed that the service
> element is not properly updated. Location attributes remain unchanged.
>
> <wsdl:service name="KpsProxy">
> <wsdl:port name="KPSSoap" binding="tns:KPSSoap">
> <soap:address location="https://www.xxxxx.xxx/kps.asmx" />
> </wsdl:port>
> <wsdl:port name="KPSSoap12" binding="tns:KPSSoap12">
> <soap12:address location="https://www.xxxxx.xxx/kps.asmx" />
> </wsdl:port>
> </wsdl:service>
>
> I guess this is a regression because that works fine with synapse 1.1.1
> release.
>
> Regards,
> Alexandre
>
> --
> View this message in context:
> http://www.nabble.com/WSDL-Generation-tp16588436p16588436.html
> Sent from the Synapse - User mailing list archive at Nabble.com.
>
>


-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"