-
1. Re: metro distro issues
heiko.braun Feb 16, 2008 3:54 PM (in response to mat.hoff)You need to supply more information about the problems you encounter. Post some example code, a detailed problem description, then someone might be able to help you.
-
2. Re: metro distro issues
mat.hoff Feb 19, 2008 12:05 AM (in response to mat.hoff)As far as the code goes, its simple anything with in the javax.jws.* namespace is not recognized. (this didn't happen until I installed JBossWS - metro) So for example the basic @WebService() is not recognized, and the import for it cannot be resolved. In its place, netbeans 6.0 (my IDE of choice) tells me that I can import org.jboss.web.WebService to fix the problem, I'm not sure that would be the correct thing to do. Also, when I try to update my web service, my project can no longer find WsImport. So basically like I said before, as soon as I install metro, I loose all jax-ws support. I figured out why this is happening, I compared the classpath with native ws and with metro. And I found the differences, jbossws-client. jar, jboss-jaxrpc.jar, jboss-jaxws.jar have all been removed. On top of all of this, I can no longer build a web service from the top down, because the project can't resolve any of the jax-ws/jaxb namespaces it tells netbeans that the runtime doesn't support the framework and it makes the suggestion that I need to download something for jaxrpc support. So with that you can get a sense of my frustration. I apologized for the non-detailed description of my issues. If there is anything in particular that I need to post to try and get the ball rolling on this let me know.
-
3. Re: metro distro issues
heiko.braun Feb 20, 2008 6:10 AM (in response to mat.hoff)
Well, the jars are different. You cannot rely on the same set of jars across stacks. Metro just does use different ones. But take a look at the build.xml that drives the samples that ship with the distro. It contains classpath references that you can reflect to build a new netbeans setup for metro.