I figured out what the problem was myself. The classes mentioned in the warnings were indeed present in the war, and were not actually the problem. However, a jar that contained the superclasses of these classes, was not in the war file, and thus could not be loaded. When I added this jar to the war, the warnings went away, and the WS web page also displays fine. So I would say there is a bug with the error message, which can potentially be very confusing. I spent a fair amount of time staring at war content, comparing package names in detail and so on. When the classloader fails, it should look at what class it is actually failing in loading, which obviously is not happening.
Another interesting side-note is that once I added the jar, I actually ran into another problem, where my config files were specifying serializer/deserializer classes instead of the factories for the same. This caused exceptions to be thrown, and the web service not to deploy, whereas with the jar missing, the web service would deploy. That means the warnings somehow caused the deployment to skip parts of the deployment. thought you might be interested in this, as it may be another bug. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863797#3863797 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863797 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
