|
| Re: Using Dali in a non-J2EE environment. [message #434634 is a reply to message #434633] |
Fri, 16 November 2007 16:35  |
 Neil Hauge
Messages: 475
Registered: July 2009 |
Senior Member |
|
|
Hi,
Regarding item 1 - There is actually a bug filed for this issue against
the component that produces this warning -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=190783. In your case, since
you are using JPA in a pure SE situation, it is probably safe to disable
the "Classpath Dependency Validator" in the Project Properties->Validator
page. This will stop this warning from displaying, and you aren't
concerned with other deployment related issues.
Unfortunately we don't have the bandwidth to maintain a Nature and Facet
structure for the Dali project, and since we pretty much have to be a
Facet to integrate with Java EE project, that is what we have to do. That
said, we are going to add support to add the JPA Facet to a pure Java
project for 2.0.
Regarding item 2 - I think what you mean to say is that you would like
for Dali to generate POJO's that implement java bean property change
notification. I think this is a valid enhancement request, but I'm not
sure that it is a trivial enhancement. Please enter this as an
enhancement in bugzilla and I will put it in the "helpwanted" category.
This basically means that this is a fine enhancement request, but we would
likely need someone to contribute the functionality for us to include it
in an upcoming release.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Dali%20J PA%20Tools&bug_severity=enhancement
Thanks for your feedback. We do appreciate it.
Neil
Alexandros Karypidis wrote:
> 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?
|
|
|
| Re: Using Dali in a non-J2EE environment. [message #607409 is a reply to message #434633] |
Fri, 16 November 2007 16:35 |
Neil Hauge
Messages: 475
Registered: July 2009 |
Senior Member |
|
|
Hi,
Regarding item 1 - There is actually a bug filed for this issue against
the component that produces this warning -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=190783 In your case, since
you are using JPA in a pure SE situation, it is probably safe to disable
the "Classpath Dependency Validator" in the Project Properties->Validator
page. This will stop this warning from displaying, and you aren't
concerned with other deployment related issues.
Unfortunately we don't have the bandwidth to maintain a Nature and Facet
structure for the Dali project, and since we pretty much have to be a
Facet to integrate with Java EE project, that is what we have to do. That
said, we are going to add support to add the JPA Facet to a pure Java
project for 2.0.
Regarding item 2 - I think what you mean to say is that you would like
for Dali to generate POJO's that implement java bean property change
notification. I think this is a valid enhancement request, but I'm not
sure that it is a trivial enhancement. Please enter this as an
enhancement in bugzilla and I will put it in the "helpwanted" category.
This basically means that this is a fine enhancement request, but we would
likely need someone to contribute the functionality for us to include it
in an upcoming release.
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Dali%20J PA%20Tools&bug_severity=enhancement
Thanks for your feedback. We do appreciate it.
Neil
Alexandros Karypidis wrote:
> 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.03241 seconds
] 
Search
Help
Register
Login
Home
