Persistence Diagram - painful reminder... take it out :(
I've tried to use the persistence diagram, and besides that it needs a
persistent unit (which I've never used before and won't be using for a
long time to give implementors some time to get it stable and to see if
it really catches on), I was DISAPPOINTED big time.
0) I'd love to use it !! (really, use)
1) as noted in previous posts, it's hidden deep down somewhere and
requires a PU
2) it it as far as I could make out "look - don't touch", ie. I can't
add attributes to Entities, change or refactor, it doesn't integrate
into the rest of IDEA
but most sadly:
3) it's a painful reminder (to the community of those who've been beta
testing it) of fabrique and how good, actually insanely great and
integrated it was there.
In fabrique, you showed (us?) how useful such a diagram could be, it
was the center of the application from which you could build the
business model and integrate it downwards toward the database and
upwards to the user interface. Non of this is available (yet?) and
although I'm hoping that you get there at one time, I suspect it won't
happen in the 6.0 or even 6.5 timeframe.
So... why not take it out completely (same as you removed the struts
diagram from the plugin), because it's not quite there yet and makes no
sense at all in the application context, and it will only hurt both the
impression users get of IDEA and, the developers who know how it might
have been... if it was done correctly.
O
Please sign in to leave a comment.
Oliver,
If you don't have a PU, what do you need this diagram for? Are you using
annotations without PU?
On 2006-08-16 17:27:07 +0200, "Mike Aizatsky (JetBrains)"
<mike.aizatsky@jetbrains.com> said:
>> I've tried to use the persistence diagram, and besides that it needs a
>> persistent unit (which I've never used before and won't be using for a
>> long time to give implementors some time to get it stable and to see if
>> it really catches on), I was DISAPPOINTED big time.
no, I just meant that I only tried out the diagram, but in my active
codebase I'm not making use of PU. Nevertheless, this kind of diagram
would be useful to model the other, (eg. plain hibernate) data objects.
The PU diagram which is present right now comes almost for free for PU
only. We'll focus on diagram editing and support for other frameworks in
Post-Demetra version.
BTW, I heard it's quite possible to use current PU diagram if you're
using Hibernate Annotations.
Mike Aizatsky (JetBrains) wrote:
I thought that the JPA spec abandoned the persistence unit? Didn't look
too close at it recently (EJB3 was too late for our project), but this
was one of the things I think I remember...
regards,
Messi
Messi wrote:
>> BTW, I heard it's quite possible to use current PU diagram if you're
>> using Hibernate Annotations.
The abandoned thing was "PAR" (persistence unit archive) concept.
Now only persistence.xml that lists all persistence units is required.
Regards,
Gregory Shrago
I have a PU, but the diagram is impossible for me to get at, since PU's according to IDEA can only exist within EJB modules, but as far as EE is concerned, they can be in any jar in the classpath.
Hello Hani,
The issue will be addressed in the next EAPs.
Module libraries will be searched for persistent classes and persistence
units.
Regards,
Gregory Shrago
Hani Suleiman wrote: