|
|
|
Re: A Dali full of bugs [message #434515 is a reply to message #434514] |
Mon, 16 July 2007 16:21 |
Neil Hauge Messages: 475 Registered: July 2009 |
Senior Member |
|
|
Hi Sanjay,
Sorry that you are having a number of issues with the latest code. Let me
try to address some of them and hopefully get a little more feedback on
some of the issues.
> First exception occurs when I start Eclipse with JPA project.
> It says error "Initializing JPA model - an error occured while traversing
> resources." Stack trace shows "java.lang.ClassCastException:
> org.eclipse.jdt.core.dom.InfixExpression". Apparantly its a known bug.
This is something that we hadn't encountered before the release by us or
apparently by the community. It seems that since we do have a 1.0 out
now, we are getting more diverse usage of the tools, and this is driving
out some new issues. Given the severity of this item, we will work to fix
it quickly.
> Then I get "unhandled event loop exception" trying to create entities from
> database. I have valid connection to Postgres and Data Source explorer
> shows tables. Yet, stacktrace shows:
> java.util.NoSuchElementException
> at
>
org.eclipse.jpt.db.internal.DTPDatabaseWrapper.getDefaultCat alogName(DTPDatabaseWrapper.java:200)
> Does this thing work with anything other than Oracle ?
We have done testing with PostgreSQL and have successfully worked with and
generated entities from PostgreSQL and many other databases. We actually
fixed a related problem with PostgreSQL late in the release cycle, but I
assume you are running the final release. What version of PostgreSQL are
you using, and is there any more error information you can provide from
the log?
> Then tons of errors like "xyz" (Entity class name) is not spelled corectly
> in persistence.xml file. Why ? The same persistence.xml works perfectly
> fine in JDeveloper and NetBeans. This may be result of above errors but
> messages are certainly not very helpfully.
This is actually new functionality in the Platform and can be
altered/disabled in the preferences under General->Editors->Text
Editors->Spelling.
> Similarly can't specify "provider" in persistence.xml (under
> persistence-unit) either. Not compliant with schema. News to me.
This is not a Dali error, but is coming from the default schema
validation. Not sure how you are specifying the provider, but I don't get
any complaints with:
<persistence-unit name="FooUnit">
<provider>Foo</provider>
...
Perhaps you are picking up an invalid schema?
> I would have thought after three years of development and a production
> release label "1.0" - Dali would be a useful tool. Unfortunately I am
> little disappointed.
The project was actually created in the summer of 2005, so we've only been
going for about 2 years. Even though that seems like a decent amount of
time, the scope and complexity of building tools for JPA (in the way we
have chosen to do so) is impressive, especially when you add the
requirement of extensibility. We are happy to have something out that
will provide more feedback and bug reports so we can improve Dali as the
project progresses.
Thanks for your feedback,
Neil
> -Sanjay
|
|
|
|
|
|
|
|
|
|
Re: A Dali full of bugs [message #602434 is a reply to message #434514] |
Mon, 16 July 2007 16:21 |
Neil Hauge Messages: 475 Registered: July 2009 |
Senior Member |
|
|
Hi Sanjay,
Sorry that you are having a number of issues with the latest code. Let me
try to address some of them and hopefully get a little more feedback on
some of the issues.
> First exception occurs when I start Eclipse with JPA project.
> It says error "Initializing JPA model - an error occured while traversing
> resources." Stack trace shows "java.lang.ClassCastException:
> org.eclipse.jdt.core.dom.InfixExpression". Apparantly its a known bug.
This is something that we hadn't encountered before the release by us or
apparently by the community. It seems that since we do have a 1.0 out
now, we are getting more diverse usage of the tools, and this is driving
out some new issues. Given the severity of this item, we will work to fix
it quickly.
> Then I get "unhandled event loop exception" trying to create entities from
> database. I have valid connection to Postgres and Data Source explorer
> shows tables. Yet, stacktrace shows:
> java.util.NoSuchElementException
> at
>
org.eclipse.jpt.db.internal.DTPDatabaseWrapper.getDefaultCat alogName(DTPDatabaseWrapper.java:200)
> Does this thing work with anything other than Oracle ?
We have done testing with PostgreSQL and have successfully worked with and
generated entities from PostgreSQL and many other databases. We actually
fixed a related problem with PostgreSQL late in the release cycle, but I
assume you are running the final release. What version of PostgreSQL are
you using, and is there any more error information you can provide from
the log?
> Then tons of errors like "xyz" (Entity class name) is not spelled corectly
> in persistence.xml file. Why ? The same persistence.xml works perfectly
> fine in JDeveloper and NetBeans. This may be result of above errors but
> messages are certainly not very helpfully.
This is actually new functionality in the Platform and can be
altered/disabled in the preferences under General->Editors->Text
Editors->Spelling.
> Similarly can't specify "provider" in persistence.xml (under
> persistence-unit) either. Not compliant with schema. News to me.
This is not a Dali error, but is coming from the default schema
validation. Not sure how you are specifying the provider, but I don't get
any complaints with:
<persistence-unit name="FooUnit">
<provider>Foo</provider>
...
Perhaps you are picking up an invalid schema?
> I would have thought after three years of development and a production
> release label "1.0" - Dali would be a useful tool. Unfortunately I am
> little disappointed.
The project was actually created in the summer of 2005, so we've only been
going for about 2 years. Even though that seems like a decent amount of
time, the scope and complexity of building tools for JPA (in the way we
have chosen to do so) is impressive, especially when you add the
requirement of extensibility. We are happy to have something out that
will provide more feedback and bug reports so we can improve Dali as the
project progresses.
Thanks for your feedback,
Neil
> -Sanjay
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07478 seconds