So I'm attempting to deploy a web service project into a tomcat server and getting the following error.
Now as I understand it, the problem is in com.gcc.openconnect.jaxws.ExceptionBean. As I can tell this class is generated from a wsgen command when I build my application, so I can't really go in and edit it. From what I can tell ExceptionBean is being generated because some of my endpoints are throwing java.lang.Exception. This code base works on various other tomcat instances but will not work on mine.
So I'm curious what the issue could be. I don't think it's a coding problem since this code base works elsewhere. I'm wondering if this sort of problem could happen because of differences between the JRE, wsgen command, or some other environmental difference.
Sorry if this isn't very detailed, but I'm not sure what information would be relevant to answer my question.
Have you downloaded and installed Metro into you Tomcat, as described here:
http://metro.java.net/2.1.1/ I would guess that your application is lacking a JAR file. Such a JAR file may be deployed to the Tomcat instance or in the web application in which you deploy your web service, in accord with the instructions for the web service stack in question. Metro will deploy the required JAR files to the Tomcat instance.
Thanks for the response. I did not have Metro installed, but I don't think that is the problem. I installed Metro, but I'm still getting the same error. I think this has to do with JAXB or some component that is out of sync with the other servers. Does anyone know if JAXB or JAXWS components significantly differ from JRE6 to JRE7, or has anyone found issues where automatically generated classes via wsgen would not generate correctly?
Read the exception: missing default constructor. Need to add this default constructor
Brian M Smith
posted 8 years ago
Again guys. Not to sound like an ass here, but this isn't a class that I created. This is a project that is working in production, but when I pull it down to a local environment it won't deploy. The class that is causing the exception is a class that is automatically generated via the wsgen command. This isn't a class that I created. Again, this is a project that will actually deploy but won't work locally for me. I'm very certain that this is a JRE or configuration issue.
Again, thanks for the responses but has anyone encountered issues where wsgen is creating "incorrect" classes?
posted 8 years ago
This is JAXB related issue. And it's a BIG topic on its own.
So Google for the nature of the exception mentioned. Post your finding that I may learn from it too. Go luck.
That which doesn't kill us makes us stronger. I think a piece of pie wouldn't kill me. Tiny ad: