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.
Try to create client against simple MS based wsdl: http://wssc.india.sun.com/BankOrder/bankorder.svc?wsdl It fails and requires real complicated intervention to make it working. There are several issues: One problem is in JAX-WS which is not considering catalog files to detect recursive imports (which is what MS does). This was tracked as 274 and is supposed to be fixed in jax-ws: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=274 Other problem is that NetBeans points wsimport in build-impl.xml to local file in the wsdl parameter. So, there are two fixes required for this: 1. Update bundled JAX-WS libraries to latest with the fix included (so that the client is represented in UI correctly) 2. Fix 'wsdl' parameter given to the wsimport task for client to point to http:// external url, not to downloaded files - in all projects
Created attachment 40088 [details] Patch
Created attachment 40089 [details] New jax-ws binaries (to be placed to websvc/external)
Well, ignore the patch - with the jaxws fix, this change shouldn't be required. This needs more investigation as command line seems to work fine, the only case when it fails is when invoked via NB.
It's finally fixed in jax-ws 2.1 hudson build #1998. So, basically what is required is: - update the jars in netbeans - fix j2seproject to use 'external' option for wsimport I'd really really really vote for this to get to 5.5.1
Ccing Milan, Petr Blaha and Petr Jiricka...
We can not use a non-FCS version of JAX-WS in the product. BTW, what version do we use now? From java.net it sounds like JAX-WS 2.0 is the latest FCS version of JAX-WS currently available: https://jax-ws.dev.java.net/2.1/
Agreed. We should find out what is the next FCS date for JAX-WS. We should however make sure we do deliver updates so that we are able to fix high priority bugs in timely manner. I'd suggest to have a way to provide update of JAX-WS bundled libraries and place them to beta/alpha whatever update centers, or start building these NB library modules directly with JAX-WS builds at java.net. Or at least, document how to do it manually.
We use JAX-WS2.1 final release (2007/02/02) in Netbeans5.5.1.
Created attachment 40194 [details] Final patch for 551
OK, I attached a patch with changes required for NB. The rest is replacing the jax-ws libraries. It's just a matter of decision what to do with it. I think we could get at least the NB part of the fix into release. It's trivial and isolated.
Created attachment 40201 [details] Final patch for 551 - part2
JAX-WS 2.1 is targetted for Appserver 9.1 beta 2 to be in FCS. Appserver 9.1 beta 2 is scheduled for javaone. We may have to get the latest jars in the IDE close to M9 FF date. This is because the JAXWS Ri is going through testing in the next couple of weeks and if they find any issues then we may have to upgrade. We have already talked at length about delivering jaxws lib through update center and such but unfortunately we cant do those until we have some stable APIs from them which will help us remove the tie-ins we have with their private APIs. But thats where we plan to go and have been tracking required RFE with the jaxws team.
Yes, we need to fix this for 5.5.1 with proper jaxws fcs bits.
Applied the fixes from Martin Grebac in the 6.0 codeline. Diffs are attached.
Diff for the ProjectJAXWSClientSupport class: http://websvc.netbeans.org/source/browse/websvc/clientapi/src/org/netbeans/modules/websvc/spi/jaxws/client/ProjectJAXWSClientSupport.java?r1=1.3&r2=1.4 Change made to the WSDLModeler: http://websvc.netbeans.org/source/browse/websvc/jaxwsmodel/src/org/netbeans/modules/websvc/api/jaxws/wsdlmodel/WsdlModeler.java?r1=1.7&r2=1.8 For changes made to the build-impl.xsl file of the J2SE project, see attachment.
Created attachment 40535 [details] Diff file for build-impl.xsl of the J2SE project
btw, the JAXWS jars in the jaxws20 module have been updated to the 04/04/2007 nightly build version in NB 6.0, as required by the HRM process for changes to 551. This is in compliance to a request from QE in order to meet the requirements of Sun Studio. When the jaxws FCS jars do come out, NB will be refreshed again.
The fix looks fine.
Continuous build 20070406-102 of 6.0 seems to be O.K. Fix works and web services functionality works fine.
Fix is O.K. in 6.0 - could you commit the fix into 5.5.1, Rico?
Fix is O.K. in 6.0 - could you please commit the fix into 5.5.1, Rico?
Will commit the fix to 5.5.1 tomorrow, April 11. The reason for this is we want the latest jaxws bits as much as possible to accommodate the FCS date of Sun Studio.
the patch for j2se project's build-impl.xsl is not correct - it does not solve the problem of running the project (ws client generation) on jdk6 - the 'fork=true' must be replaced with 'xendorsed=true' in this case
Another effect of the JAX-WS lib. upgrade is that one cannot build/deploy any web project with web service and/or ws client to tomcat now if he runs ide on JDK6.
This has been fixed in the release551 codeline. For the Java project, xendorsed was added to the wsimport invocation. For the web project, xendorsed replaced the fork="true"/jvmarg options in the wsimport invocation for Tomcat. Diffs are attached.
Created attachment 40820 [details] New diff file for build-impl.xsl for web project
Created attachment 40822 [details] New diff file for build-impl.xsl for j2se project
Shouldn't we also fix the wsimport in j2ee/clientproject ? The diffs look fine. Nevertheless, please, test thoroughly the wsimport/wsgen with Tomcat/GlassFish V1/GlassFish V2 and jdk1.5/jdk1.6. - for all project types
> Shouldn't we also fix the wsimport in j2ee/clientproject ? Yes, we should. Thanks for catching this Milan. I've build my own 5.5.1 build and replaced there jaxws jars with latest jax-ws 2.1 nightly (available at jax-ws.dev.java.net) - since this is near to what we will have in our FCS. Then I checked ws/ws from wsdl/ws client creation in web/ejb/j2se/app client project for bundled tomcat/sjsas9.0ur1p1/gf-v2-b41a when IDE runs on jdk1.5.0_11/jdk6 and everything works as it should (except of appclient project type on jdk6 which needs to be fixed). I checked also deployment of created projects and it works as well.
I tested continuous build NetBeans-release551-20070412-1339,which according to changelog should contain both fixes,but there's another problem - build of ws client fails with same dialog, but also this exception: C:\Documents and Settings\Telco\WebApplication5\nbproject\build-impl.xml:296: The <wsimport> type doesn't support the "xendorsed" attribute. at org.apache.tools.ant.IntrospectionHelper.setAttribute(IntrospectionHelper.java:389) at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:370) at org.apache.tools.ant.RuntimeConfigurable.maybeConfigure(RuntimeConfigurable.java:324) at org.apache.tools.ant.Task.maybeConfigure(Task.java:254) at org.apache.tools.ant.UnknownElement.configure(UnknownElement.java:189) at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:158) at org.apache.tools.ant.Task.perform(Task.java:363) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369) at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216) at org.apache.tools.ant.Project.executeTarget(Project.java:1185) at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40) at org.apache.tools.ant.Project.executeTargets(Project.java:1068) at org.apache.tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:240) at org.apache.tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:293) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131) BUILD FAILED (total time: 0 seconds)
That's because that build still does not contain latest JAX-WS 2.1 bits. Download them (https://jax-ws.dev.java.net/files/documents/4202/55164/JAXWS2.1_nightly.zip) and put jars into $NB_HOME/ide7/modules/ext/jaxws21/ and $NB_HOME/ide7/modules/ext/jaxws21/api then it will work.
I copied latest JAXWS2.1 bits and it works,but now I've original issue again as if there's no fix.Hovewer when I do Refresh Client on broken websvc node,after refreshing is client O.K.
Clarification - only error message appears. Broken ws node changes itself to O.K. state after while and I can Call Web Service operation and such stuff. Attaching error message.
Created attachment 40836 [details] Error dialog
That dialog is not nice (and maybe a bit confusing), but that's another (P3) issue which can wait IMHO since everything else is working
I filed issue 100824 to get rid of that error message.
Applied same fix to the J2EE app client project. Diffs attached.
Created attachment 40843 [details] Diff file for build-impl.xsl of the J2EE app client project
Migrated changes to ProjectJAXWSClientSupport and WSDLModeler to 5.5.1.
Updated the jaxws jars to the jaxws 2.1.1 FCS version
v. in 5.5.1 FCS build