Home » Eclipse Projects » Dali » JPA implementation library warning
|
Re: JPA implementation library warning [message #478984 is a reply to message #468448] |
Fri, 07 August 2009 19:34 |
Paul Fullbright Messages: 201 Registered: July 2009 |
Senior Member |
|
|
Leonard Theivendra wrote:
> Hi, when a JPA facet enabled project is created targeting a runtime with
> the necessary JPA runtime libs, this warning always appears:
> "The JPA facet requires a JPA implementation library to be present on the
> project classpath. By disabling library configuration, the user takes on
> the responsibility of ensuring that the classpath is configured
> appropriately via alternate means"
> Not sure if this is a bug since a runtime with appropriate libs is already
> targetted?
> If not, is there any way to turn this off in adopter code? i.e. for a
> project using a non-generic adopter specific platform, and a runtime that
> has the appropriate libs, it would be best if this warning didn't show up
> at all.
If your runtime provides libraries for a JPA facet, then there should be
another option: "Runtime Library Provider" among the list of library
options. Selecting this option will allow automatic classpath
configuration if you remove (or change, eventually) the JPA facet from
your project, and helps to minimize libraries brought in to your eclipse
workspace. According to the warning above, you've selected to "Disable
Library Configuration", and we feel that this is an appropriately severe
warning for users in that case. Users in this case will probably need to
actively maintain their classpaths in order to retain full Dali
functionality.
It's possible that your runtime does not return libraries specifically for
a JPA facet, even though it contains JPA libraries. If so, this is most
likely a deficiency in that particular runtime definition. See the
org.eclipse.wst.common.project.facet.core.runtimes extension point
(adapter element) for more details on this.
- Paul
|
|
| |
Re: JPA implementation library warning [message #482190 is a reply to message #481702] |
Tue, 25 August 2009 16:13 |
Paul Fullbright Messages: 201 Registered: July 2009 |
Senior Member |
|
|
Leonard Theivendra wrote:
> Thanks Paul. This appears to be a change in behaviour for Dali 2.2 since
> in 2.0.x the "Use implementation provided by server runtime" option is
> selected by default when using the same runtime provider and JPA platform.
Yes, this made the "new and noteworthy" for 2.1:
http://eclipse.org/webtools/releases/3.1.0/newandnoteworthy/ jpa.php
> In 2.2, the only option in the pulldown is "Disable library
> configuration". Is this because our server runtime doesn't define
> specific libraries for the JPA facet?
It's because it isn't set up to *provide* libraries for the JPA facet.
Note that if you use "Disable library configuration", you should be in
the same boat as 2.0.x, only with a configuration warning.
> I tried adding this but it didn't seem to help:
>
> <supported>
> <runtime-component
> id="xyz.runtime"
> version="1.0"/>
> <facet
> id="jpt.jpa"
> version="1.0, 2.0"/>
> </supported>
>
> Do you have any examples what the server runtime adapter needs to define
> to make the "Runtime library provider" option show up and get chosen by
> default?
Unfortunately, WTP server runtimes do not yet provide this functionality.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254536
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254537
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254540
For examples, you'll have to check JBoss Tools or OEPE, who I believe
already have this funtionality, and unfortunately, for more help, WTP
common would be a better place to seek it.
Hope this helps,
- Paul
|
|
|
Re: JPA implementation library warning [message #617463 is a reply to message #468448] |
Fri, 07 August 2009 19:34 |
Paul Fullbright Messages: 201 Registered: July 2009 |
Senior Member |
|
|
Leonard Theivendra wrote:
> Hi, when a JPA facet enabled project is created targeting a runtime with
> the necessary JPA runtime libs, this warning always appears:
> "The JPA facet requires a JPA implementation library to be present on the
> project classpath. By disabling library configuration, the user takes on
> the responsibility of ensuring that the classpath is configured
> appropriately via alternate means"
> Not sure if this is a bug since a runtime with appropriate libs is already
> targetted?
> If not, is there any way to turn this off in adopter code? i.e. for a
> project using a non-generic adopter specific platform, and a runtime that
> has the appropriate libs, it would be best if this warning didn't show up
> at all.
If your runtime provides libraries for a JPA facet, then there should be
another option: "Runtime Library Provider" among the list of library
options. Selecting this option will allow automatic classpath
configuration if you remove (or change, eventually) the JPA facet from
your project, and helps to minimize libraries brought in to your eclipse
workspace. According to the warning above, you've selected to "Disable
Library Configuration", and we feel that this is an appropriately severe
warning for users in that case. Users in this case will probably need to
actively maintain their classpaths in order to retain full Dali
functionality.
It's possible that your runtime does not return libraries specifically for
a JPA facet, even though it contains JPA libraries. If so, this is most
likely a deficiency in that particular runtime definition. See the
org.eclipse.wst.common.project.facet.core.runtimes extension point
(adapter element) for more details on this.
- Paul
|
|
| |
Re: JPA implementation library warning [message #617504 is a reply to message #481702] |
Tue, 25 August 2009 16:13 |
Paul Fullbright Messages: 201 Registered: July 2009 |
Senior Member |
|
|
Leonard Theivendra wrote:
> Thanks Paul. This appears to be a change in behaviour for Dali 2.2 since
> in 2.0.x the "Use implementation provided by server runtime" option is
> selected by default when using the same runtime provider and JPA platform.
Yes, this made the "new and noteworthy" for 2.1:
http://eclipse.org/webtools/releases/3.1.0/newandnoteworthy/ jpa.php
> In 2.2, the only option in the pulldown is "Disable library
> configuration". Is this because our server runtime doesn't define
> specific libraries for the JPA facet?
It's because it isn't set up to *provide* libraries for the JPA facet.
Note that if you use "Disable library configuration", you should be in
the same boat as 2.0.x, only with a configuration warning.
> I tried adding this but it didn't seem to help:
>
> <supported>
> <runtime-component
> id="xyz.runtime"
> version="1.0"/>
> <facet
> id="jpt.jpa"
> version="1.0, 2.0"/>
> </supported>
>
> Do you have any examples what the server runtime adapter needs to define
> to make the "Runtime library provider" option show up and get chosen by
> default?
Unfortunately, WTP server runtimes do not yet provide this functionality.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254536
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254537
https://bugs.eclipse.org/bugs/show_bug.cgi?id=254540
For examples, you'll have to check JBoss Tools or OEPE, who I believe
already have this funtionality, and unfortunately, for more help, WTP
common would be a better place to seek it.
Hope this helps,
- Paul
|
|
|
Goto Forum:
Current Time: Mon Sep 23 18:31:41 GMT 2024
Powered by FUDForum. Page generated in 0.05626 seconds
|