On Mon, May 6, 2013 at 4:40 PM, Alex O'Ree <[email protected]> wrote:
> Business > Service > Binding Template > Access Point > Value = usually a URL > UseType = wsdlDeployment, endPoint, hostingRedirector, or something > else that makes sense to you. The "useType" attribute is a descriptor > telling you want the value means. > > Kurt is currently working on implementing the WSDL to UDDI Technical > Note from OASIS that defines how to map Port Type and many of the > other WSDL elements into a UDDI structure. Overview URL can be used > for a WSDL location too. I"m sure Kurt will be answer to answer this > with more detail. The WSDL2UDDI should be in the next release 3.1.5 > which should hopefully be very soon (maybe next week) > Thanks Alex, Would want to know what is the most appropriate place for a WSDL URL to reside in UDDI world . > > > On Mon, May 6, 2013 at 6:54 AM, Subash Chaturanga <[email protected]> > wrote: > > Hi, > > In the use case of adding a WSDL to UDDI registry through JUDDI, I would > > like to know where in general juddi allows to put the WSDL url ? I can > see > > following two options . I would like to know the recommended, mostly used > > way to retrieve the WSDL url from a business entity. > > > > Is it BindingTemplate#getAccessPointUrl() ? (I happen to notice that > this is > > not a direct WSDL like URL, I mean like ...?wsdl, but a service endpoint > ) > > Is it TmodelInstanceInfo#getOverviewDocs()#getOverviewUrl() ? In this > case > > as I know each WSDL port type maps to a TModel, if so for each TModels I > > have for a particular WSDL should have the same overview URL ? > > > > Thanks > > -- > > Subash Chaturanga > > Sri Lanka > > > > Blog - http://subashsdm.blogspot.com/ > > Twitter - http://twitter.com/subash89 > > > -- Subash Chaturanga Department of Computer Science & Engineering University of Moratuwa Sri Lanka Blog - http://subashsdm.blogspot.com/ Twitter - http://twitter.com/subash89
