Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 54662 invoked from network); 12 Apr 2000 11:45:13 -0000 Received: from mailgate1.uea.ac.uk (139.222.230.1) by locus.apache.org with SMTP; 12 Apr 2000 11:45:13 -0000 Received: from mailserver1.uea.ac.uk [139.222.130.16] by mailgate1.uea.ac.uk with esmtp (Exim 1.73 #1) id 12fLa3-0006av-00; Wed, 12 Apr 2000 12:45:11 +0100 Received: from [139.222.176.10] (helo=nc1a.nca.uea.ac.uk ident=mail) by mailserver1.uea.ac.uk with esmtp (Exim 3.02 #1) id 12fLa3-0002UK-00 for cocoon-users@xml.apache.org; Wed, 12 Apr 2000 12:45:11 +0100 Received: from paulr by nc1a.nca.uea.ac.uk with local (Exim 3.12 #1 (Debian)) id 12fLa3-0006GC-00 for ; Wed, 12 Apr 2000 12:45:11 +0100 Date: Wed, 12 Apr 2000 12:45:11 +0100 From: Paul Russell To: cocoon-users@xml.apache.org Subject: Re: XSP class package name problem Message-ID: <20000412124511.C6608@nc1a.nca.uea.ac.uk> References: <38F2D1B2.243D24BA@denic.de> <38F3032E.A9BED94C@apache.org> <38F31569.CC89D990@denic.de> <38F398F1.49B38B5F@apache.org> <20000411235033.A430@nc1a.nca.uea.ac.uk> <38F43124.3148A407@denic.de> <20000412100856.A6608@nc1a.nca.uea.ac.uk> <38F44970.3CC30EB5@denic.de> <20000412114111.B6608@nc1a.nca.uea.ac.uk> <38F45B84.64D9A026@denic.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.9i In-Reply-To: <38F45B84.64D9A026@denic.de>; from ulim@denic.de on Wed, Apr 12, 2000 at 01:18:28PM +0200 Sender: Paul Russell X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Wed, Apr 12, 2000 at 01:18:28PM +0200, Ulrich Mayring wrote: > I'm not talking about the generated code, just the plain source code I > put in the XSP. There are classes, interfaces and everything you know > from Java - but I want to use the business objects and classes that > others designed as well. And I want to give them mine. Hrm, unless you're talking about plain simple classes that don't use syntax orthogonalily (and if you are, then they should probably be defined outside the xsp, and imported in with an tag pair) then the code doesn't even *exist* until the XSP engine has strutted its funky stuff. Either way, changing the package name by which cocoon refers too is probably not the right way to do it. In the nicest possible way, I suspect we're going to have to agree to differ on this one ;) Paul