Eclipse Plugin - no "Kodo Preferences"

I have been trying to install the Eclipse Plugin for Kodo.
In the Eclipse preferences, I can see "Kodo Preferences" listed on the
left, but when I select it nothing happens - the right hand side does not
refresh to show Kodo Preferences. After I close the Eclipse preferences
window it can not be reopened (selecting Window>Preferences appears to
have no affect). If I do not click on "Kodo Preferences", then there is no
problem opening the Eclipse preferences afterwards.

Michael, you would be correct. We defer to Eclipse's preference
persistence mechanism (which resolves to a pref_store.ini file (or
something like that) which is also a .properties file at
$WORKSPACE/.metadata/.plugins/com.solarmetric.../
On Wed, 28 May 2003 16:17:06 +0200, Michael wrote:
I just checked mine and they're not in sync with my kodo.properties file.
Apparently these aren't being used.
"Matt Bunch" <[email protected]> wrote in message
news:bb2aaq$isp$[email protected]..
I have been trying to install the Eclipse Plugin for Kodo.
In the Eclipse preferences, I can see "Kodo Preferences" listed on the
left, but when I select it nothing happens - the right hand side does not
refresh to show Kodo Preferences. After I close the Eclipse preferences
window it can not be reopened (selecting Window>Preferences appears to
have no affect). If I do not click on "Kodo Preferences", then there is no
problem opening the Eclipse preferences afterwards.
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Similar Messages

Kodo 4.0/ Eclipse Plugin problems

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

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

Kodo 2.5.4 Eclipse plugin.

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

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

Kodo 3.1.4 and Eclipse plugin

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

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

Kodo 3.3.0 Eclipse plugin for IBM Rational Application Developer 6.0

I tried to add the Kodo eclipse plugin to IBM RAD 6.0 which uses eclipse
3.0 instead of 2.1.
Following the instuction to install the eclipse plugin as follow.
First copy the directory kodo.eclipse_2.1.0 directory from the eclipse
directory
Is this still ok to copy kodo.eclipse_2.1.0 to eclipse 3.0 plugin?

Kodo's eclipse plugin follows Eclipse versioning semantics as each
plugin is marked with the -plugin- version number, not which version of
Eclipse it is compatible. So Kodo's 2.1 version number indicates the
feature set of the plugin. Its a tad confusing, but we also didn't want
to force people to make drastic changes to their plugin directory when
each minor patch is released. For the most part, you can simply put in
the newest version of kodo-jdo.jar and plugin.xml.
Gene Shen wrote:
I tried to add the Kodo eclipse plugin to IBM RAD 6.0 which uses eclipse
3.0 instead of 2.1.
Following the instuction to install the eclipse plugin as follow.
First copy the directory kodo.eclipse_2.1.0 directory from the eclipse
directory
Is this still ok to copy kodo.eclipse_2.1.0 to eclipse 3.0 plugin?
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

Eclipse plugin & errors with imports

I've been using the Eclipse plugin and it's working well. Then I added an
import to my class, and now the Kodo enhancer gives me an error (error in
build) but it's not specific. I removed the import and it goes away. I
then tried adding one line to my class:
private static org.apache.log4j.Logger log =
org.apache.log4j.Logger.getLogger(URLMonitor.class.getName());
And I get the error. When I run jdoc from a windows prompt it works fine.
I'm using Eclipse 2.1 build
200302190010.
Also, when running jdoc by hand with the -properties flag, I get:
Exception in thread "main" java.lang.IllegalArgumentException: The specified
cla
ss "-properties" could not be loaded. javax.jdo.JDOFatalUserException:
java.lan
g.ClassNotFoundException: -properties
NestedThrowables:
java.lang.ClassNotFoundException: -properties
But it still seems to pick up my properties file and it works.

Thanks for helping!
in the windows->preferences->Kodo Preferences, my parameters are below:
License key: [license key censored by [email protected]], evalud key from email
Connection driver: mysql-connector-java-3.0.6-stable-bin.jar
Connection URL: jdbc:mysql://localhost:3306/MONSOON
connection username: root
connection password: foobar
Dictionary class: com.mysql.jdbc.Driver
"Stephen Kim" <[email protected]> wrote in message
news:[email protected]...
How did you configure your Preferences panel? The Eclipse plugin
doesn't use a kodo.properties file. You should specify your driver
name, not the jar, in the preferences page.
Charle Wang wrote:
I think I have similar problem as followed: I use eclipse2.02 + kodo
2.4.2 +
Windows 2000
By following dev_doc, I imported petshop project. The menu->" Enhancer"part
works fine, and build successed, but for the file Animal.jdo, "kodo->Addto
Database" failed. Error message is bellow: (I even can not copy+pasteit)
>>
<error>-SchemaTool Failed. The message included was:
{0}
javax.jdo.JDOFatalUserException:java.lang.ClassNotFoundException:mysql-conne
ctor-java-3/0/6-stable-bin/jar
NestedThrowables:
java.lang.ClassNotFoundException:mysql-connector-java-3/0/6-stable-bin/jar
>>
<info>-Done
1. I remove the possiblity of the JDBC driver issues. because I use same
driver and parameters for Quantum_DB plugin. it works fine. I canmanipulate
the whole mySQL tables.
2. part of plugin.xml is as bellow:
<?xml version="1.0" encoding="UTF-8"?>
<plugin id="com.solarmetric.kodo"
name="%name"
version="1.0.0"
provider-name="%provider-name"
class="com.solarmetric.modules.integration.eclipse.KodoPlugin">
<runtime>

<library name="mysql-connector-java-3.0.6-stable-bin.jar"/>


3. kodo.properties is bellow:
#Thu Nov 07 12:32:12 EST 2002
com.solarmetric.kodo.LicenseKey=[license key censored by
[email protected]
com.solarmetric.kodo.PersistenceManagerClass=PetShopPersistenceManager
com.solarmetric.kodo.impl.jdbc.SynchronizeSchema=true
javax.jdo.PersistenceManagerFactoryClass=com.solarmetric.kodo.impl.jdbc.JDBC
PersistenceManagerFactory
javax.jdo.option.ConnectionDriverName=com.mysql.jdbc.Driver
javax.jdo.option.ConnectionPassword=foobar
javax.jdo.option.ConnectionURL=jdbc:mysql://localhost:3306/MONSOON
javax.jdo.option.ConnectionUserName=root
javax.jdo.option.MaxPool=0
4.I have spent a whole day, still can not make the thing move. Did Imiss
some tip? or .. ?
"Petr" <[email protected]> wrote in message
news:[email protected]...
Hi Guys,
Loosely related question, is there any chance that build of an
individual
class will some day trigger enhancement where appropriate? Currently it
seems that only full project re-build does the trick ...
It is a minor thingy, probably in 'nice to have' category.
Cheers,
Petr
Stephen Kim wrote:
Can you specify what version of Kodo you are using?
java com.solarmetric.kodo.conf.JDOVersion
If you enhance using the wrench icon/menu, do you get a more verbose
logging in the Kodo view?
On Mon, 03 Mar 2003 15:33:58 +0100, Michael Mattox wrote:
I've been using the Eclipse plugin and it's working well. Then I
added an
import to my class, and now the Kodo enhancer gives me an error (errorin
build) but it's not specific. I removed the import and it goes away.I
then tried adding one line to my class:
private static org.apache.log4j.Logger log =
org.apache.log4j.Logger.getLogger(URLMonitor.class.getName());
And I get the error. When I run jdoc from a windows prompt it worksfine.
I'm using Eclipse 2.1 build
200302190010.
Also, when running jdoc by hand with the -properties flag, I get:
Exception in thread "main" java.lang.IllegalArgumentException: Thespecified
cla
ss "-properties" could not be loaded.
javax.jdo.JDOFatalUserException:
java.lan
g.ClassNotFoundException: -properties
NestedThrowables:
java.lang.ClassNotFoundException: -properties
But it still seems to pick up my properties file and it works.--
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com

[ANNOUNCE]: myWL eclipse plugin 1.0.11 released

myWL plugin 1.0.11 released, check the project's site
http://mywl.sourceforge.net for more information.
Version 1.0.11 brings full WL6.1 support together with a new feature which
allows WL's CMP generated SQL statements to be logged and monitored.
Check the 1.0.11 Release Log:
The forthnet-eclipse-plugins team is pleased to announce the FORTHnet
WebLogic
Server Eclipse Plugin 1.0.11 release!
http://mywl.sourceforge.net/
An Eclipse 3.0 compatible plugin which allows BEA's WebLogic Server (6.1,
7.1
and 8.1) to be managed from within eclipse and thus easily debug deployed
J2EE
applications in BEA.
Changes in this version include:
New Features:
o A new feature has been added which enables, if configured to do so from
myWL's WebLogic preferences page, logging of all CMP generated SQL
statements. This is a great aid for the developer, which can now monitor
WL's generated SQL statements for finders, select methods, etc. This
feature has been tested and it is known to work with WL 8.1. Older versions
of WL may support this feature, but no testing has been made.
Fixed bugs:
o When launching WL 6.1, JVM's working dir was being incorrectly set.
o WL 6.1 launcher didn't respect user's defined JVM options.
o WL 6.1 launcher didn't respect user's defined JNI library path.
Changes:
o WL 6.1 launcher now by default adds to the server's boot classpath the
WL's
home. This eliminates the need to specify the WL's home dir in the plugin's
Classpath Preferences page.
o WL 6.1 launcher specifies by default the java security policy as defined
in
the WL_HOME/lib/weblogic.policy file.
o WL 7.1 launcher specifies by default the java security policy as defined
in
the WL_HOME/lib/weblogic.policy file.
Have fun!
-The forthnet-eclipse-plugins team
Filippos Slavik
FORTHnet R&D, Heraklion, Greece
e-mail : [email protected]
phone : (+30) 2811 391230
Key ID: 0xF4B5B375 Filippos Slavik(search pgp.mit.edu)
Key FingerPrint: 81D4 25D0 01EB 9DCA 62E4 B694 20E7 31FB F4B5 B375
"The software said 'runs on Win95 or better,' so I installed it
on Linux..."

Problem solved. After closing the perspectives I had open and reopening
them, the menu showed up in the correct perspectives.
Ignore This wrote:
I'm trying to use the Eclipse plugin with Eclipse version 2.1 (recently
released). I am aware that the Kodo documentation says it works with
Eclipse 2.0. The "Kodo" menu appears in the wrong perspective (the CVS
Repository Exploring Perspective). This makes it generally unusable.
Anyone else tried this with better success?

