You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by John Francis <jf...@cix.co.uk> on 2002/10/30 13:31:00 UTC
Why don't WSDL URLs in UDDI contain 'service' elements?
Hi,
I'm trying to knock together some code to query a UDDI registry and call a
Web Service given it's WSDL URL. I've got the latter part of the problem
working (calling the Web Service) using some of the WSDL URLs listed on
the XMethods site. However, if I navigate to the WSDL overview document
URL via the UDDI registry I seem to get a different WSDL URL with no
service element. The WSIF code (modified from the DynamicInvoker) sample
fails because this WSDL URL doesn't contain any services.
I don't understand why the UDDI registry doesn't contain a pointer to the
URL with the service element, but a different WSDL file.
Sorry if the question seems dumb, I'm a bit new to this stuff ;-)
Thanks for any help
John
Re: Why don't WSDL URLs in UDDI contain 'service' elements?
Posted by John Francis <jf...@cix.co.uk>.
> ----- Original Message -----
> From: "John Francis" <jf...@cix.co.uk>
> To: <ax...@xml.apache.org>
> Cc: <jf...@cix.co.uk>
> Sent: Thursday, October 31, 2002 11:01 AM
> Subject: Re: Why don't WSDL URLs in UDDI contain 'service' elements?
> > Thanks for the reply, John. I think I just about figured that out
> > yesterday evening. Would I be correct in thinking that I could
> > contruct my
> > own Service (ServiceImpl) object from the bindingTemplate accessPoint
> > information and pass this to WSIF's ServiceFactory along with the
> > tModel
> > WSDL definition and eventually end up with a Port that I could invoke
> > on
> > dynamically?
> >
> > John Francis
>
> John,
>
> I am afraid I don't know enough about WSIF to answer your question.
> Hopefully one of the WSIF guys will respond.
>
> John Colgrave
Thanks John, I'm deep into reading about this stuff - there's lots to know
;-)
John
Re: Why don't WSDL URLs in UDDI contain 'service' elements?
Posted by John Colgrave <co...@hursley.ibm.com>.
----- Original Message -----
From: "John Francis" <jf...@cix.co.uk>
To: <ax...@xml.apache.org>
Cc: <jf...@cix.co.uk>
Sent: Thursday, October 31, 2002 11:01 AM
Subject: Re: Why don't WSDL URLs in UDDI contain 'service' elements?
> In article <00...@T30COLGRAVE>,
> colgrave@hursley.ibm.com (John Colgrave) wrote:
>
> > ----- Original Message -----
> > From: "John Francis" <jf...@cix.co.uk>
> > To: <ax...@xml.apache.org>
> > Cc: <jf...@cix.co.uk>
> > Sent: Wednesday, October 30, 2002 12:31 PM
> > Subject: Why don't WSDL URLs in UDDI contain 'service' elements?
>
> > > I'm trying to knock together some code to query a UDDI registry and
> > > call a
> > > Web Service given it's WSDL URL. I've got the latter part of the
> > > problem
> > > working (calling the Web Service) using some of the WSDL URLs listed
> > > on
> > > the XMethods site. However, if I navigate to the WSDL overview
> > > document
> > > URL via the UDDI registry I seem to get a different WSDL URL with no
> > > service element. The WSIF code (modified from the DynamicInvoker)
> > > sample
> > > fails because this WSDL URL doesn't contain any services.
> > >
> > > I don't understand why the UDDI registry doesn't contain a pointer to
> > > the
> > > URL with the service element, but a different WSDL file.
> >
> > The UDDI Best Practice for WSDL [1] assumes that you have two WSDL
> > files:
> > one with the portType and binding(s) and the other with the service.
> > Only
> > the first is referenced in UDDI. The address information is defined by
> > the
> > bindingTemplate accessPoint.
>
> Thanks for the reply, John. I think I just about figured that out
> yesterday evening. Would I be correct in thinking that I could contruct my
> own Service (ServiceImpl) object from the bindingTemplate accessPoint
> information and pass this to WSIF's ServiceFactory along with the tModel
> WSDL definition and eventually end up with a Port that I could invoke on
> dynamically?
>
> John Francis
John,
I am afraid I don't know enough about WSIF to answer your question.
Hopefully one of the WSIF guys will respond.
John Colgrave
Re: Why don't WSDL URLs in UDDI contain 'service' elements?
Posted by John Francis <jf...@cix.co.uk>.
In article <00...@T30COLGRAVE>,
colgrave@hursley.ibm.com (John Colgrave) wrote:
> ----- Original Message -----
> From: "John Francis" <jf...@cix.co.uk>
> To: <ax...@xml.apache.org>
> Cc: <jf...@cix.co.uk>
> Sent: Wednesday, October 30, 2002 12:31 PM
> Subject: Why don't WSDL URLs in UDDI contain 'service' elements?
> > I'm trying to knock together some code to query a UDDI registry and
> > call a
> > Web Service given it's WSDL URL. I've got the latter part of the
> > problem
> > working (calling the Web Service) using some of the WSDL URLs listed
> > on
> > the XMethods site. However, if I navigate to the WSDL overview
> > document
> > URL via the UDDI registry I seem to get a different WSDL URL with no
> > service element. The WSIF code (modified from the DynamicInvoker)
> > sample
> > fails because this WSDL URL doesn't contain any services.
> >
> > I don't understand why the UDDI registry doesn't contain a pointer to
> > the
> > URL with the service element, but a different WSDL file.
>
> The UDDI Best Practice for WSDL [1] assumes that you have two WSDL
> files:
> one with the portType and binding(s) and the other with the service.
> Only
> the first is referenced in UDDI. The address information is defined by
> the
> bindingTemplate accessPoint.
Thanks for the reply, John. I think I just about figured that out
yesterday evening. Would I be correct in thinking that I could contruct my
own Service (ServiceImpl) object from the bindingTemplate accessPoint
information and pass this to WSIF's ServiceFactory along with the tModel
WSDL definition and eventually end up with a Port that I could invoke on
dynamically?
John Francis
Re: Why don't WSDL URLs in UDDI contain 'service' elements?
Posted by John Colgrave <co...@hursley.ibm.com>.
----- Original Message -----
From: "John Francis" <jf...@cix.co.uk>
To: <ax...@xml.apache.org>
Cc: <jf...@cix.co.uk>
Sent: Wednesday, October 30, 2002 12:31 PM
Subject: Why don't WSDL URLs in UDDI contain 'service' elements?
> Hi,
>
> I'm trying to knock together some code to query a UDDI registry and call a
> Web Service given it's WSDL URL. I've got the latter part of the problem
> working (calling the Web Service) using some of the WSDL URLs listed on
> the XMethods site. However, if I navigate to the WSDL overview document
> URL via the UDDI registry I seem to get a different WSDL URL with no
> service element. The WSIF code (modified from the DynamicInvoker) sample
> fails because this WSDL URL doesn't contain any services.
>
> I don't understand why the UDDI registry doesn't contain a pointer to the
> URL with the service element, but a different WSDL file.
The UDDI Best Practice for WSDL [1] assumes that you have two WSDL files:
one with the portType and binding(s) and the other with the service. Only
the first is referenced in UDDI. The address information is defined by the
bindingTemplate accessPoint.
John Colgrave
[1] http://www.uddi.org/pubs/wsdlbestpractices-V1.07-Open-20020521.pdf