Thank you Thank you!!  and God be praised.

That did it. The error is fixed.

I don't really understand why the error occurred,
but knowing that it had to do with compiling the XSP
into Java and having a way to treat the problem
goes a long way!

Lars

> From: Geoff Howard 
> Subject: Re: "The declared package does not match the 
> expected package"?
> 
> Lars Huttar wrote:
> > Geoff,
> > Thanks for your reply.
> > 
> >>From: Geoff Howard
> >>
> >>
> >>>I don't think I changed *anything* in between. Except that I added
> >>>some Microsoft SQL - JDBC driver .jar's into Tomcat 4.1\common\lib.
> >>>And I took them out again to see if that could by some wild stretch
> >>>be the problem. No difference.
> >>
> >>I interpret the above to mean there _was_ a difference.  Now 
> >>it's giving 
> >>you this "does not match expected package" error.  I missed 
> the first 
> >>part of this thread.
> > 
> > 
> > No, that was the first message in the thread...
> > What I meant was, there was no difference between the time before
> > I took out the Microsoft drivers and the time after. In both cases,
> > I got the error.
> > 
> > 
> >>>Here's the file ethnologue/sources/count-rows.xsp:
> >>
> >>I'd guess that the current or earlier version of this was 
> actually in 
> >>Ethnologue/sources/count-rows.xsp.  Is "ethnologue" really 
> lower case 
> >>everywhere?
> > 
> > 
> > Good question. It's actually uppercase in the file system,
> > and it may be that we're referencing it in lowercase, and that
> > works sometimes but not always.
> > So I'll look into that more.
> > 
> > On the other hand, it used to work, and I know I didn't change
> > the case of Ethnologue...
> 
> The specific error you were getting there looked like a 
> compiler error 
> when your xsp was turned into a java class (which is what 
> happens behind 
> the scenes).  The fact that it seemed to work before I can't explain, 
> but you may try stopping the servlet container (tomcat or jetty for 
> example), deleting the work directory (ignore that part for Jetty) and
> restarting Cocoon.  If that makes it work again it'll be a major clue.
> 
> Geoff
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to