You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by David Novogrodsky <da...@novogrodsky.net> on 2003/02/05 00:42:34 UTC
curious problem with new instalation--where are the XML files?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I just installed Cocoon on my system and I have an interesting problem.
I copied the war package into
~/jboss-3.0.4_tomcat-4.1.12/server/default/deploy and restarted the
server using the script: ~/jboss-3.0.4_tomcat-4.1.12/bin/run.sh. I got
the welcome page at http://localhost:8080/cocoon/ and I was very happy.
I ran through several of the samples and lthey seemed neat. This would
be great for a personal web site. Anyway, I wanted to do some of the
exercises so i entered http://localhost:8080/cocoon/mount and got an
error. I decided to find the mount directory.
This is where things get interesting. The cocoon directory was not
under ~/jboss-3.0.4_tomcat-4.1.12/tomcat-4.1.x/webapps but under
~/jboss-3.0.4_tomcat-4.1.12/work/mainengine/localhost . I found some
files under
~/jboss-3.0.4_tomcat-4.1.12/work/mainengine/localhost/cocoon-files/org/
apache/cocoon/www/jndi_/localhost/cocoon/ but no xml source files
Where are the xml source files? Why did the war install Cocoon to such
a weird directory? Is not this a strange problem?
David Novogrodsky
http://www.novogrodsky.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)
iD8DBQE+QE/wvgTNkiw+nMcRAoGnAKChStCs7wR1tUGLGkLbnDez9b/hkwCfWzhE
iSivrZ6qzJSS2zBSNFsBXaw=
=faxR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: curious problem with new instalation--where are the XML files?
Posted by Robert Simmons <de...@arcor.de>.
I'm afraid you are a bit confused.
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> I just installed Cocoon on my system and I have an interesting problem.
>
> I copied the war package into
> ~/jboss-3.0.4_tomcat-4.1.12/server/default/deploy and restarted the
> server using the script:
No need. Its a servlet. JBoss will do all the deployment for you.
> ~/jboss-3.0.4_tomcat-4.1.12/bin/run.sh. I got
> the welcome page at http://localhost:8080/cocoon/ and I was very happy.
Happy is good. =)
>
> I ran through several of the samples and lthey seemed neat. This would
> be great for a personal web site. Anyway, I wanted to do some of the
> exercises so i entered http://localhost:8080/cocoon/mount and got an
> error. I decided to find the mount directory.
What error did you get ? Cocoon doesnt quite work this way. In cocoon you map
a URL to a pipeline, a combination of generator, 0 to n transformers, and a
serializer. So all URLS are blocked unless they are mapped to a pipeline.
Wheras mount may be mapped to a pipeline, that doesnt guarantee that it will
give you a directory view.
>
> This is where things get interesting. The cocoon directory was not
> under ~/jboss-3.0.4_tomcat-4.1.12/tomcat-4.1.x/webapps
Why should it be? Its in the WAR file you dropped in the deploy directory.
Unpack it and deploy it exploded and you will see what I mean.
> but under
> ~/jboss-3.0.4_tomcat-4.1.12/work/mainengine/localhost . I found some
> files under
> ~/jboss-3.0.4_tomcat-4.1.12/work/mainengine/localhost/cocoon-files/org/
> apache/cocoon/www/jndi_/localhost/cocoon/ but no xml source files
No no, thats just a tomcat work directory. Temporary files there. Cocoon
takes the sitemap and actually generates a java file and compiles it. It does
that stuff in this directory. The only time you should ever have to look here
is if you get some strange exception in a sitemap or XSP page and cant figure
it out from the XML. Then you can go to the work directory and look up the
source. Otherwise forget this directory.
>
> Where are the xml source files? Why did the war install Cocoon to such
> a weird directory? Is not this a strange problem?
The war isntalled to your deploy directory. Unpack it with the jar command
and you will see all the gory guts of cocoon. You can create a directory
named cocoon.war and unpack the actual war file into this directory. Then you
can move this directory to the deploy directory of JBoss and it will treat it
exactly as if it was a war file. Refer to the JBoss documentation on
deploying exploded archives. It is within this war that you will find what
you are lookign for.
>
> David Novogrodsky
> http://www.novogrodsky.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (Darwin)
-- Derisor
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>