Exactly,

but the wsdl tag should be wrapped in an endpoint tag so, for the proxy to
work it should be modified as follows;

On 3/16/07, Michael Griffin <[EMAIL PROTECTED]> wrote:

Interesting...

So if I want to proxy as a service, I can define something like this.

<proxy name="myProxy" transports="http">

       <target>


             <endpoint>

               <wsdl uri="https://server.domain.com/some-service?wsdl";
service="serviceNameInWSDL" port="portNameInWSDL"/>


              </endpoint>

</target>

</proxy>



In this case, messages which are comming to the proxy will be forwarded to
the port of the service as provided in your wsdl.


Ruwan.

-----Original Message-----
From: Ruwan Linton [mailto:[EMAIL PROTECTED]
Sent: Friday, March 16, 2007 11:32 AM
To: [email protected]
Subject: Re: WSDL endpoints and publishWSDL


Griffin,

I think you got the idea of publishWSDL from Paul, (i.e. the wsdl that the
proxy service is published under) while this is specific to proxy,
WSDLEndpoint is a kind of a generic endpoint that you can use within the
Synapse (even for message mediation). I think it is

Further more, WSDLEndpoint represents an actual service endpoint which is
build from the provided WSDL of that actual endpoint by extracting
relevant
parameters inside Synapse. Also there are AddressEndpoints which will be
constructed from the given service endpoint uri (address).

You can specify the endpoint (Can be either WSDLEP or AddressEP or .... )
in
the proxy inside target tag to specify the ultimate message delivery
endpoint.

Any more clarifications??

Ruwan.

On 3/16/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
>
> Griffin
>
> The design is that the publishWSDL key points to the WSDL to be
> published. Synapse should automatically create the right bindings for
> you inside the WSDL showing the endpoints you've made that service
> available on.
>
> The syntax you are describing is based on the latest trunk I think.
> I'm not sure that we've implemented WSDL endpoints yet.
>
> In 0.91 we only offered the <wsdl> tag which is actually what we now
> call publishWSDL
>
> Paul
>
> On 3/16/07, Michael Griffin <[EMAIL PROTECTED]> wrote:
> > Can someone explain how I should use publishWSDL and a WSDL endpoint
in
> > relation to a proxy.  My assumption is that I can use the WSDL
endpoint
> to
> > point back to the original WSDL via URI, and using the publishWSDL key
> > present an altered variation of it that references my proxy
> endpoint.  Let
> > me know.
> >
> > Thanks,
> > Griffin
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


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



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




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

Reply via email to