Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 85063 invoked by uid 500); 3 Sep 2001 14:55:15 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 85048 invoked from network); 3 Sep 2001 14:55:14 -0000 From: Enke Michael To: cocoon-users@xml.apache.org Message-ID: <3B939A8A.8F9CF5D9@wincor-nixdorf.com> Date: Mon, 03 Sep 2001 16:58:18 +0200 Organization: Wincor Nixdorf GmbG & Co. KG X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.4.4-4GB i686) X-Accept-Language: de, en MIME-Version: 1.0 Subject: Re: Protecting your XSP Code. References: <3B8F9CC3.F6ACB2B1@alcatel.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I am also very interested in this topic. Michael Gerard Maas wrote: > > Hi all, > > I've a critical problem. We've been developing a product based on > Cocoon1.8.x/XSP and Xforms for a while. Now, the time has come to > deliver the first (beta) version to a potential customer for testing. > Nevertheless, we're afraid of the delivery, as all our "knowledge" is > encoded in the XSLT pages that produce XSP pages. We're using the Taglib > paradigm, so we've: XML -> XSL -> XSP -> XSL -> HTML. As you know, the > first XSL contains the application code, while the second (last one) is > the presentation layer. > Delivering the first XSL will give them an open book of our code and > techniques, making it very easy to plagiate. > Knowing that Cocoon only needs to compile once the pages, is there a way > I can make a "compiled" delivery, where I don't include the XSL and make > my pages based on the .class files created in the repository? > It's obvious that I've to clean up the .java from the repository as > well. > > Any ideas? > > Thanks a lot! > > Gerard. (coming back to the list after a long break) > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. > > To unsubscribe, e-mail: > For additional commands, e-mail: --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: