<error>.class is generated during deploy (deps-jar target)... hmmm

[evka85]

Hello all,

First things first - this forum is a super nice source of information and is very helpful - I've been using it for years. This is my first post however, so please go easy

I've encountered a very strange problem that I can't find any info about. Here it goes: I have an EE application with several EJB and Web modules, I run it in Glassfish 2. I use NetBeans and glassfish which come with OpenESB / GlassfishESB v2.2 (NetBeans v6.7.1 & Glassfish v2.1.1). In one of the EJB modules I have a few packages with entity beans. Now when I compile the whole application, everything is fine, but when I try to deploy it, the strangest thing happens - "<error>.class" file appears in EJBModule/build/jar/my_entity_package/ directory which also appears to be somewhat crippled and so NetBeans immediately throws this error at me during "deps-jar" build target (i.e. before the actual deployment to glassfish):

[zent]

Hi evka85

I've got almost the same problem here. Have you found a solution yet?
I have a SE application with JPA (eclipselink) and tomcat. To enable lazy loading in the entities I use static weaving. In my build.xml I added an ant task that does the weaving of the entities before packing the war file.
If I run the weaving ant task outside of netbeans it works fine, even if I run it several times. When I'm doing a clean build in Netbeans with my weaving task integreated in my build.xml everything works fine as well. As soon as I hit run, I got the same problem as you, when the build script comes to my ant task I get the following error

[kruisea]

Hi,

Same problem here I think. Disabling "Deploy on save" on the project properties (for me on the Enterprise Application project) and no more <error>.class errors.

Kruisea