Kodo 4.1...Eclipse

Does an eclipse plugin exist for the Kodo 4.1.4? I can't find the plugins directory or installation instructions. Am I missing something?

Does an eclipse plugin exist for the Kodo 4.1.4? I can't find the plugins directory or installation instructions. Am I missing something?

Similar Messages

  • Kodo 4.0/ Eclipse Plugin problems

    Hi,
    I have added Kodo plugin (2.1.0) to Eclipse (3.1.1) plugin folder as
    described in the manual. I've also copied all the Kodo libraries and
    classes12.jar into Eclipse\plugins\kodo.eclipse_2.1.0 and modified
    plugin.xml.
    I can see the menu item "Kodo" in Eclipse, but I can't start the Kodo
    preferences under Windows->Preferences. Following Error:
    Plug-in kodo was unable to load class
    kodo.jdbc.integration.eclipse.KodoPlugin.
    Does anyone have an idea?
    Thanks,
    Ingo Schneider

    Schneider wrote:
    Hi,
    I have added Kodo plugin (2.1.0) to Eclipse (3.1.1) plugin folder as
    described in the manual. I've also copied all the Kodo libraries and
    classes12.jar into Eclipsepluginskodo.eclipse_2.1.0 and modified
    plugin.xml.
    I can see the menu item "Kodo" in Eclipse, but I can't start the Kodo
    preferences under Windows->Preferences. Following Error:
    Plug-in kodo was unable to load class
    kodo.jdbc.integration.eclipse.KodoPlugin.
    Does anyone have an idea?
    Thanks,
    Ingo SchneiderI use http://www.eclipse.org/dali plugin for EJB3-persistence. It allows
    me to have different EJB3 vendors. KODO was ok for me to work with.

  • Kodo plugin for eclipse 3.1.2 : does it work ?

    hi,
    i have installed the plugin in my Eclipse plugins directory but i still
    cannot see it in Eclipse IDE.
    I tried to change perspectives, and customize it, i dont see any KODO
    views.
    Nothing.
    Does anyone know if it's bugging, or what i can do to make it work ?
    Thanks

    Are you sure that you've copied the needed jars into the plugin
    directory? I mean not only the pluing jar but also jdo-1.0.2.jar and
    kodo-run.jar, etc. You can find the list of the needed jars in plugin.xml

  • Kodo 3.1.12 and Eclipse

    Hi,
    I have added Kodo plugin to Eclipse (version 3) . I have added Kodo
    enhancer to Build sequence for the project. However when I run build I get
    an error and eclipse log file has following exception:
    ava.lang.NoClassDefFoundError: org/apache/log4j/Category
         at
    com.solarmetric.log.Log4JLogFactory.newLogAdapter(Log4JLogFactory.java:19)
         at com.solarmetric.log.LogFactoryAdapter.getLog(LogFactoryAdapter.java:25)
         at
    com.solarmetric.conf.ConfigurationImpl.getLog(ConfigurationImpl.java:115)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2168)
         at
    kodo.jdbc.integration.eclipse.EnhancerBuilder.build(EnhancerBuilder.java:40)
         at
    org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
         at
    org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268)
         at
    org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297)
         at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:198)
         at
    org.eclipse.ui.actions.GlobalBuildAction$1.run(GlobalBuildAction.java:182)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
    I have copied the log4j jar to kodo plugin directory and added libarary
    tag to plugin.xml as following:
         <library name="log4j-1.2.8.jar"/>
    What am I doing wrong?

    Mark,
    Here is my plugin.xml. classes12.jar is in the same directory as the
    plugin.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <plugin id="kodo"
         name="%name"
         version="1.0.1"
         provider-name="%provider-name"
         class="kodo.jdbc.integration.eclipse.KodoPlugin">
         <runtime>
         <!--
         Put your jdbc driver in this directory and enter the filename
         here (and configure in Preferences the changes you make) -->
              <library name="classes12.jar"/>
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
              <library name="kodo-jdo.jar"/>
              <library name="jakarta-commons-collections-2.1.jar"/>
              <library name="jakarta-commons-lang-1.0.1.jar"/>
              <library name="jakarta-commons-pool-1.0.1.jar"/>
              <library name="jakarta-regexp-1.1.jar"/>
              <library name="jca1.0.jar"/>
              <library name="jdbc2_0-stdext.jar"/>
              <library name="jdo-1.0.1.jar"/>
              <library name="jta-spec1_0_1.jar"/>
              <library name="xalan.jar"/>
              <library name="xercesImpl.jar"/>
              <library name="xml-apis.jar"/>
              <library name="jfreechart-0.9.16.jar"/>
              <library name="jcommon-0.9.1.jar"/>
              <library name="mx4j-admb.jar"/>
              <library name="mx4j-jmx.jar"/>
              <library name="mx4j-tools.jar"/>
              <library name="jline.jar"/>
              <library name="sqlline.jar"/>
         </runtime>
         <requires>
              <import plugin="org.eclipse.ui"/>
              <import plugin="org.eclipse.core.resources"/>
              <import plugin="org.eclipse.jdt.core"/>
              <import plugin="org.eclipse.jdt.launching"/>
         </requires>
         <extension point="org.eclipse.ui.actionSets">
              <actionSet id="kodo.jdbc.integration.eclipse.actionSet"
                   label="%action-set-name"
                   visible="true">
                   <menu id="kodo.menu"
                        label="%group-label">
                        <separator name="baseGroup"/>
                   </menu>
                   <action id="kodo.removeBuilder"
                        label="%remove-builder-label"
              class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
                        tooltip="%remove-builder-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        enablesFor="1">
                   </action>
                   <action id="kodo.addbuilder"
                        label="%add-builder-label"
                   class="kodo.jdbc.integration.eclipse.AddBuilderAction"
                        tooltip="%add-builder-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        enablesFor="1">
                   </action>
                   <action id="kodo.mapping.build"
                        label="%mapping-build-label"
                        tooltip="%mapping-build-tooltip"
                   class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
                        icon="icons/BuildSchemaMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="+">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.mapping.drop"
                        label="%mapping-drop-label"
                        tooltip="%mapping-drop-tooltip"
                        class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
                        icon="icons/DropMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="+">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.mapping.refresh"
                        label="%mapping-refresh-label"
                        tooltip="%mapping-refresh-tooltip"
              class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
                        icon="icons/RefreshMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="+">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.enhance"
                        label="%enhance-label"
                        icon="icons/EnhancerAction.gif"
                   class="kodo.jdbc.integration.eclipse.EnhancerAction"
                        tooltip="%enhance-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="+">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
              </actionSet>
         </extension>
         <!-- lock our actions into the base perspective -->
         <extension point="org.eclipse.ui.perspectiveExtensions">
              <perspectiveExtension targetID="org.eclipse.ui.resourcePerspective">
                   <actionSet
                        id="kodo.jdbc.integration.eclipse.actionSet">
                   </actionSet>
              </perspectiveExtension>
         </extension>
         <!-- put our extensions in -->
         <extension point="org.eclipse.ui.preferencePages">
              <page name="%preference-name"
                   class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
                   id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
              </page>
         </extension>
         <!-- lock in our eclipse-generated xml editor -->
         <extension point="org.eclipse.ui.editors">
              <editor name="%mappingeditor-name" extensions="mapping"
                   icon="icons/mapping.gif"
                   contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
                   class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
                   id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
              </editor>
              <editor name="%editor-name" extensions="jdo,schema"
                   icon="icons/metadata.gif"
                   contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
                   class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
                   id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
              </editor>
         </extension>
         <!-- lock in our "view" -->
         <extension point="org.eclipse.ui.views">
              <view id="kodo.jdbc.integration.eclipse.KodoView"
                   name="%view-name"
                   category="org.eclipse.jdt.ui.java"
                   icon="icons/kodosmall.gif"
                   class="kodo.jdbc.integration.eclipse.KodoView">
              </view>
         </extension>
         <!-- lock in our builder -->
         <extension point="org.eclipse.core.resources.builders"
              id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
              name="%builder-name">
              <builder>
                   <run
                   class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
                   </run>
              </builder>
         </extension>
         <!-- put our view onto the bottom bar -->
         <extension point="org.eclipse.ui.perspectiveExtensions">
              <perspectiveExtension
                   targetID="org.eclipse.debug.ui.DebugPerspective">
                   <view id="kodo.jdbc.integration.eclipse.KodoView"
                        relative="org.eclipse.debug.ui.ExpressionView"
                        relationship="stack"/>
                   <viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
              </perspectiveExtension>
         </extension>
    </plugin>
    Marc Prud'hommeaux wrote:
    Genna-
    Can you post your plugin.xml file? The majority of the time, this
    problem is because of an error in the configuration file.
    In article <[email protected]>, Genna Reingold wrote:
    Ok,
    I have found where log4j was coming from - I have selected my runtime
    Kodo property file in Kodo preferences. Removing reference to property
    file fixed the problem. However I have another issue now. When I run
    refresh mapping I get following error:
    <error>-An error occurred running MappingTool
         kodo.util.FatalDataStoreException: oracle.jdbc.OracleDriver
    NestedThrowables:
    java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
    I have upgraded to Kodo 3.1.15, I'm using latest Eclipse 3.0. I have
    copied classes12.jar to plugin directory and modified plugin.xml as
    prescribed in the manual.
    Stephen Kim wrote:
    Genna,
    Also note that the Eclipse plugin uses its own logging mechanism.
    Setting a kodo.Log property for the plugin's property file will not
    change the way in which the plugin logs messages (you may want to have
    an Eclipse specific property file with the Log property removed).
    Marc Prud'hommeaux wrote:
    Genna-
    It sounds like Eclipse might have an older version of the log4j jar
    file. Can you check to see if there are any other "log4j" jars in
    Eclipse's environment?
    Also, what version of Kodo are you using? Can you try with the latest
    release (3.1.5)?
    Finally, can you ensure that you are using the final 3.0 release of
    Eclipse, and not one of the betas? There are some known problems with
    some of the 3.0 betas.
    In article <[email protected]>, Genna Reingold wrote:
    Hi,
    I have added Kodo plugin to Eclipse (version 3) . I have added Kodo
    enhancer to Build sequence for the project. However when I run build I
    get
    an error and eclipse log file has following exception:
    ava.lang.NoClassDefFoundError: org/apache/log4j/Category
         atcom.solarmetric.log.Log4JLogFactory.newLogAdapter(Log4JLogFactory.java:19)
         at
    com.solarmetric.log.LogFactoryAdapter.getLog(LogFactoryAdapter.java:25)
         atcom.solarmetric.conf.ConfigurationImpl.getLog(ConfigurationImpl.java:115)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2168)
         at
    kodo.jdbc.integration.eclipse.EnhancerBuilder.build(EnhancerBuilder.java:40)
         at
    org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
         at
    org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268)
         at
    org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297)
         at
    org.eclipse.core.internal.resources.Workspace.build(Workspace.java:198)
         atorg.eclipse.ui.actions.GlobalBuildAction$1.run(GlobalBuildAction.java:182)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
    I have copied the log4j jar to kodo plugin directory and added libarary
    tag to plugin.xml as following:
         <library name="log4j-1.2.8.jar"/>
    What am I doing wrong?
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com
    Marc Prud'hommeaux
    SolarMetric Inc.

  • Kodo 3.1.4 and Eclipse plugin

    I'm currently migrating from Kodo 2.5.3 to Kodo 3.1.4, and as I'm using
    Eclipse have decided to give the Eclipse plugin a go. I've followed the
    documentation (@15.6), and am now attempting the Eclipse Sample from the
    documentation (@15.6.4). The documentation has seemed slightly incomplete,
    but I assume that's just me using Eclipse 3.0 with the doumentation being
    written for WSAD 4.
    However, when I clean the project or run the enhancer I get the following
    error:
    <error>-The Enhancer failed. The message included was:
    {0}
         org.apache.commons.lang.exception.NestableRuntimeException: Animal
    <info>-Done.
    This message doesn't seem to be giving me any info that would help me
    track down the problem, so hopefully somebody has seen it beforehand in
    these circumstances and can help me out?
    Cheers,
    Matt

    Stephen, the stack trace is as below. Apparently the Animal class isn't
    being found...? - How does the Kodo plugin look for / find it? - Eclipse
    itself has no trouble compiling it. Do I need to somehow configure my
    classpath separately for the Kodo plugin?
    !MESSAGE Errors running builder "Kodo Enhancer Builder" on project Kodo
    Pet Shop.
    !SUBENTRY 1 kodo 4 0 Aug 10, 2004 16:27:52.687
    !MESSAGE The Enhancer failed. The message included was:
    org.apache.commons.lang.exception.NestableRuntimeException: Animal
    !STACK 0
    java.lang.ClassNotFoundException: Animal
         at
    kodo.enhance.TemporaryClassLoader.loadClass(TemporaryClassLoader.java:49)
         at
    kodo.enhance.TemporaryClassLoader.loadClass(TemporaryClassLoader.java:27)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:217)
         at serp.util.Strings.toClass(Strings.java:160)
         at
    com.solarmetric.meta.ClassArgParser.parseClasses(ClassArgParser.java:77)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2176)
         at
    kodo.jdbc.integration.eclipse.EnhancerBuilder.build(EnhancerBuilder.java:40)
         at
    org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
         at
    org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268)
         at
    org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297)
         at
    org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155)
         at
    org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
    rethrown as org.apache.commons.lang.exception.NestableRuntimeException:
    Animal
         at serp.util.Strings.toClass(Strings.java:164)
         at
    com.solarmetric.meta.ClassArgParser.parseClasses(ClassArgParser.java:77)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2176)
         at
    kodo.jdbc.integration.eclipse.EnhancerBuilder.build(EnhancerBuilder.java:40)
         at
    org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:564)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:157)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:249)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
         at
    org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:229)
         at
    org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:615)
         at org.eclipse.core.runtime.Platform.run(Platform.java:747)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:232)
         at
    org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:268)
         at
    org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:297)
         at
    org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:155)
         at
    org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:212)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
    Caused by: java.lang.ClassNotFoundException: Animal
         at
    kodo.enhance.TemporaryClassLoader.loadClass(TemporaryClassLoader.java:49)
         at
    kodo.enhance.TemporaryClassLoader.loadClass(TemporaryClassLoader.java:27)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:315)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:217)
         at serp.util.Strings.toClass(Strings.java:160)
         ... 18 more
    ==================
    Stephen Kim wrote:
    Matt,
    you should see a stack trace in workspace/.metadata/.log. Can you send
    us the error so that we can fix the reproting?

  • "No suitable driver" error using Kodo 3.1.0, MySQL Connector/J & eclipse 3.0M8

    Hi,
    I'm getting the following error when trying to use the mapping tool from
    within eclipse 3.0M8:
    <error>-An error occurred running MappingTool
    kodo.util.FatalDataStoreException: No suitable driver
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    <info>-Done.
    I followed the instructions on using the eclipse plugin, including copying
    all jars from kodo's lib folder to the plugin folder, copying the MySQL
    Connector/J jar to the kodo plugin folder, adding all of those jars to the
    project classpath, and even added an entry to the plugin.xml file to
    include the MySQL Connector/J jar. If I remove the project reference to
    the MySQL Connector/J jar, the error changes to:
    <error>-An error occurred running MappingTool
    kodo.util.FatalDataStoreException: com.mysql.jdbc.Driver
    NestedThrowables:
    java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
    <info>-Done.
    This would imply that adding a <library> entry for the MySQL Connector/J
    jar in my plugin.xml does not have any effect; if I remove it, I see the
    same error as above. If I add the MySQL jar back to the project
    classpath, the error changes back to 'No suitable driver' as above.
    The behavior is the same whether I use the Kodo preferences
    (Window\Preferences\Kodo Preferences) individually without a
    kodo.properties file, or when I clear all individual properties and
    indicate a kodo.properties file.
    Help?
    Thanks,
    Matthew
    Here's my kodo.properties file:
    # Kodo JDO Properties configuration
    kodo.LicenseKey: xxx
    javax.jdo.PersistenceManagerFactoryClass:
    kodo.jdbc.runtime.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName: com.mysql.jdbc.Driver
    javax.jdo.option.ConnectionUserName: root
    javax.jdo.option.ConnectionPassword:
    javax.jdo.option.ConnectionURL: jdbc:mysql://localhost/kodo
    javax.jdo.option.Optimistic: true
    javax.jdo.option.RetainValues: true
    javax.jdo.option.NontransactionalRead: true
    kodo.Log: DefaultLevel=WARN, Runtime=INFO, Tool=INFO
    Here's my eclipse-3.0M8/plugins/kodo.eclipse_2.1.0/plugin.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <plugin id="kodo"
    name="%name"
    version="1.0.1"
    provider-name="%provider-name"
    class="kodo.jdbc.integration.eclipse.KodoPlugin">
    <runtime>
    <!--
    Put your jdbc driver in this directory and enter the filename
    here (and configure in Preferences the changes you make) -->
    <!--<library name="jdbc-hsql-1_7_0.jar"/>-->
    <library name="mysql-connector-java-3.0.11-stable-bin.jar"/>
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <library name="kodo-jdo.jar"/>
    <library name="jakarta-commons-collections-2.1.jar"/>
    <library name="jakarta-commons-lang-1.0.1.jar"/>
    <library name="jakarta-commons-pool-1.0.1.jar"/>
    <library name="jakarta-regexp-1.1.jar"/>
    <library name="jca1.0.jar"/>
    <library name="jdbc2_0-stdext.jar"/>
    <library name="jdo-1.0.1.jar"/>
    <library name="jta-spec1_0_1.jar"/>
    <library name="xalan.jar"/>
    <library name="xercesImpl.jar"/>
    <library name="xml-apis.jar"/>
    <library name="jfreechart-0.9.16.jar"/>
    <library name="jcommon-0.9.1.jar"/>
    <library name="mx4j-admb.jar"/>
    <library name="mx4j-jmx.jar"/>
    <library name="mx4j-tools.jar"/>
    <library name="jline.jar"/>
    <library name="sqlline.jar"/>
    </runtime>
    <requires>
    <import plugin="org.eclipse.ui"/>
    <import plugin="org.eclipse.core.resources"/>
    <import plugin="org.eclipse.jdt.core"/>
    <import plugin="org.eclipse.jdt.launching"/>
    </requires>
    <extension point="org.eclipse.ui.actionSets">
    <actionSet id="kodo.jdbc.integration.eclipse.actionSet"
    label="%action-set-name"
    visible="true">
    <menu id="kodo.menu"
    label="%group-label">
    <separator name="baseGroup"/>
    </menu>
    <action id="kodo.removeBuilder"
    label="%remove-builder-label"
    class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
    tooltip="%remove-builder-tooltip"
    menubarPath="kodo.menu/baseGroup"
    enablesFor="1">
    </action>
    <action id="kodo.addbuilder"
    label="%add-builder-label"
    class="kodo.jdbc.integration.eclipse.AddBuilderAction"
    tooltip="%add-builder-tooltip"
    menubarPath="kodo.menu/baseGroup"
    enablesFor="1">
    </action>
    <action id="kodo.mapping.build"
    label="%mapping-build-label"
    tooltip="%mapping-build-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
    icon="icons/BuildSchemaMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.mapping.drop"
    label="%mapping-drop-label"
    tooltip="%mapping-drop-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
    icon="icons/DropMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.mapping.refresh"
    label="%mapping-refresh-label"
    tooltip="%mapping-refresh-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
    icon="icons/RefreshMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.enhance"
    label="%enhance-label"
    icon="icons/EnhancerAction.gif"
    class="kodo.jdbc.integration.eclipse.EnhancerAction"
    tooltip="%enhance-tooltip"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    </actionSet>
    </extension>
    <!-- lock our actions into the base perspective -->
    <extension point="org.eclipse.ui.perspectiveExtensions">
    <perspectiveExtension
    targetID="org.eclipse.ui.resourcePerspective">
    <actionSet
    id="kodo.jdbc.integration.eclipse.actionSet">
    </actionSet>
    </perspectiveExtension>
    </extension>
    <!-- put our extensions in -->
    <extension point="org.eclipse.ui.preferencePages">
    <page name="%preference-name"
    class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
    id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
    </page>
    </extension>
    <!-- lock in our eclipse-generated xml editor -->
    <extension point="org.eclipse.ui.editors">
    <editor name="%mappingeditor-name" extensions="mapping"
    icon="icons/mapping.gif"
    contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
    class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
    id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
    </editor>
    <editor name="%editor-name" extensions="jdo,schema"
    icon="icons/metadata.gif"
    contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
    class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
    id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
    </editor>
    </extension>
    <!-- lock in our "view" -->
    <extension point="org.eclipse.ui.views">
    <view id="kodo.jdbc.integration.eclipse.KodoView"
    name="%view-name"
    category="org.eclipse.jdt.ui.java"
    icon="icons/kodosmall.gif"
    class="kodo.jdbc.integration.eclipse.KodoView">
    </view>
    </extension>
    <!-- lock in our builder -->
    <extension point="org.eclipse.core.resources.builders"
    id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
    name="%builder-name">
    <builder>
    <run
    class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
    </run>
    </builder>
    </extension>
    <!-- put our view onto the bottom bar -->
    <extension point="org.eclipse.ui.perspectiveExtensions">
    <perspectiveExtension
    targetID="org.eclipse.debug.ui.DebugPerspective">
    <view id="kodo.jdbc.integration.eclipse.KodoView"
    relative="org.eclipse.debug.ui.ExpressionView"
    relationship="stack"/>
    <viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
    </perspectiveExtension>
    </extension>
    </plugin>

    I am not using Eclipse but am also experiencing problems similar to those
    described below. The fact is I cannot validate a configuration file which
    specifies either a traditional MySQL driver or a MySQL DataSoure.
    I am using what I believe to be the official stable version of MySQL
    Connector/J which is 3.0.11 and has been for several months. Are you
    saying that 3.0.11 (or even 3.0.8) is not supported?
    3.0.12 was recently released as the latest stable version so 3.0.11 should
    at least be supported by now.
    -Neil
    Stephen Kim wrote:
    The milestones are not fully supported versions as they are of beta
    quality. I would suggest using a proper release instead.
    Wolfgang Kundrus wrote:
    Hi,
    I have excactly the same behaviour here with Eclipse 3.0M8 and MySQL. It
    is the same with 3.0.8. and 3.0.11. What is the solution ?
    Best regards
    Wolfgang Kundrus
    Marc Prud'hommeaux wrote:
    Matthew-
    Everything looks correct to me. If you try an older version of the MySQL
    driver (such as 3.0.8, which is what we test with), do you see anything
    different?
    If you try to run a stand-alone Kodo program using the MySQL driver, do
    you see the same exception? If so, can you post the complete stack
    trace?
    In article <[email protected]>, Matthew T. Adams wrote:
    Hi,
    I'm getting the following error when trying to use the mapping tool from
    within eclipse 3.0M8:
    <error>-An error occurred running MappingTool
    kodo.util.FatalDataStoreException: No suitable driver
    NestedThrowables:
    java.sql.SQLException: No suitable driver
    <info>-Done.
    I followed the instructions on using the eclipse plugin, including copying
    all jars from kodo's lib folder to the plugin folder, copying the MySQL
    Connector/J jar to the kodo plugin folder, adding all of those jars to the
    project classpath, and even added an entry to the plugin.xml file to
    include the MySQL Connector/J jar. If I remove the project reference to
    the MySQL Connector/J jar, the error changes to:
    <error>-An error occurred running MappingTool
    kodo.util.FatalDataStoreException: com.mysql.jdbc.Driver
    NestedThrowables:
    java.lang.ClassNotFoundException: com.mysql.jdbc.Driver
    <info>-Done.
    This would imply that adding a <library> entry for the MySQL Connector/J
    jar in my plugin.xml does not have any effect; if I remove it, I see the
    same error as above. If I add the MySQL jar back to the project
    classpath, the error changes back to 'No suitable driver' as above.
    The behavior is the same whether I use the Kodo preferences
    (WindowPreferencesKodo Preferences) individually without a
    kodo.properties file, or when I clear all individual properties and
    indicate a kodo.properties file.
    Help?
    Thanks,
    Matthew
    Here's my kodo.properties file:
    # Kodo JDO Properties configuration
    kodo.LicenseKey: xxx
    javax.jdo.PersistenceManagerFactoryClass:
    kodo.jdbc.runtime.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName: com.mysql.jdbc.Driver
    javax.jdo.option.ConnectionUserName: root
    javax.jdo.option.ConnectionPassword:
    javax.jdo.option.ConnectionURL: jdbc:mysql://localhost/kodo
    javax.jdo.option.Optimistic: true
    javax.jdo.option.RetainValues: true
    javax.jdo.option.NontransactionalRead: true
    kodo.Log: DefaultLevel=WARN, Runtime=INFO, Tool=INFO
    Here's my eclipse-3.0M8/plugins/kodo.eclipse_2.1.0/plugin.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <plugin id="kodo"
    name="%name"
    version="1.0.1"
    provider-name="%provider-name"
    class="kodo.jdbc.integration.eclipse.KodoPlugin">
    <runtime>
    <!--
    Put your jdbc driver in this directory and enter the filename
    here (and configure in Preferences the changes you make) -->
    <!--<library name="jdbc-hsql-1_7_0.jar"/>-->
    <library name="mysql-connector-java-3.0.11-stable-bin.jar"/>
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <!-- ########### do not modify below ######### -->
    <library name="kodo-jdo.jar"/>
    <library name="jakarta-commons-collections-2.1.jar"/>
    <library name="jakarta-commons-lang-1.0.1.jar"/>
    <library name="jakarta-commons-pool-1.0.1.jar"/>
    <library name="jakarta-regexp-1.1.jar"/>
    <library name="jca1.0.jar"/>
    <library name="jdbc2_0-stdext.jar"/>
    <library name="jdo-1.0.1.jar"/>
    <library name="jta-spec1_0_1.jar"/>
    <library name="xalan.jar"/>
    <library name="xercesImpl.jar"/>
    <library name="xml-apis.jar"/>
    <library name="jfreechart-0.9.16.jar"/>
    <library name="jcommon-0.9.1.jar"/>
    <library name="mx4j-admb.jar"/>
    <library name="mx4j-jmx.jar"/>
    <library name="mx4j-tools.jar"/>
    <library name="jline.jar"/>
    <library name="sqlline.jar"/>
    </runtime>
    <requires>
    <import plugin="org.eclipse.ui"/>
    <import plugin="org.eclipse.core.resources"/>
    <import plugin="org.eclipse.jdt.core"/>
    <import plugin="org.eclipse.jdt.launching"/>
    </requires>
    <extension point="org.eclipse.ui.actionSets">
    <actionSet id="kodo.jdbc.integration.eclipse.actionSet"
    label="%action-set-name"
    visible="true">
    <menu id="kodo.menu"
    label="%group-label">
    <separator name="baseGroup"/>
    </menu>
    <action id="kodo.removeBuilder"
    label="%remove-builder-label"
    class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
    tooltip="%remove-builder-tooltip"
    menubarPath="kodo.menu/baseGroup"
    enablesFor="1">
    </action>
    <action id="kodo.addbuilder"
    label="%add-builder-label"
    class="kodo.jdbc.integration.eclipse.AddBuilderAction"
    tooltip="%add-builder-tooltip"
    menubarPath="kodo.menu/baseGroup"
    enablesFor="1">
    </action>
    <action id="kodo.mapping.build"
    label="%mapping-build-label"
    tooltip="%mapping-build-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
    icon="icons/BuildSchemaMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.mapping.drop"
    label="%mapping-drop-label"
    tooltip="%mapping-drop-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
    icon="icons/DropMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.mapping.refresh"
    label="%mapping-refresh-label"
    tooltip="%mapping-refresh-tooltip"
    class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
    icon="icons/RefreshMappingTool.gif"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    <action id="kodo.enhance"
    label="%enhance-label"
    icon="icons/EnhancerAction.gif"
    class="kodo.jdbc.integration.eclipse.EnhancerAction"
    tooltip="%enhance-tooltip"
    menubarPath="kodo.menu/baseGroup"
    toolbarPath="Normal/Kodo"
    enablesFor="+">
    <selection class="org.eclipse.core.resources.IFile"
    name="*.jdo">
    </selection>
    </action>
    </actionSet>
    </extension>
    <!-- lock our actions into the base perspective -->
    <extension point="org.eclipse.ui.perspectiveExtensions">
    <perspectiveExtension
    targetID="org.eclipse.ui.resourcePerspective">
    <actionSet
    id="kodo.jdbc.integration.eclipse.actionSet">
    </actionSet>
    </perspectiveExtension>
    </extension>
    <!-- put our extensions in -->
    <extension point="org.eclipse.ui.preferencePages">
    <page name="%preference-name"
    class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
    id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
    </page>
    </extension>
    <!-- lock in our eclipse-generated xml editor -->
    <extension point="org.eclipse.ui.editors">
    <editor name="%mappingeditor-name" extensions="mapping"
    icon="icons/mapping.gif"
    contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
    >>
    class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
    id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
    </editor>
    <editor name="%editor-name" extensions="jdo,schema"
    icon="icons/metadata.gif"
    contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
    >>
    class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
    id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
    </editor>
    </extension>
    <!-- lock in our "view" -->
    <extension point="org.eclipse.ui.views">
    <view id="kodo.jdbc.integration.eclipse.KodoView"
    name="%view-name"
    category="org.eclipse.jdt.ui.java"
    icon="icons/kodosmall.gif"
    class="kodo.jdbc.integration.eclipse.KodoView">
    </view>
    </extension>
    <!-- lock in our builder -->
    <extension point="org.eclipse.core.resources.builders"
    id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
    name="%builder-name">
    <builder>
    <run
    class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
    </run>
    </builder>
    </extension>
    <!-- put our view onto the bottom bar -->
    <extension point="org.eclipse.ui.perspectiveExtensions">
    <perspectiveExtension
    targetID="org.eclipse.debug.ui.DebugPerspective">
    <view id="kodo.jdbc.integration.eclipse.KodoView"
    relative="org.eclipse.debug.ui.ExpressionView"
    relationship="stack"/>
    <viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
    </perspectiveExtension>
    </extension>
    </plugin>
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • Enhancer fails in Eclipse, ClassCastException

    I have followed the Eclipse / WebSphere Studio Integration instructions
    (in Developer's Guide).
    When I select the package.jdo file for enhancement, the enhancer fails and
    Eclipse logs the following:
    !ENTRY kodo 4 0 2005-04-10 22:30:06.968
    !MESSAGE The Enhancer failed. The message included was:
    {0}
    !STACK 0
    java.lang.ClassCastException
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at serp.xml.XMLFactory.checkSAXCache(XMLFactory.java:217)
         at serp.xml.XMLFactory.getSAXParser(XMLFactory.java:66)
         at
    com.solarmetric.meta.XMLMetaDataParser.parseNew(XMLMetaDataParser.java:359)
         at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:325)
         at
    com.solarmetric.meta.ClassArgParser.getFromMetaData(ClassArgParser.java:182)
         at
    com.solarmetric.meta.ClassArgParser.parseClassNames(ClassArgParser.java:98)
         at
    com.solarmetric.meta.ClassArgParser.parseClasses(ClassArgParser.java:74)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2657)
         at
    kodo.jdbc.integration.eclipse.EnhancerAction.handleFiles(EnhancerAction.java:27)
         at
    kodo.jdbc.integration.eclipse.AbstractMetadataAction.run(AbstractMetadataAction.java:63)
         at
    org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:244)
         at
    org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:220)
         at
    org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:557)
         at
    org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:507)
         at
    org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:421)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2908)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2541)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1612)
         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1578)
         at
    org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:293)
         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
         at
    org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228)
         at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:333)
         at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:150)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:268)
         at org.eclipse.core.launcher.Main.basicRun(Main.java:260)
         at org.eclipse.core.launcher.Main.run(Main.java:887)
         at org.eclipse.core.launcher.Main.main(Main.java:871)
    I use Eclipse 3.1.0 and Kodo JDO 3.3.1.
    Can anyone explain to me why this occurs?
    Best regards
    Jarl

    Thank you, now everything works as expected.
    (A also removed references to these files in relevant plugin.xml file.)
    Can you tell me why it was neccessary to remove these files?
    Stephen Kim wrote:
    You may want to try removing xalan.jar, xml-apis.jar, and xercesImpl.jar
    from Kodo Eclipse plugin directory.
    Circula wrote:
    I have followed the Eclipse / WebSphere Studio Integration instructions
    (in Developer's Guide).
    When I select the package.jdo file for enhancement, the enhancer fails and
    Eclipse logs the following:
    !ENTRY kodo 4 0 2005-04-10 22:30:06.968
    !MESSAGE The Enhancer failed. The message included was:
    !STACK 0
    java.lang.ClassCastException
         at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
         at serp.xml.XMLFactory.checkSAXCache(XMLFactory.java:217)
         at serp.xml.XMLFactory.getSAXParser(XMLFactory.java:66)
         at
    com.solarmetric.meta.XMLMetaDataParser.parseNew(XMLMetaDataParser.java:359)
         at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:325)
         at
    com.solarmetric.meta.ClassArgParser.getFromMetaData(ClassArgParser.java:182)
         at
    com.solarmetric.meta.ClassArgParser.parseClassNames(ClassArgParser.java:98)
         at
    com.solarmetric.meta.ClassArgParser.parseClasses(ClassArgParser.java:74)
         at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2657)
         at
    kodo.jdbc.integration.eclipse.EnhancerAction.handleFiles(EnhancerAction.java:27)
         at
    kodo.jdbc.integration.eclipse.AbstractMetadataAction.run(AbstractMetadataAction.java:63)
         at
    org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:244)
         at
    org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:220)
         at
    org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:557)
         at
    org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:507)
         at
    org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:421)
         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:842)
         at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2908)
         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2541)
         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1612)
         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1578)
         at
    org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:293)
         at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144)
         at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102)
         at
    org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:228)
         at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:333)
         at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:150)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:268)
         at org.eclipse.core.launcher.Main.basicRun(Main.java:260)
         at org.eclipse.core.launcher.Main.run(Main.java:887)
         at org.eclipse.core.launcher.Main.main(Main.java:871)
    I use Eclipse 3.1.0 and Kodo JDO 3.3.1.
    Can anyone explain to me why this occurs?
    Best regards
    Jarl
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • Kodo Error - plug-in

    Kodo plug-in and JBuilder:
    If I create one class with absolutely nothing in it except one declaration:
    private ArrayList test = new ArrayList();
    and then compile that class and then right click on the class and select
    "Create JDO metadata" it successfully creates the the .jdo file
    If I create another class with nothing in it except one declaration:
    private ArrayList<String> test = new ArrayList<String>();
    and then compile that class and then right click on the class and select
    "Create JDO metadata" I get the following Kodo error.
    com.borland.jbuilder.jot.JotParseException: <identifier> expected at line
    24
    at com.borland.jbuilder.jot.src.JotLog.printError(Unknown Source)
    at com.borland.compiler.frontend.Report.error(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.k(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.l(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.addDef(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.a(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.b(Unknown Source)
    at com.borland.jbuilder.jot.src.JotParser.compilationUnit(Unknown Source)
    at com.borland.jbuilder.jot.src.SrcFile.elementParse(Unknown Source)
    at com.borland.jbuilder.jot.src.k.l(Unknown Source)
    at com.borland.jbuilder.jot.src.l.l(Unknown Source)
    at com.borland.jbuilder.jot.src.SrcFile.getPackage(Unknown Source)
    at
    kodo.jdbc.integration.jbuilder.JDOFileNode.getClassName(JDOFileNode.java:286)
    at
    kodo.jdbc.integration.jbuilder.JDOFileNode.getClassName(JDOFileNode.java:300)
    at
    kodo.jdbc.integration.jbuilder.JDOFileNode.assignUrl(JDOFileNode.java:247)
    at
    kodo.jdbc.integration.jbuilder.JDOFileNode.createNewNode(JDOFileNode.java:208)
    at
    kodo.jdbc.integration.jbuilder.JDOFileCreateAction.perform(JDOFileCreateAction.java:52)
    at
    kodo.jdbc.integration.jbuilder.SafeBrowserAction.actionPerformed(SafeBrowserAction.java:70)
    at com.borland.primetime.ide.BrowserAction.actionPerformed(Unknown
    Source)
    at
    com.borland.primetime.actions.ActionMenuItem$2.actionPerformed(Unknown
    Source)
    at
    javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
    at
    javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
    at
    javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
    at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
    at javax.swing.AbstractButton.doClick(AbstractButton.java:302)
    at
    javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1000)
    at
    javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1041)
    at
    java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231)
    at java.awt.Component.processMouseEvent(Component.java:5488)
    at javax.swing.JComponent.processMouseEvent(JComponent.java:3107)
    at java.awt.Component.processEvent(Component.java:5253)
    at java.awt.Container.processEvent(Container.java:1966)
    at java.awt.Component.dispatchEventImpl(Component.java:3955)
    at java.awt.Container.dispatchEventImpl(Container.java:2024)
    at java.awt.Component.dispatchEvent(Component.java:3803)
    at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
    at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
    at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
    at java.awt.Container.dispatchEventImpl(Container.java:2010)
    at java.awt.Window.dispatchEventImpl(Window.java:1825)
    at java.awt.Component.dispatchEvent(Component.java:3803)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
    at
    java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
    at
    java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

    Schneider wrote:
    Hi,
    I have added Kodo plugin (2.1.0) to Eclipse (3.1.1) plugin folder as
    described in the manual. I've also copied all the Kodo libraries and
    classes12.jar into Eclipsepluginskodo.eclipse_2.1.0 and modified
    plugin.xml.
    I can see the menu item "Kodo" in Eclipse, but I can't start the Kodo
    preferences under Windows->Preferences. Following Error:
    Plug-in kodo was unable to load class
    kodo.jdbc.integration.eclipse.KodoPlugin.
    Does anyone have an idea?
    Thanks,
    Ingo SchneiderI use http://www.eclipse.org/dali plugin for EJB3-persistence. It allows
    me to have different EJB3 vendors. KODO was ok for me to work with.

  • Eclipse plug-in error - driver not found error with DB2

    Hi,
    i am using websphere studio developer and the kodo 3.0 implementation.
    I have set up the kodo plug in and i get an error when i try to create the
    database schema:
    kodo.util.FatalDataStoreException: No suitable driver
    It can't find the DB2 driver. This is the information I have in the kodo
    properties:
    javax.jdo.option.ConnectionDriverName: COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL: jdbc:db2:baokodo
    The DB2 driver jar is in the kodo eclipse plugin directory and I am
    referencing this jar file in the plugin xml file.

    The plug in is finding the driver class but it does not like the driver
    for some reason. It tells me no suitable driver found.
    Here is my plugin.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <plugin id="kodo"
         name="%name"
         version="1.0.1"
         provider-name="%provider-name"
         class="kodo.jdbc.integration.eclipse.KodoPlugin">
         <runtime>
              <library name="db2java.jar"/>
              <library name="kodo-jdo.jar"/>
              <library name="jakarta-commons-collections-2.1.jar"/>
              <library name="jakarta-commons-lang-1.0.1.jar"/>
              <library name="jakarta-commons-logging-1.0.3.jar"/>
              <library name="jakarta-commons-pool-1.0.1.jar"/>
              <library name="jakarta-regexp-1.1.jar"/>
              <library name="jca1.0.jar"/>
              <library name="jdbc2_0-stdext.jar"/>
              <library name="jdo-1.0.1.jar"/>
              <library name="jta-spec1_0_1.jar"/>
              <library name="xalan.jar"/>
              <library name="xercesImpl.jar"/>
              <library name="xml-apis.jar"/>
              <library name="jfreechart-0.9.13.jar"/>
              <library name="jcommon-0.8.8.jar"/>
         </runtime>
         <requires>
              <import plugin="org.eclipse.ui"/>
              <import plugin="org.eclipse.core.resources"/>
              <import plugin="org.eclipse.jdt.core"/>
              <import plugin="org.eclipse.jdt.launching"/>
         </requires>
         <extension point="org.eclipse.ui.actionSets">
              <actionSet id="kodo.jdbc.integration.eclipse.actionSet"
                   label="%action-set-name"
                   visible="true">
                   <menu id="kodo.menu"
                        label="%group-label">
                        <separator name="baseGroup"/>
                   </menu>
                   <action id="kodo.removeBuilder"
                        label="%remove-builder-label"
              class="kodo.jdbc.integration.eclipse.RemoveBuilderAction"
                        tooltip="%remove-builder-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        enablesFor="1">
                   </action>
                   <action id="kodo.addbuilder"
                        label="%add-builder-label"
                   class="kodo.jdbc.integration.eclipse.AddBuilderAction"
                        tooltip="%add-builder-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        enablesFor="1">
                   </action>
                   <action id="kodo.mapping.build"
                        label="%mapping-build-label"
                        tooltip="%mapping-build-tooltip"
                   class="kodo.jdbc.integration.eclipse.MappingToolAction$BuildSchema"
                        icon="icons/BuildSchemaMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="1">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.mapping.drop"
                        label="%mapping-drop-label"
                        tooltip="%mapping-drop-tooltip"
                        class="kodo.jdbc.integration.eclipse.MappingToolAction$Drop"
                        icon="icons/DropMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="1">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.mapping.refresh"
                        label="%mapping-refresh-label"
                        tooltip="%mapping-refresh-tooltip"
              class="kodo.jdbc.integration.eclipse.MappingToolAction$Refresh"
                        icon="icons/RefreshMappingTool.gif"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="1">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
                   <action id="kodo.enhance"
                        label="%enhance-label"
                        icon="icons/EnhancerAction.gif"
                   class="kodo.jdbc.integration.eclipse.EnhancerAction"
                        tooltip="%enhance-tooltip"
                        menubarPath="kodo.menu/baseGroup"
                        toolbarPath="Normal/Kodo"
                        enablesFor="1">
                        <selection class="org.eclipse.core.resources.IFile"
                             name="*.jdo">
                        </selection>
                   </action>
              </actionSet>
         </extension>
         <!-- lock our actions into the base perspective -->
         <extension point="org.eclipse.ui.perspectiveExtensions">
              <perspectiveExtension targetID="org.eclipse.ui.resourcePerspective">
                   <actionSet
                        id="kodo.jdbc.integration.eclipse.actionSet">
                   </actionSet>
              </perspectiveExtension>
         </extension>
         <!-- put our extensions in -->
         <extension point="org.eclipse.ui.preferencePages">
              <page name="%preference-name"
                   class="kodo.jdbc.integration.eclipse.KodoPreferencePage"
                   id="kodo.jdbc.integration.eclipse.preferences.KodoPreferencePage">
              </page>
         </extension>
         <!-- lock in our eclipse-generated xml editor -->
         <extension point="org.eclipse.ui.editors">
              <editor name="%mappingeditor-name" extensions="mapping"
                   icon="icons/mapping.gif"
                   contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
                   class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
                   id="kodo.jdbc.integration.eclipse.editor.XMLEditorMapping">
              </editor>
              <editor name="%editor-name" extensions="jdo,schema"
                   icon="icons/metadata.gif"
                   contributorClass="org.eclipse.ui.texteditor.BasicTextEditorActionContributor"
                   class="kodo.jdbc.integration.eclipse.editor.XMLEditor"
                   id="kodo.jdbc.integration.eclipse.editor.XMLEditor">
              </editor>
         </extension>
         <!-- lock in our "view" -->
         <extension point="org.eclipse.ui.views">
              <view id="kodo.jdbc.integration.eclipse.KodoView"
                   name="%view-name"
                   category="org.eclipse.jdt.ui.java"
                   icon="icons/kodosmall.gif"
                   class="kodo.jdbc.integration.eclipse.KodoView">
              </view>
         </extension>
         <!-- lock in our builder -->
         <extension point="org.eclipse.core.resources.builders"
              id="kodo.jdbc.integration.eclipse.EnhancerBuilder"
              name="%builder-name">
              <builder>
                   <run
                   class="kodo.jdbc.integration.eclipse.EnhancerBuilder">
                   </run>
              </builder>
         </extension>
         <!-- put our view onto the bottom bar -->
         <extension point="org.eclipse.ui.perspectiveExtensions">
              <perspectiveExtension
                   targetID="org.eclipse.debug.ui.DebugPerspective">
                   <view id="kodo.jdbc.integration.eclipse.KodoView"
                        relative="org.eclipse.debug.ui.ExpressionView"
                        relationship="stack"/>
                   <viewShortcut id="org.eclipse.jdt.debug.ui.DisplayView"/>
              </perspectiveExtension>
         </extension>
    </plugin>
    Here is the kodo.properties file:
    # Kodo JDO Properties configuration
    # To evaluate or purchase a license key, visit http://www.solarmetric.com
    kodo.LicenseKey: xxxxxxx
    javax.jdo.PersistenceManagerFactoryClass:
    kodo.jdbc.runtime.JDBCPersistenceManagerFactory
    javax.jdo.option.ConnectionDriverName: COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionUserName: db2admin
    javax.jdo.option.ConnectionPassword: db2admin
    javax.jdo.option.ConnectionURL: jdbc:db2:baokodo
    javax.jdo.option.Optimistic: true
    javax.jdo.option.RetainValues: true
    javax.jdo.option.NontransactionalRead: true
    # By default, Kodo stores object-relational mapping information in .mapping
    # files. Other common options are storing the information in a special
    # database table Kodo creates or as extensions in JDO metadata. Uncomment
    # one of the properties below to use one of these options. See the
    reference
    # guide for a full list of mapping factories to choose from.
    #kodo.jdbc.MappingFactory: db
    #kodo.jdbc.MappingFactory: metadata
    # Kodo provides a management / monitoring capability. It can be enabled
    # locally (in the same JVM) by setting the kodo.ManagementUI property to
    # "gui". Remote management / monitoring can be enabled by setting the
    # kodo.ManagementServer property, and by running the remotemanagementtool
    # in another process.
    # kodo.ManagementUI: gui
    # kodo.ManagementServer: true(host="localhost",port=1234)
    Stephen Kim wrote:
    Can you post your plugin.xml? We have tested against WebSphere Studio 4
    and 5.
    TD wrote:
    I am specifying a properties file in the preferences pane.
    Still not sure why this doesn't work...
    Have you been able to get it to work in websphere studio.
    Stephen Kim wrote:
    The plugin does not use any kodo.properties by default. You have to
    configure it through the Preferences pane (which you can point to your
    kodo.properties file)
    TD wrote:
    Hi,
    i am using websphere studio developer and the kodo 3.0 implementation.
    I have set up the kodo plug in and i get an error when i try to create the
    database schema:
    kodo.util.FatalDataStoreException: No suitable driver
    It can't find the DB2 driver. This is the information I have in the kodo
    properties:
    javax.jdo.option.ConnectionDriverName: COM.ibm.db2.jdbc.app.DB2Driver
    javax.jdo.option.ConnectionURL: jdbc:db2:baokodo
    The DB2 driver jar is in the kodo eclipse plugin directory and I am
    referencing this jar file in the plugin xml file.
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • Eclipse plugin output

    I'm having, or at least think I'm having, a problem with the Eclipse
    plugin that I'm hoping somebody can help me with. I'm not getting any sort
    of feedback when I enhance or perform schema operations. The Kodo View in
    Eclipse shows nothing and one or both of the Log/Output panes of the View
    go gray. Shouldn't I expect some sort of output?
    Thanks,
    Scott

    Its probable that when you select yes, that actual work is not getting
    done and the error is not being logged correctly. How did you configure
    your database connection? If you select yes (e.g. actually create the
    tables), can you see the changes being made in the database? If not, are
    you able to connect using Kodo standalone?
    We focus our plugins towards major releases and can't verify our plugin
    compatibility with each minor or milestone release. Sorry about the
    difficulty there. Unfortunately, Eclipse's API often changes drastically
    without notice.
    On Tue, 21 Jan 2003 19:39:21 +0000, Scott Leschke wrote:
    Steve,
    Thanks for the response. I was using the 2.1 M4 release (latest stable)
    but that appears to have a problem with the core Java builder (I got an
    error about an NPE on a full project rebuild, could be interaction the the
    ClearCase plugin). I moved up to the latest integration build, the NPE
    went away but still had the output problems. Today I backed down to the M3
    release where I was, and now get output. I am still a bit confused though,
    when I select one of the schema options, and select \"No\" to the question
    regarding actually altering the schema, I get the following output in the
    Output window.
    <error>-SchemaTool failed. The message included was:
    {0}
    javax.jdo.JDOFataDataStoreException: Io exception: The Network Adapter
    could not establish the connection
    NestedThrowables:
    java.sql.SQLException: Io exception: The Network Adapter could not
    establish the connection
    <info>-Done
    What\'s up with that?
    Scott
    Steve Kim wrote:
    Can you tell me what version of Eclipse you are using? There are some
    known problems with Eclipse 1.0 based IDEs. Also, can you send a
    portion of the log (if any)? The log file is located at
    $ECLIPSE/workbench/.metadata/.log
    Thanks
    Steve
    Scott Leschke wrote:
    I\'m having, or at least think I\'m having, a problem with the Eclipse
    plugin that I\'m hoping somebody can help me with. I\'m not getting any
    sort
    of feedback when I enhance or perform schema operations. The Kodo View in
    Eclipse shows nothing and one or both of the Log/Output panes of the View
    go gray. Shouldn\'t I expect some sort of output?
    Thanks,
    Scott
    Stephen Kim
    [email protected]
    SolarMetric, Inc.
    http://www.solarmetric.com

  • ClassNotFoundException when running Schema tool in Eclipse

    I just installed the Kodo plugin for eclipse (WebSphere Studio Application
    Developer V5.1) and am trying to run the samples. I am using DB2 as the
    persistence database, and I have copied the db2java.zip file to the
    com.solarmetric.kodo_1.0.1 directory within the eclipse plugin. In the Kodo
    preferences, I specified COM.ibm.db2.jdbc.app.DB2Driver as the database
    driver class.
    When I click the Animal.jdo file and select "Add to Database" from the Kodo
    menu, I receive the following error:
    java.lang.ClassNotFoundException: COM.ibm.db2.jdbc.app.DB2Driver
    I have added the db2java.zip file to the build path of the project. What
    else do I have to do to get the schema tool to find the db2java.zip file
    that contains the driver class?
    Merrill Higginson
    Senior Consultant
    Versant Corporation

    You have to edit plugin.xml to include your JBDC driver to the plugin
    classpath. I'm not sure about .jar vs. .zip issues but I think you'll
    be ok either way.
    [email protected] wrote:
    I just installed the Kodo plugin for eclipse (WebSphere Studio Application
    Developer V5.1) and am trying to run the samples. I am using DB2 as the
    persistence database, and I have copied the db2java.zip file to the
    com.solarmetric.kodo_1.0.1 directory within the eclipse plugin. In the Kodo
    preferences, I specified COM.ibm.db2.jdbc.app.DB2Driver as the database
    driver class.
    When I click the Animal.jdo file and select "Add to Database" from the Kodo
    menu, I receive the following error:
    java.lang.ClassNotFoundException: COM.ibm.db2.jdbc.app.DB2Driver
    I have added the db2java.zip file to the build path of the project. What
    else do I have to do to get the schema tool to find the db2java.zip file
    that contains the driver class?
    Merrill Higginson
    Senior Consultant
    Versant Corporation
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

  • Kodoplugin for Eclipse not up to date?

    Hi,
    when installing the kodo-eclipse plugin (yes i also installed a odbc library) there are just errors in the GUI:
    Unable to create view: Plug-in kodo was unable to load class kodo.jdbc.integration.eclipse.KodoView
    I searched through all jar files of kodo, but the class KodoView does not exist at all! It seems to me, that the plugin is designed for the old kodo 3. If yes why is this old plugin still shipped with the current version 4 of kodo? And more interesing, when will there be a new version of the eclipse plugin released?
    Best Wishes
    Sven Weingartner

    Sven-
    Kodo 4.0.0 does not support the old eclipse plugin. Do you see the
    Eclipse plugin in Kodo 4.0.0 anywhere? It should no longer be there.
    The path to Eclipse integration is now done using Kodo integration in
    BEA Weblogic Workshop.
    Sven Weingartner wrote:
    Hi,
    when installing the kodo-eclipse plugin (yes i also installed a odbc library) there are just errors in the GUI:
    Unable to create view: Plug-in kodo was unable to load class kodo.jdbc.integration.eclipse.KodoView
    I searched through all jar files of kodo, but the class KodoView does not exist at all! It seems to me, that the plugin is designed for the old kodo 3. If yes why is this old plugin still shipped with the current version 4 of kodo? And more interesing, when will there be a new version of the eclipse plugin released?
    Best Wishes
    Sven Weingartner

  • Eclipse RCP Application, Plugins and Classloader

    Hi there,
    I'm currently evaluatin KODO within an eclipse RCP application.
    Anything went fine until I started to modularize my classes into
    different plugins.
    Background:
    ===========
    The application consists of a "main" plugin, a "basic persistence layer"
    plugin and an "additional persitent classes" plugin.
    "basic" contains anything for kodo connections and persistence managers
    and some general persitent classes
    "additional" introduces some applicationspecific persitent classes.
    the persistent classes of any plugin are registered using
    "kodo.PersistentClasses".
    I use "kodo.ClassResolver" to point to a class
    "MultiPluginClassResolver" which inherits from
    "MultiLoaderClassResolver" and has the classloader of each plugin
    registered.
    main depends on "basic" and "additional".
    Problem:
    ========
    Whenever I instaniate a PersistenceManager from within plugin "basic"
    kodo throws a ClassNotFoundException as shown below.
    de.bioassay.pla.assay.Assay is a class from plugin "additional"
    What am I missing?
    297 WARN [main] kodo.Runtime - java.lang.ClassNotFoundException:
    de.bioassay.pla.assay.Assay
    java.lang.ClassNotFoundException: de.bioassay.pla.assay.Assay
         at serp.util.MultiClassLoader.findClass(MultiClassLoader.java:230)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
         at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:242)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.loadPersistentClasses(PersistenceManagerFactoryImpl.java:208)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:151)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:104)
         at
    kodo.runtime.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:97)
    regards
    Markus

    Hi again.
    could solve the problem on my own:
    the "additional" plugin didn't have the jdo libraries within the
    runtime classpath. The solution was to export the jdo libraries from
    within the "base" plugin.
    regards
    Markus
    M. Stier schrieb:
    Problem:
    ========
    Whenever I instaniate a PersistenceManager from within plugin "basic"
    kodo throws a ClassNotFoundException as shown below.
    de.bioassay.pla.assay.Assay is a class from plugin "additional"
    What am I missing?

  • Webshpere Studio Site Developer 5.1.1

    We have added the Kodo plug-in as instructed into the C:\Program
    Files\IBM\WebSphere Studio\Site Developer\v5.1.1\eclipse\plugins\
    directory. When you select package.jdo in your project and then "Ehance
    Metadata" menu item of the Kodo menu we get the following error response:
    <error>-The Enhancer failed. The message included was:
    {0}
    org.apache.commons.lang.exception.NestableRuntimeException:
    com.progressive.claims.entities.ProgressivePerson
    <info>-Done.
    if I look in the .log file at ...\My
    Documents\IBM\wssitedev51\workspace\.metadata it shows that the above
    error is a rethrow and that the real error is a class not found exception.
    The ProgressivePerson class is the first defined in the package.jdo file
    driving the enhancement and exists in the project being enhanced. I have
    done a build all prior to trying to enhance.
    I also have Eclipse 2.1 installed elsewhere on my machine, and the exact
    same project and Kodo plug-in installed, works just fine. I need to get
    this working in Websphere Studio... looks like a classpath issue for the
    WSSD initiated Kodo Enhancer....

    Evidently, when the Kodo Enhancer runs it cannot handle this type UNC pathInteresting ... we have not heard of any problems using Kodo against a
    UNC path.
    If you run the enhancer (jdoc.bat) from a command prompt using the UNC
    path, do you still get the same error?
    In article <[email protected]>, Robert Grimwade wrote:
    This issue apparently has been resolved. The default in WebSphere Studio
    is to place the workspace directory in "My
    Documents\IBM\wssitedev51\workspace". On our system this resolves to a
    UNC path such as "\\Server\joeUser\My
    Documents\IBM\wssitedev51\workspace". Evidently, when the Kodo Enhancer
    runs it cannot handle this type UNC path, and needs a specific mapped
    drive path - such as "U:\My Documents\IBM\wssitedev51\workspace". Once
    the default project path is set using a mapped drive, everything seems to
    work just fine. This was the actual difference between the integration of
    Kodo with regular Eclipse and the integration with WebSphere Studio Site
    Developer......
    Robert Grimwade wrote:
    We have added the Kodo plug-in as instructed into the C:Program
    FilesIBMWebSphere StudioSite Developerv5.1.1eclipseplugins
    directory. When you select package.jdo in your project and then "Ehance
    Metadata" menu item of the Kodo menu we get the following error response:
    <error>-The Enhancer failed. The message included was:
    org.apache.commons.lang.exception.NestableRuntimeException:
    com.progressive.claims.entities.ProgressivePerson
    <info>-Done.
    if I look in the .log file at ...My
    DocumentsIBMwssitedev51workspace.metadata it shows that the above
    error is a rethrow and that the real error is a class not found exception.
    The ProgressivePerson class is the first defined in the package.jdo file
    driving the enhancement and exists in the project being enhanced. I have
    done a build all prior to trying to enhance.
    I also have Eclipse 2.1 installed elsewhere on my machine, and the exact
    same project and Kodo plug-in installed, works just fine. I need to get
    this working in Websphere Studio... looks like a classpath issue for the
    WSSD initiated Kodo Enhancer....
    Marc Prud'hommeaux [email protected]
    SolarMetric Inc. http://www.solarmetric.com

  • Kodo 2.5.4 Eclipse plugin.

    Hi,
    I previously used Kodo 2.4.3. The Eclipse plugin with all it's enhancement
    tools worked fine. The size of the com.solarmetric.kodo_1.0.0 plugin is
    6.75 MB.
    The Kodo 2.5.4 plugin doesn't work with Eclipse. The size of the
    com.solarmetric.kodo_1.0.1 plugin is 7.81 KB.
    I've downloaded Kodo 2.5.4 twice and encountered the problem with 2
    different installations.
    regards T Bye

    By what do you mean not work? Does it give you an exception? Have you
    fully uninstalled and re-installed the new com.solar... directory as the
    library requirements are significantly different.
    Tharald B wrote:
    Hi,
    I previously used Kodo 2.4.3. The Eclipse plugin with all it's enhancement
    tools worked fine. The size of the com.solarmetric.kodo_1.0.0 plugin is
    6.75 MB.
    The Kodo 2.5.4 plugin doesn't work with Eclipse. The size of the
    com.solarmetric.kodo_1.0.1 plugin is 7.81 KB.
    I've downloaded Kodo 2.5.4 twice and encountered the problem with 2
    different installations.
    regards T Bye
    Steve Kim
    [email protected]
    SolarMetric Inc.
    http://www.solarmetric.com

