This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 109037 - Implementing a Web service client for an enterprise EJB module porject fails with error
Summary: Implementing a Web service client for an enterprise EJB module porject fails ...
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Client (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-06 17:18 UTC by pvarghese
Modified: 2007-09-28 12:11 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
WSDL file for the issue (2.39 KB, application/octet-stream)
2007-07-06 17:20 UTC, pvarghese
Details
jpeg file of the error dialog (34.60 KB, application/octet-stream)
2007-07-06 17:21 UTC, pvarghese
Details
improved error dialog (35.34 KB, image/jpeg)
2007-09-28 12:00 UTC, Milan Kuchtiak
Details
Fixed wsdl file. (2.38 KB, text/xml)
2007-09-28 12:05 UTC, Milan Kuchtiak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pvarghese 2007-07-06 17:18:32 UTC
Netbeans build: netbeans-trunk-nightly-200707030000-full.zip

Trying to implement a web service client for an enterprise EJB module project fails with the following error.

wsimport-init:
wsimport-client-check-TwoWay:
wsimport-client-TwoWay:
Consider using <depends>/<produces> so that wsimport won't do unnecessary compilation
parsing WSDL...
[ERROR] in message "TwoWayMsg", part "TwoWayPart" must specify a "element" attribute
  line 19 of
file:/C:/workbench/IntergrationProjs/EjbToBpel/EJBModule1/src/conf/xml-resources/web-service-references/TwoWay/wsdl/TwoWay.wsdl
BUILD SUCCESSFUL (total time: 4 seconds)

The WSDL has a message defined on a schema type as follows
    <message name="TwoWayMsg">
        <wsdl:part name="TwoWayPart" type="ns0:msgType"/>
    </message>

The binding for the interface using this message is marked as style="rpc" as follows.
        <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>

This seems to be a valid scenario and should be supported for SOA composite applications JavaEE interaction scenarios.

The wsdl file is attached for reference and testing.

Steps to reproduce:
1. import the attached wsdl or store it in local folder.
2. create an enterprise EJB module project.
3. right click the EJB module project and select the option "web service client" from the Web Service" category.
4. on the wizard select the local file for the WSDL file selection
5. point to the wsdl file in the local directory, enter a package name and click finish
6. observe the error dialog

The jpeg file of the error dialog is attached.
Comment 1 pvarghese 2007-07-06 17:20:23 UTC
Created attachment 44776 [details]
WSDL file for the issue
Comment 2 pvarghese 2007-07-06 17:21:23 UTC
Created attachment 44777 [details]
jpeg file of the error dialog
Comment 3 Milan Kuchtiak 2007-09-28 11:57:43 UTC
The Error dialog hes been improved. See the attachment.

The wsdl file you attached doesn't conforms the Basic Profile:
http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html

- rule R2717 : soap:body in input/output must specify the namespace attribute
- rule R2205 : wsdl:fault must refer to a wsdl:message where wsdl:part has element attribute specified.

JAX-WS can not generate client from this wsdl file.

I fixed the wsdl file to satisfy the WS-I Basic profile. See the atachment.
Comment 4 Milan Kuchtiak 2007-09-28 12:00:59 UTC
Created attachment 49731 [details]
improved error dialog
Comment 5 Milan Kuchtiak 2007-09-28 12:05:24 UTC
Created attachment 49732 [details]
Fixed wsdl file.
Comment 6 Milan Kuchtiak 2007-09-28 12:11:10 UTC
See also:
https://jax-rpc.dev.java.net/docs/wsdl-bindings.html#rpc/litFault