Jars from common/lib not picked up in Netbeans when using JBoss...

[chagharu]

I'm having a go at getting JBoss (5.1.0.GA) working with NetBeans 6.5 and seem to have fallen at the first hurdle. When trying to compile a basic hello world servlet, NB reports several errors as it cannot find the javax.servlet package. I found that JBoss keeps this package in servlet-api.jar, which is found in <JBoss_Home>/common/lib.

It appears that this directory is not included in the server libraries by NB, even though JBoss uses this as the "parent" lib that is included in all server instance libs.

I tried adding the servlet-api.jar as a compile time library in NB, however this causes either -
a)A blank page when the war is deployed OR
b)A 500 error with the following message

[chagharu]

If anyone is having the same problem here, there is a workaround to this - I guess the permanent fix will be in a future version of NB. But thought I'd try posting in case there was another way...

Workaround is to compile your project in Glassfish by right clicking the project in the projects tab, clicking on the "run" category in the left hand pane and select GlassFish V3 from the server drop down menu on the right (This assumes that the GF server is installed with NB). Click Ok, then do a clean and build of the project.

When the project has built, go back to the menu above, select the JBoss server and click OK. The project will show errors but if you run or deploy the project without trying to build, then JBoss will be able to use its common/lib libraries to deploy the appropriate J2EE class files.

Hope this helps.

[chagharu]

Quicker workaround (can't believe I missed this before!)...

Add the required jars as a compile time library in NB but ensure that the package tick box is unchecked when the library/jar is added. This ensures the jar is only used for compilation and is not deployed with the project.

Stupid that I missed this before - that was why I was getting the linkage error. The project was deployed with the jar and JBoss didn't know whether to use the one in the common/lib or the one deployed with it...

Still would be nice for NB to recognise JBoss's common/lib directory somehow though...

[lloy0076]

Yes, it would be nice if this had somehow been "fixed" or more well documented; making a we application only to find the Servlet APIs mysteriously missing was rather disconcerting.

DSL