java.lang.VerifyError: field not type compatible (class: org/apache/xerces/parsers/IntegratedParserConfiguration method: configurePipeline()V) at pc: 4" I thought that it was just the xalan.jar that was upsetting the process but it does in fact seem to be both that, and the "xercesImpl.jar". On the enhancer I have got it to work by re-building without the enhancer addded to the build. Then enhancing each project individually using the ant task. I am still unable however to add the enhancer to the build using the plugin and then re-build all. this will return me the same jdoGetManagedFieldCount error, even if I have re-built without the enhancer previously. This all seems a little awkward, so if there is something I can do to get the build to work with the plugin, and using the enhancer, that would be ideal. Marc Prud'hommeaux wrote: BD- The build problems sound to me like some of your persistent classes have been recompiled, but others have not. Have you tried completely rebuilding all the classes in your project before doing any enhancement? In addition when I was migrating the metadata, I had problems with the Apache libraries, which caused a failure when I ran the "migrate-meta" task. I ended up replacing the two files (xalan.jar and xercesImpl.jar) that were packaged with Kodo3 with ones from our previous Kodo install and the migrate worked fine. Is there a problem with these files? We did upgrade the version of xercesImpl.jar we ship with 3.0, but I would be surprised if this would cause problems. Can you post the exception you get when you try to use the old jars? In article < bqdvtj$ei5$1@solarmetric.netmar.com >, BD wrote: Kodo version 3.0.0 / using IBM Websphere/Eclipse I am testing a migration to Kodo 3, and I am having problems with enhancing when building the project using the plug-in. The error returned is shown below... Problems occurred building the selected resources. packagedesc/ta/event/Bean.jdoGetManagedFieldCount()I Also, I have attempted to enhance the project using the ANT task, but that also fails with the following error trace. java.lang.NoSuchMethodError: packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V

Oracle Community | 3004 | 1 decade ago
tip
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    Enhance Errors in Kodo 3

    Oracle Community | 1 decade ago | 3004
    java.lang.VerifyError: field not type compatible (class: org/apache/xerces/parsers/IntegratedParserConfiguration method: configurePipeline()V) at pc: 4" I thought that it was just the xalan.jar that was upsetting the process but it does in fact seem to be both that, and the "xercesImpl.jar". On the enhancer I have got it to work by re-building without the enhancer addded to the build. Then enhancing each project individually using the ant task. I am still unable however to add the enhancer to the build using the plugin and then re-build all. this will return me the same jdoGetManagedFieldCount error, even if I have re-built without the enhancer previously. This all seems a little awkward, so if there is something I can do to get the build to work with the plugin, and using the enhancer, that would be ideal. Marc Prud'hommeaux wrote: BD- The build problems sound to me like some of your persistent classes have been recompiled, but others have not. Have you tried completely rebuilding all the classes in your project before doing any enhancement? In addition when I was migrating the metadata, I had problems with the Apache libraries, which caused a failure when I ran the "migrate-meta" task. I ended up replacing the two files (xalan.jar and xercesImpl.jar) that were packaged with Kodo3 with ones from our previous Kodo install and the migrate worked fine. Is there a problem with these files? We did upgrade the version of xercesImpl.jar we ship with 3.0, but I would be surprised if this would cause problems. Can you post the exception you get when you try to use the old jars? In article < bqdvtj$ei5$1@solarmetric.netmar.com >, BD wrote: Kodo version 3.0.0 / using IBM Websphere/Eclipse I am testing a migration to Kodo 3, and I am having problems with enhancing when building the project using the plug-in. The error returned is shown below... Problems occurred building the selected resources. packagedesc/ta/event/Bean.jdoGetManagedFieldCount()I Also, I have attempted to enhance the project using the ANT task, but that also fails with the following error trace. java.lang.NoSuchMethodError: packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V
  2. 0

    [DERBY-4142] java.lang.VerifyError causing java.sql.SQLException: Cannot create an instance of generated class ... in lang.GeneratedColumnsTest and GeneratedColumnsPermsTest on IBM iseries - ASF JIRA

    apache.org | 1 year ago
    java.sql.SQLException: Cannot create an instance of generated class org.apache.derby.exe.acd83d18d1x0120x62bdx2dffxffffb19003081.
  3. 0

    [MenuMgmt] Exception in menu contribution causes workbench to fail to start

    Eclipse Bugzilla | 1 decade ago | john.arthorne
    java.lang.VerifyError: class load failed (class: org/eclipse/ui/internal/newbuild/BuildSetAction method: addAllProjects(Lorg/eclipse/core/resources/IProject;Ljava/util/HashSet;)V) at pc: 58
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Got a Problem with attachment, PLEASE HELP!!!!

    Oracle Community | 10 years ago | 843830
    java.lang.VerifyError: javax/mail/internet/MimeBodyPart.setDataHandler(Ljavax/activation/DataHandler;)V

    Root Cause Analysis

    1. java.lang.VerifyError

      field not type compatible (class: org/apache/xerces/parsers/IntegratedParserConfiguration method: configurePipeline()V) at pc: 4" I thought that it was just the xalan.jar that was upsetting the process but it does in fact seem to be both that, and the "xercesImpl.jar". On the enhancer I have got it to work by re-building without the enhancer addded to the build. Then enhancing each project individually using the ant task. I am still unable however to add the enhancer to the build using the plugin and then re-build all. this will return me the same jdoGetManagedFieldCount error, even if I have re-built without the enhancer previously. This all seems a little awkward, so if there is something I can do to get the build to work with the plugin, and using the enhancer, that would be ideal. Marc Prud'hommeaux wrote: BD- The build problems sound to me like some of your persistent classes have been recompiled, but others have not. Have you tried completely rebuilding all the classes in your project before doing any enhancement? In addition when I was migrating the metadata, I had problems with the Apache libraries, which caused a failure when I ran the "migrate-meta" task. I ended up replacing the two files (xalan.jar and xercesImpl.jar) that were packaged with Kodo3 with ones from our previous Kodo install and the migrate worked fine. Is there a problem with these files? We did upgrade the version of xercesImpl.jar we ship with 3.0, but I would be surprised if this would cause problems. Can you post the exception you get when you try to use the old jars? In article < bqdvtj$ei5$1@solarmetric.netmar.com >, BD wrote: Kodo version 3.0.0 / using IBM Websphere/Eclipse I am testing a migration to Kodo 3, and I am having problems with enhancing when building the project using the plug-in. The error returned is shown below... Problems occurred building the selected resources. packagedesc/ta/event/Bean.jdoGetManagedFieldCount()I Also, I have attempted to enhance the project using the ANT task, but that also fails with the following error trace. java.lang.NoSuchMethodError: packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V

      at java.lang.Throwable.<init>()
    2. Java RT
      Throwable.<init>
      1. java.lang.Throwable.<init>(Throwable.java)
      2. java.lang.Throwable.<init>(Throwable.java)
      2 frames