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 107463 - JAX-RPC client can not be generated for Web Service
Summary: JAX-RPC client can not be generated for Web Service
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords:
Depends on:
Blocks: 106402
  Show dependency tree
 
Reported: 2007-06-20 15:55 UTC by Roman Mostyka
Modified: 2007-06-27 15:30 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screenshot of "Information" dialog. (107.17 KB, image/jpeg)
2007-06-21 10:53 UTC, Roman Mostyka
Details
modified wsdl file (3.24 KB, text/xml)
2007-06-22 02:08 UTC, Quy Nguyen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Mostyka 2007-06-20 15:55:53 UTC
1. Rightclick "Web Service" node and select "Add Web Service...".
2. In appeared dialog enter http://ghobad.homelinux.com:8080/FarsiDate/PersianCalendarService?WSDL in "WSDL URL" field.
3. Click "Add" button.

Result: "Information" modal dialog appears with message "Unable to generate the JAX-RPC client. This web service will
not function for J2EE 1.4 projects." and JAX-RPC client for W/S is not created.
This W/S can not be used in J2EE 1.4 application.
Comment 1 Quy Nguyen 2007-06-20 20:45:47 UTC
This works for me on both JDK 1.5.0_06 and JDK 1.6.0_01 (this is after fixing IZ 107468).  Can you attach a screenshot
showing the contents of the Output window when the error occurs?
Comment 2 Roman Mostyka 2007-06-21 10:50:24 UTC
I tried reproduce on Mac OS X and everything was fine, so probably it is Windows specific issue. I tried on other
Windows XP and with the same result.
I use:
Product Version: NetBeans IDE Dev (Build 200706190000, C/C++ Pack 20070619)
Java: 1.6.0_01; Java HotSpot(TM) Client VM 1.6.0_01-b06
Comment 3 Roman Mostyka 2007-06-21 10:53:37 UTC
Created attachment 44155 [details]
Screenshot of "Information" dialog.
Comment 4 Quy Nguyen 2007-06-21 19:16:23 UTC
I am also running on Windows XP, and the issue is not occurring for me.  The wscompile tool has the following error
message in the attached screenshot: 

error: modeler error: invalid entity name: "CurrentPersianDate" (in namespace "http://farsi/")

There appears to be a problem resolving the schema type definitions in the import, although I don't know why I don't see
the issue.
Comment 5 Quy Nguyen 2007-06-22 02:08:06 UTC
Created attachment 44234 [details]
modified wsdl file
Comment 6 Quy Nguyen 2007-06-22 02:10:03 UTC
Since I can't reproduce the issue on my machine, could you try to import this modified wsdl to see if the error still
occurs?  I removed the schema xsd import and replaced it with the type definitions directly.
Comment 7 Roman Mostyka 2007-06-22 15:24:01 UTC
With attached WSDL file everything is OK with JAX-RPC and with JAX-WS.
Comment 8 Quy Nguyen 2007-06-22 20:04:17 UTC
Is the proxy server correctly set on the machines used for these tests?
Comment 9 Roman Mostyka 2007-06-25 11:03:13 UTC
Yes, I'm able to add different Web Services from Internet.
Comment 10 Peter Pis 2007-06-25 19:25:59 UTC
This issue is showstopper for M10. Please integrate the fix into the trunk and "release60-m10" branch. 
Comment 11 Quy Nguyen 2007-06-26 03:41:06 UTC
This issue is caused by importing a wsdl with an embedded xsd schema when there is a proxy present.  There is a
workaround available - download the xsd schema files onto the local machine and change the corresponding schema URLs.

Comment 12 Peter Pis 2007-06-26 08:27:09 UTC
This issue has been marked as a STOPPER for M10. There two solutions: either provide the fix into the trunk and
"release60-m10" branch or remove the dependency from M10 umbrella issue and mention it in the release notes.
Comment 13 Ch Nguyen 2007-06-26 14:59:59 UTC
Per Quy, the fix for this issue is high-risk and will take a bit of time.  Since there is a work around,  this should no
longer a stopper.  I'm lowering the priority to P2 and Quy will look into fixing this post-M10.  In the mean time should
release note this for M10.

Tammie, can you remove this from the stopper list?
Comment 14 Quy Nguyen 2007-06-26 17:13:13 UTC
I have implemented a fix for this that was verified by QE to not cause additional regressions, so this can be resolved
for M10.
Comment 15 Quy Nguyen 2007-06-26 19:13:01 UTC
Fixed in trunk and in the release60-m10 branch.  This fix uses the xml retriever api to copy the referenced schemas to
avoid proxy issues with the wsimport ant task.

Checking in nbproject/project.xml;
/cvs/visualweb/websvcmgr/nbproject/project.xml,v  <--  project.xml
new revision: 1.10; previous revision: 1.9
done
Checking in release/ws_import_compile.xml;
/cvs/visualweb/websvcmgr/release/ws_import_compile.xml,v  <--  ws_import_compile.xml
new revision: 1.16; previous revision: 1.15
done
Checking in src/org/netbeans/modules/visualweb/websvcmgr/codegen/Wsdl2Java.java;

/cvs/visualweb/websvcmgr/src/org/netbeans/modules/visualweb/websvcmgr/codegen/Wsdl2Java.java,v  <--  Wsdl2Java.java
new revision: 1.17; previous revision: 1.16
done


Checking in nbproject/project.xml;
/cvs/visualweb/websvcmgr/nbproject/project.xml,v  <--  project.xml
new revision: 1.9.2.1; previous revision: 1.9
done
Checking in release/ws_import_compile.xml;
/cvs/visualweb/websvcmgr/release/ws_import_compile.xml,v  <--  ws_import_compile.xml
new revision: 1.15.2.1; previous revision: 1.15
done
Checking in src/org/netbeans/modules/visualweb/websvcmgr/codegen/Wsdl2Java.java;

/cvs/visualweb/websvcmgr/src/org/netbeans/modules/visualweb/websvcmgr/codegen/Wsdl2Java.java,v  <--  Wsdl2Java.java
new revision: 1.16.2.1; previous revision: 1.16
done
Comment 16 Peter Pis 2007-06-26 20:00:20 UTC
To Reporter: Could you please verify this issue for M10? Thanks.
Comment 17 Roman Mostyka 2007-06-27 15:30:39 UTC
I verified this issue with build from trunk.