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 49441 invoked from network); 4 Feb 2000 01:12:32 -0000 Received: from swcp.com (HELO kitsune.swcp.com) (198.59.115.2) by locus.apache.org with SMTP; 4 Feb 2000 01:12:32 -0000 Received: from finux.com (finux.finux.com [198.59.115.59]) by kitsune.swcp.com (8.8.8/1.2.3) with ESMTP id SAA17452 for ; Thu, 3 Feb 2000 18:12:35 -0700 (MST) Sender: montefin@swcp.com Message-ID: <389A279C.8F1B3366@finux.com> Date: Thu, 03 Feb 2000 18:13:00 -0700 From: montefin Organization: finux.com X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: cocoon-users@xml.apache.org Subject: Still no cocoon.jar, guys References: <000e01bf6e65$64d69540$171ea8c0@venus.private.uwc.mplik.ru> <3899F11D.47B5837F@finux.com> <3899F750.353EE730@ticketweb.com> Content-Type: multipart/mixed; boundary="------------005CAAE81DC797DE07946D54" --------------005CAAE81DC797DE07946D54 Content-Type: multipart/alternative; boundary="------------4919AED3FA7EBA5A6814F683" --------------4919AED3FA7EBA5A6814F683 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit First of all, thanks for your responses to my question. This is a good group and I'd hate to belabor it with what seems utterly dumb on my part, but here goes... First, just in case it matters, I downloaded the Cocoon-1.6.1.jar file into a Linux environment. Originally, I did jar -xvf on the archive which supposedly works more or less like tar -xvf on a tarball. I got an expanded directory called cocoon-1.6.1 with a bin subdirectory that had a file called Cocoon.jar in it. Ok, I knew there was supposed to be a cocoon.jar file somewhere so I did jar -xvf on that file also and got an expanded directory with a subdirectory called org which began the standard path of org/apache/cocoon that we're all familiar with. I updatedb'd, which in unix updates the file system tracking data base, and did a locate on the entire system for cocoon.jar and found nothing except the cocoon.jar that exists on my Exeter installation on another server which is ported differently. I grep'ed, the entire cocoon-1.6.1 directory system for a cocoon.jar file too with no success. I also used ant in the cocoon-1.6.1 directory to build a dist of Cocoon., The build seemed to go ok except for 2 deprecation warnings. In any event there was no cocoon.jar file in that build either. I applied the advice given here and went back and did the same things using unzip and got the same results: no file labeled cocoon.jar, only Cocoon.jar Because of a section in the install documentation, I at first thought the Cocoon.jar file could be used as a target. That section reads (pasting here): ------------------------------------------------------------- "Here is an example: wrapper.classpath=/usr/local/java/lib/cocoon.jar wrapper.classpath=/usr/local/java/lib/xerces.jar wrapper.classpath=/usr/local/java/lib/xalan.jar wrapper.classpath=/usr/local/java/lib/fop.jar wrapper.classpath=/usr/local/java/lib/regexp.jar wrapper.classpath=/usr/local/java/lib/jndi.jar from this version of Cocoon the Cocoon.jar package should be added to the servlet engine classpath as any other required package (as shown above). " ------------------------------------------------------------- But from comments I've seen posted here, it seems the lower case file, cocoon.jar, is essential, and since I'm still having problems getting Cocoon to parse it's own samples and examples, but not oddly enough .class and .xml files created here, I suppose it is essential. Just as a sidelight, the jar -xvf procedure did result in xerces.jar and xalan.jar files, but now I'm concerned that though labeled correctly those files too may not be operative or fully operative. So, do I scrap the whole thing and start over...or look for an rpm from Red Hat, or give up and let Exeter's Cocoon engine do what it does so seamlessly on my other Apache server? I'd really like to make this version of Cocoon work as I am evaluating it for use in an enterprise E-commerce suite vis a vis Exeter. Zope and php3 which I have working here just fine, each on its own server. Those softwares had their own installation challenges, but nothing of this magnitutde. If anyone could help me just get over these inital roadblocks, I'd really appreciate it. Thanks, montefin Rick Tyler wrote: > > Where is cocoon.jar? The one with the small "c". > > I too had the same problem when I first attempted > to download and run Cocoon. > > The confusion stems from the fact a .jar file has > essentially the same structure as a .zip file > (which was unknown to me when I started playing > around with this stuff) and someone at the Apache > project thought it was clever to start naming > the binary distributions with the .jar, instead > of .zip, extension. > > The problem with this cleverness is that the > natural assumption of a newcomer is to assume that > the .jar found in the download directory is the same > .jar needed by the class loader. > > So, to answer your question, use WinZip to extract > the contents of the Cocoon.jar which you downloaded > and you will find the cocoon.jar you are looking for. > > I would argue that this convention of naming binary > distributions with the .zip extension, while quite > clever, is inherently confusing and that .jar should > only be used for files intended as targets for the > Java class loader. > > Just my 2 cents - it would have saved me half a day > of spinning my wheels and wasting the bandwidth of > this mailing list. > > - RT > > --------------------------------------------------------------------- > To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org > For additional commands, e-mail: cocoon-users-help@xml.apache.org -- In Life Timing is everything; in Linux Permissions is everything. http://www.montefin.com/~montefin (up 24/7) http://finux.com/ (our Linux/Apache served PHP3 site...evenings & weekends) http://finux.com:8080 (our Zope portal...evenings & weekends) http://finux.com:8085 (our XML adventures...evenings & weekends) --------------4919AED3FA7EBA5A6814F683 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit First of all, thanks for your responses to my question. This is a good group and I'd hate to belabor it with what seems utterly dumb on my part, but here goes...

