Enhance Errors in Kodo 3

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.
[jdoc] java.lang.NoSuchMethodError:
packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V
[jdoc]      at java.lang.Throwable.<init>(Throwable.java)
[jdoc]      at java.lang.Throwable.<init>(Throwable.java)
[jdoc]      at
java.lang.NoSuchMethodError.<init>(NoSuchMethodError.java:56)
[jdoc]      at packagedesc.ta.event.Process.<init>(Process.java:42)
[jdoc]      at packagedesc.ta.event.Process.<clinit>(Process.java)
[jdoc]      at java.lang.Class.initializeImpl(Native Method)
[jdoc]      at java.lang.Class.initialize(Class.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
packagedesc.ta.event.ScheduledEvent.class$(ScheduledEvent.java)
[jdoc]      at
packagedesc.ta.event.ScheduledEvent.<clinit>(ScheduledEvent.java)
[jdoc]      at java.lang.Class.initializeImpl(Native Method)
[jdoc]      at java.lang.Class.initialize(Class.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
serp.util.MultiClassLoader.findClass(MultiClassLoader.java:224)
[jdoc]      at java.lang.ClassLoader.loadClass(ClassLoader.java)
[jdoc]      at java.lang.ClassLoader.loadClass(ClassLoader.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.classForName(CFMetaDataParser.java:214)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.classForName(CFMetaDataParser.java:188)
[jdoc]      at
kodo.meta.JDOMetaDataParser.startCollection(JDOMetaDataParser.java:321)
[jdoc]      at
kodo.meta.JDOMetaDataParser.startClassElement(JDOMetaDataParser.java:194)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.startElement(CFMetaDataParser.java:69)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.startElement(XMLMetaDataParser.java:354)
[jdoc]      at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java)
[jdoc]      at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java)
[jdoc]      at
org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java)
[jdoc]      at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidator.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java)
[jdoc]      at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java)
[jdoc]      at
org.apache.xerces.parsers.XMLParser.parse(XMLParser.java)
[jdoc]      at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java)
[jdoc]      at javax.xml.parsers.SAXParser.parse(SAXParser.java:394)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:309)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:254)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:234)
[jdoc]      at
kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositoryImpl.java:175)
[jdoc]      at
kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.java:129)
[jdoc]      at kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)
[jdoc]      at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2162)
[jdoc]      at
kodo.ant.JDOEnhancerTask.executeOn(JDOEnhancerTask.java:65)
[jdoc]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
[jdoc]      at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
[jdoc]      at org.apache.tools.ant.Task.perform(Task.java:341)
[jdoc]      at org.apache.tools.ant.Target.execute(Target.java:309)
[jdoc]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[jdoc]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[jdoc]      at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
[jdoc]      at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
[jdoc]      at org.apache.tools.ant.Task.perform(Task.java:341)
[jdoc]      at org.apache.tools.ant.Target.execute(Target.java:309)
[jdoc]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[jdoc]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[jdoc]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:571)
[jdoc]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
[jdoc]      at
java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:199)
[jdoc]      at java.lang.reflect.Method.invoke(Method.java)
[jdoc]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
[jdoc]      at
org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
[jdoc]      at java.lang.Thread.run(Thread.java:801)
[jdoc] BUILD FAILED: file:D:/Work/Shared/build.xml:45:
java.lang.NoSuchMethodError:
packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V
the call to the method that fails is shown below:
private Set dependentEvents = new HashSet();
private transient BOSet dependentEventsContext = new BOSet(this);
The method that is being reported in the NoSuchMethodError is shown below.
public BOSet(BusinessObject obj) {
     setParent(obj);
The Business Object being passed into this method is the top level
abstract business object, and all persistable business objects extend this
class.
I don't know that both these errors are the same problem, or whether they
are both different symptoms of another problem.
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?

Marc
I gave the error for the jar file in my second post.....
"BUILD FAILED: 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 <[email protected]>, 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.
[jdoc] java.lang.NoSuchMethodError:
packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V
[jdoc]      at java.lang.Throwable.<init>(Throwable.java)
[jdoc]      at java.lang.Throwable.<init>(Throwable.java)
[jdoc]      at
java.lang.NoSuchMethodError.<init>(NoSuchMethodError.java:56)
[jdoc]      at packagedesc.ta.event.Process.<init>(Process.java:42)
[jdoc]      at packagedesc.ta.event.Process.<clinit>(Process.java)
[jdoc]      at java.lang.Class.initializeImpl(Native Method)
[jdoc]      at java.lang.Class.initialize(Class.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
packagedesc.ta.event.ScheduledEvent.class$(ScheduledEvent.java)
[jdoc]      at
packagedesc.ta.event.ScheduledEvent.<clinit>(ScheduledEvent.java)
[jdoc]      at java.lang.Class.initializeImpl(Native Method)
[jdoc]      at java.lang.Class.initialize(Class.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
serp.util.MultiClassLoader.findClass(MultiClassLoader.java:224)
[jdoc]      at java.lang.ClassLoader.loadClass(ClassLoader.java)
[jdoc]      at java.lang.ClassLoader.loadClass(ClassLoader.java)
[jdoc]      at java.lang.Class.forNameImpl(Native Method)
[jdoc]      at java.lang.Class.forName(Class.java)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.classForName(CFMetaDataParser.java:214)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.classForName(CFMetaDataParser.java:188)
[jdoc]      at
kodo.meta.JDOMetaDataParser.startCollection(JDOMetaDataParser.java:321)
[jdoc]      at
kodo.meta.JDOMetaDataParser.startClassElement(JDOMetaDataParser.java:194)
[jdoc]      at
com.solarmetric.meta.CFMetaDataParser.startElement(CFMetaDataParser.java:69)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.startElement(XMLMetaDataParser.java:354)
[jdoc]      at
org.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java)
[jdoc]      at
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java)
[jdoc]      at
org.apache.xerces.impl.XMLNamespaceBinder.emptyElement(XMLNamespaceBinder.java)
[jdoc]      at
org.apache.xerces.impl.dtd.XMLDTDValidator.emptyElement(XMLDTDValidator.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java)
[jdoc]      at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java)
[jdoc]      at
org.apache.xerces.parsers.StandardParserConfiguration.parse(StandardParserConfiguration.java)
[jdoc]      at
org.apache.xerces.parsers.XMLParser.parse(XMLParser.java)
[jdoc]      at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java)
[jdoc]      at javax.xml.parsers.SAXParser.parse(SAXParser.java:394)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:309)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:254)
[jdoc]      at
com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:234)
[jdoc]      at
kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositoryImpl.java:175)
[jdoc]      at
kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.java:129)
[jdoc]      at kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)
[jdoc]      at kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2162)
[jdoc]      at
kodo.ant.JDOEnhancerTask.executeOn(JDOEnhancerTask.java:65)
[jdoc]      at com.solarmetric.ant.TaskBase.execute(TaskBase.java:105)
[jdoc]      at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
[jdoc]      at org.apache.tools.ant.Task.perform(Task.java:341)
[jdoc]      at org.apache.tools.ant.Target.execute(Target.java:309)
[jdoc]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[jdoc]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[jdoc]      at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:397)
[jdoc]      at
org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:143)
[jdoc]      at org.apache.tools.ant.Task.perform(Task.java:341)
[jdoc]      at org.apache.tools.ant.Target.execute(Target.java:309)
[jdoc]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[jdoc]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[jdoc]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:571)
[jdoc]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
[jdoc]      at
java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:199)
[jdoc]      at java.lang.reflect.Method.invoke(Method.java)
[jdoc]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
[jdoc]      at
org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
[jdoc]      at java.lang.Thread.run(Thread.java:801)
[jdoc] BUILD FAILED: file:D:/Work/Shared/build.xml:45:
java.lang.NoSuchMethodError:
packagedesc/ta/shared/BOSet.<init>(Lpackagedesc/ta/shared/BusinessObject;)V
the call to the method that fails is shown below:
private Set dependentEvents = new HashSet();
private transient BOSet dependentEventsContext = new BOSet(this);
The method that is being reported in the NoSuchMethodError is shown below.
public BOSet(BusinessObject obj) {
     setParent(obj);
The Business Object being passed into this method is the top level
abstract business object, and all persistable business objects extend this
class.
I don't know that both these errors are the same problem, or whether they
are both different symptoms of another problem.
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?
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Similar Messages

  • "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

  • New SOD and enhanced error handling?

    Hi,
    I have been studying the new SOD. It looks very good. The only thing I am missing is enhanced error handling. Has this been dropped or is it under "Numerous functional and performance improvements"?
    Being able to catch exceptions from database triggers etc. is the only bigger flaw I see in this great tool ;-)
    Regards Pete

    Pete,
    Yes we are still intending to enhance our error handling capabilities.
    We have not finalized exactly what enhancements we are making with these yet.
    Regards,
    David
    Message was edited by:
    dpeake

  • EEWB Enhancement Error while adding new field

    Hello Experts ,
                         The requirement is to add the attachment feild in the support desk message screen (CRMD_ORDER) in the Fast track tab , although in the transaction tab already the document option is available for attachments the end user's want it in intial screen.
    I have tried this using EASY ENHANCEMENT WORKBENCH - EEWB as per the suggestions given by experts in SDN,now i face a problem in EEWB .
    I have created a object and extention in EEWB under a project,the it took me to the wizard automatically ,i followed up the notes in wizard  to ADD_NEW_FIELDS and after it is completed, it shows a ERROR message as "Definition CRM_BTX_ADD_NEW_FIELDS is of the type 'TSK' and should run on an external system. This is not permissible. Only definitions of type 'SEQ' may be created for external systems." What does this Error Mean?Should i have to follow any system settings for this?
    Note : I have made the  system settings in EEWC -System Data Maintenence      before enhancement.
    Has any one worked with EEWB to ADD new fields,if so then please give me a solution to solve this problem.
    Thanks & Regards,
    Mohana Priya

    Hi Priya,
    We are also facing similar error in EEWB. If you have solved this problem, please update thread.
    Thanks
    Dhanraj

  • Lookup in Xi using XSLT with Java enhancement "Error"

    Hi Experts,
    I need your advice urgently.
    I have done message mapping using XSLT mapping with Java enhancement.
    I included the code for SAP DB connection to read from the table.
    I imported both the sapdbc-7_6_00_30_5567 Driver.jar and my custom jar into imported archives.
    I used the java functions in my XSLT to get the lookup value.
    The code was working correctly in NWDS, but when i tried to execute the scenario, it gave me 'SYSTEM ERROR'
    Following is the error as seen in SXMB_MONI
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">TRANSFORMER_EXCEPTION</SAP:Code>
      <SAP:P1>PortalTransaction_EP_to_Insert_EP_DB</SAP:P1>
      <SAP:P2>http://ab.com/xys/subscription</SAP:P2>
      <SAP:P3>8abf9c80-ad4a-11db-bb9a-ccaaac110865</SAP:P3>
      <SAP:P4>-1</SAP:P4>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Exception occurred during XSLT mapping of the application</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Following is the DEBUG trace when i tries to test the Interface Mapping
    Creating mapping sequence with 2 steps.
    Creating step 0
    Creating XSLT mapping PortalTransaction_SUBSYS_to_PortalTransaction_EP
    Creating step 1
    Creating XSLT mapping PortalTransaction_EP_to_Insert_EP_DB
    Start executing mapping sequence with 2 steps.
    Executing mapping step 0
    Call XSLT processor with stylsheet PortalTransaction_SUBSYS_to_PortalTransaction_EP.xsl.
    Returned form XSLT processor.
    XSLT transformation: PortalTransaction_SUBSYS_to_PortalTransaction_EP.xsl completed with 0 warning(s).
    Mapping step 0 has been executed.
    Executing mapping step 1
    Call XSLT processor with stylsheet PortalTransaction_EP_to_Insert_EP_DB.xsl.
    Loaded class com.cityandguilds.clasp.xi.DateTimeFunctions
    Method fatalError called, terminate transformation
    javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:251) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:65) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) ... 19 more Caused by: java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) ... 34 more -
    com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) -
    at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:65) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) ... 34 more
    TransfromerException during XSLT processing:
    javax.xml.transform.TransformerException: com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:251) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:65) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) ... 19 more Caused by: java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) ... 34 more -
    com.sap.engine.lib.xml.util.NestedException: java.lang.ClassNotFoundException: Class doesn't have appropriate method! -> java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) -
    at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:65) at com.sap.engine.lib.xsl.xpath.JLBLibrary.getFunction(JLBLibrary.java:107) at com.sap.engine.lib.xsl.xpath.LibraryManager.getFunction(LibraryManager.java:76) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:98) at com.sap.engine.lib.xsl.xpath.ETFunction.evaluate(ETFunction.java:83) at com.sap.engine.lib.xsl.xpath.XPathProcessor.innerProcess(XPathProcessor.java:56) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:43) at com.sap.engine.lib.xsl.xpath.XPathProcessor.process(XPathProcessor.java:51) at com.sap.engine.lib.xsl.xslt.XSLVariable.process(XSLVariable.java:132) at com.sap.engine.lib.xsl.xslt.XSLNode.processFromFirst(XSLNode.java:296) at com.sap.engine.lib.xsl.xslt.XSLTemplate.process(XSLTemplate.java:272) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:463) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:431) at com.sap.engine.lib.xsl.xslt.XSLStylesheet.process(XSLStylesheet.java:394) at com.sap.engine.lib.jaxp.TransformerImpl.transformWithStylesheet(TransformerImpl.java:398) at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:240) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingTransformer.transform(RepMappingTransformer.java:150) at com.sap.aii.ibrep.server.mapping.ibrun.RepXSLTMapping.execute(RepXSLTMapping.java:81) at com.sap.aii.ibrep.server.mapping.ibrun.RepSequenceMapping.execute(RepSequenceMapping.java:54) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:167) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.ClassNotFoundException: Class doesn't have appropriate method! at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.init(JLBFunction.java:273) at com.sap.engine.lib.xsl.xpath.functions.JLBFunction.<init>(JLBFunction.java:63) ... 34 more
    17:44:11 End of test
    Thanks in advance,
    Mona

    Hi,
    Thanks to all who replied.
    I solved the problem.
    I was calling the java method from XSLT without passing any arguement.
    I realised that the java methods called from XSLT should always have input parameter. So i changed the javamethod call from
    public static String getCurrentRecNo() to public static String getCurrentRecNo(Object test)
    and it worked.
    Can anybody explain me why java methods called from XSLT should always have an input arguement.
    Thanks
    Mona

  • Structure Enhancement Error Error in Extended Program Check in ECC 6.0

    Hi Experts,
    I am working on ECC 6.0 I am a structure like "BAPIACWT09" , "BAPIACCAIT" in my program when i run Extended Program Check i am getting an error 
    <b>
    "BAPIACWT09" can be enhanced. After a structure enhancement, the semantics of the  parameter transfer may change.</b>
    How to eliminate this Error

    Raghu,
    Every structure has to be created with an enhancement category.
    In Transaction SE11, when you are creating a structure or a table , go to extras - enhancement category to see it.
    I guess BAPIACWT09 has been defined with a category of can be enhanced, and SAP is warning you that if the enhancement is used in the future your program can have syntax errors.
    There is nothing you can do about this.  If you find out something, Please share.

  • Read_text in enhancement error

    when I use FM read_text in my report programe, it's ok. But I use the same parameters for read_text and put the read_text into enhancement QQMA0001, but it has error when running. The error information is CALL_FUNCTION_CONFLICT_LENG.
    Please help me.

    check the fields lengths.
    Regards
    Prabhu

  • R3 Datasource enhancement error

    Hi All
    Please would it be possible to provide advice. I've used RSA6 in R3 to enhance a master data attributes Datasource with a new field and need to code the enhancement. I'm no expert but this is the code I've used:
    TABLE: P0006. 
    DATA: L_TABIX  LIKE SY-TABIX.
    case i_chabasnm.
    *Enhancement of Candidate attributes
    WHEN '0CANDIDATE'.
          CASE i_datasource.
              WHEN '0CANDIDATE_ATTR'.
                  DATA: l_S_rcf_s_bw_0candidate_attr like       
                        rcf_s_bw_0candidate_attr.
                          LOOP AT I_t_data into l_s_rcf_s_bw_0candidate_attr.
                              l_tabix = sy-tabix.
                              SELECT single * from P0006 WHERE LIFNR =
                              l_s_rcf_s_bw_0candidate_attr_s-lfnr.
                                  IF sy-subrc = 0.
                                      l_s_rcf_s_bw_0candidate_attr_s-zzpstlz
                                       = P0006-pstlz.
                                       MODIFY i_t_data from
                                       l_s_rcf_s_bw_0candidate_attr INDEX  l_tabix.
                                   ENDIF.
                             ENDLOOP.
             ENDCASE.
    ENDCASE.                                 
    When I check this code I'm getting a syntax error: '  "P0006" is not defined in the ABAP Dictionary as a table, projection view or database view.' I agree with this, P0006 is a Structure.
    My question is what changes should I therefore make to the code?
    Thank you in advance, hope someone can help will assign points!
    Helen

    Hi Subray
    Many thanks for your response; changing the table/structure to PA0006 fixed the error message:
    "P0006" is not defined in the ABAP Dictionary as a table, projection view or database view.'
    However I'm now getting a new error message. I entered the query on the ABAP forum (with the same subject header) and received a response there, which I'm also looking into.
    Will post any successes with this ABAP thread for completeness in this forum as well.
    Thanks again
    Helen

  • Enhancement Error at Selection Screen of standard program

    Hi, can implicit enhancement be added to selection screen? When I tried to add a parameter after first selection-screen block or inside the block, always get error message during activation. The standard program i try to enhance is report LSO_RHXBUCH0 (Bookings per Participant). I am sure there is no syntax error on the codes I wrote. The error message is "Between "DATA BEGIN OF' name" and "DATA END OF name" only data statements are allowed.
    Here the code, see enhancement: ZIMP_BOOKING_PARTICIPANT
    -v-Block 1-----v-
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
    PARAMETERS pchplvar LIKE pchdy-plvar NO-DISPLAY.         "Planvariante
    PARAMETERS pchotype LIKE pchdy-otype NO-DISPLAY.         "Objekttyp
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS ptyp1 LIKE hrvpv-ptyp1 RADIOBUTTON GROUP xxx. "Objekttyp1
    SELECTION-SCREEN COMMENT 4(22) ptxt1 FOR FIELD ptyp1.
    SELECTION-SCREEN POSITION 27.
    PARAMETERS ptyp2 LIKE hrvpv-ptyp2 RADIOBUTTON GROUP xxx. "Objekttyp2
    SELECTION-SCREEN COMMENT 30(22) ptxt2 FOR FIELD ptyp2.
    SELECTION-SCREEN POSITION 53.
    PARAMETERS ptyp3 LIKE hrvpv-ptyp3 RADIOBUTTON GROUP xxx. "Objekttyp3
    SELECTION-SCREEN COMMENT 56(22) ptxt3 FOR FIELD ptyp3.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS ptyp4 LIKE hrvpv-ptyp4 RADIOBUTTON GROUP xxx. "Objekttyp4
    SELECTION-SCREEN COMMENT 4(22) ptxt4 FOR FIELD ptyp4.
    SELECTION-SCREEN POSITION 27.
    PARAMETERS ptyp5 LIKE hrvpv-ptyp5 RADIOBUTTON GROUP xxx. "Objekttyp5
    SELECTION-SCREEN COMMENT 30(22) ptxt5 FOR FIELD ptyp5.
    SELECTION-SCREEN POSITION 53.
    PARAMETERS ptyp6 LIKE hrvpv-ptyp6 RADIOBUTTON GROUP xxx. "Objekttyp6
    SELECTION-SCREEN COMMENT 56(20) ptxt6 FOR FIELD ptyp6.
    SELECTION-SCREEN PUSHBUTTON 76(4) morepart USER-COMMAND more.
    SELECTION-SCREEN END OF LINE.
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(3 ) Struct. %F4_MACO_TAB, End                                                                                S
    rhx-f4-objid-data.
    SELECT-OPTIONS pchobjid FOR objec-realo NO INTERVALS.      "Teilnehmer
    PARAMETERS pchseark LIKE pchdy-seark.  "Suchbegriff
    PARAMETERS pchostat LIKE pchdy-ostat NO-DISPLAY.         "Objektstatus
    PARAMETERS pchistat LIKE pchdy-istat NO-DISPLAY.          "Datenstatus
    Strukturparameter
    PARAMETERS pchwegid LIKE pchdy-wegid NO-DISPLAY.
    PARAMETERS pchsvect LIKE pchdy-svect NO-DISPLAY.
    PARAMETERS pchactiv LIKE pchdy-activ NO-DISPLAY.
    PARAMETERS pchdepth LIKE pchdy-depth NO-DISPLAY.
    PARAMETERS pchdymod LIKE t77s3-dymod NO-DISPLAY.       "Dynp.variation
    SELECTION-SCREEN END OF BLOCK b1.
    --Block 1------
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Struct. $PCH_TEXTPOOL_KEY, End                                                                                S
    $$-Start: (1 )----
    $$
    ENHANCEMENT 1  ZIMP_BOOKING_PARTICIPANT.    "active version
    *SELECTION-SCREEN BEGIN OF BLOCK bb2.
    PARAMETERS tpchdepth LIKE pchdy-depth NO-DISPLAY.
    *SELECTION-SCREEN END OF BLOCK bb2.
    ENDENHANCEMENT.
    $$-End:   (1 )----
    $$
    rhx-obeg-radios-define.
    -Block 2 (Aufbereitungsoption)-----
    *SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-RB3.
    PARAMETER : tc LIKE pp0j-tc_disp NO-DISPLAY.
    *SELECTION-SCREEN END OF BLOCK B3.

    Hi, can implicit enhancement be added to selection screen? When I tried to add a parameter after first selection-screen block or inside the block, always get error message during activation. The standard program i try to enhance is report LSO_RHXBUCH0 (Bookings per Participant). I am sure there is no syntax error on the codes I wrote. The error message is "Between "DATA BEGIN OF' name" and "DATA END OF name" only data statements are allowed.
    Here the code, see enhancement: ZIMP_BOOKING_PARTICIPANT
    -v-Block 1-----v-
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
    PARAMETERS pchplvar LIKE pchdy-plvar NO-DISPLAY.         "Planvariante
    PARAMETERS pchotype LIKE pchdy-otype NO-DISPLAY.         "Objekttyp
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS ptyp1 LIKE hrvpv-ptyp1 RADIOBUTTON GROUP xxx. "Objekttyp1
    SELECTION-SCREEN COMMENT 4(22) ptxt1 FOR FIELD ptyp1.
    SELECTION-SCREEN POSITION 27.
    PARAMETERS ptyp2 LIKE hrvpv-ptyp2 RADIOBUTTON GROUP xxx. "Objekttyp2
    SELECTION-SCREEN COMMENT 30(22) ptxt2 FOR FIELD ptyp2.
    SELECTION-SCREEN POSITION 53.
    PARAMETERS ptyp3 LIKE hrvpv-ptyp3 RADIOBUTTON GROUP xxx. "Objekttyp3
    SELECTION-SCREEN COMMENT 56(22) ptxt3 FOR FIELD ptyp3.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN BEGIN OF LINE.
    PARAMETERS ptyp4 LIKE hrvpv-ptyp4 RADIOBUTTON GROUP xxx. "Objekttyp4
    SELECTION-SCREEN COMMENT 4(22) ptxt4 FOR FIELD ptyp4.
    SELECTION-SCREEN POSITION 27.
    PARAMETERS ptyp5 LIKE hrvpv-ptyp5 RADIOBUTTON GROUP xxx. "Objekttyp5
    SELECTION-SCREEN COMMENT 30(22) ptxt5 FOR FIELD ptyp5.
    SELECTION-SCREEN POSITION 53.
    PARAMETERS ptyp6 LIKE hrvpv-ptyp6 RADIOBUTTON GROUP xxx. "Objekttyp6
    SELECTION-SCREEN COMMENT 56(20) ptxt6 FOR FIELD ptyp6.
    SELECTION-SCREEN PUSHBUTTON 76(4) morepart USER-COMMAND more.
    SELECTION-SCREEN END OF LINE.
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(3 ) Struct. %F4_MACO_TAB, End                                                                                S
    rhx-f4-objid-data.
    SELECT-OPTIONS pchobjid FOR objec-realo NO INTERVALS.      "Teilnehmer
    PARAMETERS pchseark LIKE pchdy-seark.  "Suchbegriff
    PARAMETERS pchostat LIKE pchdy-ostat NO-DISPLAY.         "Objektstatus
    PARAMETERS pchistat LIKE pchdy-istat NO-DISPLAY.          "Datenstatus
    Strukturparameter
    PARAMETERS pchwegid LIKE pchdy-wegid NO-DISPLAY.
    PARAMETERS pchsvect LIKE pchdy-svect NO-DISPLAY.
    PARAMETERS pchactiv LIKE pchdy-activ NO-DISPLAY.
    PARAMETERS pchdepth LIKE pchdy-depth NO-DISPLAY.
    PARAMETERS pchdymod LIKE t77s3-dymod NO-DISPLAY.       "Dynp.variation
    SELECTION-SCREEN END OF BLOCK b1.
    --Block 1------
    """""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1 ) Struct. $PCH_TEXTPOOL_KEY, End                                                                                S
    $$-Start: (1 )----
    $$
    ENHANCEMENT 1  ZIMP_BOOKING_PARTICIPANT.    "active version
    *SELECTION-SCREEN BEGIN OF BLOCK bb2.
    PARAMETERS tpchdepth LIKE pchdy-depth NO-DISPLAY.
    *SELECTION-SCREEN END OF BLOCK bb2.
    ENDENHANCEMENT.
    $$-End:   (1 )----
    $$
    rhx-obeg-radios-define.
    -Block 2 (Aufbereitungsoption)-----
    *SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-RB3.
    PARAMETER : tc LIKE pp0j-tc_disp NO-DISPLAY.
    *SELECTION-SCREEN END OF BLOCK B3.

  • File adapter module enhancement error

    Hello All,
    We have a EDI scenario where data for 110 is to be transfered to SAP. Here customer is not able to ahead with seeburger hence decided to develope a adapter module. We have done that  and started testing . While testing we are getting a error, in which ":" is field separator which is getting converted to  "[]" . This we found when we debugged module process method. Pl can you suggest why this conversion is happening and how to resolve.
    If you see , When I use only standared sap module file is getting read as it is. There is no such conversion happening.
    Pl can you suggest at the earliest possible.
    thanks,
    Sharada

    Hi,
    I think you have done a typo error. is it not
    localejbs/SeeClassifier classifier*
    To find the correct JNDI lookup name, log in to Visual Administrator of the J2EE Engine and in server node look for the JNDI Registry Service.Spot your desired bean and fetch the whole JNDI name form there.
    Regards,
    Sudharshan N A

  • Enhance errors OS10...3.1

    Hello BlackBerry Support Community Forums
    I will provide two images
    With official OS10.3.1565 for Z10
    Clearly the application "Games" still appears after the upgrade.
    When this application services do not work, and BlackBerry to inform would removed in OS10.3.1.
    I want to also report this bug.
    In BlackBerry Passport icon paste...
    The icon should not be away from the text box...
    Sorry for my bad English...
    I want BlackBerry to work to correct small errors.
    Regards.
    BBM Channels  PIN: C0007093A
    Do not forget to give LIKE    Those people who help you and advise you about your doubts.  if the review has been SOLVED** # 4LL  #ÉliteRoad  Make a backup of your BlackBerry
    BlackBerry Protect and  BlackBerry Link constantly.  #ichooseBlackBerry10 Gutijose14 Forums Veteran I

    hello,
    first for the apps that used scoreloop, I advise you to contact each developer and tell them about those issues. They are supposed to release a new version of their game, without the Scoreloop connectivity.
    For your other apps, please state their version number and where you downloaded them (BB World or snap or Amazon or ?).
    besides, please tell us what OS you have now (give us the Software Release).
    The search box on top-right of this page is your true friend, and the public Knowledge Base too:

  • Kodo in  jbuilder

    I have succeed in creating metedate and mapping and schema in
    kodoworkbench for my project model,but I fail to run the project due to
    kodo enhance. I think that the classes have been enhanced in
    kodoworkbench . why ? the follow is the error message :
    kodo.enhance.JDOEnhancer: kodo.util.FatalException: java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.-NestedThrowables:-java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositoryImpl.java:180)--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.java:129)--at
    kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)--at
    kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2181)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.doBuild(JDOEnhancerTask.java:101)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.build(JDOEnhancerTask.java:74)--at
    com.borland.primetime.build.BuildTask.execute(Unknown Source)--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.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)--at
    org.apache.tools.ant.Task.perform(Task.java:341)--at
    org.apache.tools.ant.Target.execute(Target.java:309)--at
    org.apache.tools.ant.Target.performTasks(Target.java:336)--at
    com.borland.primetime.build.y.executeTarget(Unknown Source)--at
    com.borland.primetime.build.y.executeTargets(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.BuildProcess.run(Unknown Source)--at
    java.lang.Thread.run(Thread.java:534)--Caused by: java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:320)--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:260)--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:240)--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositoryImpl.java:175)--...
    20 more--NestedThrowablesStackTrace:--java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:320)--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:260)--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:240)--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositoryImpl.java:175)--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.java:129)--at
    kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)--at
    kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2181)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.doBuild(JDOEnhancerTask.java:101)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.build(JDOEnhancerTask.java:74)--at
    com.borland.primetime.build.BuildTask.execute(Unknown Source)--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.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)--at
    org.apache.tools.ant.Task.perform(Task.java:341)--at
    org.apache.tools.ant.Target.execute(Target.java:309)--at
    org.apache.tools.ant.Target.performTasks(Target.java:336)--at
    com.borland.primetime.build.y.executeTarget(Unknown Source)--at
    com.borland.primetime.build.y.executeTargets(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.BuildProcess.run(Unknown Source)--at
    java.lang.Thread.run(Thread.java:534)--

    all the classes in the package have been complied , or the classes can
    not be added to the metadata in the workbench .
    Greg Campbell wrote:
    Is the "ProductDeploy" class compiled? The JDOEnhancer works on compiled
    bytecode (ProductDeploy.class) not source code (ProductDeploy.java).
    Thanks,
    Greg
    "qiyongzhen" <[email protected]> wrote in message
    news:[email protected]...
    I have succeed in creating metedate and mapping and schema in
    kodoworkbench for my project model,but I fail to run the project due to
    kodo enhance. I think that the classes have been enhanced in
    kodoworkbench . why ? the follow is the error message :
    kodo.enhance.JDOEnhancer: kodo.util.FatalException: java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.-NestedThrowables:-java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositor
    yImpl.java:180)--at
    >
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.ja
    va:129)--at
    kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)--at
    kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2181)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.doBuild(JDOEnhancerTask.java:
    101)--at
    >
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.build(JDOEnhancerTask.java:74
    )--at
    com.borland.primetime.build.BuildTask.execute(Unknown Source)--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.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)--at
    org.apache.tools.ant.Task.perform(Task.java:341)--at
    org.apache.tools.ant.Target.execute(Target.java:309)--at
    org.apache.tools.ant.Target.performTasks(Target.java:336)--at
    com.borland.primetime.build.y.executeTarget(Unknown Source)--at
    com.borland.primetime.build.y.executeTargets(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.BuildProcess.run(Unknown Source)--at
    java.lang.Thread.run(Thread.java:534)--Caused by: java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:320)--at
    >
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:260)--at
    >
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:240)--at
    >
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositor
    yImpl.java:175)--...
    20 more--NestedThrowablesStackTrace:--java.io.IOException:
    org.xml.sax.SAXException:
    file:/C:/Home/fashionASP/classes/com/ideal/platformASP/entity/package.jdo
    [Location: Line: 20, C: 70]: Type "ProductDeploy" could not be
    instantiated.--at
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:320)--at
    >
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:260)--at
    >
    com.solarmetric.meta.XMLMetaDataParser.parse(XMLMetaDataParser.java:240)--at
    >
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaDataInternal(JDOMetaDataRepositor
    yImpl.java:175)--at
    >
    kodo.meta.JDOMetaDataRepositoryImpl.getMetaData(JDOMetaDataRepositoryImpl.ja
    va:129)--at
    kodo.enhance.JDOEnhancer.<init>(JDOEnhancer.java:110)--at
    kodo.enhance.JDOEnhancer.run(JDOEnhancer.java:2181)--at
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.doBuild(JDOEnhancerTask.java:
    101)--at
    >
    kodo.jdbc.integration.jbuilder.JDOEnhancerTask.build(JDOEnhancerTask.java:74
    )--at
    com.borland.primetime.build.BuildTask.execute(Unknown Source)--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.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:147)--at
    org.apache.tools.ant.Task.perform(Task.java:341)--at
    org.apache.tools.ant.Target.execute(Target.java:309)--at
    org.apache.tools.ant.Target.performTasks(Target.java:336)--at
    com.borland.primetime.build.y.executeTarget(Unknown Source)--at
    com.borland.primetime.build.y.executeTargets(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.y.build(Unknown Source)--at
    com.borland.primetime.build.BuildProcess.run(Unknown Source)--at
    java.lang.Thread.run(Thread.java:534)--

  • Configuring Kodo logging ...

    Hi Guys,
    Can somebody help me on this one? I have been banging my head against wall
    for quite a while.
    I am basically trying to limit the amount of logging Kodo produces by
    providing log4j.properties (attached bellow).
    We have Kodo (2.4.2) deployed on Websphere (WAS 5.0) server. For some
    reason, Kodo libraries need to be deployed via Websphere extension
    classloader (../websphere/AppServer/lib/ext).
    To eliminate the classloader issues, I have tried heaps of locations for
    the log4j.properties and to my surprise, none of it worked. Tested
    locations included:
    log4j.properties in (../websphere/AppServer/lib/ext
    log4j.properties inside of jar file in (../websphere/AppServer/lib/ext
    log4j.properties in kodo.jar (desperate)
    log4j.properties in ../Websphere/AppServer/properties
    log4j.properties on classpath when starting the server (java -cp
    xxx;log4j.properties ... )
    and a few others.
    As you may guess, no luck. I can get the properties file myself as shown
    bellow(that is, 'log4j.properties' loads fine, '/log4j.properties' returns
    null). Does Kodo look for log4j.properties or '/log4j.properties'?
    The test code was classloaded from the same location as Kodo.jar etc
    (../websphere/AppServer/lib/ext)
    Anyway, it may be just that I am a bit fuzzy on what is exactly happening
    when common-loggings/log4j initialize andI would definitelly appretiate a
    pointer in the right direction if that is the case.
    Kodo should use log4j as long as the log4j.1.2.7.jar file is present on
    the classpath, right?
    Thank you for your help!
    Petr
    Testing code loading the properties:
    URL ps = getClass().getClassLoader().getResource("log4j.properties");
              URL ps2 = getClass().getClassLoader().getResource("/log4j.properties");
              URL sps =
                   getClass().getClassLoader().getSystemClassLoader().getResource("log4j.properties");
              URL sps2 =
                   getClass().getClassLoader().getSystemClassLoader().getResource("/log4j.properties");
              System.out.println("CheckClassPath - log4j.properties: " + ps);
              System.out.println("CheckClassPath - /log4j.properties: " + ps2);
              System.out.println("CheckClassPath system - log4j.properties: " + sps);
              System.out.println("CheckClassPath system - /log4j.properties: " + sps2);
    Output snippet:
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
    log4j.properties:
    file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
    /log4j.properties: null
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
    - log4j.properties:
    file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
    - /log4j.properties: null
    log4j.properties:
    # Set root logger level to DEBUG and its only appender to A1.
    log4j.rootCategory=ERROR, console
    #Subsystem level settings
    log4j.logger.servicenet.core =DEBUG
    log4j.logger.servicenet.core.test =FATAL
    #KODO - disabled
    log4j.rootCategory=ERROR, console
    log4j.category.com.solarmetric.kodo = ERROR, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.SQL=FATAL, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.JDBC=FATAL, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.Schema=ERROR, console
    log4j.category.com.solarmetric.kodo.Performance=ERROR, console
    log4j.category.com.solarmetric.kodo.MetaData=ERROR, console
    log4j.category.com.solarmetric.kodo.Enhance=ERROR, console
    log4j.category.com.solarmetric.kodo.Query=ERROR, console
    log4j.category.com.solarmetric.kodo.Runtime=ERROR, console
    log4j.appender.console=org.apache.log4j.ConsoleAppender
    log4j.appender.console.layout=org.apache.log4j.PatternLayout
    log4j.appender.console.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

    I'm afraid I don't get it. Can someone tell me specifically, what to
    do, to prevent kodo from logging anything to stdout (or anywhere else,
    really)
    I do not want to adjust my log4j root logging verbosity, as I use that
    for my application too.
    Preferably I should be able to do this from the kodo.properties file
    itself, rather than play
    guess-where-in-the-classpath-is-the-proper-log4j.properties file.
    Petr Bulanek wrote:
    Hi Stephen,
    That was it. Man, I would like to buy you a drink!!! :-))))
    I should not forget Marc, you guys are all great!
    Thank you!!!
    Petr
    Stephen Kim wrote:
    I think the property you are looking for is:
    org.apache.commons.logging.LogFactory
    See further documentation on Jakarta's logging page at:
    http://jakarta.apache.org/commons/logging/api/org/apache/commons/logging/package-frame.html
    Petr Bulanek wrote:
    Hi Stephen,
    Thank you for your reply.
    I have tried the following combinations in my startServer.bat script:
    SET LOG4J=-Dlog4j.configuration=file:/c:/log4j.properties
    and
    SET LOG4J=-Dlog4j.configuration=/log4j.properties
    "%JAVA_HOME%binjava" %LOG4J% %WAS_TRACE% %DEBUG% %CONSOLE_ENCODING%
    "%CLIENTSAS%" "-classpath" "%WAS_CLASSPATH%;/log4j.properties;"
    "-Dws.ext.dirs=%WAS_EXT_DIRS%;c:/log4j.properties;" %USER_INSTALL_PROP%
    "-Dwas.install.root=%WAS_HOME%" "com.ibm.ws.bootstrap.WSLauncher"
    "com.ibm.ws.management.tools.WsServerLauncher" "%CONFIG_ROOT%"
    "%WAS_CELL%" "%WAS_NODE%" %*
    and none of them made any difference. I wonder if it could be the case
    that Kodo is not using log4j, but some other logging method instead.
    Could just having jdk 1.4 installed make any difference? Is there anything
    I can do to force Kodo to use log4j instead of relying on default
    initialization of common-loggings?
    Thank you,
    Petr
    You might want to set the system property explicity:
    from log4j's docs:
    Set the resource string variable to the value of the log4j.configuration
    system property. The preferred way to specify the default initialization
    file is through the log4j.configuration system property. In case the
    system property log4j.configuration is not defined, then set the string
    variable resource to its default value "log4j.properties".
    Petr Bulanek wrote:
    Hi Guys,
    Can somebody help me on this one? I have been banging my head against wall
    for quite a while.
    I am basically trying to limit the amount of logging Kodo produces by
    providing log4j.properties (attached bellow).
    We have Kodo (2.4.2) deployed on Websphere (WAS 5.0) server. For some
    reason, Kodo libraries need to be deployed via Websphere extension
    classloader (../websphere/AppServer/lib/ext).
    To eliminate the classloader issues, I have tried heaps of locations for
    the log4j.properties and to my surprise, none of it worked. Tested
    locations included:
    log4j.properties in (../websphere/AppServer/lib/ext
    log4j.properties inside of jar file in (../websphere/AppServer/lib/ext
    log4j.properties in kodo.jar (desperate)
    log4j.properties in ../Websphere/AppServer/properties
    log4j.properties on classpath when starting the server (java -cp
    xxx;log4j.properties ... )
    and a few others.
    As you may guess, no luck. I can get the properties file myself as shown
    bellow(that is, 'log4j.properties' loads fine, '/log4j.properties' returns
    null). Does Kodo look for log4j.properties or '/log4j.properties'?
    The test code was classloaded from the same location as Kodo.jar etc
    (../websphere/AppServer/lib/ext)
    Anyway, it may be just that I am a bit fuzzy on what is exactly happening
    when common-loggings/log4j initialize andI would definitelly appretiate a
    pointer in the right direction if that is the case.
    Kodo should use log4j as long as the log4j.1.2.7.jar file is present on
    the classpath, right?
    Thank you for your help!
    Petr
    Testing code loading the properties:
    URL ps = getClass().getClassLoader().getResource("log4j.properties");
              URL ps2 = getClass().getClassLoader().getResource("/log4j.properties");
              URL sps =
                   getClass().getClassLoader().getSystemClassLoader().getResource("log4j.properties");
              URL sps2 =
                   getClass().getClassLoader().getSystemClassLoader().getResource("/log4j.properties");
              System.out.println("CheckClassPath - log4j.properties: " + ps);
              System.out.println("CheckClassPath - /log4j.properties: " + ps2);
              System.out.println("CheckClassPath system - log4j.properties: " + sps);
              System.out.println("CheckClassPath system - /log4j.properties: " +sps2);
    Output snippet:
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
    log4j.properties:
    file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath -
    /log4j.properties: null
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
    - log4j.properties:
    file:/C:/Program%20Files/WebSphere/AppServer/properties/log4j.properties
    [1/04/03 17:28:20:285 EST] 1a9ec7b6 SystemOut O CheckClassPath system
    - /log4j.properties: null
    log4j.properties:
    # Set root logger level to DEBUG and its only appender to A1.
    log4j.rootCategory=ERROR, console
    #Subsystem level settings
    log4j.logger.servicenet.core =DEBUG
    log4j.logger.servicenet.core.test =FATAL
    #KODO - disabled
    log4j.rootCategory=ERROR, console
    log4j.category.com.solarmetric.kodo = ERROR, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.SQL=FATAL, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.JDBC=FATAL, console
    log4j.category.com.solarmetric.kodo.impl.jdbc.Schema=ERROR, console
    log4j.category.com.solarmetric.kodo.Performance=ERROR, console
    log4j.category.com.solarmetric.kodo.MetaData=ERROR, console
    log4j.category.com.solarmetric.kodo.Enhance=ERROR, console
    log4j.category.com.solarmetric.kodo.Query=ERROR, console
    log4j.category.com.solarmetric.kodo.Runtime=ERROR, console
    log4j.appender.console=org.apache.log4j.ConsoleAppender
    log4j.appender.console.layout=org.apache.log4j.PatternLayout
    log4j.appender.console.layout.ConversionPattern=%-4r [%t] %-5p %c %x -%m%n
    Stephen Kim
    [email protected]
    SolarMetric, Inc.
    http://www.solarmetric.com
    Stephen Kim
    [email protected]
    SolarMetric, Inc.
    http://www.solarmetric.com

  • 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.

  • 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

Maybe you are looking for