Hi Joe,

Thanks, I did remove it. Not that it helped ;)

There was more to the messages, basically going down the list of classes
that were undefined. 

I have changed the package the servlet is in to be in the same hierarchy
as others being run and that has somehow resolved this issue, even
though the rest of the servlets don't use the apache commons. I have no
idea why it's now working again, but I'll be grateful for it. Thanks for
the help!

Janene McCrillis

Message: 3
Date: Mon, 10 Sep 2007 08:46:22 -1000
From: Joe Dane <[EMAIL PROTECTED]>
Subject: Re: [Resin-interest] Classpath problem
To: General Discussion for the Resin application server
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed

I will reiterate Daniel's good advice: never put application  
libraries/classes in the "global" classpath, unless you are  
absolutely certain you know what you're doing.  Even then, you  
probably should avoid the practice.

As to your particular problem, I notice that the error message seems  
a bit odd:

On Sep 7, 2007, at 10:32 AM, Janene McCrillis wrote:

> The resin error log file shows this:
> [2007/09/07 14:05:59] Unresolved compilation problems:
>       The import org.apache cannot be resolved

Is that the entire message?  That would seem to indicate not a  
library problem at all, but a compilation problem.  In particular,  
that you've got the nonsensical statement

import org.apache

somewhere.  Actually, I've noticed something that I consider  
fascinating, which is that when I do an over-hasty compile/deploy and  
I miss the fact that one of my Java classes has compilation errors,  
resin (which has no access to the source) presents me with an error  
message like the one above, and includes an error message from the  
*compiler*.  Fascinating, because it seems to mean that even though  
the compile failed, the compiler produced some sort of object code  
which indicates the error, and the loading JVM is able to read that  
code and recreate the compiler message.




resin-interest mailing list

Reply via email to