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.
The following exception is generated when compiling web service included in J2EE application: RmiModeler error: java.lang.ClassNotFoundException: com$acme$conversational$gen$ws$ConversationalWebServiceSEI at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:685) at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.buildEncodedModel(RmiModeler.java:523) at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:459) at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88) at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63) at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714) at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43) at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22) CAUSE: java.lang.ClassNotFoundException: com$acme$conversational$gen$ws$ConversationalWebServiceSEI at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:242) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:78) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:84) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:84) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:84) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:84) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getLoadableClassName(RmiUtils.java:84) at com.sun.xml.rpc.processor.modeler.rmi.RmiUtils.getRealName(RmiUtils.java:54) at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.modelPort(RmiModeler.java:676) at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.buildEncodedModel(RmiModeler.java:523) at com.sun.xml.rpc.processor.modeler.rmi.RmiModeler.buildModel(RmiModeler.java:459) at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88) at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63) at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714) at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43) at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22) error: RmiModeler error: java.lang.ClassNotFoundException: com$acme$conversational$gen$ws$ConversationalWebServiceSEI
I think it's more serious. Upgrading to P1.
When I build EJB module and Web application at first then building of whole Enterprise Application passes. When I select Clean & Build on Enterprise Application it fails.
It's probably related to this bug too: When I tried to deploy such enterprise application, I got error that ear is not valid J2EE archive. When I looked at it I found out that web.xml is missing inside war.
I looks like the problem is caused by my ear libraries packaging changes. I will try to fix it even I am not so much familiar witg web services.
fixed Checking in build-impl.xsl; /cvs/web/project/src/org/netbeans/modules/web/project/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.66; previous revision: 1.65 done
i'm able to reproduce this in build 200502012121.
I fixed the problem in web appplication. Now it fails when there is a webservice in an ejb project. Please add exact steps to reproduce the problem next time. It will help me save some time and easy verification as well. Thanks.
I have created a fix and jungi is going to verify it tomorrow. If the fix is ok, I will integrate it.
fixed in trunk Checking in src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.25; previous revision: 1.24 done
fixed in QBE200502012121 branch as well.
v. 200502061900
I'm reopening this issue because part of the fix (revision 1.25 of build-impl.xsl for ejbjarproject) caused bug #54835. <wscompile-init> was changed to depend on <do-compile>. This cannot be done ever because this task is a shared dependency with tasks that are done during the <pre-compile> phase (hence the new circular dependency bug referenced above.) <wscompile-init> is an init task and should not need to depend on anything (except maybe <init> itself, but it has not been necessary to make that explicit.) I do not understand why it was deemed necessary change it to fix this bug, but if someone can explain it to me, I would be happy to help devise a better solution.
fixed in trunk. The wscompile-init now depends on init. Sorry for the troubles, I do not understand how I could create such a stupid dependency ;-) Thanks jungi for exploring this! I will commit the fix into qbuild branch after QE checks it. Checking in build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.28; previous revision: 1.27 done
checked in build 200502170805, marku, can you commit it to qbuild branch? Thanks.
and to beta branch too, please
fixed in QBE200502151900 Checking in build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.27.4.1; previous revision: 1.27 done fixed in release41_beta Checking in build-impl.xsl; /cvs/j2ee/ejbjarproject/src/org/netbeans/modules/j2ee/ejbjarproject/resources/build-impl.xsl,v <-- build-impl.xsl new revision: 1.27.2.1; previous revision: 1.27 done
verified