[chrismiles]

I am compiling through JBuilder - I am pointing it to the JDK that came with Sun Application Server 8.2, which is java 1.5.0_06-b05.

This is what it is setting the classpath to when building the project.

C:\Documents and Settings\Chris\Desktop\implementation\projects\cakeinabox\classes;C:\Sun\AppServer\jdk\demo\jfc\CodePointIM\CodePointIM.jar;C:\Sun\AppServer\jdk\demo\jfc\Java2D\Java2Demo.jar;C:\Sun\AppServer\jdk\demo\plugin\jfc\CodePointIM\CodePointIM.jar;C:\Sun\AppServer\jdk\demo\plugin\jfc\Java2D\Java2Demo.jar;C:\Sun\AppServer\jdk\lib\dt.jar;C:\Sun\AppServer\jdk\lib\htmlconverter.jar;C:\Sun\AppServer\jdk\lib\jconsole.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\jdk\sample\jnlp\servlet\jardiff.jar;C:\Sun\AppServer\jdk\sample\jnlp\servlet\jnlp-servlet.jar;C:\Sun\AppServer\jdk\sample\jnlp\servlet\jnlp.jar;C:\Sun\AppServer\jdk\jre\lib\charsets.jar;C:\Sun\AppServer\jdk\jre\lib\deploy.jar;C:\Sun\AppServer\jdk\jre\lib\ext\dnsns.jar;C:\Sun\AppServer\jdk\jre\lib\ext\localedata.jar;C:\Sun\AppServer\jdk\jre\lib\ext\sunjce_provider.jar;C:\Sun\AppServer\jdk\jre\lib\ext\sunpkcs11.jar;C:\Sun\AppServer\jdk\jre\lib\im\indicim.jar;C:\Sun\AppServer\jdk\jre\lib\im\thaiim.jar;C:\Sun\AppServer\jdk\jre\lib\javaws.jar;C:\Sun\AppServer\jdk\jre\lib\jce.jar;C:\Sun\AppServer\jdk\jre\lib\jsse.jar;C:\Sun\AppServer\jdk\jre\lib\plugin.jar;C:\Sun\AppServer\jdk\jre\lib\rt.jar;C:\jboss-4.0.4.GA\lib\commons-httpclient.jar;C:\jboss-4.0.4.GA\lib\commons-logging.jar;C:\jboss-4.0.4.GA\lib\concurrent.jar;C:\jboss-4.0.4.GA\lib\dom4j.jar;C:\jboss-4.0.4.GA\lib\endorsed;C:\jboss-4.0.4.GA\lib\endorsed\resolver.jar;C:\jboss-4.0.4.GA\lib\endorsed\serializer.jar;C:\jboss-4.0.4.GA\lib\endorsed\xalan.jar;C:\jboss-4.0.4.GA\lib\endorsed\xercesImpl.jar;C:\jboss-4.0.4.GA\lib\endorsed\xml-apis.jar;C:\jboss-4.0.4.GA\lib\getopt.jar;C:\jboss-4.0.4.GA\lib\jboss-common.jar;C:\jboss-4.0.4.GA\lib\jboss-jmx.jar;C:\jboss-4.0.4.GA\lib\jboss-system.jar;C:\jboss-4.0.4.GA\lib\jboss-xml-binding.jar;C:\jboss-4.0.4.GA\lib\log4j-boot.jar;C:\jboss-4.0.4.GA\lib\namespace.jar;C:\jboss-4.0.4.GA\lib\webdavlib.jar;C:\jboss-4.0.4.GA\server\default\lib\activation.jar;C:\jboss-4.0.4.GA\server\default\lib\antlr-2.7.6.jar;C:\jboss-4.0.4.GA\server\default\lib\autonumber-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\bcel.jar;C:\jboss-4.0.4.GA\server\default\lib\bindingservice-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\bsf.jar;C:\jboss-4.0.4.GA\server\default\lib\bsh-1.3.0.jar;C:\jboss-4.0.4.GA\server\default\lib\bsh-deployer.jar;C:\jboss-4.0.4.GA\server\default\lib\cglib.jar;C:\jboss-4.0.4.GA\server\default\lib\commons-collections.jar;C:\jboss-4.0.4.GA\server\default\lib\commons-httpclient.jar;C:\jboss-4.0.4.GA\server\default\lib\commons-logging.jar;C:\jboss-4.0.4.GA\server\default\lib\hibernate3.jar;C:\jboss-4.0.4.GA\server\default\lib\hsqldb.jar;C:\jboss-4.0.4.GA\server\default\lib\hsqldb-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\javassist.jar;C:\jboss-4.0.4.GA\server\default\lib\javax.servlet.jar;C:\jboss-4.0.4.GA\server\default\lib\javax.servlet.jsp.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-backport-concurrent.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-common-jdbc-wrapper.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-hibernate.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-j2ee.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-jaxrpc.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-jca.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-jsr77.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-jsr88.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-management.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-monitoring.jar;C:\jboss-4.0.4.GA\server\default\lib\jbossmq.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-remoting.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-remoting-int.jar;C:\jboss-4.0.4.GA\server\default\lib\jbossretro-rt.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-saaj.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-serialization.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-srp.jar;C:\jboss-4.0.4.GA\server\default\lib\jbosssx.jar;C:\jboss-4.0.4.GA\server\default\lib\jboss-transaction.jar;C:\jboss-4.0.4.GA\server\default\lib\jmx-adaptor-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\jnpserver.jar;C:\jboss-4.0.4.GA\server\default\lib\jpl-pattern.jar;C:\jboss-4.0.4.GA\server\default\lib\jpl-util.jar;C:\jboss-4.0.4.GA\server\default\lib\log4j.jar;C:\jboss-4.0.4.GA\server\default\lib\mail.jar;C:\jboss-4.0.4.GA\server\default\lib\mail-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\properties-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\scheduler-plugin.jar;C:\jboss-4.0.4.GA\server\default\lib\scheduler-plugin-example.jar;C:\jboss-4.0.4.GA\server\default\lib\snmp-support.jar;C:\jboss-4.0.4.GA\server\default\lib\wsdl4j.jar;C:\jboss-4.0.4.GA\server\default\lib\xmlentitymgr.jar

[starksm64]

Then file a bug report with jbuilder or sun as google shows this is a common problem with jbuilder+jdk5. Its outside of the scope of jboss.

http://www.google.com/search?q=VerifyError+JBuilder

[starksm64]

If you want to file a bug report in our jira to allows someone to evaluate the bytecode issue, use:
http://jira.jboss.com/jira/browse/JBAS

[chrismiles]

good call... never experienced a problem with JBuilder itself like that before.

compiled by hand and everything is working excellent now.

thanks for your time and patience.