Maybe you are looking for

  • Ios 8.3 losing clipboard information

    Since updating to ios 8.3, my clipboard data doesn't seem to stick around.  Almost like theres a timeout.  This is annoying because I use it for inserting the same bit of text quite often. Not a signature, but actually during a login for a game app..

  • Anyone know what this is? "This site is blocked because it is haram.� You must not visit this web site. Baba"

    I am getting the above message on many of the websites that I use, including YouTube, Soundcloud and others. It seems like a virus. I can't access the sites at all - not using Google Chrome or Safari. Anyone know what this isand how to get rid of it?

  • Have lost sound on my hp g6000!

    laptop c. 18 months old always been fine. Suddenly have lost all sound...the 'speaker' icon on bottom right of screen has vanished too. Any help gratefully received please! Best wishes,  Kevin tech 'no' !

  • Stable but not stable?

    Hi, i overclocked my athlon 64 3000+ to 2.4 and ran 24 hours in Prime95 with no problem with htt @ 4x267, but when i play games, there's a weird sound (scary)    and sometimes it freezes for a few seconds. First i thought the htt was too high, so i l

  • Purchase Requisition Closure

    Hi, 1) I have a scenario where a PR is raised for 100 qty of a certain item and released. A PO is then created (based on the PR) for Qty of 70. Now I donu2019t want another PO to be created for the remaining 30 qty (based on the same PR). So is there