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.
Glen Mazza wrote: OK, but I suspect the WEB-INF/lib deployment technique is becoming a little bit more common today than it used to be in the past. In production hosting environments, at least on accounts I've worked on so far, web server admins want deployable WARs and EARs with everything needed within them, without the admins needing to alter their JDK or shared folders. Further, I think having all the needed JARs in the WEB-INF/lib folder is the most common way of doing things for Mavenized projects. FWIW, on the CXF user's list--I don't think I've ever heard anyone copy libs to the shared or JDK folders (although I'm sure it happens), but that may be because CXF has so many more JARs and CXF projects tend to be more Maven-based. Still, one change I would like to see on the NetBeans side would be for it to allow me to configure WS security with Tomcat as the server without me needing to first copy anything to my Tomcat shared folders. Since I place the Metro jars in the WEB-INF/lib directory of the WAR when I'm done, up to now I've had to lie and tell NetBeans I'm using GlassFish to get my security configuration done, *then* I copy the modified WSDLs to my separate Maven project. See here for the complete discussion: http://www.nabble.com/metro-on-tomcat.xml-for-Tomcat-6-tt20457366.html
Not sure I understand the request, I think it already works this way. When you create web project (with e.g. Tomcat as target server), create a library called e.g. Metro1.4 and add it to the project. Then creating WS works fine, as well as Edit WS Attributes with QoS tab. Please reopen with more details if I misunderstood the request.