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.
Build 200904140201, JDK 1.6.0_13 / 1.5.0_18, Win Vista Create new JAX-RPC web service on Glassfish v2.1 in web project (you need to install JAX-RPC plugin) and deploy it.Create another web application and web service client on the service. Client is generated,Build Successfull,only down left on the status bar,there's brief message: Error creating Java from WSDL file. Try to set HTTP Proxy. Also - there's only wsdl's name as client's node, marked as Unregistered service (tooltip) and I can't Call Web service's operation from index.jsp, because service's node can't be opened to list operations .
Probably a regression.
The wscompile, that is called from WS code, fails with the following error : JDK1.6: error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider org.netbeans.modules.openide.modules.PatchedPublicProcessor could not be instantiated: java.lang.ClassCastException error: compilation failed, errors should have been reported JDK1.5: error: Exception thrown while constructing Processor object: javax/annotation/processing/AbstractProcessor error: compilation failed, errors should have been reported This is a regression since Netbeans 6.5. Should we implement something on web services site ? I'd ask Jesse for help. What is the roll of PatchedPublicProcessor ? Could you please give me some glue, then possibly, reassign back to me. Thank You.
I'm afraid there's not enough here for me to go on. If the problem occurs during an Ant task (when run inside the IDE but not when run from the command line), I would want a ZIP of an Ant build script and any necessary supporting files (JARs, sample sources, ...) so that I can reproduce without having to have all of these EE-related modules installed and the complex setup run. PatchedPublicProcessor is a JSR 269 annotation processor in openide.modules. You could probably see the stack trace for the CCE if you set Ant to run in Verbose mode. It is quite possible that the wscompile task does some tricks with ClassLoader's and gets it wrong.
JAX-RPC support in IDE calls programaticaly wscompile tool. The Ant task works without any problems. The code is included in: websvc.registry module, extsrc source root org.netbeans.modules.websvc.registry.jaxrpc.Wsdl2Java#execute() method Basically, JAX-RPC internal class : com.sun.xml.rpc.spi.tools.CompileTool is created and run() method called on that class. IDE creates arguments for wscompile tool and passes those arguments to CompileTool.run(String[] args) method I'll try to get more information from that tool. Yes, running wscompile with verbose="true" is a good idea. This is the classpath we pass to wscompile tool: "modules/ext/jaxrpc16/activation.jar", "modules/ext/jaxrpc16/jax-qname.jar", "modules/ext/jaxrpc16/jaxp-api.jar", "modules/ext/jaxrpc16/FastInfoset.jar", "modules/ext/jaxrpc16/jaxrpc-api.jar", "modules/ext/jaxrpc16/jaxrpc-impl.jar", "modules/ext/jaxrpc16/jaxrpc-spi.jar", "modules/ext/jaxrpc16/jsr173_api.jar", "modules/ext/jaxrpc16/mail.jar", "modules/ext/jaxrpc16/relaxngDatatype.jar", "modules/ext/jaxrpc16/saaj-api.jar", "modules/ext/jaxrpc16/saaj-impl.jar", "modules/ext/jaxrpc16/xsdlib.jar"
By "Verbose" mode I meant Tools > Options > Misc > Ant. This would show where the actual CCE occurs. The root problem is probably that some code invoked by wscompile uses ClassLoader.getSystemClassLoader() when it should not: when running Ant inside the IDE, CL.sCL will include openide.util, openide.modules, and o.n.bootstrap (i.e. -classpath lib/*.jar); whereas the ClassLoader used to load ant.jar does not include these things (nor does ${java.class.path}).
I am not able to get more info from wscompile tool. I am not sure com.sun.xml.rpc.spi.tools.CompileTool has something common with Ant. As I said doing the same with Ant works fine. JAX-RPC support has its own class loader (URLClassLoader). That might be an issue.
Integrated into 'main-golden', will be available in build *200904160201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/3dcf8d99d4d3 User: mkuchtiak@netbeans.org Log: #162585: don't need to consider jar files needed for jdk1.4
Fixed. Problem was in ClassLoader. The code was really running under SystemClassLoader. I've changed the code to use the specific class loader created in websvc.registry module. Thank You for help. Details: http://hg.netbeans.org/main?cmd=changeset;node=72c41f08c2b7
Integrated into 'main-golden', will be available in build *200904170201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/72c41f08c2b7 User: mkuchtiak@netbeans.org Log: #162585: run wscompile tool in another class loader (Class Loader obtained from Wsdl2Java class), extend JAX-RPC 1.6 public packages
ver.