| Classpath dependancy validator warning [message #538095] |
Fri, 04 June 2010 18:26  |
Eclipse User |
|
|
|
I am curious what, if anything, to do with the following warning (from the "Markers" tab):
Classpath entry org.eclipse.datatools.connectivity.jdt.DRIVERLIBRARY/Postgre SQL JDBC Driver will not be exported or published. Runtime ClassNotFoundExceptions may result.
Indeed, in the project in question, I get a ClassNotFound exception. Where can I learn about this? I don't see anything in the Connectivity properties that says anything about exporting or not.
In scrutinizing the various warning messages, I also have a warning during the startup of the Apache server:
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: [long path list here]
And:
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:Nearby' did not find a matching property.
What is the significance of these?
In part, this is a continuation of exploring a question I have in earlier. Hopefully the different emphasis of the question will prevent this from being perceived as a double post, and I promise to follow up in each context as appropriate.
Thanks!
|
|
|
| Re: Classpath dependancy validator warning [message #538106 is a reply to message #538095] |
Sat, 05 June 2010 00:13  |
| Eclipse User |
|
|
|
On 6/4/2010 4:26 PM, Phil Freihofner wrote:
> I am curious what, if anything, to do with the following warning (from
> the "Markers" tab):
>
> Classpath entry
> org.eclipse.datatools.connectivity.jdt.DRIVERLIBRARY/Postgre SQL JDBC
> Driver will not be exported or published. Runtime
> ClassNotFoundExceptions may result.
>
> Indeed, in the project in question, I get a ClassNotFound exception.
> Where can I learn about this? I don't see anything in the Connectivity
> properties that says anything about exporting or not.
>
> In scrutinizing the various warning messages, I also have a warning
> during the startup of the Apache server:
> INFO: The APR based Apache Tomcat Native library which allows optimal
> performance in production environments was not found on the
> java.library.path: [long path list here]
>
> And:
>
> WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting
> property 'source' to 'org.eclipse.jst.jee.server:Nearby' did not find a
> matching property.
>
> What is the significance of these?
>
> In part, this is a continuation of exploring a question I have in
> earlier. Hopefully the different emphasis of the question will prevent
> this from being perceived as a double post, and I promise to follow up
> in each context as appropriate.
>
> Thanks!
I believe what you're seeing is this.
In Java Build Path -> Libraries you have libraries, other than the JRE
System Library, that contribute to your project. If you plan on
deploying the application to a container like Tomcat, you need to decide
whether and which of the libraries to copy to the WAR for that purpose.
This is done by selecting them in Properties -> Java EE Module
Dependencies. Once you do this, I think your warnings will disappear.
Your container may already offer some of the libraries you otherwise
must add to your project. So, you might decline to fix this. However, if
you can't run when you deploy, then this is an indication that you
should include the JARs containing the missing symbols.
Hope this is a) accurate and b) that it helps.
Russ Bateman
|
|
|
|
|
|
| Re: Classpath dependancy validator warning [message #634493 is a reply to message #634491] |
Thu, 21 October 2010 19:43 |
| Eclipse User |
|
|
|
On 2010.10.21 17:27, Phil Freihofner wrote:
> Hi - I am now using a different setup and am getting this same error.
> Unfortunatly, the solution does not seem to be possible in this new
> context.
>
> Error warning:
> Classpath Dependency Validator Message
> Classpath entry
> org.eclipse.datatools.connectivity.jdt.DRIVERLIBRARY/MySQL JDBC Driver
> will not be exported or published. Runtime ClassNotFoundExceptions may
> result.
>
> I am now using:
> Eclipse Java EE IDE for Web Developers.
> Version: Helios Release
> Build id: 20100617-1415
>
> I am using Tomcat 7.0.2.
>
> The JDBC driver was added to the Build Path via AddLibrary>Connectivity
> Driver Definition. The same method of adding this driver code works for
> a different project that does NOT use Apache.
>
> Previously, I was able to select the project's "Properties>Java EE
> Module Dependencies". With this new version of Eclipse, the "Java EE
> Module Dependencies" does not exist, and I am having trouble trying to
> determine what the equivalent might be.
>
> Many thanks!
>
> Phil Freihofner
You must ask this in the eclipse webtools forum if you want an answer.
This is exactly why I don't use Helios for web-application development.
I think they broke this aspect of WTP for Helios and only the super
gurus are able to work around it or explain how it's done instead of
using the old Java EE Module Dependencies configuration. I still don't
get how to do it, but Galileo works perfectly, so I haven't stressed
over it. For WTP stuff (and Android for now), I just stay with Galileo.
Otherwise, Helios works well.
|
|
|
|
|
|
|
|
|
| Re: Classpath dependancy validator warning [message #1844338 is a reply to message #1844287] |
Thu, 09 September 2021 15:16 |
| Eclipse User |
|
|
|
Fundamentally the message is telling you that you've added a library to the Java Build Path that won't
be published with the web app, and that usually leads to runtime errors. You can mark it for deployment
using the Deployment Assembly property page. The message may stick around until you Build or Validate
the project.
|
|
|
Powered by
FUDForum. Page generated in 0.10753 seconds
Home