Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dali » Questions about M1, I2 drop of Dali
Questions about M1, I2 drop of Dali [message #578067] Thu, 23 March 2006 14:35
Kevin Sutter is currently offline Kevin SutterFriend
Messages: 104
Registered: July 2009
Senior Member
I've been experimenting with the Milestone 1 drivers of Dali and recently
moved up to the Iteration 2 driver. I have the following observations.
I'm not sure if these are bugs and should be reported via Bugzilla, or
maybe I'm just not educated enough yet... :-)

o MySQL still doesn't work. I get many, many errors in the error.log
whenever I attempt to use a MySQL connection. But, part of the problem
might be due to the non-support of MySQL 5.0. I'm using 5.0 (current
download), but the Eclipse Dali tooling only seems to recognize 4.0 and
4.1. Maybe that's part of the problem.

o The Persistence Properties seems to have a problem with any value for
the GenerationType other than Auto. I am now getting the following error
when the GenerationType is either Sequence or Table. I have specified the
required name field, but I still get the following error (sorry for the

Severity Description Resource In Folder Location Creation Time Id
2 Sequence generator "null" cannot be
resolved jpa.dali/src/com/ibm/ws/persistence/dali line
46 March 22, 2006 11:07:35 AM 16315

o I also have noticed that the fields don't always get updated in the
Persistence Properties and/or the corresponding code. For example, while
I was experimenting with reproducing the above problem, I now have an
annotation that indicates a GeneratedValue with a name of "a", but the
Persistence Properties panel doesn't display this name...

o I have to question why the database connection has to be associated at
the project level. Couldn't you have one Entity that accesses DB2 and
another that access MySQL? It seems that we need the ability to associate
a database connection at the package level at the least and at the
Object/Entity level, preferred. Or, maybe a means of overriding the
persistence information at these lower levels?

o The generation of Entities and DDL are a nice addition, but here again,
these seem to be at too high of a level. Doing this at that project level
seems too high. Maybe for simple projects, but not in reality. Maybe I'm
looking for too many features too early... If you are planning to improve
on this, I just can't tell from the milestone plan.

o I can't get the DDL generation to work at all. I can click on it and
it acts like it's doing something, but I don't see anything get generated.
And, since this is at the project level, will it be traversing all
Entities in the project and attempting to generate the ddl associated with
every Entity. If the Entity was already properly annotated based on a
database connection, will it generate ddl anyway? I really wanted this
feature to work since I am not a ddl expert and wanted to work top down.
It's just not intuitive yet.

o The generation of Entities worked. But, it automatically overwrote the
code that was already present in my Entity classes. That's not very
nice... :-) If it's going to create Entities that already exist, it
should ask whether you want to overwrite the code already present, or
maybe offer to write a separate file with a different name.

Maybe this was too much for single post. Just trying to figure out the
best way to communicate these observations. Thanks!

Previous Topic:Looking for Versant opensource JDO runtime
Next Topic:ClassLoader, GlassFish for Java SE and Eclipse-RichClient
Goto Forum:

Current Time: Sun Jun 26 17:32:51 GMT 2016

Powered by FUDForum. Page generated in 0.02343 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software