WSAD 5 / Eclipse plugin not working

I have installed the Kodo plugin into my Websphere Application Developer
5.1.0 environment. I have configured the Kodo preferences and selected "Add
Enhancer to Build" for my project.
Still, the other items on the Kodo menu remain grayed out ("Enhance
Metadata", "Refresh Mappings", etc.). Can anyone tell me what I'm doing
wrong?
Thanks in advance,
Kevin Keigwin
Architect
SellCore

Hi,
there is a typo in the plugin.xml file for the Kodo plugin.
change the following line -
<library name="jakarta-commons-logging-1.0.2.jar"/>
to -
<library name="jakarta-commons-logging-1.0.3.jar"/>
and restart Eclipse.
Should do the trick.
Simon
"Darville" <[email protected]> wrote in message
news:bfo9s9$h8e$[email protected]..
Darville wrote:
James Eitzmann wrote:
I am trying to evaluate jdo implementations. I have installed the
eclipse
plugin according to the instructions, but it is not working. I amrunning
with eclipse 2.1 on windows. I can see the menu items and the entry inthe
preferences panel but when I click on the preferences item, nothing
happens. When I try to switch to the kodo view, I get a problemsshowing
view error message. I am using kodo 2.5.2.
Does anyone have any suggestions?
Thanks
Hello,
I am experiencing the same problem
using kodo 2.5.2
using eclispe 2.1.1 (windows)
ChristopheOops, the solution was already in the forum
See mail from Aapo (07-17-03)
This is a copy of the mail :
<<
Hi,
while trying to get KODO Eclipse plugin to work,
I noticed that in plugin.xml there was incorrect reference
to the jakarta-loggings jar : the version number is wrong:
1.0.2 -> 1.0.3.
Changing this I could get it working.
Aapo
>

Eclipse plugin not working

I am trying to evaluate jdo implementations. I have installed the eclipse
plugin according to the instructions, but it is not working. I am running
with eclipse 2.1 on windows. I can see the menu items and the entry in the
preferences panel but when I click on the preferences item, nothing
happens. When I try to switch to the kodo view, I get a problems showing
view error message. I am using kodo 2.5.2.
Does anyone have any suggestions?
Thanks

Hi,
there is a typo in the plugin.xml file for the Kodo plugin.
change the following line -
<library name="jakarta-commons-logging-1.0.2.jar"/>
to -
<library name="jakarta-commons-logging-1.0.3.jar"/>
and restart Eclipse.
Should do the trick.
Simon
"Darville" <[email protected]> wrote in message
news:bfo9s9$h8e$[email protected]..
Darville wrote:
James Eitzmann wrote:
I am trying to evaluate jdo implementations. I have installed the
eclipse
plugin according to the instructions, but it is not working. I amrunning
with eclipse 2.1 on windows. I can see the menu items and the entry inthe
preferences panel but when I click on the preferences item, nothing
happens. When I try to switch to the kodo view, I get a problemsshowing
view error message. I am using kodo 2.5.2.
Does anyone have any suggestions?
Thanks
Hello,
I am experiencing the same problem
using kodo 2.5.2
using eclispe 2.1.1 (windows)
ChristopheOops, the solution was already in the forum
See mail from Aapo (07-17-03)
This is a copy of the mail :
<<
Hi,
while trying to get KODO Eclipse plugin to work,
I noticed that in plugin.xml there was incorrect reference
to the jakarta-loggings jar : the version number is wrong:
1.0.2 -> 1.0.3.
Changing this I could get it working.
Aapo
>

Error when starting weblogic from forthnet eclipse plugin?

Hi,
I'm getting an error when trying to start my weblogic server from the forthnet eclipse plugin. (However, it works to start the server from a command prompt on the machine it is running on, and also, it works to stop the server from eclipse)
Server and eclipse is running on Windows.
The error reported is:
<2004-sep-01 kl 16:13 CEST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not obtain an exclusive lock for directory: .\decisionsite81\ldap\ldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down.>
<2004-sep-01 kl 16:13 CEST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not obtain an exclusive lock for directory: .\decisionsite81\ldap\ldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down.>
<2004-sep-01 kl 16:13 CEST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not obtain an exclusive lock for directory: .\decisionsite81\ldap\ldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down.>
<2004-sep-01 kl 16:13 CEST> <Warning> <EmbeddedLDAP> <BEA-171520> <Could not obtain an exclusive lock for directory: .\decisionsite81\ldap\ldapfiles. Waiting for 10 seconds and then retrying in case existing WebLogic Server is still shutting down.>
<2004-sep-01 kl 16:13 CEST> <Error> <EmbeddedLDAP> <BEA-171519> <Could not obtain an exclusive lock to the embedded LDAP data files directory: .\decisionsite81\ldap\ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.>
<2004-sep-01 kl 16:13 CEST> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.server.ServiceFailureException: Could not obtain an exclusive lock to the embedded LDAP data files directory: .\decisionsite81\ldap\ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.
weblogic.server.ServiceFailureException: Could not obtain an exclusive lock to the embedded LDAP data files directory: .\decisionsite81\ldap\ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.
     at weblogic.ldap.EmbeddedLDAP.ensureExclusiveAccess(EmbeddedLDAP.java:959)
     at weblogic.ldap.EmbeddedLDAP.initialize(EmbeddedLDAP.java:221)
     at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:814)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
     at weblogic.Server.main(Server.java:32)
