Home » Eclipse Projects » Dali » M6 feedback
|
Re: M6 feedback [message #434416 is a reply to message #434414] |
Tue, 17 April 2007 16:15 |
Neil Hauge Messages: 475 Registered: July 2009 |
Senior Member |
|
|
Hi,
Glad to hear that things are working for you. Regarding the error
messages, I wanted to make sure you are getting full validation. In M6,
Dali requires that you include your Entities in the persistence.xml file
to get validation. If your classes are annotated with @Entity, you can
use the right-click menu on the persistence.xml to "JPA Tools->Synchronize
Classes", which will add the Entity references to your persistence.xml
file. All of this is currently required to get validation of your
Entities, which should include validation for all basic table concepts
(tables and columns).
Wanted to make sure everything was working for you.
Also, could you be a bit more specific on your first and third items below
regarding the views?
Thanks for the feedback,
Neil
Gereon Fassbender wrote:
> Hi,
> M6 is working fine here :-)
> Here is my list of "nice to have features":
> I would like much more error messages on erroneous source files.
> Because you can configure a database connection, maybe the consistence
> with the database could be checked (but should be optional).
> JPA view:
> - the view is unsorted, I would prefer the order of occurrence in the
> source, some people might prefer alphabetical order
> - transient fields should be filtered out - maybe optional
> BTW: fields which have no setter are not displayed
> - it would be helpful if the column-names would be displayed (e.g. in
> brackets, really cool would be a TreeTable)
> Gereon
|
|
|
Re: M6 feedback [message #434418 is a reply to message #434416] |
Wed, 18 April 2007 22:55 |
Gereon Fassbender Messages: 16 Registered: July 2009 |
Junior Member |
|
|
Hi Neil,
> Dali requires that you include your Entities in the persistence.xml file
> to get validation. If your classes are annotated with @Entity, you can
Yes I added it there. I get the "no ID defined" error, but it was the
only one so far.
Examples for errors: wrong type in getter, duplicate (db-)column names,
mix of field and property based access, missing setter(?), wrong
temporal type, wrong "mappedBy" property, improper property-type in
OneToMany relationship.
When you read the database schema, you could add much more checks.
I just noticed, the links to the classes in the persistence.xml are
checked now, that's really nice.
> Also, could you be a bit more specific on your first and third items
> below regarding the views?
I tested the first again and the order was the same as in the source -
strange. Then I added a new property in the middle and it appeared at
the end of the list. It was still unsorted after close/reopen the file
or changing the perspective. The view seems to be sorted only after a
Eclipse restart.
With column-name I meant the *database* column name. Maybe it could be
helpful to see it in the JPA Structure View. (not important, nice to have)
A TreeTable is a visual component which is a tree but also has columns.
In SWT it is called TableTree. This would be really cool because you can
show the name in one column along with other information.
Gereon
|
|
|
Re: M6 feedback [message #593622 is a reply to message #434414] |
Tue, 17 April 2007 16:15 |
Neil Hauge Messages: 475 Registered: July 2009 |
Senior Member |
|
|
Hi,
Glad to hear that things are working for you. Regarding the error
messages, I wanted to make sure you are getting full validation. In M6,
Dali requires that you include your Entities in the persistence.xml file
to get validation. If your classes are annotated with @Entity, you can
use the right-click menu on the persistence.xml to "JPA Tools->Synchronize
Classes", which will add the Entity references to your persistence.xml
file. All of this is currently required to get validation of your
Entities, which should include validation for all basic table concepts
(tables and columns).
Wanted to make sure everything was working for you.
Also, could you be a bit more specific on your first and third items below
regarding the views?
Thanks for the feedback,
Neil
Gereon Fassbender wrote:
> Hi,
> M6 is working fine here :-)
> Here is my list of "nice to have features":
> I would like much more error messages on erroneous source files.
> Because you can configure a database connection, maybe the consistence
> with the database could be checked (but should be optional).
> JPA view:
> - the view is unsorted, I would prefer the order of occurrence in the
> source, some people might prefer alphabetical order
> - transient fields should be filtered out - maybe optional
> BTW: fields which have no setter are not displayed
> - it would be helpful if the column-names would be displayed (e.g. in
> brackets, really cool would be a TreeTable)
> Gereon
|
|
|
Re: M6 feedback [message #593640 is a reply to message #434416] |
Wed, 18 April 2007 22:55 |
Gereon Fassbender Messages: 16 Registered: July 2009 |
Junior Member |
|
|
Hi Neil,
> Dali requires that you include your Entities in the persistence.xml file
> to get validation. If your classes are annotated with @Entity, you can
Yes I added it there. I get the "no ID defined" error, but it was the
only one so far.
Examples for errors: wrong type in getter, duplicate (db-)column names,
mix of field and property based access, missing setter(?), wrong
temporal type, wrong "mappedBy" property, improper property-type in
OneToMany relationship.
When you read the database schema, you could add much more checks.
I just noticed, the links to the classes in the persistence.xml are
checked now, that's really nice.
> Also, could you be a bit more specific on your first and third items
> below regarding the views?
I tested the first again and the order was the same as in the source -
strange. Then I added a new property in the middle and it appeared at
the end of the list. It was still unsorted after close/reopen the file
or changing the perspective. The view seems to be sorted only after a
Eclipse restart.
With column-name I meant the *database* column name. Maybe it could be
helpful to see it in the JPA Structure View. (not important, nice to have)
A TreeTable is a visual component which is a tree but also has columns.
In SWT it is called TableTree. This would be really cool because you can
show the name in one column along with other information.
Gereon
|
|
|
Goto Forum:
Current Time: Mon Sep 23 21:02:16 GMT 2024
Powered by FUDForum. Page generated in 0.03807 seconds
|