Yes Javier, that's how it works. The JavaAPI was generated directly from
the UDDI xsds, so it should map exactly to the UDDI spec. --K
On 3/20/11 6:19 PM, Javier Molina wrote:
Hi Kurt,
After having another go, I think I understand how the XML->Java
mapping works, any top level elements that are allowed multiple times
must be created by adding them to the collection returned by the
getter, for elements that appear only once, a direct setter should be
available.
Thanks,
Javier.
On 12 March 2011 01:28, Kurt T Stam <[email protected]
<mailto:[email protected]>> wrote:
Hi Javier,
tModel.getOverViewDoc() gives you a list, then you can add to this
list.
Cheers,
--Kurt
On 3/11/11 12:14 AM, El Javi Bolaños Molina wrote:
Hi all,
I am trying to register a Webservice using the jUDDI API
according to
http://www.oasis-open.org/committees/uddi-spec/doc/bp/uddi-spec-tc-bp-using-wsdl-v108-20021110.pdf
The basic idea as I understand is that the bindingTemplate
accessPonit should point to the actual service while
tModel.OverviewDoc.OverviewUrl needs to point to the WSDL
definition.
The problem now is that as far as I see tModel does not have a
setter for Overviewdoc.
I think there are various setters missing across the uddi
model classes in jUDDI API, was that made deliberately, is
that a bug or I am going the wrong path to create my own tModels?
Thanks,
Javier.
--
Javier Molina MACS
IT Consultant/Java Developer
(M) 0449 640 386
(e) [email protected] <mailto:[email protected]>