First, just in case it matters, I downloaded the Cocoon-1.6.1.jar file into a Linux environment.

Originally, I did jar -xvf on the archive which supposedly works more or less like tar -xvf on a tarball. I got an expanded directory called cocoon-1.6.1 with a bin subdirectory that had a file called Cocoon.jar in it.

Ok, I knew there was supposed to be a cocoon.jar file somewhere so I did jar -xvf on that file also and got an expanded directory with a subdirectory called org which began the standard path of org/apache/cocoon that we're all familiar with.

I updatedb'd, which in unix updates the file system tracking data base, and did a locate on the entire system for cocoon.jar and found nothing except the cocoon.jar that exists on my Exeter installation on another server which is ported differently.

I grep'ed, the entire cocoon-1.6.1 directory system for a cocoon.jar file too with no success.

I also used ant in the cocoon-1.6.1 directory to build a dist of Cocoon., The build seemed to go ok except for 2 deprecation warnings.  In any event there was no cocoon.jar file in that build either.

I applied the advice given here and went back and did the same things using unzip and got the same results: no file labeled cocoon.jar, only Cocoon.jar

Because of a section in the install documentation, I at first thought the Cocoon.jar file could be used as a target. That section reads (pasting here):

-------------------------------------------------------------
"Here is an example:

                                               wrapper.classpath=/usr/local/java/lib/cocoon.jar
                                               wrapper.classpath=/usr/local/java/lib/xerces.jar
                                               wrapper.classpath=/usr/local/java/lib/xalan.jar
                                               wrapper.classpath=/usr/local/java/lib/fop.jar
                                               wrapper.classpath=/usr/local/java/lib/regexp.jar
                                               wrapper.classpath=/usr/local/java/lib/jndi.jar
 

                        from this version of Cocoon the Cocoon.jar package should be added to the servlet engine classpath as any other required package (as shown above). "
-------------------------------------------------------------

But from comments I've seen posted here, it seems the lower case file, cocoon.jar, is essential, and since I'm still having problems getting Cocoon to parse it's own samples and examples, but not oddly enough .class and .xml files created here, I suppose it is essential.

Just as a sidelight, the jar -xvf procedure did result in xerces.jar and xalan.jar files, but now I'm concerned that though labeled correctly those files too may not be operative or fully operative.

So, do I scrap the whole thing and start over...or look for an rpm from Red Hat, or give up and let Exeter's Cocoon engine do what it does so seamlessly on my other Apache server?

I'd really like to make this version of Cocoon work as I am evaluating it for use in an enterprise E-commerce suite vis a vis Exeter. Zope and php3 which I have working here just fine, each on its own server. Those softwares had their own installation challenges, but nothing of this magnitutde.

If anyone could help me just get over these inital roadblocks, I'd really appreciate it.

Thanks,

montefin
 
 

Rick Tyler wrote:

> Where is cocoon.jar? The one with the small "c".

I too had the same problem when I first attempted
to download and run Cocoon.

The confusion stems from the fact a .jar file has
essentially the same structure as a .zip file
(which was unknown to me when I started playing
around with this stuff) and someone at the Apache
project thought it was clever to start naming
the binary distributions with the .jar, instead
of .zip, extension.

The problem with this cleverness is that the
natural assumption of a newcomer is to assume that
the .jar found in the download directory is the same
.jar needed by the class loader.

So, to answer your question, use WinZip to extract
the contents of the Cocoon.jar which you downloaded
and you will find the cocoon.jar you are looking for.

I would argue that this convention of naming binary
distributions with the .zip extension, while quite
clever, is inherently confusing and that .jar should
only be used for files intended as targets for the
Java class loader.

Just my 2 cents - it would have saved me half a day
of spinning my wheels and wasting the bandwidth of
this mailing list.

- RT

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-users-help@xml.apache.org

-- 
In Life Timing is everything; in Linux Permissions is everything.
http://www.montefin.com/~montefin (up 24/7)
http://finux.com/ (our Linux/Apache served PHP3 site...evenings & weekends)
http://finux.com:8080 (our Zope portal...evenings & weekends)
http://finux.com:8085 (our XML adventures...evenings & weekends)
  --------------4919AED3FA7EBA5A6814F683-- --------------005CAAE81DC797DE07946D54 Content-Type: text/x-vcard; charset=us-ascii; name="montefin.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for montefin Content-Disposition: attachment; filename="montefin.vcf" begin:vcard n:;montefin x-mozilla-html:TRUE org:montefin(tm) Enterprises -- Webforward(tm);Linux, Apache, Java, XML, Exeter, Cocoon, Zope, Php3, SQL adr:;;;;;; version:2.1 email;internet:montefin@finux.com title:Captain note:In Life Timing is everything. In Linux Permissions is everything. x-mozilla-cpt:;-18720 fn:montefin end:vcard --------------005CAAE81DC797DE07946D54--