Eclipse Community Forums: Dali » Questions about M1, I2 drop of Dali

Help

Home

Home » Eclipse Projects » Dali » Questions about M1, I2 drop of Dali

Show: Today's Messages :: Show Polls :: Message Navigator

Questions about M1, I2 drop of Dali [message #433631]

Thu, 23 March 2006 14:35

Kevin Sutter

Messages: 106
Registered: July 2009

Senior Member

Hi,
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
formatting).

Severity Description Resource In Folder Location Creation Time Id
2 Sequence generator "null" cannot be
resolved Address.java 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!

Kevin

Report message to a moderator

Re: Questions about M1, I2 drop of Dali [message #433635 is a reply to message #433631]

Wed, 29 March 2006 15:59

Karen Butzke

Messages: 220
Registered: July 2009

Senior Member

answers inline:

> 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.

We are using the RDB component of WTP for defining connections, accessing
the database, and generating ddl. After WTP 1.5 is released as part of
Calisto, we will be migrating to use the DataTools Project(DTP).

> 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
> formatting).

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

I can't seem to reproduce this problem, what do you have in the source
code when you see this error?

> 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...

Could you open a bug against Dali in bugzilla for this problem?

> 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?

This should be taken into account as we work on our "persistence unit"
support. I am not sure of the how we will handle multiple persistence
units per eclipse projects, but this is where you would define connection
information moving forward. I would imagine that for the .5 release we
will only support 1 persistence unit per eclipse project. We should make
this explicit in our milestone plan.

> 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.

DDL and entity generation are works in progress, we can add this to the
backlog of things that would be good to have for these. Could you open an
enhancment request for ddl gen?

> 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.

Did an error go to the error log? Did the entity generation wizard ever
open? The point of the DDL gen is to take the already annotated classes
and create ddl. At a minimum you will have to add the Entity anotation
and the id annotation and annotations for any reference mappings. After
that the generator will use the defaults defined in the persistence spec.
Yes, if the entity is annotated with info based on the database
connection, it will generate ddl.

> 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.

It would be great if you would add your suggestions to the enhancement
request for entity generation. This was a first pass at implementing it
with the minimum requirements. bug #130581

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

We are happy to get feedback from the community!

thanks,
Karen

Report message to a moderator

Re: Questions about M1, I2 drop of Dali [message #433643 is a reply to message #433635]

Tue, 04 April 2006 17:34

Kevin Sutter

Messages: 106
Registered: July 2009

Senior Member

Thank you, Karen, for your quick reply. I have created the appropriate
defects and/or features in Bugzilla. Additional comments are posted
below. Thanks again.

Kevin

---------------------------------
Karen Moore wrote:

> answers inline:

>> 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.

> We are using the RDB component of WTP for defining connections, accessing
> the database, and generating ddl. After WTP 1.5 is released as part of
> Calisto, we will be migrating to use the DataTools Project(DTP).

Okay, so the newer version of WTP/DTP should provide better database
connection support. I'm assuming that this will be part of the initial
Dali release.

>> 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
>> formatting).

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

> I can't seem to reproduce this problem, what do you have in the source
> code when you see this error?

Bugzilla report #134811 was created for this problem.

>> 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...

> Could you open a bug against Dali in bugzilla for this problem?

Bugzilla report #134819 was created for this problem.

>> 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?

> This should be taken into account as we work on our "persistence unit"
> support. I am not sure of the how we will handle multiple persistence
> units per eclipse projects, but this is where you would define connection
> information moving forward. I would imagine that for the .5 release we
> will only support 1 persistence unit per eclipse project. We should make
> this explicit in our milestone plan.

That would help with my expectations. Thanks.

>> 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.

> DDL and entity generation are works in progress, we can add this to the
> backlog of things that would be good to have for these. Could you open an
> enhancment request for ddl gen?

Feature enhancement #134821 was created for this request.

>> 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.

> Did an error go to the error log? Did the entity generation wizard ever
> open? The point of the DDL gen is to take the already annotated classes
> and create ddl. At a minimum you will have to add the Entity anotation
> and the id annotation and annotations for any reference mappings. After
> that the generator will use the defaults defined in the persistence spec.
> Yes, if the entity is annotated with info based on the database
> connection, it will generate ddl.

I never did receive the ddl generation wizard to appear. I have opened
bug report #134825 to track this problem.

>> 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.

> It would be great if you would add your suggestions to the enhancement
> request for entity generation. This was a first pass at implementing it
> with the minimum requirements. bug #130581

Will do. Thanks.

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

> We are happy to get feedback from the community!

> thanks,
> Karen

Report message to a moderator