Viewing javadoc's in eclipse

Hello, just a quick one...
When using eclipse, if i click on a class name which is in the standard API then i can view the javadoc through eclipse, how can i set this up so i can view it for non standerd classes, which come with the source code and or javadocs in a seperate file?
Thanks for any help

Select your project, then navigate to Project > Properties; select 'Java Build Path' and select the tab 'Libraries'; select the .jar file you want to attach javadocs for (expand it) and select the option 'Javadoc location'; select the directory where the (API) docs are stored and voila.
kind regards,
Jos

Similar Messages

  • Viewing java code in Eclipse

    This question of mine is not directly related to Java but I couldn�t find a better place to post this question. I have a java application contained in 2 zip files. I am viewing the files in eclipse. I created a project and extracted both the zip files here. But now, when I open a file to view the code, red lines show all over. When I scroll my mouse on top of the element it shows errors like this:
    ServletException cannot be resolved to a type
    HttpServletRequest cannot be resolved to a type
    HttpServletResponse cannot be resolved to a type
    The method init() is undefined for the type Object
    The method destroy() is undefined for the type ObjectI know I can view the code in a simple java editor too, but I am using Eclipse as I want to learn. Can someone please tell me what could be the problem??
    Thanks
    Mick

    well, obviously the servlet classes are not found in this jar.
    remember that my jar is servlet.jar without the "s" as opposed to yours.
    i'm sure you can download the servlet.jar from suns site somewhere. google for
    servlet + java + tutorial
    and you'll find the prerequisites, including getting this jar.
    btw, you mentioned that you have code for an application. a servlet is not exactly an application. are you sure, that you want to work with that servlet?
    as i said, to run it, you'll need a web server and servlet container.
    if you want to get to know eclipse then you might work on an ordinary application.

  • How to view Swing sources in Eclipse

    HI all,
    I work with Eclipse and I want to through Swing code to analyse what is processed.
    I know it is possible to view Swing source, but I can find the Swing sources in the java jdk delivery.
    How can I do that?
    Thanks.
    Herve.

    Well something is missing.
    Just below, I give you 2 lines of the calling stack. The first is my code with the current line, which is 41. My code is called from some Swing code and you can see that the caller line is not available. So when I move forward with Step Over, I can see the swing code, but the current line is lost!
    JComboBoxWrapped$Model.getSelectedItem() line: 41     
    JComboBox.setModel(ComboBoxModel) line: not available

  • FlexPMD View not displaying results Eclipse 3.6

    Below are the relevant software installations. FlexPMD is configured as defined in the documentation.
    When running FlexPMD, it appears to be churning away, however, there are no results that appear in the FlexPMD View window. Is this an issue only with Eclipse 3.6???
    ** Software versions ***
    FlexPMD 1.0.0.v200912091712
    flex-pmd-all-in-one-bundle-1.2
    Eclipse 3.6
    FlashBuilder 4.0.1
    *** Eclipse Log File Entries ***
    !ENTRY org.eclipse.ui 2 0 2011-02-27 10:49:20.167
    !MESSAGE Warnings while parsing the key bindings from the 'org.eclipse.ui.commands' extension point
    !SUBENTRY 1 org.eclipse.ui 2 0 2011-02-27 10:49:20.167
    !MESSAGE Cannot bind to an undefined command: plug-in='com.adobe.ac.pmd.eclipse', id='com.adobe.ac.pmd.eclipse.flexpmd.runCommand.category'
    !ENTRY org.eclipse.ui 4 4 2011-02-27 10:49:20.707
    !MESSAGE Unable to create menu item "com.adobe.ac.pmd.eclipse.toolbar.runCommand", command "com.adobe.ac.pmd.eclipse.flexpmd.runCommand.category" not defined

    Thanks, I removed the old version and installed the new one using the url
    provided. Initially, the same results. When I looked at the log, I could see
    there was a permissions error when FlexPMD tries to access one of its temp
    directories (see below)
    !ENTRY com.adobe.ac.pmd.eclipse 1 0 2011-02-28 08:42:17.003
    !MESSAGE [java, -Xmx256m, -jar,
    C:/eclipse/configuration/org.eclipse.osgi/bundles/874/1/.cp/flexPmdRuntime//flex-pmd-comma nd-line-1.1.jar,
    -s,
    C:\workspace\BlissClient\src\com\othenos\bliss\business\DocumentDelegate.as,
    -o, C:\Users\Mike\AppData\Local\Temp\flexpmd5980952838914453410dir]
    !ENTRY com.adobe.ac.pmd.eclipse 1 0 2011-02-28 08:42:22.112
    !MESSAGE Feb 28, 2011 8:42:22 AM
    com.adobe.ac.pmd.engines.AbstractFlexPmdEngine
    WARNING: Access is denied at
    java.io.WinNTFileSystem.createFileExclusively(Native Method)
    java.io.File.checkAndCreate(Unknown Source)
    java.io.File.createTempFile(Unknown Source)
    So, I  quite eclipse and ran it as administrator. This time there FlexPMD
    was able to perform the operations and display the results.
    I do not know if this problem is related to something I have done regarding
    installation of eclipse or if it has something to do with the way FlexPMD is
    installed. Normally, I do not have to run eclipse as administrator to get
    plugins to work. I suspect it has to do with the FlexPMD's creation of the
    temp directory. If there is anything else I can do to help you with this
    issue please let me know.
    Thanks for the fix. I am looking forward to using the capabilities of
    FlexPMD.
    -Mike Robinson

  • Viewing JavaDoc HTML files inside a JFrame

    hi all,
    how can I display any of JavaDoc HTML files (as overview-summary.html or index.html) inside a JFrame?
    in addition, the user should be able to use hyperlinks.
    I used JEditorPane, but in it I can't use hyperlinks.
    thanks for your answers. :)

    Hey thats something like a bew browser right if you want to i can send you an example for you but i'm curious you want to use JFileChooser or just open the html page like internet and provide links however send me a message to [email protected] to send you the example and watch if it works for you

  • Viewing javadoc in external browser (NetBeans)

    OK, so i know this question is awfully specific, but I haven't been able to google myself out of it.
    I've downloaded and installed NetBeans v. 6.7.1 on Windows 7. When i ctrl + space identifiers and the javadoc popup appears, the button for browsing the javadoc in an external browser (in my case, Firefox) is dimmed. My solution to this problem used to be to go Tools -> Java Platforms, and just add the javadocs zip-file under the Javadoc tab of the JDK. Does not work here!
    Any help appreciated...

    Yeah, there's a problem with the combination of 6.7.1 and Java 7 javadocs. Java 6 docs work for me. I posted to the NB Users forum a week ago, but no response. Here's the post. Add to it and bump it, maybe someone has more info.
    [http://www.nabble.com/NB-6.7.1-Javadoc-Index-Search-not-working-w-JDK-7b67-Javadoc-to24882301.html#a24882301]
    What you describe I also see.
    Move any further discussion to NB forums, not here.

  • Viewing Swing GUI  in Eclipse Galileo IDE

    Hi,
    I have created a client GUI which I'd like to view but my application is not complete, still need to define pages that control the context menu that will display the gui. Is there a way/ plugins to view gui before completion?
    Thanks.

    the best is your own mind and fingers.

  • Using javadocs in Eclipse

    My team and I are trying to use javadocs in eclipse to document our source codes. I have used the javadoc generator in eclipse but do I have to manual comment in the details of the javadoc such as parameters, and a summary of the method? Is it possible to hide the javadocs? We just want to have a seperate folder for javadocs where we can view/edit the javadocs and still have no javadocs or comments within our code. anyone got suggestions????

    Hi,
    Well, Eclipse adds nothing special here. But you have actually an interesting idea...
    Some (long) time ago I used to hear that it was hailed as a big progress a possibility to store all actual descriptions along with the Java code and to generate by them the entire finished documentation automatically. But now, it seems, you want to go back in time...
    I believe, the standard Javadoc is unable to support anything like this.
    However, if you still want to use Javadoc in such an arrangement so as to generate the overall documentation skeleton (as well as to employ Javadoc's HTML output engine), you will need to develop your own doclet or a taglet, at least.
    For instance, you could introduce some special tags using which you would specify the locations of your description files (directly or using some identifiers). Then, your taglet would process those tags, read those descriptions from the files and feed them to Javadoc.
    Another way is to imply the locations of your description files from the program element (i.e. class, method or field) being processed by Javadoc. The doclet API provides all necessary information together with the location of a Java source file. So you could use it to find your custom description files somewhere nearby it.
    I suggest also to look at this product:
    http://www.filigris.com/products/docflex_javadoc/
    This is a highly customizable Javadoc doclet. More precisely, this is a system for rapid development of professional quality doclets from scratch (with the support of both framed/single-file HTML and RTF output). If you are prepared to buy some number of licenses, we could very much customize this product for your needs. So, your task will be solved with no problem.
    Regards,
    Leonid Rudy
    http://www.docflex.com

  • Is there any way to view the Java API through Eclipse or any IDE?

    I usually use Eclipse to code and sometimes, when i'm typing a method it will show a small list of the methods available for that class. Does Eclipse (or any other IDE, but Eclipse especially), have the java API available for view somewhere in the program?
    Thanks.

    In Eclipse Select Window -> Show View -> JavaDoc. If you're JRE is set up correctly, it will show you the JavaDoc of the currently selected class/method/member variable in that view.
    If it isn't, then go to Window -> Preferences -> Java -> Installed JRE and edit the JavaDoc location of the rt.jar (for Java 6 http://java.sun.com/javase/6/docs/api/ is a good value, as long as you're online).

  • How do I import Eclipse Help project/pages?

    I have an Eclipse Help project with about 100 html topic pages that I created in Eclipse and organized in various folders. However, the editor in Eclipse that I am using is not very advanced and it's quite tedious to manage the help project and cannot easily create other help formats. I want to try RoboHelp 8 as the authoring environment and have it output Eclipse Help (which I hear it can do).
    However, I can't find a way to easily import my existing Eclipse Help pages and folder structure. Is there a way to do this without breaking anything (like images or css) or having to go to each page and do some fixing up?
    Ideally, I would like some kind of two-way transfer so I can share the project with others on my team using Eclipse to edit the topics; but I realize that may be too much to ask for.

    Peter, thank you for your reply.
    I went ahead and re-created the folder structure and imported the topic pages into each folder. This part seems to work fine. However, I have a few issues:
    1) When I double-click on the topic pages they open in Notepad rather than the built-in editor. If I right-click on a topic and choose Edit With Design View, that works, but is quite tedious to do for every page. I also notice that if I make a change to the page in design view and save it, from then on it opens in Design View.
    I see that the files that open in Design View have the following markup added:
    <meta name="generator" content="Adobe RoboHelp 8" />
    Is there a way to have these .html pages always open in Design View by default, at least for this project?
    2) I used the instructions here to create Eclipse Help: http://blogs.adobe.com/techcomm/2009/12/how_to_generate_eclipse_help_from_robohelp.html
    When I bring up the pages in Eclipse, the ones that I edited using the Design View seem OK (so far), however the ones that were imported from original Eclipse Help format now show this error when I try to view them:
    An error occured while processing the requested document:
    org.xml.sax.SAXParseException: Content is not allowed in prolog.
    at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
    at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
    at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:56)
    at org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLProcessor.java:49)
    at org.eclipse.help.internal.xhtml.DynamicXHTMLProcessor.process(DynamicXHTMLProcessor.java: 66)
    at org.eclipse.help.internal.webapp.servlet.DynamicXHTMLFilter$1.close(DynamicXHTMLFilter.ja va:81)
    at java.io.FilterOutputStream.close(Unknown Source)
    at org.eclipse.help.internal.webapp.servlet.FilterHTMLHeadAndBodyOutputStream.close(FilterHT MLHeadAndBodyOutputStream.java:311)
    Any idea why I am getting this error? I am using the EclipseHelp.jsx that came with RoboHelp 8.0.0.203 (incidentally, the "latest" script file pointed to in the link above actually has an older copyright date so it would not seem that it's the latest). Would solving #1 solve this issue?
    3) I set a default topic for my books, which works fine in Web Help. But when I try to view the book in Eclipse, it displays a Contents list instead of the default topic.
    Any idea how to fix this?
    Thanks in advance,
    Dan

  • Using Eclipse project definitions to build the Flex SDK

    It would be great if someone from Adobe could post on the recommended usage of the Eclipse project definitions in the development/eclipse/ subdirectory of the 3.0.x trunk distribution. I would like to debug some compiler modifications that I am working on.
    I saw Peter Farland demo this setup at 360Flex, but was unable to capture all the details of the Eclipse configuration that he discussed in his talk.
    thanks!

    If you go to the framework project’s properties, there is a section called Flex Library Compiler, you want to use a specific flex sdk (add a new sdk which points to the trunk, and use that) — you are probably building /against/ the wrong sdk, right code, wrong compiler.
    - Jono
    From: Ben Clinkinbeard <[email protected]>
    Reply-To: <[email protected]>
    Date: Thu, 3 Apr 2008 12:56:01 -0700
    To: <[email protected]>
    Subject: Re: Using Eclipse project definitions to build the Flex SDK
    A new message was posted by Ben Clinkinbeard in
    Developers --
      Using Eclipse project definitions to build the Flex SDK
    Sorry, I'm not following. My SDK project is from the trunk.
    Thanks,
    Ben
    On Thu, Apr 3, 2008 at 3:32 PM, Jono Spiro <[email protected]> wrote:
    A new message was posted by Jono Spiro in
    Developers --
      Using Eclipse project definitions to build the Flex SDK
    Try changing the sdk for the framework lib project to trunk (you'll need to add a new flex sdk, name it whatever you want) -- it's in the project properties. It's using the wrong compiler.
    - Jono
    From: Ben Clinkinbeard <[email protected]>
    Reply-To: <[email protected]>
    Date: Thu, 3 Apr 2008 05:13:43 -0700
    To: <[email protected]>
    Subject: Re: Using Eclipse project definitions to build the Flex SDK
    A new message was posted by Ben Clinkinbeard in
    Developers --
      Using Eclipse project definitions to build the Flex SDK
    I am running FB on top of Eclipse 3.3.2.
    <http://3.3.2.>  <
    <http://3.3.2.>
    http://3.3.2.>  I checked out the whole SDK trunk and can build the main ant task with no errors. I used the instructions mentioned above to create a Flex framework library project and thats where the error comes in. (I had tried to manually build a framework project a few times and it was a nightmare.) I would probably prefer to work on the 3.0.x branch/tag as I hope to submit a patch or two but saw Joe mention that the project defs only existed in the trunk.
    Searching Google for the oem error turns up lots of links about projects that had assets deleted and the build got confused but following the instructions on how to fix proved unsuccessful.
    Thanks,
    Ben
    On Thu, Apr 3, 2008 at 1:45 AM, Jono Spiro <[email protected]> wrote:
    A new message was posted by Jono Spiro in
    Developers --
      Using Eclipse project definitions to build the Flex SDK
    I always forget what that error means when it comes up -- though it's been ages since I've seen it last, literally.
    Joe: Since you mention Java 1.5, I'm guessing the errors are in the asdoc package? Those should be turned off (read: turned into a warning) -- Eclipse is a little too persnickety about that particular error. There's a preference for this in the Java section under warnings and errors. It's turned off in the trunk dev projects. Otherwise, you should be able to run the compiler directly with no problems (okay, one more caveat: there's a class loader issue with the OEM, fixed in trunk if you look for my Java 1.5 checkin).
    Ben: What is your setup? What are you building (Ryan mentions trunk, Joe mentions 30x), which Eclipse, which dev projects, did you build the sdk from the commandline first, etc.?
    Cheers,
    Jono
    View/reply at Using Eclipse project definitions to build the Flex SDK <
    <http://www.adobeforums.com/webx?13@@.59b4a9d4/3>
    http://www.adobeforums.com/webx?13@@.59b4a9d4/3>
    Replies by email are OK.
    Use the unsubscribe <
    <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>
    http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>  form to cancel your email subscription.
    View/reply at Using Eclipse project definitions to build the Flex SDK <
    <http://www.adobeforums.com/webx?13@@.59b4a9d4/5>
    http://www.adobeforums.com/webx?13@@.59b4a9d4/5>
    Replies by email are OK.
    Use the unsubscribe <
    <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>
    http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3
    <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3> >  form to cancel your email subscription.
    View/reply at Using Eclipse project definitions to build the Flex SDK
    <http://www.adobeforums.com/webx?13@@.59b4a9d4/6>
    Replies by email are OK.
    Use the unsubscribe
    <http://www.adobeforums.com/webx?280@@.59b4a9d4%21folder=.3c060fa3>  form to cancel your email subscription.
    View/reply at Using Eclipse project definitions to build the Flex SDK
    <http://www.adobeforums.com/webx?13@@.59b4a9d4/7>
    Replies by email are OK.
    Use the unsubscribe
    <http://www.adobeforums.com/webx?280@@.59b4a9d4!folder=.3c060fa3>  form to cancel your email subscription.

  • How do I get javadoc to open in window rather than tab?

    Hi,
    Does anyone know how to get javadoc to open in a new window rather than a tab?
    Thanks,
    Will
    Message was edited by:
    decuser

    At this time that feature is not available. If you are trying to view Javadoc and Code at the same time you can try a split pane view that places both documents side-by-side.
    --RiC                                                                                                                                                                                                                                                                                                                                                                               

  • 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

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

Maybe you are looking for