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.
Almost every time I clean and build my enterprise application I get the following exception: com.sun.enterprise.admin.common.exception.DeploymentException: Unrecognized module type for /home/fjaekel/NetBeansProjects/PortalTecnicoEAR/dist/gfdeploy; the archive may be incorrectly constructed, non-existent, or inaccessible from the server. For example, an application client jar should include the proper manifest file entry, and an ejb jar should contain at least one EJB. at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile(DeploymentServiceUtils.java:1175) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:734) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223) Caused by: java.io.IOException: Cannot determine the Java EE module type for /home/fjaekel/NetBeansProjects/PortalTecnicoEAR/dist/gfdeploy at com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistForArchive(PluggableArchivistsHelper.java:137) at com.sun.enterprise.deployment.archivist.PluggableArchivistsHelper.getArchivistForArchive(PluggableArchivistsHelper.java:98) at com.sun.enterprise.deployment.archivist.ArchivistFactory.getArchivistForArchive(ArchivistFactory.java:101) at com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.getTypeFromFile(DeploymentServiceUtils.java:1170) ... 3 more
I can only redeploy the application again if I undeploy it directly on the server. For example, go to services window > Servers > Glassfish V2 > Enterprise Applications and undeploy it.
V2 issue --> sunappsrv9 How many and of what kind are the modules in your EAR? Is this an EAR project or a Deployable Archive project?
I have 1 Web module and two EJB modules. The Web module builds the EJB module 1 and the EJB module 1 builds the EJB module 2. I think it is an EAR project. I created it at File > New Project > Enterprise > Enterprise Application.
Does your EJB module contain any true EJB's, such as Session Beans, Message Driven Beans, or Entity Beans -- EJB 3.0 Entity Classes do not count as EJB's (nor must they go into an ejb module -- they can go directly into your web app if you are accessing them directly).
Yes. Clean and Build has some bad interactions with GF directory deployment and Windows. There isn't much the plugin can do about them, though. 6.5 has a new feature... "Undeploy on clean" that addresses this issue, it has been implemented in each of the deployable project types.. web, ejb and ear... Please give it a try. NOTE: you may need to delete the build.xml and nbproject\build-impl.xml files from all the projects before you open them in 6.5, since it looks like the undeploy on clean is dependent on changes in the build scripts... I am going to close this as worksforme since I could not replicate the issue. Filer: please try out a recent build of 6.5 and see if you still run into this issue. If you do, please reopen the issue and attach a (set of) sample project(s) that demonstrate the issue.
Both modules contains Session Beans. I'm using Linux. I'll try NetBeans 6.5 when it's released. The beta version is crashing for me.
Please get a recent build from http://bits.netbeans.org/download/trunk/nightly/latest/ and try it, soon. If you wait until after the 6.5 release and the issue is still present in the 6.5 code... you will end up waiting until NB 7.0 to get a fix... Do not waste the opportunity to help us make sure the IDE works for you, while we still have a chance to resolve bugs.
I've worked for some days with build 200810011401. Every time I needed to redeploy the application I cleaned and builded it and the deployment occurred without problems. The only thing that happened sometimes was a random bug with clean and build, where the projects where not recognized between each other, causing lots of compilation errors. But to solve it I needed only to send the IDE clean and build the project again.