>
<2004-sep-01 kl 16:13 CEST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.server.ServiceFailureException: Could not obtain an exclusive lock to the embedded LDAP data files directory: .\decisionsite81\ldap\ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.>
I've tried removing the "EmbeddedLDAP.lok" file, but without luck.

Which version of your eclipse? I am using eclipse 3.0 and I am able to start weblogic 8.1 from eclipse.
I did the following steps:
1.create a new domain through weblogic's configuration wizard --> basic weblogic server domain --> Express --> proive the user name and password --> development mode, and sun sdk (or other jdk) --> your new domain name
2. configure weblogic setting in eclipse: preferences --> weblogic --> 8.1, C:\bea\weblogic81, your newly created domain name --> C:\bea\user_projects\domains (domain directory) --> myserver --> admin (or your user name) --> password --> localhost --> 7001
after that, you should be able to click on "start weblogic server" button from toolbar.
Hope my two cents solve your problem.

Eclipse plugin not working with Eclipse 2.1

I'm trying to use the Eclipse plugin with Eclipse version 2.1 (recently
released). I am aware that the Kodo documentation says it works with
Eclipse 2.0. The "Kodo" menu appears in the wrong perspective (the CVS
Repository Exploring Perspective). This makes it generally unusable.
Anyone else tried this with better success?

Problem solved. After closing the perspectives I had open and reopening
them, the menu showed up in the correct perspectives.
Ignore This wrote:
I'm trying to use the Eclipse plugin with Eclipse version 2.1 (recently
released). I am aware that the Kodo documentation says it works with
Eclipse 2.0. The "Kodo" menu appears in the wrong perspective (the CVS
Repository Exploring Perspective). This makes it generally unusable.
Anyone else tried this with better success?

Is it possible to specify MLS port in Mission Control Eclipse plugin?

I'm running the Mission Control plugin in Eclipse to manage a remote server behind a firewall. I'm able to run the JRockit console, however I am unable to run Memory Leak Detector. It seems I need to specify the MLS port, or I need to turn off the firewall to allow the MLS to use a random port. Turning off the firewall is not a option.
Is it possible specify the MLS port in the Eclipse Mission Control Plugin? I can't find anywhere to do. Is it possible to somehow include it as part of the Custom JMX URL?
FYI, I have to use the Eclipse plugin because I'm working on OSX, and that seems to be my only option.

You should be able to specifiy which port is used for Memleak in the Mission Control preferences,
Mission Control/Memory Leak Detector/Communication - Use fixed port
If you can't see those prefs, which version of Mission Control are you using?
Klara, Mission Control dev

Eclipse plugin output

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

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

