[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dali-dev] Re: Dali Planning
|
Hi guys,
Regarding Dali 2.0, hare are two areas that I wouldn't mind seeing.
1) Handle populating persistence.xml with connection info (maybe this was
already in plan).
a) It seems redundant that I create a connection when I add the JPA facet and
generate my entities, and then I need to put all of those same connection
properties into my persistence.xml, and the tools already know what needs to go
in there. I realize that this is provider-specific, so it probably has to tie
in there.
b) if using a datasource, it would be nice if there was some way to add that
(either from the wizard, or an editor).
2) Allow developers and providers to better extend Dali's and utilize
capabilities.
a) I would like to extend/override some of Dali's entity generation. Bug 186288
mentions that I can provide my own Generation wizard, which is really not what I
would want to do. I just want to do some simple things such as choose how
temporal types are generated (for example, java.util.Date vs. java.sql.Date as I
mentioned previously). I'd rather not have to do a whole bunch of extending
internal Dali wizards just to get some small improvements (or worse as I'm doing
now, and running a post-operation to go through all the generated entities and
load up the Dali models to add annotations to the entities, etc).
b) open up the Dali models and make them usable from outside of the JPA
properties view. Dali has some really nice models which are currently all
marked internal. It would be nice to open these up and make it easy to update
them. Currently this is difficult in that they seem somewhat tied to the
property view and it's not easy to run these operations outside of the UI
thread. Each model update needs to be wrapped in a Display.syncExec (bug
184479), and some model updates are slow as they send a lot of notifications
(bug 191122) even if called headlessly from outside the properties view. And
currently, I need to get the compilation unit after each model update and save
it myself. If I'm dealing with the Dali model, ideally I wouldn't have to know
about or interact with compilation units.
The Dali 1.0 release is fantastic, and I look forward to 2.0. Thanks for all
the good work, guys.
-Tom
