Re: Using Netbeans for Web Services.

From:

"Mike Schilling" <mscottschilling@hotmail.com>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 27 May 2009 10:32:47 -0700

Message-ID:

<3PeTl.31029$YU2.20649@nlpi066.nbdc.sbc.com>

RedGrittyBrick wrote:

I'm using the Netbeans IDE to generate client code from WSDL for a
web-service.

The code generated is not taking into account some parts of the
definitions (time = \d\d:\d\d:\d\d) and this results in error
messages
from the web-service.

Should I expect Netbeans to handle this better?

Do I need to dig through dozens of generated classes to see if I can
find where it incorrectly serializes the data and fix it myself?

Should I provide some intelligent feedback to the suppliers of the
WSDL+XSD?
*** What do other folk do?

You can certainly file a bug (NetBeans seems not to be distinguishing
time from dateTime). Since NetBeans is open source, you could also
fix it yourself :-) Or, you could look for other client-generation
software that handles this better (you might look at Axis.)

The WSDL referers to XSD files that contain definitions like this:

  <xs:complexType name="HeaderType">
    <xs:sequence>
      <xs:element name="DateOfPreparation" type="bbb:DateType"/>
      <xs:element name="TimeOfPreparation" type="bbb:TimeType"/>
    </xs:sequence>
  </xs:complexType>

  <xs:simpleType name="TimeType">
    <xs:restriction base="xs:time">
      <xs:pattern value="\d{2}:\d{2}:\d{2}(\.\d+)?"/>
    </xs:restriction>
  </xs:simpleType>

NetBeans generates an API that can be used like this

  headerType.setTimeOfPreparation(new GregorianCalendar());

However the transmitted XML clearly ignores the XSD restriction
patterns:
<a:DateOfPreparation>2009-05-27T12:27:19.109+01:00</a:DateOfPreparation>
<a:TimeOfPreparation>2009-05-27T12:27:19.109+01:00</a:TimeOfPreparation>