Eclipse plugin Memory Leak

Hello all,
I just started using Kodo. Everything works very well and this is a nice
product. My only problem is that there seems to be a memory leak when
using the Eclipse plugin. The memory taken by the javaw process in task
manager grows and grows if I keep using the mapping tool from inside
eclipse with the kodo buttons on top. When memory usage gets to around
400mb I restart Eclipse.
Has anyone else run into this problem? Is there any way around it?
Thanks in advance,
Adam.

Adam-
We haven't seen any reports of this. Can you describe the actions you
take with Kodo? Specifically, are there any particular actions that if
you just repeat over and over, Eclipse runs out of memory?
Also, what version of Eclipse are you using? Earlier versions has a bug
with an interaction with ant has a memory leak. See:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=24448
In article <cqk2qt$ovn$[email protected]>, Goerge wrote:
>
Hello all,
I just started using Kodo. Everything works very well and this is a nice
product. My only problem is that there seems to be a memory leak when
using the Eclipse plugin. The memory taken by the javaw process in task
manager grows and grows if I keep using the mapping tool from inside
eclipse with the kodo buttons on top. When memory usage gets to around
400mb I restart Eclipse.
Has anyone else run into this problem? Is there any way around it?
Thanks in advance,
Adam.
Marc Prud'hommeaux
SolarMetric Inc.

