Cool thanks Neil, I'll open an ER for 1).
One other thing that comes to mind: would it be possible for Dali to
provide some product customization settings? There is a mechanism that wtp
provides (I believe) for adaptors to set default values for things like
wtp wizard pages, etc... i.e. being able to set the default value for
platform in the JPA facet config. Let me know if I need to open an ER for
this too.
Regards,
Len.
------------------------------------------
Leonard Theivendra
Websphere / IBM Software Solutions Toronto
email: theivend@xxxxxxxxxx
tel: (905) 413-3777 tie: 969-3777
fax: (905) 413-4920
Neil Hauge <neil.hauge@xxxxxxxxxx>
Sent by: dali-dev-bounces@xxxxxxxxxxx
07/11/2007 05:42 PM
Please respond to
neil.hauge@xxxxxxxxxx; Please respond to
"General Dali EJB ORM developer discussion." <dali-dev@xxxxxxxxxxx>
To
"General Dali EJB ORM developer discussion." <dali-dev@xxxxxxxxxxx>
cc
Chuck Bridgham <cbridgha@xxxxxxxxxx>
Subject
Re: [dali-dev] Re:Dali Planning
Hey Len,
1) Sounds cool. We didn't know about this functionality, but it sounds
like a nice enhancement. I don't think there is an ER logged for this
yet, so feel free to enter one. We will investigate, but it sounds like
something that should be in the 2.0 plan.
2) Yes, this is in the tentative plan for 2.0 that is taking shape, and
will soon be posted on the wiki.
3) Yes, definitely quick fixes, and regarding annotation completion
proposals, check out the 1.0 release. We have most of this covered.
Check out https://bugs.eclipse.org/bugs/show_bug.cgi?id=181471.
Thanks for the feedback,
Neil
Leonard Theivendra wrote:
1) One area that we'd like to see some improvements on is the
importing/exporting of jars/ears with JPA artifacts (not sure if this is
already logged as a requirement?). For example, when importing a jar
with
JPA artifacts, it would be nice if the JPA facet gets set on the project
that gets created. WTP's EJB import operations I believe provide an
extension point where child operations can be hooked in to detect certain
artifacts and then set the necessary facets (Chuck can provide more
info).
So at the very least, Dali could hook into the EJB jar import op so that
when EJB jars with JPA artifacts are imported, the JPA facet gets set. I
suspect doing this for generic non-EJB jars shouldn't be too much of a
stretch, and some WTP code could be employed there too?
2) Are there any plans to contribute to the navigator to display JPA
beans
based on annotations and xml metadata? I recall there was some discussion
early in the 1.0 timeframe about doing something in 2.0 for contributing
to
the common navigator, with tree navigation to entities based on
persistence.xml and persistence units.
3) Any plans for quick fixes, refactorings, and annotation completion
proposals in Dali 2.0?
Regards,
Len.
------------------------------------------
Leonard Theivendra
Websphere / IBM Software Solutions Toronto
email: theivend@xxxxxxxxxx
tel: (905) 413-3777 tie: 969-3777
fax: (905) 413-4920
----- Forwarded by Leonard Theivendra/Toronto/IBM on 07/05/2007 02:22 PM
-----
Neil Hauge
<neil.hauge@oracl
e.com> To
Sent by: "General Dali EJB ORM developer
dali-dev-bounces@ discussion."
<dali-dev@xxxxxxxxxxx>
eclipse.org cc
Subject
07/02/2007 04:10 [dali-dev] Dali Planning
PM
Please respond to
neil.hauge@oracle
.com; Please
respond to
"General Dali EJB
ORM developer
discussion."
<dali-dev@eclipse
.org>
Adopters,
We are going to be thinking about Dali (2.0?) in the near future, so I
wanted to start a thread to gather any new requirements that may have
come up recently. Much of what has been discussed is either logged as
an enhancement, or is documented on the wiki here -
http://wiki.eclipse.org/Dali_Extension_Requirements_Meeting:_1-24-07.
What I would like to know is if there are any other things that we
should be thinking about as we try to plan for the next major release.
Please feel free to use this e-mail thread to bring up anything that
hasn't been logged yet. We can discuss any new requirements and log
appropriate bugs for them. If necessary or desired, we could have a
requirements call to discuss these new items as well.
Thanks,
Neil Hauge
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev
_______________________________________________
dali-dev mailing list
dali-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dali-dev