Hi, I've had this error myself, but it was tricky to track down.
In my case, I had a class that I had modified and put into a new JAR file, whilst still having the original version in an older JAR file. JBOSS was seeing the older version, which had differend method signatures. So, I would suggest that you a) get your code compiling in a totally seperate location and a copy of the JAR files you think you need. Make sure you delete ALL your old build locations (.class files) to make sure everything is ok b) copy only these new JAR files back into a clean JBOSS installation and hopefully the problem will have gone away. Cheers, Jason View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3865598#3865598 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3865598 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