NullPointerException in Schematool ANT-Task and Eclipse-plugin

Hi,
When running the Schematool from the Eclipse-plugin or from the ANT-task,
I get a NullPointerException. The ANT-plugin gives a more-or-less usefull
exception-traceback, the Eclipse-plugin doesn't give any useful hints.
The funny thing however is that from the commandline it all works!
The exception from ANT is:
[schematool] com.solarmetric.kodo.runtime.FatalException: There was an
error mapping field "operator" of type "class
com.unisys.nl.ruleengine.rules.CompoundCondition" to a schema.
[schematool] NestedThrowables:
[schematool] java.lang.NullPointerException
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMapping(Mapping.java:244)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMappings(Mapping.java:131)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMappings(Mapping.java:86)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createMappings(SchemaTool.java:831)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:333)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1166)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1102)
[schematool]      at
com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
[schematool]      at
com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
[schematool]      at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
[schematool]      at org.apache.tools.ant.Task.perform(Task.java:341)
[schematool]      at org.apache.tools.ant.Target.execute(Target.java:309)
[schematool]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[schematool]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[schematool]      at
org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[schematool]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
[schematool]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
[schematool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[schematool]      at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[schematool]      at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[schematool]      at java.lang.reflect.Method.invoke(Method.java:324)
[schematool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
[schematool]      at
org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
[schematool]      at java.lang.Thread.run(Thread.java:534)
[schematool] NestedThrowablesStackTrace:
[schematool] java.lang.NullPointerException
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.StringificationMapping.findMethod(StringificationMapping.java:215)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.StringificationMapping.getExternalizer(StringificationMapping.java:123)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.StringificationMapping.getExternalizer(StringificationMapping.java:112)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.StringificationMapping.install(StringificationMapping.java:105)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMapping(Mapping.java:234)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMappings(Mapping.java:131)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.ormapping.Mapping.createMappings(Mapping.java:86)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.createMappings(SchemaTool.java:831)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:333)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.refresh(SchemaTool.java:321)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1166)
[schematool]      at
com.solarmetric.kodo.impl.jdbc.schema.SchemaTool.main(SchemaTool.java:1102)
[schematool]      at
com.solarmetric.modules.integration.ant.SchemaToolTask.executeOn(SchemaToolTask.java:54)
[schematool]      at
com.solarmetric.modules.integration.ant.TaskBase.execute(TaskBase.java:118)
[schematool]      at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:193)
[schematool]      at org.apache.tools.ant.Task.perform(Task.java:341)
[schematool]      at org.apache.tools.ant.Target.execute(Target.java:309)
[schematool]      at
org.apache.tools.ant.Target.performTasks(Target.java:336)
[schematool]      at
org.apache.tools.ant.Project.executeTarget(Project.java:1339)
[schematool]      at
org.apache.tools.ant.Project.executeTargets(Project.java:1255)
[schematool]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:569)
[schematool]      at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:367)
[schematool]      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
[schematool]      at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[schematool]      at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[schematool]      at java.lang.reflect.Method.invoke(Method.java:324)
[schematool]      at org.eclipse.ant.core.AntRunner.run(AntRunner.java:335)
[schematool]      at
org.eclipse.ui.externaltools.internal.ant.launchConfigurations.AntLaunchDelegate$1.run(AntLaunchDelegate.java:172)
[schematool]      at java.lang.Thread.run(Thread.java:534)
[schematool] BUILD FAILED:
file:C:/java/eclipse/workspace/EclipseProject/build.xml:84:
com.solarmetric.kodo.runtime.FatalException: There was an error mapping
field "operator" of type "class
com.unisys.nl.ruleengine.rules.CompoundCondition" to a schema.
NestedThrowables:
java.lang.NullPointerException
The .jdo file is:
<?xml version="1.0" encoding="UTF-8"?>
<jdo>
<package name="com.unisys.nl.ruleengine.rules">
<class name="Condition">
     <extension vendor-name="kodo" key="table" value="condition"/>
     </class>
