| Using Dali in a non-J2EE environment. [message #607408] |
Thu, 15 November 2007 16:45 |
 Alex Mising name
Messages: 149
Registered: March 2010 |
Senior Member |
|
|
Hi all,
I've recently started using Eclipse to develop RCP applications. I am
using Dali in that context. One of my apps uses the OpenJPA
implementation and Derby for the backend. The other uses Hibernate and
Oracle 10g. I'd like to share a couple of thoughts on my experience:
1) One thing that I find inconvenient is that Dali projects are defined
as J2EE projects. Since JPA can be used in non J2EE environments, I'd
very much prefer it if they were pure Java projects.
Currently, I create a Dali project with no target runtime and then
convert it to a plug-in using the context menu "PDE Tools->Convert
projects to plug-in projects".
One gets the following irritating warnings (perhaps because the J2EE
module not being included in an EAR?):
Classpath entry org.eclipse.jdt.USER_LIBRARY/OpenJPA 1.0.1 will not be
exported or published. Runtime ClassNotFoundExceptions may result.
dali.prj P/dali.prj 1195066325500 1308
Severity and Description Path Resource Location Creation Time Id
Classpath entry org.eclipse.pde.core.requiredPlugins will not be
exported or published. Runtime ClassNotFoundExceptions may result.
dali.prj P/dali.prj 1195066325500 1309
2) It'd be quite convenient to be able to generate beans instead of
pojos. A lot of entities in client-server apps are presented to users
for editing using data-bound widgets. Adding an extra menu entry
"Generate entity beans..." that has the code generator add javabeans
property change listeners, should be fairly trivial. It would greatly
enhance ease use of entities with GUI controls.
I know (1) is just a nuisance, but I believe (2) is a legitimate
enhancement. Any comments on that? Would the Dali team be willing to add
such a feature?
|
|
|
Powered by
FUDForum. Page generated in 0.02570 seconds
] 
Search
Help
Register
Login
Home
