Deploy war through netbeans onto glassfish v3 beta?

Someone using the Stateless annotations in ManagedBeans is reporting a similar problem on the java. Net Forums.

Someone using the @Stateless annotations in ManagedBeans is reporting a similar problem on the java. Net Forums. I don't know if this applies to you but the given workaround was: Go to the admin console, go to the update center, and install EJB.

I didn't test it myself so I can't confirm this will help.

Thanks Pascal, when I go to update tool, I do have glassfish ejb container & glassfish ejb lite container added. I can understand that there is perhaps something in the project that is making glassfish think that there are EJBs in the project, however from what I can tell ejb support is installed. – dpb Oct 26 '09 at 18:46 This was more a guess than a serious lead.

Actually, this really looks like a bug to me. Maybe you'll be more lucky if you report it in NetBeans' issue tracker. – Pascal Thivent Oct 26 '09 at 18:54 Good idea, I filed a bug: glassfish.dev.java.Net/issues/show_bug.

Cgi? Id=10592 – dpb Oct 27 '09 at 3:58.

Https://glassfish.dev.java. Net/issues/show_bug. Cgi?

Id=10592 From the bug: Ok, found the cause (thanks much for providing the test case! ): 1. EjbSniffer was retrieved after scanning the archive: one (or more) of the library jars packaged in the archive contains EJBs with component annotations.So the ejb container was asked to load the module later.

2. The ejb container was not able to find the corresponding metadata because the web. Xml is 2.4 version so the meta-data processing skipped the annotation processing (we only process annotations for Java EE 5+ schema versions).

After I changed the web. Xml to reference 2.5 schema (you can do 3.0 schema as well): " rel="nofollow">java.sun.com/xml/ns/javaee/web-app_2_5.x... The app deployed successfully. Please give it a try and let me know if it works for you.

I have 3_0 schema and I still get the error. What's more interesting is I have two wars, one is the example project from weld archetype, and the other is a customization of that. The custom war doesn't work.

I've checked side by side, it's the same except for more model classes and more properties in persistence.xml.

Just my $0.02... I had the same error after I added the JaxMe library (version 0.5.2) to my application. This caused a deployment failure on one of my war modules - which confused the hell out of me, because I didn't make any changes to that module. Removing JaxMe fixed the problem.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.