<class name="ConditionDummyPlaceHolder"
persistence-capable-superclass="Condition">
     <field name="m_condition">
<extension vendor-name="kodo" key="data-column"
value="condition"/>
          <extension vendor-name="kodo" key="dependent" value="true"/>
     </field>
</class>
<class name="AtomicCondition"
persistence-capable-superclass="Condition">
               <field name="lefthand">
<extension vendor-name="kodo" key="dependent"
value="true"/>
               </field>
     <field name="operator">
          <extension vendor-name="kodo" key="externalizer"
value="toString"/>
          <extension vendor-name="kodo" key="factory"
value="getOperatorWithSymbol"/>
     </field>
               <field name="righthand">
<extension vendor-name="kodo" key="dependent"
value="true"/>
               </field>
</class>
<class name="CompoundCondition"
persistence-capable-superclass="Condition">
<field name="subConditions">
<collection
element-type="com.unisys.nl.ruleengine.rules.Condition"/>
<extension vendor-name="kodo" key="element-dependent"
value="true"/>
<extension vendor-name="kodo" key="ordered" value="true"/>
</field>
     <field name="operator">
          <extension vendor-name="kodo" key="externalizer"
value="toString"/>
          <extension vendor-name="kodo" key="factory"
value="getOperatorWithSymbol"/>
     </field>
</class>
<class name="ConditionValue">
     <extension vendor-name="kodo" key="table"
value="condition_value"/>
</class>
<class name="DerivedValue"
persistence-capable-superclass="ConditionValue">
     <field name="valueProperty">
          <extension vendor-name="kodo" key="dependent" value="true"/>
     </field>
</class>
<class name="SimpleValue"
persistence-capable-superclass="ConditionValue"/>
<class name="Rule" persistence-capable-superclass="RuleSetElement">
     <extension vendor-name="kodo" key="table" value="rule"/>
     <field name="context">
          <extension vendor-name="kodo" key="dependent" value="false"/>
     </field>
     <field name="condition">
          <extension vendor-name="kodo" key="dependent" value="true"/>
     </field>
     <field name="comment">
<extension vendor-name="kodo" key="column-length"
value="-1"/>
</field>
     </class>
<class name="RuleSet"
persistence-capable-superclass="RuleSetElement">
     <extension vendor-name="kodo" key="table" value="ruleset"/>
<field name="rules">
<collection
element-type="com.unisys.nl.ruleengine.rules.RuleSetElement"/>
<extension vendor-name="kodo" key="element-dependent"
value="true"/>
</field>
</class>
<class name="RuleSetElement">
     <extension vendor-name="kodo" key="table"
value="ruleset_element"/>
</class>
</package>
</jdo>
Any pointers what I'm doing wrong here?
(Another data-point: when I moved the sources to the laptop of a collegue,
and we try to generate the schema there, the plugin complains about not
having any JDO metadata available for the class RelationOperator - which
is the type of the field 'operator' that gives the NPE.
I'm using KODO-JDO 2.5.0RC2)
--Tim

Tim-
This seems to be a problem with ClassLoader interactions; it will be
fixed for the next 2.5 RC (or final release). Thanks for pointing it
out.
In article <bbngrl$j47$[email protected]>, Tim van der Leeuw wrote:
>
Hi,
When running the Schematool from the Eclipse-plugin or from the ANT-task,
I get a NullPointerException. The ANT-plugin gives a more-or-less usefull
exception-traceback, the Eclipse-plugin doesn't give any useful hints.
The funny thing however is that from the commandline it all works!--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Eclipse Plugin - no "Kodo Preferences"

Similar Messages

Maybe you are looking for