Category

Europa woes with JPA and Dali

I was looking forward to the Europa Eclipse release. There are nice things included. But,…

For an all-in-one jee download you also had to go to the update manager to download DTP “enablement” to do anything. Poor out-of-the-box experience right away.

After updating and rebooting I get this in a dialog box after the “resynching” process:
An error occurred while traversing resources.

org.eclipse.jdt.core.dom.TypeLiteral cannot be cast to org.eclipse.jdt.core.dom.StringLiteral

Fine. What do I do about it?

There are show stopper bugs when you try to use JPA and the Dali tools.
The validation on persistence.xml fails. The xsd – and the JPA spec – and gazillions of examples on the web – allow multiple persistence units in this file. In this release you will be flagged with the red X of death and told your are using “multiple persistence units” in the problems view. How about following the JPA spec please?

OK, I moved the other PUs and have just one going to derby via glassfish jpa in a JSE simple example. Trying to simply assign the Id annotation in the JPA details view generates a “Unhandled event loop exception” in the error log. (stack trace appended below).

Yeesh.

One Reply to “Europa woes with JPA and Dali”

  1. There are show stopper bugs when you try to use JPA and the Dali tools.
    The validation on persistence.xml fails. The xsd – and the JPA spec –
    and gazillions of examples on the web – allow multiple persistence
    units in this file. In this release you will be flagged with the red
    X of death and told your are using “multiple persistence units”
    in the problems view. How about following the JPA spec please?

    Thanks for trying out Dali and I’m sorry you’re having troubles.
    Multiple persistence unit support is not in Dali 1.0 but support is on the
    roadmap for 2.0. It’s a pretty tough feature to implement and, AFAIK, no
    other JPA tooling supports multiple persistence units at this time. The issues
    center on understanding context. For example, if an entity is included in
    multiple persistence units, each targeting different database schemas, what
    happens when you want to provide code assist for annotations referencing schema
    values. What values should be shown in the code assist drop down for @Table?
    The Dali team is looking for feedback on how we can smoothly add multiple
    persistence unit support into 2.0 so it would be great if you can contribute to
    the discussion! The Dali newsgroup is a good place to contribute feedback:
    http://www.eclipse.org/newsportal/thread.php?group=eclipse.technology.dali

    After updating and rebooting I get this in a dialog box after the
    “resynching” process:
    An error occurred while traversing resources.
    org.eclipse.jdt.core.dom.TypeLiteral cannot be cast to org.eclipse.jdt.core.dom.StringLiteral

    It looks like you’ve hit a bug discovered after 1.0 went out:
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=196086. This should be fixed in
    the WTP 2.0/Dali 1.0 maintenance release scheduled for September.

    OK, I moved the other PUs and have just one going to derby via
    glassfish jpa in a JSE simple example. Trying to simply assign
    the Id annotation in the JPA details view generates a “Unhandled
    event loop exception” in the error log. (stack trace appended below).

    Not sure how you got this but it maybe a result of some bad state resulting
    from the previous exception. Hopefully you don’t see it after a restart.

    Again, I’m sorry you’re encountering problems but I hope you’ll
    log bugs in Bugzilla for things you hit and enhancement requests for things you
    think are missing. The Dali community needs more user feedback! We’d
    really appreciate your help!

    Shaun Smith
    Dali co-Lead
    EclipseLink Ecosystem Development Lead

Leave a Reply to Shaun Smith Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.