c1 to c2 migration

2003-03-18 Thread JADOUL LAURENT
Hi,

I have to do a migration of an web application. But  I don't know what are the key 
point of this operation.

Is there a documentation that explain this kind of work ?

Currently the application runs on a Apache Tomcat 3.12 under a Suse Linux 6.4 
distribution. wiith the version 1.3 of JDK and cocoon 1.8.

And I have to redeploy this application under Apache Tomcat 4.1.18 (no prob) but with 
cocoon 2.0

thanks for your help

Jadoul Laurent

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



C1 to C2 migration help

2002-05-03 Thread Skip Carter


I am trying to move from cocoon 1 to cocoon 2 using the combination
Linux with Apache 1.3.24 and Tomcat 4.0.4, Cocoon 2.0.2. and JDK 1.4.0
I am using the 'mod_webapp' connector between Apache and Tomcat.

All of the demonstration and provided examples work with the above combination.
My own servlets and xml work as well.  But I still have a problem:

I can't figure out how to get Apache to pass on all URL requests with a given
extension for either Tomcat or Cocoon to handle, like the old ApJservAction
mechanism did ( e.g. ApJServAction .jsp /servlets/nl.nmg.jsp.JSPServlet )


I was able to accomplish this by combining a rewrite rule and a WebAppDeploy
statement in the apache.conf file,

  RewriteRule ^/(.*)\.jsp$ /jspages/$1.jsp [R]

  WebAppDeploy jspages warpConnection /jspages


but this causes a redirect and a new page request resulting in a new URL
being displayed on the browser; its not really the same as what ApJservAction 
did.

How do I achieve the equivalent of ApJservAction ?


Thanks,



-- 
 Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
 Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
 1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
 Monterey, CA. 93940












-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: Moving from C1 to C2

2002-02-21 Thread Olivier Rossel

Olivier Richaud wrote:

>We think it's time for us to move from C1 to C2. Along other things that we
>consider, is i18n that we are force to integrate.
>
>Now, our system is composed of :
>- XSP pages ;
>- a logicsheet that supply the main common functionnality shared by the XSP
>pages ;
>- 1 big stylesheet for the whole site, and 2 secondary stylesheets to render
>reports in HTML and PDF.
>
>One big problem we foudn was the complexity of C2 coming with vairous
>samples that are useless for our purposes. Do we have to recreate the war,
>or is there any stripped version of C2 ready for prime time?
>
>Other point : Some tests pointed out difficulties with logicsheets and XSP.
>In the past, we just added the namespace for our logicsheet to the xsp:page
>tag, and here it goes, provided that the cocoon.properties file was OK. We
>made the similar modification to cocoon.xconf file, and we failed to find
>any valid explanation. But, we made it work without any logicsheet.
>
>I would be pleased to hear of anybody that moved from C1 to C2.
>
>Regards.
>
>Olivier.
>
The concept of sitemap is here to replace the various commands for 
Cocoon, that were embedded
into XSP pages.

The general process in a sitemap is not far from what you are explaining:
XSP -> logicsheet -> XSL -> output format.

In a sitemap the process is called a pipeline with 3 kind of step:
generation==production of the XML representing datas (only one 
generation per pipeline)
transformation==manipulation of the XML (any number of successive 
transformation s per pipeline)
serialization==transformation from the final XML tree to an output 
format (one serialization per pipeline)

The sitemap is also a kind of BIG mod_rewrite rules. In fact, it is a 
mapping between
URLs and pipelines.

What you want to do in C2, for your application, is to map
"http://server_URL/context_URL/path/to/foobar.xsp"; to the (classic) 
pipeline XSP->XSL->HTML/PDF.

The URL received by the sitemap manager of Cocoon from the appli server 
is the URL after the context_URL.
So you have to map /path/to/foobar.xsp with the pipeline.
The mapping can use wildcards, so you can have a mapping **/*.xsp <-> 
pipeline.
(** means any string including  /, * means any string with no / inside)

Then you will want to define the classic pipeline. Take an example 
derivated from the default sitemap:






This is exactly an XML version of the pipeline described above.
{1} and {2} are only recalls of the matching pattern (very similar to 
sed or perl system of matching/replacing).
For PDF generation, the final step of transformation must provide XSL:FO
and the serializer mu be of type="fo2pdf".

For logicsheet management, I presume adding it to the directory where 
other taglibs reside should be enough
(not sure on that one).

Hope it helps.
(Hope I did not write too many wrong stuff)


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Moving from C1 to C2

2002-02-21 Thread Olivier Richaud

We think it's time for us to move from C1 to C2. Along other things that we
consider, is i18n that we are force to integrate.

Now, our system is composed of :
- XSP pages ;
- a logicsheet that supply the main common functionnality shared by the XSP
pages ;
- 1 big stylesheet for the whole site, and 2 secondary stylesheets to render
reports in HTML and PDF.

One big problem we foudn was the complexity of C2 coming with vairous
samples that are useless for our purposes. Do we have to recreate the war,
or is there any stripped version of C2 ready for prime time?

Other point : Some tests pointed out difficulties with logicsheets and XSP.
In the past, we just added the namespace for our logicsheet to the xsp:page
tag, and here it goes, provided that the cocoon.properties file was OK. We
made the similar modification to cocoon.xconf file, and we failed to find
any valid explanation. But, we made it work without any logicsheet.

I would be pleased to hear of anybody that moved from C1 to C2.

Regards.

Olivier.


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Moving from C1 to C2

2002-02-21 Thread Olivier Richaud

We think it's time for us to move from C1 to C2. Along other things that we
consider, is i18n that we are force to integrate.

Now, our system is composed of :
- XSP pages ;
- a logicsheet that supply the main common functionnality shared by the XSP
pages ;
- 1 big stylesheet for the whole site, and 2 secondary stylesheets to render
reports in HTML and PDF.

One big problem we foudn was the complexity of C2 coming with vairous
samples that are useless for our purposes. Do we have to recreate the war,
or is there any stripped version of C2 ready for prime time?

Other point : Some tests pointed out difficulties with logicsheets and XSP.
In the past, we just added the namespace for our logicsheet to the xsp:page
tag, and here it goes, provided that the cocoon.properties file was OK. We
made the similar modification to cocoon.xconf file, and we failed to find
any valid explanation. But, we made it work without any logicsheet.

I would be pleased to hear of anybody that moved from C1 to C2.

Regards.

Olivier.


BEGIN:VCARD
VERSION:2.1
N:Richaud;Olivier
FN:Olivier Richaud
NICKNAME:richaud
ORG:StrongHoldNET
TITLE:VP Production
TEL;WORK;VOICE:04 93 22 13 07
TEL;CELL;VOICE:06 21 01 55 35
TEL;WORK;FAX:04 93 22 13 01
ADR;WORK:;;17 Chemin des Travails;Cagnes sur Mer, 06;;06250;France
LABEL;WORK;ENCODING=QUOTED-PRINTABLE:17 Chemin des Travails=0D=0ACagnes sur Mer, 06 06250=0D=0AFrance
X-WAB-GENDER:2
URL;HOME:http://www.richaud.net
URL;WORK:http://www.strongholdnet.com
BDAY:20010429
EMAIL;PREF;INTERNET:[EMAIL PROTECTED]
REV:2003T214434Z
END:VCARD



-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


Migration C1 to C2

2001-08-21 Thread Drasko Kokic

I am trying to migrate one of C1 applications onto C2
platform.  I have problems with following
classes/objects/methods: session, servletContext,
sendRedirect.
I know that redirects should be treated outside of XSP
(in Actions) and that session could be accessed via
session logicsheet but how to access the equivalent of
C1 servletContext?  In the generated java code there
is a small remark that context is pointing to the
ServletContext, but it is not exactly the same as in
C1 (it is missing the log method).
Anybody have an idea ...
Drasko

__
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/


-
Please check that your question has not already been answered in the
FAQ before posting. 

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


Re: C1 to C2, FAQ

2001-07-24 Thread Davanum Srinivas

Andre,

I checked in your faq's. can you do a "build docs" from the latest cvs version and 
take a look

Thanks,
dims

--- Andre Juffer <[EMAIL PROTECTED]> wrote:
> Hi Davanum,
> 
> 
> the original problem was how to get apache working together with tomcat
> and Cocccn2. There is actually a FAQ "Why does nothing happen when I
> access 'http://localhost/cocoon/'?" Some possibilities are listed there.
> in addition to these, in the case of mod_jk, it is crucial to include
> the directive
> 
> JkMount /cocoon/* ajp12
> 
> along with other directives that are already listed in mod_jk.conf-auto
> in the tomcat/conf directory. One could add the above directive at the 
> end of httpd.conf.
> 
> 
> 
> The second problem I was looking into was the following. How can I use
> the request http://your.server.org/Foo/welcome (as an example), where
> Foo is an application that depends on Cocoon2, instead of employing
> something like http://your.server.org/cocoon/Foo/welcome. So, it would
> not be required to always include "cocoon" in the request. Mainly based 
> upon Luca Morandini's suggestions, I could get things to work with the 
> following two modifications:
> 
> 1. Add to httpd.cond:
> 
> RewriteEngine On
> RewriteLog "/var/log/rewrite.log"
> RewriteLogLevel 0
> RewriteRule ^/Foo /cocoon/Foo/ [R]
> RewriteRule ^/Foo(.*) /cocoon/Foo$1 [R]
> 
> The file rewrite.log does not have to be located in /var/log. For 
> instance, under Windows NT other locations may be appropriate. The 
> RewriteLogLevel should be set 3 for debug purposes. The third line is 
> essentially a redirect, so that Foo become /cocoon/Foo/ with the 
> trailing /, without it the request would not map onto
> 
> 
>
> 
> 
> if I request http://your.server.org/Foo.
> 
> Finally, the last RewriteRule could depend on the local settings.
> The original suggestion by Luca was a single line entry (that replaces 
> both RewriteRules above) according to
> 
> RewriteRule Foo/(.*) /cocoon/Foo/$1 [PT]
> 
> but this did not work in my case (Slackware Linux with Apache1.3, 
> tomcat3.2.2, Cocoon2). Again, these RewriteRules may vary somewhat 
> depending on the local settings. You may have to experiment somewhat
> 
> 2. Add to the sitemap.xmap in the cocoon directory:
> 
> 
> 
> check-reload="yes" reload-method="synchron"/>
> 
> 
> 
> Here, /www/Foo is a some directory on the local file system where the 
> xml, xsp, .., files of the application Foo live.
> 
> As Luca pointed out, the src attribute may have to include "file://"
> 
> I hope that the information above is useful for others as well.
> 
> 
> With thanks to Luca, Lajos, Anders, and others.
> 
> Cheers,
> Andre.
> 
> 
> 
> 
> 
> Davanum Srinivas wrote:
> 
>  > Andre,
>  >
>  > Can you re-post the complete instructions in the form of a FAQ? I 
> will check it in.
>  >
>  > Thanks,
>  > dims
>  >
>  > --- Andre Juffer <[EMAIL PROTECTED]> wrote:
>  >
>  >> Hi All,
>  >>
>  >> I got it finally working. The directive
>  >>
>  >> JkMount /cocoon/* ajp12
>  >>
>  >> did it. I apparently kept on missing that part, since this was not
>  >> required for tomcat-apache-cocoon1, where always, it seems, .xml was
>  >> employed to redirect xml request to cocoon1.
>  >>
>  >> I would support the suggestion of Luca to put these few things into the
>  >> FAQ, because I would assume that more people make the same mistake 
> as I did.
>  >>
>  >> Thank you for your help,
>  >>
>  >> Andre.
>  >>
>  >>
>  >>
>  >> Luca Morandini wrote:
>  >>
>  >>
>  >>> Andre,
>  >>>
>  >>>  this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
>  >>> will be overwritten every time you start Tomcat):
>  >>>
>  >>> 
>  >>>
>  >>> JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
>  >>> JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
>  >>> JkLogLevel warn
>  >>> JkMount /*.jsp ajp12
>  >>> JkMount /*.xml ajp12
>  >>>
>  >>> JkMount /cocoon/* ajp12
>  >>>
>  >>> 
>  >>>
>  >>>  I presume this will do the trick of redirecting.
>  >>>
>  >>>  Moreover, somewhere down mod_jk.conf, there is this cocoon-related 
> stuff:
>  >>>
>  >>> #
>  >>> # The following line makes apache aware of the location of the /cocoon
>  >>> context
>  >>> #
>  >>> Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
>  >>> 
>  >>> Options Indexes FollowSymLinks
>  >>> 
>  >>>
>  >>> #
>  >>> # The following line mounts all JSP files and the /servlet/ uri to 
> tomcat
>  >>> #
>  >>> JkMount /cocoon/servlet/* ajp12
>  >>> JkMount /cocoon/*.jsp ajp12
>  >>>
>  >>> #
>  >>> # The following line prohibits users from directly accessing WEB-INF
>  >>> #
>  >>> 
>  >>> AllowOverride None
>  >>> deny from all
>  >>> 
>  >>>
>  >>> #
>  >>> # Use Directory too. On Windows, Location doesn't work unless case 
> matches
>  >>> #
>  >>> 
>  >>> AllowOverride None
>  >>> deny from all
>  >>> 
>  >>>
>  >>> #
>  >>> # The following line prohibits users from directly accessing META-INF
>  >>> #
>  >>> 
>  >>> Allo

Re: C1 to C2, FAQ

2001-07-20 Thread Andre Juffer

Hi Davanum,


the original problem was how to get apache working together with tomcat
and Cocccn2. There is actually a FAQ "Why does nothing happen when I
access 'http://localhost/cocoon/'?" Some possibilities are listed there.
in addition to these, in the case of mod_jk, it is crucial to include
the directive

JkMount /cocoon/* ajp12

along with other directives that are already listed in mod_jk.conf-auto
in the tomcat/conf directory. One could add the above directive at the 
end of httpd.conf.



The second problem I was looking into was the following. How can I use
the request http://your.server.org/Foo/welcome (as an example), where
Foo is an application that depends on Cocoon2, instead of employing
something like http://your.server.org/cocoon/Foo/welcome. So, it would
not be required to always include "cocoon" in the request. Mainly based 
upon Luca Morandini's suggestions, I could get things to work with the 
following two modifications:

1. Add to httpd.cond:

RewriteEngine On
RewriteLog "/var/log/rewrite.log"
RewriteLogLevel 0
RewriteRule ^/Foo /cocoon/Foo/ [R]
RewriteRule ^/Foo(.*) /cocoon/Foo$1 [R]

The file rewrite.log does not have to be located in /var/log. For 
instance, under Windows NT other locations may be appropriate. The 
RewriteLogLevel should be set 3 for debug purposes. The third line is 
essentially a redirect, so that Foo become /cocoon/Foo/ with the 
trailing /, without it the request would not map onto


   


if I request http://your.server.org/Foo.

Finally, the last RewriteRule could depend on the local settings.
The original suggestion by Luca was a single line entry (that replaces 
both RewriteRules above) according to

RewriteRule Foo/(.*) /cocoon/Foo/$1 [PT]

but this did not work in my case (Slackware Linux with Apache1.3, 
tomcat3.2.2, Cocoon2). Again, these RewriteRules may vary somewhat 
depending on the local settings. You may have to experiment somewhat

2. Add to the sitemap.xmap in the cocoon directory:



  



Here, /www/Foo is a some directory on the local file system where the 
xml, xsp, .., files of the application Foo live.

As Luca pointed out, the src attribute may have to include "file://"

I hope that the information above is useful for others as well.


With thanks to Luca, Lajos, Anders, and others.

Cheers,
Andre.





Davanum Srinivas wrote:

 > Andre,
 >
 > Can you re-post the complete instructions in the form of a FAQ? I 
will check it in.
 >
 > Thanks,
 > dims
 >
 > --- Andre Juffer <[EMAIL PROTECTED]> wrote:
 >
 >> Hi All,
 >>
 >> I got it finally working. The directive
 >>
 >> JkMount /cocoon/* ajp12
 >>
 >> did it. I apparently kept on missing that part, since this was not
 >> required for tomcat-apache-cocoon1, where always, it seems, .xml was
 >> employed to redirect xml request to cocoon1.
 >>
 >> I would support the suggestion of Luca to put these few things into the
 >> FAQ, because I would assume that more people make the same mistake 
as I did.
 >>
 >> Thank you for your help,
 >>
 >> Andre.
 >>
 >>
 >>
 >> Luca Morandini wrote:
 >>
 >>
 >>> Andre,
 >>>
 >>>this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
 >>> will be overwritten every time you start Tomcat):
 >>>
 >>> 
 >>>
 >>> JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
 >>> JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
 >>> JkLogLevel warn
 >>> JkMount /*.jsp ajp12
 >>> JkMount /*.xml ajp12
 >>>
 >>> JkMount /cocoon/* ajp12
 >>>
 >>> 
 >>>
 >>>I presume this will do the trick of redirecting.
 >>>
 >>>Moreover, somewhere down mod_jk.conf, there is this cocoon-related 
stuff:
 >>>
 >>> #
 >>> # The following line makes apache aware of the location of the /cocoon
 >>> context
 >>> #
 >>> Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
 >>> 
 >>> Options Indexes FollowSymLinks
 >>> 
 >>>
 >>> #
 >>> # The following line mounts all JSP files and the /servlet/ uri to 
tomcat
 >>> #
 >>> JkMount /cocoon/servlet/* ajp12
 >>> JkMount /cocoon/*.jsp ajp12
 >>>
 >>> #
 >>> # The following line prohibits users from directly accessing WEB-INF
 >>> #
 >>> 
 >>> AllowOverride None
 >>> deny from all
 >>> 
 >>>
 >>> #
 >>> # Use Directory too. On Windows, Location doesn't work unless case 
matches
 >>> #
 >>> 
 >>> AllowOverride None
 >>> deny from all
 >>> 
 >>>
 >>> #
 >>> # The following line prohibits users from directly accessing META-INF
 >>> #
 >>> 
 >>> AllowOverride None
 >>> deny from all
 >>> 
 >>>
 >>> #
 >>> # Use Directory too. On Windows, Location doesn't work unless case 
matches
 >>> #
 >>> 
 >>> AllowOverride None
 >>> deny from all
 >>> 
 >>>
 >


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: C1 to C2

2001-07-18 Thread Andre Juffer



Davanum Srinivas wrote:

> Andre,
> 
> Can you re-post the complete instructions in the form of a FAQ? I will check it in.

Yes, I'll see to it and send something in within the next day or so.

Cheers,
Andre


> 
> Thanks,
> dims
> 
> --- Andre Juffer <[EMAIL PROTECTED]> wrote:
> 
>> Hi All,
>> 
>> I got it finally working. The directive
>> 
>> JkMount /cocoon/* ajp12
>> 
>> did it. I apparently kept on missing that part, since this was not 
>> required for tomcat-apache-cocoon1, where always, it seems, .xml was 
>> employed to redirect xml request to cocoon1.
>> 
>> I would support the suggestion of Luca to put these few things into the 
>> FAQ, because I would assume that more people make the same mistake as I did.
>> 
>> Thank you for your help,
>> 
>> Andre.
>> 
>> 
>> 
>> Luca Morandini wrote:
>> 
>> 
>>> Andre,
>>> 
>>> this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
>>> will be overwritten every time you start Tomcat):
>>> 
>>> 
>>> 
>>> JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
>>> JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
>>> JkLogLevel warn
>>> JkMount /*.jsp ajp12
>>> JkMount /*.xml ajp12
>>> 
>>> JkMount /cocoon/* ajp12
>>> 
>>> 
>>> 
>>> I presume this will do the trick of redirecting.
>>> 
>>> Moreover, somewhere down mod_jk.conf, there is this cocoon-related stuff:
>>> 
>>> #
>>> # The following line makes apache aware of the location of the /cocoon
>>> context
>>> #
>>> Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
>>> 
>>> Options Indexes FollowSymLinks
>>> 
>>> 
>>> #
>>> # The following line mounts all JSP files and the /servlet/ uri to tomcat
>>> #
>>> JkMount /cocoon/servlet/* ajp12
>>> JkMount /cocoon/*.jsp ajp12
>>> 
>>> #
>>> # The following line prohibits users from directly accessing WEB-INF
>>> #
>>> 
>>> AllowOverride None
>>> deny from all
>>> 
>>> 
>>> #
>>> # Use Directory too. On Windows, Location doesn't work unless case matches
>>> #
>>> 
>>> AllowOverride None
>>> deny from all
>>> 
>>> 
>>> #
>>> # The following line prohibits users from directly accessing META-INF
>>> #
>>> 
>>> AllowOverride None
>>> deny from all
>>> 
>>> 
>>> #
>>> # Use Directory too. On Windows, Location doesn't work unless case matches
>>> #
>>> 
>>> AllowOverride None
>>> deny from all
>>> 
>>> 
>>> By the way, I'm not using Linux, but Windows NT 4.0 (as you may guess from
>>> the paths...).
>>> 
>>> Best regards,
>>>  
>>> -
>>>Luca Morandini
>>>GIS Consultant
>>> [EMAIL PROTECTED]
>>>   +39 0744 59  85  1 Office
>>>   +39 0335 681 02 12 Mobile
>>> http://utenti.tripod.it/lmorandini/index.html
>>> -
>>> 
>>> 
>>> 
>>> 
>>>> -Original Message-
>>>> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
>>>> Sent: martedì 17 luglio 2001 23.13
>>>> To: [EMAIL PROTECTED]
>>>> Subject: Re: C1 to C2
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Luca Morandini wrote:
>>>> 
>>>> 
>>>> 
>>>>> Andre,
>>>>> 
>>>>>   I used mod_jk instead of jserv, hence, I can't be of much
>>>> 
>>>> assistance.
>>>> 
>>>> 
>>>>>   I would suggest you to switch to mod_jk, which is
>>>> 
>>>> (reportedly) better, then
>>>> 
>>>> 
>>>>> we may work out the problem...
>>>> 
>>>> Hi Luca,
>>>> 
>>>> All right, I switched to mod_jk. No change, however, everything I had
>>>> with jserv also applies to jk. The directory /cocoon is displayed if I
>>>> do the request localhost/cocoon in the same way as /localhost/examples
>>>> would do. Is 

Re: C1 to C2

2001-07-18 Thread Mike Haarman


Yes, it works here as well, with ajp13.  The difference is changing this
line:

JkMount /cocoon/*.xml ajp13

to:

JkMount /cocoon/* ajp13

I've noticed a variety of other directives in the snips here and on the
tomcat list, but this is the one that got C2 working.  I suppose the
distinction is that the sitemap is handling all sorts of goodness in
addition to .xml files.

Andre, will you take up dims offer to write something for the FAQ?  I will
be glad to if you are averse to it.

Mike





Andre Juffer <[EMAIL PROTECTED]> on 07/18/2001 11:46:45 AM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: C1 to C2


Hi All,

I got it finally working. The directive

JkMount /cocoon/* ajp12

did it. I apparently kept on missing that part, since this was not
required for tomcat-apache-cocoon1, where always, it seems, .xml was
employed to redirect xml request to cocoon1.

I would support the suggestion of Luca to put these few things into the
FAQ, because I would assume that more people make the same mistake as I
did.

Thank you for your help,

Andre.



Luca Morandini wrote:

> Andre,
>
>this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or
it
> will be overwritten every time you start Tomcat):
>
> 
>
> JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
> JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
> JkLogLevel warn
> JkMount /*.jsp ajp12
> JkMount /*.xml ajp12
>
> JkMount /cocoon/* ajp12
>
> 
>
>I presume this will do the trick of redirecting.
>
>Moreover, somewhere down mod_jk.conf, there is this cocoon-related
stuff:
>
> #
> # The following line makes apache aware of the location of the /cocoon
> context
> #
> Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
> 
> Options Indexes FollowSymLinks
> 
>
> #
> # The following line mounts all JSP files and the /servlet/ uri to tomcat
> #
> JkMount /cocoon/servlet/* ajp12
> JkMount /cocoon/*.jsp ajp12
>
> #
> # The following line prohibits users from directly accessing WEB-INF
> #
> 
> AllowOverride None
> deny from all
> 
>
> #
> # Use Directory too. On Windows, Location doesn't work unless case
matches
> #
> 
> AllowOverride None
> deny from all
> 
>
> #
> # The following line prohibits users from directly accessing META-INF
> #
> 
> AllowOverride None
> deny from all
> 
>
> #
> # Use Directory too. On Windows, Location doesn't work unless case
matches
> #
> 
> AllowOverride None
> deny from all
> 
>
>By the way, I'm not using Linux, but Windows NT 4.0 (as you may guess
from
> the paths...).
>
> Best regards,
>
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>       +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
>
>
>
>> -Original Message-
>> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
>> Sent: martedì 17 luglio 2001 23.13
>> To: [EMAIL PROTECTED]
>> Subject: Re: C1 to C2
>>
>>
>>
>>
>> Luca Morandini wrote:
>>
>>
>>> Andre,
>>>
>>>  I used mod_jk instead of jserv, hence, I can't be of much
>>
>> assistance.
>>
>>>  I would suggest you to switch to mod_jk, which is
>>
>> (reportedly) better, then
>>
>>> we may work out the problem...
>>
>> Hi Luca,
>>
>> All right, I switched to mod_jk. No change, however, everything I had
>> with jserv also applies to jk. The directory /cocoon is displayed if I
>> do the request localhost/cocoon in the same way as /localhost/examples
>> would do. Is this in fact to be expected, since localhost:8080/cocoon
>> results in the welcome page, so the latter request compiles the sitemap.
>> If I do localhost:8080/examples I also get a listing of the directory
>> examples, but now tomcat handled the request.
>>
>> Again, localhost:8080/cocoon works entirely correct.
>>
>> Maybe you could show me your server.xml and mod-jk.conf-auto files to
>> see what you have in your case. Are you accidentally using a linux
>> (Slackware) based system?
>>
>> Cheers,
>> Andre
>>
>>
>>>
>>> Best regards,
>>>
>>> -
>>>Luca Morandini
>>>GIS Consultant
>>> [EMAIL PROTECTED]
>>>   +39 0744 59  85  1 Of

Re: C1 to C2

2001-07-18 Thread Davanum Srinivas

Andre,

Can you re-post the complete instructions in the form of a FAQ? I will check it in.

Thanks,
dims

--- Andre Juffer <[EMAIL PROTECTED]> wrote:
> Hi All,
> 
> I got it finally working. The directive
> 
> JkMount /cocoon/* ajp12
> 
> did it. I apparently kept on missing that part, since this was not 
> required for tomcat-apache-cocoon1, where always, it seems, .xml was 
> employed to redirect xml request to cocoon1.
> 
> I would support the suggestion of Luca to put these few things into the 
> FAQ, because I would assume that more people make the same mistake as I did.
> 
> Thank you for your help,
> 
> Andre.
> 
> 
> 
> Luca Morandini wrote:
> 
> > Andre,
> > 
> > this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
> > will be overwritten every time you start Tomcat):
> > 
> > 
> > 
> > JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
> > JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
> > JkLogLevel warn
> > JkMount /*.jsp ajp12
> > JkMount /*.xml ajp12
> > 
> > JkMount /cocoon/* ajp12
> > 
> > 
> > 
> > I presume this will do the trick of redirecting.
> > 
> > Moreover, somewhere down mod_jk.conf, there is this cocoon-related stuff:
> > 
> > #
> > # The following line makes apache aware of the location of the /cocoon
> > context
> > #
> > Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
> > 
> > Options Indexes FollowSymLinks
> > 
> > 
> > #
> > # The following line mounts all JSP files and the /servlet/ uri to tomcat
> > #
> > JkMount /cocoon/servlet/* ajp12
> > JkMount /cocoon/*.jsp ajp12
> > 
> > #
> > # The following line prohibits users from directly accessing WEB-INF
> > #
> > 
> > AllowOverride None
> > deny from all
> > 
> > 
> > #
> > # Use Directory too. On Windows, Location doesn't work unless case matches
> > #
> > 
> > AllowOverride None
> > deny from all
> > 
> > 
> > #
> > # The following line prohibits users from directly accessing META-INF
> > #
> > 
> > AllowOverride None
> > deny from all
> > 
> > 
> > #
> > # Use Directory too. On Windows, Location doesn't work unless case matches
> > #
> > 
> > AllowOverride None
> > deny from all
> > 
> > 
> > By the way, I'm not using Linux, but Windows NT 4.0 (as you may guess from
> > the paths...).
> > 
> > Best regards,
> >  
> > -
> >Luca Morandini
> >GIS Consultant
> > [EMAIL PROTECTED]
> >   +39 0744 59  85  1 Office
> >   +39 0335 681 02 12 Mobile
> > http://utenti.tripod.it/lmorandini/index.html
> > -
> > 
> > 
> > 
> >> -Original Message-
> >> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> >> Sent: martedì 17 luglio 2001 23.13
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: C1 to C2
> >> 
> >> 
> >> 
> >> 
> >> Luca Morandini wrote:
> >> 
> >> 
> >>> Andre,
> >>> 
> >>>   I used mod_jk instead of jserv, hence, I can't be of much
> >> 
> >> assistance.
> >> 
> >>>   I would suggest you to switch to mod_jk, which is
> >> 
> >> (reportedly) better, then
> >> 
> >>> we may work out the problem...
> >> 
> >> Hi Luca,
> >> 
> >> All right, I switched to mod_jk. No change, however, everything I had
> >> with jserv also applies to jk. The directory /cocoon is displayed if I
> >> do the request localhost/cocoon in the same way as /localhost/examples
> >> would do. Is this in fact to be expected, since localhost:8080/cocoon
> >> results in the welcome page, so the latter request compiles the sitemap.
> >> If I do localhost:8080/examples I also get a listing of the directory
> >> examples, but now tomcat handled the request.
> >> 
> >> Again, localhost:8080/cocoon works entirely correct.
> >> 
> >> Maybe you could show me your server.xml and mod-jk.conf-auto files to
> >> see what you have in your case. Are you accidentally using a linux
> >> (Slackware) based system?
> >> 
> >> Cheers,
> >> Andre
> >> 
> >&

Re: C1 to C2

2001-07-18 Thread Andre Juffer

Hi All,

I got it finally working. The directive

JkMount /cocoon/* ajp12

did it. I apparently kept on missing that part, since this was not 
required for tomcat-apache-cocoon1, where always, it seems, .xml was 
employed to redirect xml request to cocoon1.

I would support the suggestion of Luca to put these few things into the 
FAQ, because I would assume that more people make the same mistake as I did.

Thank you for your help,

Andre.



Luca Morandini wrote:

> Andre,
> 
>   this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
> will be overwritten every time you start Tomcat):
> 
> 
> 
> JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
> JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
> JkLogLevel warn
> JkMount /*.jsp ajp12
> JkMount /*.xml ajp12
> 
> JkMount /cocoon/* ajp12
> 
> 
> 
>   I presume this will do the trick of redirecting.
> 
>   Moreover, somewhere down mod_jk.conf, there is this cocoon-related stuff:
> 
> #
> # The following line makes apache aware of the location of the /cocoon
> context
> #
> Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"
> 
> Options Indexes FollowSymLinks
> 
> 
> #
> # The following line mounts all JSP files and the /servlet/ uri to tomcat
> #
> JkMount /cocoon/servlet/* ajp12
> JkMount /cocoon/*.jsp ajp12
> 
> #
> # The following line prohibits users from directly accessing WEB-INF
> #
> 
> AllowOverride None
> deny from all
> 
> 
> #
> # Use Directory too. On Windows, Location doesn't work unless case matches
> #
> 
> AllowOverride None
> deny from all
> 
> 
> #
> # The following line prohibits users from directly accessing META-INF
> #
> 
> AllowOverride None
> deny from all
> 
> 
> #
> # Use Directory too. On Windows, Location doesn't work unless case matches
> #
> 
> AllowOverride None
> deny from all
> 
> 
>   By the way, I'm not using Linux, but Windows NT 4.0 (as you may guess from
> the paths...).
> 
> Best regards,
>  
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>   +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
> 
> 
> 
>> -Original Message-
>> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
>> Sent: martedì 17 luglio 2001 23.13
>> To: [EMAIL PROTECTED]
>> Subject: Re: C1 to C2
>> 
>> 
>> 
>> 
>> Luca Morandini wrote:
>> 
>> 
>>> Andre,
>>> 
>>> I used mod_jk instead of jserv, hence, I can't be of much
>> 
>> assistance.
>> 
>>> I would suggest you to switch to mod_jk, which is
>> 
>> (reportedly) better, then
>> 
>>> we may work out the problem...
>> 
>> Hi Luca,
>> 
>> All right, I switched to mod_jk. No change, however, everything I had
>> with jserv also applies to jk. The directory /cocoon is displayed if I
>> do the request localhost/cocoon in the same way as /localhost/examples
>> would do. Is this in fact to be expected, since localhost:8080/cocoon
>> results in the welcome page, so the latter request compiles the sitemap.
>> If I do localhost:8080/examples I also get a listing of the directory
>> examples, but now tomcat handled the request.
>> 
>> Again, localhost:8080/cocoon works entirely correct.
>> 
>> Maybe you could show me your server.xml and mod-jk.conf-auto files to
>> see what you have in your case. Are you accidentally using a linux
>> (Slackware) based system?
>> 
>> Cheers,
>> Andre
>> 
>> 
>>> 
>>> Best regards,
>>> 
>>> -
>>>Luca Morandini
>>>GIS Consultant
>>> [EMAIL PROTECTED]
>>>   +39 0744 59  85  1 Office
>>>   +39 0335 681 02 12 Mobile
>>> http://utenti.tripod.it/lmorandini/index.html
>>> -
>>> 
>>> 
>>> 
>>> 
>>>> -Original Message-
>>>> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
>>>> Sent: lunedì 16 luglio 2001 23.38
>>>> To: [EMAIL PROTECTED]
>>>> Subject: C1 to C2
>>>> 
>>>> 
>>>> Luca, Anders, Lajos,
>>>> 
>>>> I keep on having the same pr

mod_jk.conf-auto [wa: RE: C1 to C2]

2001-07-18 Thread Luca Morandini

> -Original Message-
> From: Lajos Moczar [mailto:[EMAIL PROTECTED]]
> Sent: mercoledì 18 luglio 2001 3.10
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> I always point directly to mod_jk.conf-auto in httpd.conf because it
> will always be up to date. It is created each time Tomcat starts to
> reflect that latest context information for each webapp. If I have
> things that I want to add, I just put them in httpd.conf after the
> include for mod_jk. Thus:
>
> Include /usr/local/jakarta-tomcat/conf/mod_jk.conf-auto
> JkMount /*.xml ajp13

Lajos,

you're way makes. On the other hand, you'll have to look in two places in
order to understand the complete Tomcat configuration.


> Is that a problem that mod_jk.conf-auto gets overwritten every time? If I
> get rid of it, isn't it always newly created?
>

Ulrich,

yes. it is created every time, but if you tell Apache not to load it (and
load mod_jk.conf, instead) it will be simply ignored... 


All,

anyway, my point was in suggesting Andre to modify mod_jk.conf to make
Cocoon work properly, and this couldn't be done whith mod_jk.conf-auto,
since your changes will be written on water... unless you use Lajos's way
(see above).

Best regards,

-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Re: C1 to C2

2001-07-17 Thread Sergio Carvalho


Can anyone inform me of the advantages of mod_jk over mod_proxy + URL rewriting 
engine? 
I had all kinds of problems with mod_jk, and am now a happy user of mod_proxy, but I 
never see this approach suggested.


On Tue, 17 Jul 2001 00:38:16 +0300, Andre Juffer <[EMAIL PROTECTED]> wrote:
--
> Luca, Anders, Lajos,
> 
> I keep on having the same problem. While localhost:8080/cocoon correctly 
> displays the welcome page of cocoon2, it seems to be impossible for me 
> to get apache + tomcat 3.2.2 + cocoon2 working together, such also the 
> request localhost/cocoon displays the welcome page.
> 
> The following is what being including into httpd.conf (in addition to 
> what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
> 
> 
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
> 
> Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
> 
>  Options Indexes FollowSymLinks
> 
> ApJServMount /cocoon/servlet /cocoon
> 
>  AllowOverride None
>  deny from all
> 
> 
>  AllowOverride None
>  deny from all
> 
> 
> RewriteEngine On
> RewriteLog "/var/log/rewrite.log"
> RewriteLogLevel 3
> RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]
> 
> 
> The rewriting is actually working in the way it should (Thanks Luca). 
> Also, localhost/cocoon in fact displays the CONTENT of the 
> webapps/cocoon directory and the same for localhost/Biocomputing/ (with 
> the trailing /), which gives me correctly the /cocoon/Biocomputing 
> directory.
> 
> The key problem are these lines (I think)
> 
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
> 
> In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet 
> is responding (in the way it should):
> 
> ---
> Cocoon 2 - Resource not found
> type resource-not-found
> message Resource not found
> description The requested URI "/cocoon/welcome.xml" was not found.
> sender org.apache.cocoon.servlet.CocoonServlet
> source Cocoon servlet
> request-uri
> /cocoon/welcome.xml
> path-info
> welcome.xml
> ---
> 
> The sitemap is not compiled, though. If I add to the sitemap the following
> 
> ---
> 
>  
> 
> ---
> 
> localhost/cocoon/welcome.xml will not display the welcome. It is shown, 
> of course, upon the request localhost:8080/cocoon/welcome.xml.
> 
> In fact, the request localhost/cocoon/welcome results in
> 
> 
> Not Found
> The requested URL /cocoon/welcome was not found on this server.
> Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
> -
> 
> So, in the latter case, Apache is handling the request instead of 
> cocoon2. Obviously, this is because there is no .xml extension.
> 
> If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly 
> have you for AddType and AddHandler directives in your configuration?
> 
> Of course, I can always write all my files ending with e.g. xml, xsp and 
> adapt the sitemap accordingly (and use 8080). No objections there, but 
> it is ugly. Currently, I think, requests like /Foo/foo 
> without having some extension at the foo, cannot be resolved correctly 
> in a simple way such that cocoon2 takes over the request.
> 
> Or do I still miss something totally . what, on earth?
> 
> Cheers,
> Andre.
> 
> 
> 
> 
> 
> -- 
> Andre H. Juffer  | Phone: +358-8-553 1683
> The Biocenter and| Fax: +358-8-553-1141
>  the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
> University of Oulu, Finland  | WWW: http://www.biochem.oulu.fi/research.html
> 
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
> 



--
Sergio Carvalho
---
[EMAIL PROTECTED]

If at first you don't succeed, skydiving is not for you

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: C1 to C2

2001-07-17 Thread Lajos Moczar

I always point directly to mod_jk.conf-auto in httpd.conf because it 
will always be up to date. It is created each time Tomcat starts to 
reflect that latest context information for each webapp. If I have 
things that I want to add, I just put them in httpd.conf after the 
include for mod_jk. Thus:

Include /usr/local/jakarta-tomcat/conf/mod_jk.conf-auto
JkMount /*.xml ajp13


Lajos


Uli Mayring wrote:

> On Wed, 18 Jul 2001, Luca Morandini wrote:
> 
> 
>> Andre,
>> 
>> this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
>> will be overwritten every time you start Tomcat):
> 
> 
> Is that a problem that mod_jk.conf-auto gets overwritten every time? If I
> get rid of it, isn't it always newly created?
> 
> Ulrich
> 
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: C1 to C2

2001-07-17 Thread Uli Mayring

On Wed, 18 Jul 2001, Luca Morandini wrote:

> Andre,
> 
> this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
> will be overwritten every time you start Tomcat):

Is that a problem that mod_jk.conf-auto gets overwritten every time? If I
get rid of it, isn't it always newly created?

Ulrich


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: C1 to C2

2001-07-17 Thread Luca Morandini

Andre,

this is snippet from my mod_jk.conf (get rid of mod_jk.conf-auto, or it
will be overwritten every time you start Tomcat):



JkWorkersFile "C:/Apps/Tomcat/conf/workers.properties"
JkLogFile "C:/Apps/Tomcat/logs/mod_jk.log"
JkLogLevel warn
JkMount /*.jsp ajp12
JkMount /*.xml ajp12

JkMount /cocoon/* ajp12



I presume this will do the trick of redirecting.

Moreover, somewhere down mod_jk.conf, there is this cocoon-related stuff:

#
# The following line makes apache aware of the location of the /cocoon
context
#
Alias /cocoon "C:/Apps/Tomcat/webapps/cocoon"

Options Indexes FollowSymLinks


#
# The following line mounts all JSP files and the /servlet/ uri to tomcat
#
JkMount /cocoon/servlet/* ajp12
JkMount /cocoon/*.jsp ajp12

#
# The following line prohibits users from directly accessing WEB-INF
#

AllowOverride None
deny from all


#
# Use Directory too. On Windows, Location doesn't work unless case matches
#

AllowOverride None
deny from all


#
# The following line prohibits users from directly accessing META-INF
#

AllowOverride None
deny from all


#
# Use Directory too. On Windows, Location doesn't work unless case matches
#

AllowOverride None
deny from all


By the way, I'm not using Linux, but Windows NT 4.0 (as you may guess from
the paths...).

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: martedì 17 luglio 2001 23.13
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
>
>
> Luca Morandini wrote:
>
> > Andre,
> >
> > I used mod_jk instead of jserv, hence, I can't be of much
> assistance.
> >
> > I would suggest you to switch to mod_jk, which is
> (reportedly) better, then
> > we may work out the problem...
>
> Hi Luca,
>
> All right, I switched to mod_jk. No change, however, everything I had
> with jserv also applies to jk. The directory /cocoon is displayed if I
> do the request localhost/cocoon in the same way as /localhost/examples
> would do. Is this in fact to be expected, since localhost:8080/cocoon
> results in the welcome page, so the latter request compiles the sitemap.
> If I do localhost:8080/examples I also get a listing of the directory
> examples, but now tomcat handled the request.
>
> Again, localhost:8080/cocoon works entirely correct.
>
> Maybe you could show me your server.xml and mod-jk.conf-auto files to
> see what you have in your case. Are you accidentally using a linux
> (Slackware) based system?
>
> Cheers,
> Andre
>
> >
> >
> > Best regards,
> >
> > -
> >Luca Morandini
> >GIS Consultant
> > [EMAIL PROTECTED]
> >   +39 0744 59  85  1 Office
> >   +39 0335 681 02 12 Mobile
> > http://utenti.tripod.it/lmorandini/index.html
> > -
> >
> >
> >
> >> -Original Message-
> >> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> >> Sent: lunedì 16 luglio 2001 23.38
> >> To: [EMAIL PROTECTED]
> >> Subject: C1 to C2
> >>
> >>
> >> Luca, Anders, Lajos,
> >>
> >> I keep on having the same problem. While localhost:8080/cocoon
> correctly
> >> displays the welcome page of cocoon2, it seems to be impossible for me
> >> to get apache + tomcat 3.2.2 + cocoon2 working together, such also the
> >> request localhost/cocoon displays the welcome page.
> >>
> >> The following is what being including into httpd.conf (in addition to
> >> what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
> >>
> >> 
> >> AddType text/xml .xml
> >> AddHandler jserv-servlet .xml
> >>
> >> Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
> >> 
> >>  Options Indexes FollowSymLinks
> >> 
> >> ApJServMount /cocoon/servlet /cocoon
> >> 
> >>  AllowOverride None
> >>  deny from all
> >> 
> >> 
> >>  AllowOverride None
> >>  deny from all
> >> 
> >>
> >> RewriteEngine On
> >> RewriteLog "/var/log/rewrite.log"
> >> RewriteLogLevel 3
> >> RewriteRule Bio

RE: C1 to C2

2001-07-17 Thread Luca Morandini

Lajos,

since this seems to be a popular topic: why don't we make a FAQ entry on
the topic and put it on the Cocoon site ?

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Lajos Moczar [mailto:[EMAIL PROTECTED]]
> Sent: martedì 17 luglio 2001 20.11
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> Andre:
>
> You might check out some guides I've written when I was struggling with
> this stuff. They're at my site, galatea.com (powered by Cocoon 1.8.2 but
> soon 2.1!). I explain how to get mod_jk working which, as Luca points
> out, it preferable. If these still can't help you, I'll play around some
> more with my own configurations and see what I can come up with.
>
> Regards,
>
> Lajos
>
>
> Andre Juffer wrote:
>
> > Luca, Anders, Lajos,
> >
> > I keep on having the same problem. While localhost:8080/cocoon
> correctly
> > displays the welcome page of cocoon2, it seems to be impossible for me
> > to get apache + tomcat 3.2.2 + cocoon2 working together, such also the
> > request localhost/cocoon displays the welcome page.
> >
> > The following is what being including into httpd.conf (in addition to
> > what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
> >
> > 
> > AddType text/xml .xml
> > AddHandler jserv-servlet .xml
> >
> > Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
> > 
> > Options Indexes FollowSymLinks
> > 
> > ApJServMount /cocoon/servlet /cocoon
> > 
> > AllowOverride None
> > deny from all
> > 
> > 
> > AllowOverride None
> > deny from all
> > 
> >
> > RewriteEngine On
> > RewriteLog "/var/log/rewrite.log"
> > RewriteLogLevel 3
> > RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]
> > 
> >
> > The rewriting is actually working in the way it should (Thanks Luca).
> > Also, localhost/cocoon in fact displays the CONTENT of the
> > webapps/cocoon directory and the same for localhost/Biocomputing/ (with
> > the trailing /), which gives me correctly the /cocoon/Biocomputing
> > directory.
> >
> > The key problem are these lines (I think)
> >
> > AddType text/xml .xml
> > AddHandler jserv-servlet .xml
> >
> > In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet
> > is responding (in the way it should):
> >
> > ---
> > Cocoon 2 - Resource not found
> > type resource-not-found
> > message Resource not found
> > description The requested URI "/cocoon/welcome.xml" was not found.
> > sender org.apache.cocoon.servlet.CocoonServlet
> > source Cocoon servlet
> > request-uri
> > /cocoon/welcome.xml
> > path-info
> > welcome.xml
> > ---
> >
> > The sitemap is not compiled, though. If I add to the sitemap
> the following
> >
> > ---
> >
> > 
> >
> > ---
> >
> > localhost/cocoon/welcome.xml will not display the welcome. It is shown,
> > of course, upon the request localhost:8080/cocoon/welcome.xml.
> >
> > In fact, the request localhost/cocoon/welcome results in
> >
> > 
> > Not Found
> > The requested URL /cocoon/welcome was not found on this server.
> > Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
> > -
> >
> > So, in the latter case, Apache is handling the request instead of
> > cocoon2. Obviously, this is because there is no .xml extension.
> >
> > If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly
> > have you for AddType and AddHandler directives in your configuration?
> >
> > Of course, I can always write all my files ending with e.g.
> xml, xsp and
> > adapt the sitemap accordingly (and use 8080). No objections there, but
> > it is ugly. Currently, I think, requests like /Foo/foo
> > without having some extension at the foo, cannot be resolved correctly
> > in a simple way such that cocoon2 takes over the request.
> >
> > Or do I still miss something totally . what, on earth?
> >
> > Cheers,
> > Andre.
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Re: C1 to C2

2001-07-17 Thread Lajos Moczar

Andre:

You might check out some guides I've written when I was struggling with 
this stuff. They're at my site, galatea.com (powered by Cocoon 1.8.2 but 
soon 2.1!). I explain how to get mod_jk working which, as Luca points 
out, it preferable. If these still can't help you, I'll play around some 
more with my own configurations and see what I can come up with.

Regards,

Lajos


Andre Juffer wrote:

> Luca, Anders, Lajos,
> 
> I keep on having the same problem. While localhost:8080/cocoon correctly 
> displays the welcome page of cocoon2, it seems to be impossible for me 
> to get apache + tomcat 3.2.2 + cocoon2 working together, such also the 
> request localhost/cocoon displays the welcome page.
> 
> The following is what being including into httpd.conf (in addition to 
> what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
> 
> 
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
> 
> Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
> 
> Options Indexes FollowSymLinks
> 
> ApJServMount /cocoon/servlet /cocoon
> 
> AllowOverride None
> deny from all
> 
> 
> AllowOverride None
> deny from all
> 
> 
> RewriteEngine On
> RewriteLog "/var/log/rewrite.log"
> RewriteLogLevel 3
> RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]
> 
> 
> The rewriting is actually working in the way it should (Thanks Luca). 
> Also, localhost/cocoon in fact displays the CONTENT of the 
> webapps/cocoon directory and the same for localhost/Biocomputing/ (with 
> the trailing /), which gives me correctly the /cocoon/Biocomputing 
> directory.
> 
> The key problem are these lines (I think)
> 
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
> 
> In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet 
> is responding (in the way it should):
> 
> ---
> Cocoon 2 - Resource not found
> type resource-not-found
> message Resource not found
> description The requested URI "/cocoon/welcome.xml" was not found.
> sender org.apache.cocoon.servlet.CocoonServlet
> source Cocoon servlet
> request-uri
> /cocoon/welcome.xml
> path-info
> welcome.xml
> ---
> 
> The sitemap is not compiled, though. If I add to the sitemap the following
> 
> ---
>
> 
>
> ---
> 
> localhost/cocoon/welcome.xml will not display the welcome. It is shown, 
> of course, upon the request localhost:8080/cocoon/welcome.xml.
> 
> In fact, the request localhost/cocoon/welcome results in
> 
> 
> Not Found
> The requested URL /cocoon/welcome was not found on this server.
> Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
> -
> 
> So, in the latter case, Apache is handling the request instead of 
> cocoon2. Obviously, this is because there is no .xml extension.
> 
> If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly 
> have you for AddType and AddHandler directives in your configuration?
> 
> Of course, I can always write all my files ending with e.g. xml, xsp and 
> adapt the sitemap accordingly (and use 8080). No objections there, but 
> it is ugly. Currently, I think, requests like /Foo/foo 
> without having some extension at the foo, cannot be resolved correctly 
> in a simple way such that cocoon2 takes over the request.
> 
> Or do I still miss something totally . what, on earth?
> 
> Cheers,
> Andre.


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: C1 to C2

2001-07-17 Thread Andre Juffer



Luca Morandini wrote:

> Andre,
> 
>   I used mod_jk instead of jserv, hence, I can't be of much assistance.
> 
>   I would suggest you to switch to mod_jk, which is (reportedly) better, then
> we may work out the problem...

Hi Luca,

All right, I switched to mod_jk. No change, however, everything I had 
with jserv also applies to jk. The directory /cocoon is displayed if I 
do the request localhost/cocoon in the same way as /localhost/examples 
would do. Is this in fact to be expected, since localhost:8080/cocoon 
results in the welcome page, so the latter request compiles the sitemap. 
If I do localhost:8080/examples I also get a listing of the directory 
examples, but now tomcat handled the request.

Again, localhost:8080/cocoon works entirely correct.

Maybe you could show me your server.xml and mod-jk.conf-auto files to 
see what you have in your case. Are you accidentally using a linux 
(Slackware) based system?

Cheers,
Andre

> 
> 
> Best regards,
>  
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>   +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
> 
> 
> 
>> -Original Message-
>> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
>> Sent: lunedì 16 luglio 2001 23.38
>> To: [EMAIL PROTECTED]
>> Subject: C1 to C2
>> 
>> 
>> Luca, Anders, Lajos,
>> 
>> I keep on having the same problem. While localhost:8080/cocoon correctly
>> displays the welcome page of cocoon2, it seems to be impossible for me
>> to get apache + tomcat 3.2.2 + cocoon2 working together, such also the
>> request localhost/cocoon displays the welcome page.
>> 
>> The following is what being including into httpd.conf (in addition to
>> what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
>> 
>> 
>> AddType text/xml .xml
>> AddHandler jserv-servlet .xml
>> 
>> Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
>> 
>>  Options Indexes FollowSymLinks
>> 
>> ApJServMount /cocoon/servlet /cocoon
>> 
>>  AllowOverride None
>>  deny from all
>> 
>> 
>>  AllowOverride None
>>  deny from all
>> 
>> 
>> RewriteEngine On
>> RewriteLog "/var/log/rewrite.log"
>> RewriteLogLevel 3
>> RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]
>> 
>> 
>> The rewriting is actually working in the way it should (Thanks Luca).
>> Also, localhost/cocoon in fact displays the CONTENT of the
>> webapps/cocoon directory and the same for localhost/Biocomputing/ (with
>> the trailing /), which gives me correctly the /cocoon/Biocomputing
>> directory.
>> 
>> The key problem are these lines (I think)
>> 
>> AddType text/xml .xml
>> AddHandler jserv-servlet .xml
>> 
>> In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet
>> is responding (in the way it should):
>> 
>> ---
>> Cocoon 2 - Resource not found
>> type resource-not-found
>> message Resource not found
>> description The requested URI "/cocoon/welcome.xml" was not found.
>> sender org.apache.cocoon.servlet.CocoonServlet
>> source Cocoon servlet
>> request-uri
>> /cocoon/welcome.xml
>> path-info
>> welcome.xml
>> ---
>> 
>> The sitemap is not compiled, though. If I add to the sitemap the following
>> 
>> ---
>> 
>>  
>> 
>> ---
>> 
>> localhost/cocoon/welcome.xml will not display the welcome. It is shown,
>> of course, upon the request localhost:8080/cocoon/welcome.xml.
>> 
>> In fact, the request localhost/cocoon/welcome results in
>> 
>> 
>> Not Found
>> The requested URL /cocoon/welcome was not found on this server.
>> Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
>> -
>> 
>> So, in the latter case, Apache is handling the request instead of
>> cocoon2. Obviously, this is because there is no .xml extension.
>> 
>> If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly
>> have you for AddType and AddHandler directives in your configuration?
>> 
>> Of course, I can always write all my files ending with e.g. xml, xsp and
>> adapt the sitemap accordingly (and use 8080). No objections there, but
>> it is ugly. Currently, I think, requests like /Foo/foo
>> without having some extension at the foo, cannot b

C1 to C2

2001-07-16 Thread Andre Juffer

Luca, Anders, Lajos,

I keep on having the same problem. While localhost:8080/cocoon correctly 
displays the welcome page of cocoon2, it seems to be impossible for me 
to get apache + tomcat 3.2.2 + cocoon2 working together, such also the 
request localhost/cocoon displays the welcome page.

The following is what being including into httpd.conf (in addition to 
what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):


AddType text/xml .xml
AddHandler jserv-servlet .xml

Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"

 Options Indexes FollowSymLinks

ApJServMount /cocoon/servlet /cocoon

 AllowOverride None
 deny from all


 AllowOverride None
 deny from all


RewriteEngine On
RewriteLog "/var/log/rewrite.log"
RewriteLogLevel 3
RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]


The rewriting is actually working in the way it should (Thanks Luca). 
Also, localhost/cocoon in fact displays the CONTENT of the 
webapps/cocoon directory and the same for localhost/Biocomputing/ (with 
the trailing /), which gives me correctly the /cocoon/Biocomputing 
directory.

The key problem are these lines (I think)

AddType text/xml .xml
AddHandler jserv-servlet .xml

In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet 
is responding (in the way it should):

---
Cocoon 2 - Resource not found
type resource-not-found
message Resource not found
description The requested URI "/cocoon/welcome.xml" was not found.
sender org.apache.cocoon.servlet.CocoonServlet
source Cocoon servlet
request-uri
/cocoon/welcome.xml
path-info
welcome.xml
---

The sitemap is not compiled, though. If I add to the sitemap the following

---

 

---

localhost/cocoon/welcome.xml will not display the welcome. It is shown, 
of course, upon the request localhost:8080/cocoon/welcome.xml.

In fact, the request localhost/cocoon/welcome results in


Not Found
The requested URL /cocoon/welcome was not found on this server.
Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
-

So, in the latter case, Apache is handling the request instead of 
cocoon2. Obviously, this is because there is no .xml extension.

If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly 
have you for AddType and AddHandler directives in your configuration?

Of course, I can always write all my files ending with e.g. xml, xsp and 
adapt the sitemap accordingly (and use 8080). No objections there, but 
it is ugly. Currently, I think, requests like /Foo/foo 
without having some extension at the foo, cannot be resolved correctly 
in a simple way such that cocoon2 takes over the request.

Or do I still miss something totally . what, on earth?

Cheers,
Andre.





-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
 the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW: http://www.biochem.oulu.fi/research.html


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: C1 to C2

2001-07-16 Thread Luca Morandini

Andre,

I used mod_jk instead of jserv, hence, I can't be of much assistance.

I would suggest you to switch to mod_jk, which is (reportedly) better, then
we may work out the problem...


Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: lunedì 16 luglio 2001 23.38
> To: [EMAIL PROTECTED]
> Subject: C1 to C2
>
>
> Luca, Anders, Lajos,
>
> I keep on having the same problem. While localhost:8080/cocoon correctly
> displays the welcome page of cocoon2, it seems to be impossible for me
> to get apache + tomcat 3.2.2 + cocoon2 working together, such also the
> request localhost/cocoon displays the welcome page.
>
> The following is what being including into httpd.conf (in addition to
> what is already given in tomcat-3.2.2/conf/tomcat-apache.conf):
>
> 
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
>
> Alias /cocoon "/usr/local/jakarta-tomcat-3.2.2/webapps/cocoon"
> 
>  Options Indexes FollowSymLinks
> 
> ApJServMount /cocoon/servlet /cocoon
> 
>  AllowOverride None
>  deny from all
> 
> 
>  AllowOverride None
>  deny from all
> 
>
> RewriteEngine On
> RewriteLog "/var/log/rewrite.log"
> RewriteLogLevel 3
> RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]
> 
>
> The rewriting is actually working in the way it should (Thanks Luca).
> Also, localhost/cocoon in fact displays the CONTENT of the
> webapps/cocoon directory and the same for localhost/Biocomputing/ (with
> the trailing /), which gives me correctly the /cocoon/Biocomputing
> directory.
>
> The key problem are these lines (I think)
>
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
>
> In fact, if I request localhost/cocoon/welcome.xml, the cocoon2 servlet
> is responding (in the way it should):
>
> ---
> Cocoon 2 - Resource not found
> type resource-not-found
> message Resource not found
> description The requested URI "/cocoon/welcome.xml" was not found.
> sender org.apache.cocoon.servlet.CocoonServlet
> source Cocoon servlet
> request-uri
> /cocoon/welcome.xml
> path-info
> welcome.xml
> ---
>
> The sitemap is not compiled, though. If I add to the sitemap the following
>
> ---
> 
>  
> 
> ---
>
> localhost/cocoon/welcome.xml will not display the welcome. It is shown,
> of course, upon the request localhost:8080/cocoon/welcome.xml.
>
> In fact, the request localhost/cocoon/welcome results in
>
> 
> Not Found
> The requested URL /cocoon/welcome was not found on this server.
> Apache/1.3.12 Server at ajuffer-dsl.oulu.fi Port 80
> -
>
> So, in the latter case, Apache is handling the request instead of
> cocoon2. Obviously, this is because there is no .xml extension.
>
> If you are using Tomcat 3.2.2, Apache 1.3.* and cocoon2, what exactly
> have you for AddType and AddHandler directives in your configuration?
>
> Of course, I can always write all my files ending with e.g. xml, xsp and
> adapt the sitemap accordingly (and use 8080). No objections there, but
> it is ugly. Currently, I think, requests like /Foo/foo
> without having some extension at the foo, cannot be resolved correctly
> in a simple way such that cocoon2 takes over the request.
>
> Or do I still miss something totally . what, on earth?
>
> Cheers,
> Andre.
>
>
>
>
>
> --
> Andre H. Juffer  | Phone: +358-8-553 1683
> The Biocenter and| Fax: +358-8-553-1141
>  the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
> University of Oulu, Finland  | WWW:
> http://www.biochem.oulu.fi/research.html
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Re: OT: Tomcat version [was Re: Fw: RE: C1 to C2]

2001-07-16 Thread Andre Juffer

Arnaud Vandyck wrote:
> 
> On Mon, 16 Jul 2001 12:58:36 +0300, Andre Juffer <[EMAIL PROTECTED]> wrote:
> 
> > Arnaud,
> >
> > just wondering, do you have a setup with tomcat3 or tomcat4. I am
> > currently playing with apache1.3-tomcat4-cocoon2, but it seems that the
> > way to get apache 1.3 and tomcat4 working together is different than the
> > way this is carried out for apache1.3 and tomcat3.
> 
> Andre,
> 
> I use Tomcat 3.3. I tried to get Tomcat4 but had some problems to make
> it work with Apache.

OK, I had also problems. I cannot really find any clear documentation on
this. I will go back to tomcat 3.3.

Thanks,
Andre


> 
> Regards,
> 
> --Arnaud
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>

-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW:
http://www.biochem.oulu.fi/research.html

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




OT: Tomcat version [was Re: Fw: RE: C1 to C2]

2001-07-16 Thread Arnaud Vandyck

On Mon, 16 Jul 2001 12:58:36 +0300, Andre Juffer <[EMAIL PROTECTED]> wrote:

> Arnaud,
> 
> just wondering, do you have a setup with tomcat3 or tomcat4. I am
> currently playing with apache1.3-tomcat4-cocoon2, but it seems that the
> way to get apache 1.3 and tomcat4 working together is different than the
> way this is carried out for apache1.3 and tomcat3.

Andre,

I use Tomcat 3.3. I tried to get Tomcat4 but had some problems to make
it work with Apache.

Regards,

--Arnaud


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: Fw: RE: C1 to C2

2001-07-16 Thread Andre Juffer

Arnaud,

just wondering, do you have a setup with tomcat3 or tomcat4. I am
currently playing with apache1.3-tomcat4-cocoon2, but it seems that the
way to get apache 1.3 and tomcat4 working together is different than the
way this is carried out for apache1.3 and tomcat3.

Cheers,
Andre.


Arnaud Vandyck wrote:
> 
> Sorry, I thought the reply was not on the list so I posted in
> private. And sorry for this mail, I think the charset is not correct
> but I've just installed Mew (Messaging in Emacs World) and I did not
> configure it at the time ;)
> 
> --Arnaud
> 
>   ------------
> 
> Subject: RE: C1 to C2
> Date: Fri, 13 Jul 2001 16:12:11 +0200
> From: "Luca Morandini" <[EMAIL PROTECTED]>
> To: "Arnaud Vandyck" <[EMAIL PROTECTED]>
> 
> Arnaud,
> 
> could you, please, post your reply to the cocoon-users' mailing list as
> well ?
> I think this matter is of general interest.
> 
> Best regards,
> 
> -
>Luca Morandini
> -
> 
> > -Original Message-
> > From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> > Sent: venerdì 13 luglio 2001 15.41
> > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > Subject: RE: C1 to C2
> >
> >
> > On Fri, 13 Jul 2001 15:31:56 +0200, "Luca Morandini"
> > <[EMAIL PROTECTED]> wrote:
> >
> > > > -Original Message-
> > > > From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> > > > Sent: venerdì 13 luglio 2001 14.53
> > > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > > Subject: RE: C1 to C2
> > > >
> > > > If you only pass xml files to C2, you'll loose the ability to
> > > > construct dynamic pdf with the pdf extension and so on with .txt or
> > > > .sh or .jpg, and so on...
> > > >
> > > you may pass every URI you want to Cocoon, whathever the
> > extension. Of
> > > course, you will have to rely on the Apache rewrite engine to
> > handle this
> > > job (I mean: switching URI between Apache or Cocoon).
> > > This URI switching task might be pretty tricky and,
> > moreover, is bound to
> > > put application logic outside the sitemap... which is unfortunate.
> >
> > I did never work with the Apache rewrite engine, this is my first
> > error ;)
> >
> > > > In your configuration, what will you do if you got to serve static xml
> > > > files (example: applet configuration)?
> > > >
> > > I'll tell Apache NOT to pass xml files contained in a
> > subsite to Cocoon.
> > > For instance, every URI in www.foobar.com/foo/static won't be passed to
> > > Cocoon but served directly by Apache, while every URI in
> > >  www.foobar.com/foo/dynamic will be passed to Cocoon for
> > further processing.
> >
> > I think MY mistake was to tell apache to relay * to Cocoon. The other
> > mapping did not work anymore!
> >
> > But I did not want to check all the extension type (well, I should
> > because they are not so many)! ;)
> >
> > Thanks for the tips, I'll try
> >
> > --Arnaud
> >
> 
>   
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>

-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW:
http://www.biochem.oulu.fi/research.html

-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Fw: RE: C1 to C2

2001-07-16 Thread Arnaud Vandyck

Sorry, I thought the reply was not on the list so I posted in
private. And sorry for this mail, I think the charset is not correct
but I've just installed Mew (Messaging in Emacs World) and I did not
configure it at the time ;)


--Arnaud



Arnaud,

could you, please, post your reply to the cocoon-users' mailing list as
well ?
I think this matter is of general interest.

Best regards,
 
-
   Luca Morandini
-


> -Original Message-
> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 15.41
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: C1 to C2
>
>
> On Fri, 13 Jul 2001 15:31:56 +0200, "Luca Morandini"
> <[EMAIL PROTECTED]> wrote:
>
> > > -Original Message-
> > > From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> > > Sent: venerdì 13 luglio 2001 14.53
> > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > > Subject: RE: C1 to C2
> > >
> > > If you only pass xml files to C2, you'll loose the ability to
> > > construct dynamic pdf with the pdf extension and so on with .txt or
> > > .sh or .jpg, and so on...
> > >
> > you may pass every URI you want to Cocoon, whathever the
> extension. Of
> > course, you will have to rely on the Apache rewrite engine to
> handle this
> > job (I mean: switching URI between Apache or Cocoon).
> > This URI switching task might be pretty tricky and,
> moreover, is bound to
> > put application logic outside the sitemap... which is unfortunate.
>
> I did never work with the Apache rewrite engine, this is my first
> error ;)
>
> > > In your configuration, what will you do if you got to serve static xml
> > > files (example: applet configuration)?
> > >
> > I'll tell Apache NOT to pass xml files contained in a
> subsite to Cocoon.
> > For instance, every URI in www.foobar.com/foo/static won't be passed to
> > Cocoon but served directly by Apache, while every URI in
> >  www.foobar.com/foo/dynamic will be passed to Cocoon for
> further processing.
>
> I think MY mistake was to tell apache to relay * to Cocoon. The other
> mapping did not work anymore!
>
> But I did not want to check all the extension type (well, I should
> because they are not so many)! ;)
>
> Thanks for the tips, I'll try
>
> --Arnaud
>





-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


RE: C1 to C2

2001-07-13 Thread Luca Morandini

Andre,

I think you shouldn't put the entire URI in the substitution rule, instead,
try the following:

RewriteRule Biocomputing/(.*) /cocoon/Biocomputing/$1 [PT]

BTW, don't forget to pass every URI with /cocoon to Tomcat, in order to
avoid specifying port 8080.

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 22.23
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> Luca,
>
> I have been playing with your suggestions. This is what I have added to
> httpd.conf as a test case:
>
>
> 
> RewriteEngine On
> RewriteLog "/var/log/rewrite.log"
> RewriteLogLevel 3
> RewriteRule Biocomputing/(.*)
> http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/$1 [PT]>
> 
>
> (The last two lines is actually one line in the file.)
>
> After requesting http://ajuffer-dsl.oulu.fi/Biocomputing/users-database,
> the rewrite.log shows me this:
>
> 
>
> 127.0.0.1 - - [13/Jul/2001:22:56:13 +0300]
> [ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) init rewrite
> engine with requested uri /Biocomputing/users-database
> 127.0.0.1 - - [13/Jul/2001:22:56:13 +0300]
> [ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (3) applying
> pattern 'Biocomputing/(.*)' to uri '/Biocomputing/users-database'
> 127.0.0.1 - - [13/Jul/2001:22:56:13 +0300]
> [ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) rewrite
> /Biocomputing/users-database ->
> http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database
> 127.0.0.1 - - [13/Jul/2001:22:56:13 +0300]
> [ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) implicitly
> forcing redirect (rc=302) with
> http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database
> 127.0.0.1 - - [13/Jul/2001:22:56:13 +0300]
> [ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) forcing
> 'http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database' to
> get passed through to next API URI-to-filename handler
>
> 
>
> (ajuffer-dsl.oulu.fi is the machine at home, behind firewall, and
> Biocomputing is an application we are working on, far from complete
> right now).
>
> It seems to me that the request
> http://ajuffer-dsl.oulu.fi/Biocomputing/users-database is correctly
> rewritten as
> http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database.
>
> Still, I get an error message:
>
>
> 
>
> Found The document has moved here.
>
> Additionally, a 400 Bad Request error was encountered while trying to
> use an ErrorDocument to handle the request. Apache/1.3.12 Server at
> ajuffer-dsl.oulu.fi Port 80
>
> 
>
> In fact, the apache error log file tells me:
>
> [Fri Jul 13 22:56:13 2001] [error] [client 127.0.0.1] Invalid URI in
> request GET /Biocomputing/users-database HTTP/1.1
>
> 
>
> The request
> http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database
> directly to tomcat4
> itself works perfectly all right, so no problem there.
>
> So, within Apache the URL Rewriting works ok, but it seems to me that
> not a new http request is carried out ("resetting the location header"
> as one can do with Javascript), The request remains within Apache.
>
> Cheers,
> Andre.
>
>
>
>
> Luca Morandini wrote:
>
> >> -Original Message-
> >> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> >> Sent: venerdì 13 luglio 2001 14.53
> >> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> >> Subject: RE: C1 to C2
> >>
> >> If you only pass xml files to C2, you'll loose the ability to
> >> construct dynamic pdf with the pdf extension and so on with .txt or
> >> .sh or .jpg, and so on...
> >>
> >
> > you may pass every URI you want to Cocoon, whathever the
> extension. Of
> > course, you will have to rely on the Apache rewrite engine to
> handle this
> > job (I mean: switching URI between Apache or Cocoon).
> > This URI switching task might be pretty tricky and,
> moreover, is bound to
> > put application logic outside the sitemap... which is unfortunate.
> >
> >
> >> In your configuration, what will you do if you got to serve static xml
> >> files (example: applet configuration)?
> >>
> >
> > I&#

Re: C1 to C2

2001-07-13 Thread Andre Juffer

Luca,

I have been playing with your suggestions. This is what I have added to 
httpd.conf as a test case:



RewriteEngine On
RewriteLog "/var/log/rewrite.log"
RewriteLogLevel 3
RewriteRule Biocomputing/(.*) 
http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/$1 [PT]



(The last two lines is actually one line in the file.)

After requesting http://ajuffer-dsl.oulu.fi/Biocomputing/users-database, 
the rewrite.log shows me this:



127.0.0.1 - - [13/Jul/2001:22:56:13 +0300] 
[ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) init rewrite 
engine with requested uri /Biocomputing/users-database
127.0.0.1 - - [13/Jul/2001:22:56:13 +0300] 
[ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (3) applying 
pattern 'Biocomputing/(.*)' to uri '/Biocomputing/users-database'
127.0.0.1 - - [13/Jul/2001:22:56:13 +0300] 
[ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) rewrite 
/Biocomputing/users-database -> 
http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database
127.0.0.1 - - [13/Jul/2001:22:56:13 +0300] 
[ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) implicitly 
forcing redirect (rc=302) with 
http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database
127.0.0.1 - - [13/Jul/2001:22:56:13 +0300] 
[ajuffer-dsl.oulu.fi/sid#80ad324][rid#80d15dc/initial] (2) forcing 
'http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database' to 
get passed through to next API URI-to-filename handler



(ajuffer-dsl.oulu.fi is the machine at home, behind firewall, and 
Biocomputing is an application we are working on, far from complete 
right now).

It seems to me that the request 
http://ajuffer-dsl.oulu.fi/Biocomputing/users-database is correctly 
rewritten as 
http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database.

Still, I get an error message:




Found The document has moved here.

Additionally, a 400 Bad Request error was encountered while trying to 
use an ErrorDocument to handle the request. Apache/1.3.12 Server at 
ajuffer-dsl.oulu.fi Port 80



In fact, the apache error log file tells me:

[Fri Jul 13 22:56:13 2001] [error] [client 127.0.0.1] Invalid URI in 
request GET /Biocomputing/users-database HTTP/1.1



The request 
http://ajuffer-dsl.oulu.fi:8080/cocoon/Biocomputing/users-database 
directly to tomcat4
itself works perfectly all right, so no problem there.

So, within Apache the URL Rewriting works ok, but it seems to me that 
not a new http request is carried out ("resetting the location header" 
as one can do with Javascript), The request remains within Apache.

Cheers,
Andre.




Luca Morandini wrote:

>> -Original Message-
>> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
>> Sent: venerdì 13 luglio 2001 14.53
>> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>> Subject: RE: C1 to C2
>> 
>> If you only pass xml files to C2, you'll loose the ability to
>> construct dynamic pdf with the pdf extension and so on with .txt or
>> .sh or .jpg, and so on...
>> 
> 
>   you may pass every URI you want to Cocoon, whathever the extension. Of
> course, you will have to rely on the Apache rewrite engine to handle this
> job (I mean: switching URI between Apache or Cocoon).
>   This URI switching task might be pretty tricky and, moreover, is bound to
> put application logic outside the sitemap... which is unfortunate.
> 
> 
>> In your configuration, what will you do if you got to serve static xml
>> files (example: applet configuration)?
>> 
> 
>   I'll tell Apache NOT to pass xml files contained in a subsite to Cocoon.
> For instance, every URI in www.foobar.com/foo/static won't be passed to
> Cocoon but served directly by Apache, while every URI in
>  www.foobar.com/foo/dynamic will be passed to Cocoon for further processing.
> 
> Best regards,
>  
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>   +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
> 
> 
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>


-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
 the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW: http://www.biochem.oulu.fi/research.html


-

RE: C1 to C2

2001-07-13 Thread Luca Morandini

> -Original Message-
> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 14.53
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: C1 to C2
>
> If you only pass xml files to C2, you'll loose the ability to
> construct dynamic pdf with the pdf extension and so on with .txt or
> .sh or .jpg, and so on...
>
you may pass every URI you want to Cocoon, whathever the extension. Of
course, you will have to rely on the Apache rewrite engine to handle this
job (I mean: switching URI between Apache or Cocoon).
This URI switching task might be pretty tricky and, moreover, is bound to
put application logic outside the sitemap... which is unfortunate.

> In your configuration, what will you do if you got to serve static xml
> files (example: applet configuration)?
>
I'll tell Apache NOT to pass xml files contained in a subsite to Cocoon.
For instance, every URI in www.foobar.com/foo/static won't be passed to
Cocoon but served directly by Apache, while every URI in
 www.foobar.com/foo/dynamic will be passed to Cocoon for further processing.

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-



-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-13 Thread Anders Lindh


Hmm. My guess is that you'd have to have matching patterns in the apache
configuration,
which isn't always possible and kinda sucks.

- Anders


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
Juffer
Sent: 13. heinakuuta 2001 15:28
To: [EMAIL PROTECTED]
Subject: Re: C1 to C2


Anders Lindh wrote:
>
> >Be aware that C2 will serve _all_ the pages (including the static
> >ones). If you are in an Apache+Tomcat+Cocoon context, this mean that
> >Everything on your site will be served by C2.
>
> If you use apache you tell it what requests to pass to Tomcat (with mod_jk
> or mod_jserv). You can e.g tell it to pass requests for all .xml files in
> /cocoon to Tomcat (and cocoon if configured properly). This way all static
> content can be served by apache (x100 faster) and all dynamic pages by
> tomcat/cocoon.


Yes, this is correct. This is the way I have done in the past
(apache-tomcat-cocoon1). But is this going to work only if one uses the
extension .xml., since Cocoon2 also uses patterns in its sitemap (e.g.
"welcome" instead of "welcome.xml")?



For tomcat-apache-cocoon1, the following is what I have in httpd.conf:

LoadModule jserv_module libexec/mod_jserv.so
ApJServManual on
ApJServDefaultProtocol ajpv12
ApJServSecretKey DISABLED
ApJServMountCopy on
ApJServLogLevel notice

ApJServDefaultHost localhost
ApJServDefaultPort 8007

ApJServMount default /root

AddType test/jsp .jsp
AddHandler jserv-servlet .jsp
AddType text/xml .xml
AddHandler jserv-servlet .xml

Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon


Options Indexes FollowSymLinks

ApJServMount /cocoon /cocoon
AddType text/xml .xml
AddHandler jserv-servlet .xml

AllowOverride None
deny from all


Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/Foo

Options Indexes FollowSymLinks

ApJServMount /Foo/servlet /Foo

AllowOverride None
deny from all




The server.xml in tomcat/conf in fact includes an entry for cocoon1 as
follows:




  org.apache.cocoon.Cocoon
  org.apache.cocoon.Cocoon
  
properties

  cocoon.properties

  




  org.apache.cocoon.Cocoon
  *.xml


>



Everything that has the extension .xml including those in /Foo
automatically is forwarded to cocoon1 and therefore served by cocoon1,
while the static files are served by the Apache webserver. This all
works very nicely.

It must be possible to do the same thing with cocoon2 somehow, but it
seems to me that these "patterns" could cause some problems.

Andre.



> - Anders
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>

--
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW:
http://www.biochem.oulu.fi/research.html

-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-13 Thread Luca Morandini


> -Original Message-
> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 14.53
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: C1 to C2
>
> If you only pass xml files to C2, you'll loose the ability to
> construct dynamic pdf with the pdf extension and so on with .txt or
> .sh or .jpg, and so on...
>
you may pass every URI you want to Cocoon, whathever the extension. Of
course, you will have to rely on the Apache rewrite engine to handle this
job (I mean: switching URI between Apache or Cocoon).
This URI switching task might be pretty tricky and, moreover, is bound to
put application logic outside the sitemap... which is unfortunate.

> In your configuration, what will you do if you got to serve static xml
> files (example: applet configuration)?
>
I'll tell Apache NOT to pass xml files contained in a subsite to Cocoon.
For instance, every URI in www.foobar.com/foo/static won't be passed to
Cocoon but served directly by Apache, while every URI in
 www.foobar.com/foo/dynamic will be passed to Cocoon for further processing.

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-



-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-13 Thread Arnaud Vandyck

On Fri, 13 Jul 2001 12:47:31 +0200, "Luca Morandini" <[EMAIL PROTECTED]> wrote:

> Arnaud,
> 
>   I don't  think that  C2 will serve  everything which is  passed to
> Apache if you  move it to ROOT. On the contrary,  it will serve only
> what Apache chooses to pass to Tomcat.
> 
>   For instance, you can choose to pass to Tomcat (and, subsequently,
> to Cocoon) only *.xml files or only what is in a specified URI (say,
> foo/bar/*).


On Fri, 13 Jul 2001 13:45:03 +0300, "Anders Lindh" <[EMAIL PROTECTED]> wrote:

>  If you use apache you tell it what requests to pass to Tomcat (with
> mod_jk or mod_jserv).  You can e.g tell it to  pass requests for all
> .xml  files   in  /cocoon  to  Tomcat  (and   cocoon  if  configured
> properly). This way all static content can be served by apache (x100
> faster) and all dynamic pages by tomcat/cocoon.

Well I understand but in the early years of C2, one important thing
was that the sitemap may "organize" the site cleanner...

If you only pass xml files to C2, you'll loose the ability to
construct dynamic pdf with the pdf extension and so on with .txt or
.sh or .jpg, and so on...

One or two month ago, I posted something I did with C2:
- one xml file with the user's datas;
- one xslt file to transform the user's datas into bash code to create
  linux user's;
- one xslt file to transform the user's datas into sql code to insert
  them into postgres;
- ont xslt file to render the user's datas in html.

So, you apply the file with the proper extension and C2 do the job!

If I want to do that, I have to mount C2 on an other webapp than the
ROOT one and pass * to /cocoon/ (on my system, /www/ ;))

Apache only serves /servlet and *.jps to ROOT.

In your configuration, what will you do if you got to serve static xml
files (example: applet configuration)?

I think the best way to use C2 is to give it a proper context or a
proper VirtualHost (if you can change your dns settings, I can not)...

--Arnaud

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: C1 to C2

2001-07-13 Thread Andre Juffer

Anders Lindh wrote:
> 
> >Be aware that C2 will serve _all_ the pages (including the static
> >ones). If you are in an Apache+Tomcat+Cocoon context, this mean that
> >Everything on your site will be served by C2.
> 
> If you use apache you tell it what requests to pass to Tomcat (with mod_jk
> or mod_jserv). You can e.g tell it to pass requests for all .xml files in
> /cocoon to Tomcat (and cocoon if configured properly). This way all static
> content can be served by apache (x100 faster) and all dynamic pages by
> tomcat/cocoon.


Yes, this is correct. This is the way I have done in the past
(apache-tomcat-cocoon1). But is this going to work only if one uses the
extension .xml., since Cocoon2 also uses patterns in its sitemap (e.g.
"welcome" instead of "welcome.xml")?



For tomcat-apache-cocoon1, the following is what I have in httpd.conf:

LoadModule jserv_module libexec/mod_jserv.so
ApJServManual on
ApJServDefaultProtocol ajpv12
ApJServSecretKey DISABLED
ApJServMountCopy on
ApJServLogLevel notice
 
ApJServDefaultHost localhost
ApJServDefaultPort 8007
 
ApJServMount default /root
 
AddType test/jsp .jsp
AddHandler jserv-servlet .jsp
AddType text/xml .xml
AddHandler jserv-servlet .xml
 
Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon
 

Options Indexes FollowSymLinks

ApJServMount /cocoon /cocoon
AddType text/xml .xml
AddHandler jserv-servlet .xml

AllowOverride None
deny from all


Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/Foo

Options Indexes FollowSymLinks

ApJServMount /Foo/servlet /Foo

AllowOverride None
deny from all




The server.xml in tomcat/conf in fact includes an entry for cocoon1 as
follows:


 

  org.apache.cocoon.Cocoon
  org.apache.cocoon.Cocoon
  
properties

  cocoon.properties

  

 
 

  org.apache.cocoon.Cocoon
  *.xml

 
> 



Everything that has the extension .xml including those in /Foo
automatically is forwarded to cocoon1 and therefore served by cocoon1,
while the static files are served by the Apache webserver. This all
works very nicely.

It must be possible to do the same thing with cocoon2 somehow, but it
seems to me that these "patterns" could cause some problems.

Andre.



> - Anders
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. 
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>

-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW:
http://www.biochem.oulu.fi/research.html

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: C1 to C2

2001-07-13 Thread Luca Morandini

Arnaud,

I don't think that C2 will serve everything which is passed to Apache if
you move it to ROOT. On the contrary, it will serve only what Apache chooses
to pass to Tomcat.
For instance, you can choose to pass to Tomcat (and, subsequently, to
Cocoon) only *.xml files or only what is in a specified URI (say,
foo/bar/*).

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 11.15
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> Le Thu, 12 Jul 2001 21:49:19 -0600, Lajos Moczar
> <[EMAIL PROTECTED]> écrivait:
>
> lmocz> If I understand you correctly, all you have to do is
> rename cocoon.war
> lmocz> to ROOT.war - this will eliminate the need for the
> "cocoon/" after your
> lmocz> hostname, since the ROOT webapp equates to "/". Dont'
> forget to copy all
> lmocz> your own stuff from $TOMCAT_HOME/webapps/cocoon to
> lmocz> $TOMCAT_HOME/webapps/ROOT.
>
> Be aware that C2 will serve _all_ the pages (including the static
> ones). If you are in an Apache+Tomcat+Cocoon context, this mean that
> Everything on your site will be served by C2.
>
> Am I Wrong?
>
> Well I didn't find a way to do it! So, no php, no cgi and no other
> webapps (Apache+Tomcat+Cocoon)! If someone know how to avoid
> this, I'll be glad to know ;)
>
> --Arnaud
>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-13 Thread Anders Lindh

>Be aware that C2 will serve _all_ the pages (including the static
>ones). If you are in an Apache+Tomcat+Cocoon context, this mean that
>Everything on your site will be served by C2.

If you use apache you tell it what requests to pass to Tomcat (with mod_jk
or mod_jserv). You can e.g tell it to pass requests for all .xml files in
/cocoon to Tomcat (and cocoon if configured properly). This way all static
content can be served by apache (x100 faster) and all dynamic pages by
tomcat/cocoon.

- Anders


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: C1 to C2

2001-07-13 Thread Arnaud Vandyck

Le Thu, 12 Jul 2001 21:49:19 -0600, Lajos Moczar <[EMAIL PROTECTED]> écrivait:

lmocz> If I understand you correctly, all you have to do is rename cocoon.war 
lmocz> to ROOT.war - this will eliminate the need for the "cocoon/" after your 
lmocz> hostname, since the ROOT webapp equates to "/". Dont' forget to copy all 
lmocz> your own stuff from $TOMCAT_HOME/webapps/cocoon to 
lmocz> $TOMCAT_HOME/webapps/ROOT.

Be aware that C2 will serve _all_ the pages (including the static
ones). If you are in an Apache+Tomcat+Cocoon context, this mean that
Everything on your site will be served by C2.

Am I Wrong?

Well I didn't find a way to do it! So, no php, no cgi and no other
webapps (Apache+Tomcat+Cocoon)! If someone know how to avoid this, I'll be glad to 
know ;)

--Arnaud



RE: C1 to C2

2001-07-13 Thread Luca Morandini

> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: giovedì 12 luglio 2001 19.43
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
> So, apparently it is not possible to have something like
> mydomain.com/Foo/foo, and one must always use something like
> mydomain.com/cocoon/Foo/foo, if I understood you correctly. That is too
> bad, since it was certainly possible with cocoon1. There must (should)
> be a way around it.

Andre,

I apologize for not being clear, but I stated exactly the opposite.

If you use, as I did, the rewrite engine of Apache, you can redirect URIs
from, say, mydomain.com/Foo/foo to mydomain.com/cocoon/Foo/foo.

I can't tell you whether this works for other Web-servers as well; but I'm
inclined to think every decent Web-server has a way of dealing with URI
rewriting.


> -Original Message-
> From: Lajos Moczar [mailto:[EMAIL PROTECTED]]
> Sent: venerdì 13 luglio 2001 5.49
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
> If I understand you correctly, all you have to do is rename cocoon.war
> to ROOT.war - this will eliminate the need for the "cocoon/" after your
> hostname, since the ROOT webapp equates to "/". Dont' forget to copy all
> your own stuff from $TOMCAT_HOME/webapps/cocoon to
> $TOMCAT_HOME/webapps/ROOT.
>
Lajos,

the thing you suggested may work too, but I still think that URI rewriting
is prefereable: it's more flexible and easier to implement.

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: giovedì 12 luglio 2001 19.43
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
>
>
> Luca Morandini wrote:
>
> >> -Original Message-
> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Andre
> >> Juffer
> >> Sent: giovedì 12 luglio 2001 15.11
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: C1 to C2
> >>
> >>
> >> Luca Morandini wrote:
> >>
> >>>> -Original Message-
> >>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> >>>
> >> Behalf Of Andre
> >>
> >>>> Juffer
> >>>> Sent: giovedì 12 luglio 2001 13.35
> >>>> To: [EMAIL PROTECTED]
> >>>> Subject: Re: C1 to C2
> >>>>
> >>>
> >>> Hmmm... why you would like to start a different context ?
> >>> I assumed you wanted just to put you application in a
> >>
> >> directory other than
> >>
> >>> \webapps\cocoon... am I wrong ?
> >>
> >>
> >> You are entirely correct. That is exactly what I have in mind. I should
> >> say that all static html (normally in public_html in user's
> >> subdirectories, as is common under Unix) are still served directly by
> >> the Apache webserver. Nothing of that is going through cocoon. Under
> >> cocoon1, one uses tomcat where files with the extension .xml where
> >> served by tomcat and ultimately by cocoon1. I was under the impression
> >> that things with cocoon2 were done in a similar way, but maybe
> >> everything should be served by cocoon2 first (including these html
> >> files) and the sitemap would than start the appropriate
> pipelines? (That
> >> would explain the word sitemap). So, cocoon2 would control the complete
> >> website (both static and dynamic files). Is the Apache
> webserver in fact
> >> still required to run on the server?
> >>
> >
> >
> > No, you could dispense with Apache and run everything on
> Tomcat, though it
> > seems an overkill to me (and less stable, too).
> >
> > Talking about C2, there is no need to start another Cocoon
> context, far
> > from it... you should just tell Cocoon to find your files where
> they are.
> > The mechanism to do that is to modify the sitemap (the one
> I've named
> > "general sitemap" in my previous message) in order to mount the
> sub-sitemap
> > correctly.
> >
> > The odd thihg about this is that you may find your site
> only by referring
> > to an URI with "cocoon" in it, like <...>\cocoon\cru\index.xml.
> >
> > Next step i

Re: C1 to C2

2001-07-12 Thread Lajos Moczar

If I understand you correctly, all you have to do is rename cocoon.war 
to ROOT.war - this will eliminate the need for the "cocoon/" after your 
hostname, since the ROOT webapp equates to "/". Dont' forget to copy all 
your own stuff from $TOMCAT_HOME/webapps/cocoon to 
$TOMCAT_HOME/webapps/ROOT.


Lajos Moczar
galatea.com

Andre Juffer wrote:

> 
> 
> Luca Morandini wrote:
> 
>>> -Original Message-
>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
>>> Juffer
>>> Sent: giovedì 12 luglio 2001 15.11
>>> To: [EMAIL PROTECTED]
>>> Subject: Re: C1 to C2
>>> 
>>> 
>>> Luca Morandini wrote:
>>> 
>>>>> -Original Message-
>>>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>>>> 
>>>> 
>>> Behalf Of Andre
>>> 
>>>>> Juffer
>>>>> Sent: giovedì 12 luglio 2001 13.35
>>>>> To: [EMAIL PROTECTED]
>>>>> Subject: Re: C1 to C2
>>>>> 
>>>> 
>>>> Hmmm... why you would like to start a different context ?
>>>> I assumed you wanted just to put you application in a
>>> 
>>> 
>>> directory other than
>>> 
>>>> \webapps\cocoon... am I wrong ?
>>> 
>>> 
>>> 
>>> You are entirely correct. That is exactly what I have in mind. I should
>>> say that all static html (normally in public_html in user's
>>> subdirectories, as is common under Unix) are still served directly by
>>> the Apache webserver. Nothing of that is going through cocoon. Under
>>> cocoon1, one uses tomcat where files with the extension .xml where
>>> served by tomcat and ultimately by cocoon1. I was under the impression
>>> that things with cocoon2 were done in a similar way, but maybe
>>> everything should be served by cocoon2 first (including these html
>>> files) and the sitemap would than start the appropriate pipelines? (That
>>> would explain the word sitemap). So, cocoon2 would control the complete
>>> website (both static and dynamic files). Is the Apache webserver in fact
>>> still required to run on the server?
>>> 
>> 
>> 
>> No, you could dispense with Apache and run everything on Tomcat, 
>> though it
>> seems an overkill to me (and less stable, too).
>> 
>> Talking about C2, there is no need to start another Cocoon 
>> context, far
>> from it... you should just tell Cocoon to find your files where they are.
>> The mechanism to do that is to modify the sitemap (the one I've named
>> "general sitemap" in my previous message) in order to mount the 
>> sub-sitemap
>> correctly.
>> 
>> The odd thihg about this is that you may find your site only by 
>> referring
>> to an URI with "cocoon" in it, like <...>\cocoon\cru\index.xml.
>> 
>> Next step is to tell Apache to redirect everything from "cru" to
>> "coocon\cru" (provided, of course, "cru" is the name of you application);
>> I've used the rewrite engine of Apache, adding the following to 
>> httpd.conf:
>> 
>> RewriteEngine On
>> RewriteLog "C:/apps/apache/logs/rewrite.log"
>> RewriteLogLevel 0
>> RewriteRule cru/(.*) /cocoon/cru/$1 [PT]
>> 
>> It works, but it took me half a day to figure it out the whole 
>> process :(
> 
> 
> 
> 
> So, apparently it is not possible to have something like 
> mydomain.com/Foo/foo, and one must always use something like 
> mydomain.com/cocoon/Foo/foo, if I understood you correctly. That is too 
> bad, since it was certainly possible with cocoon1. There must (should) 
> be a way around it.
> 
> 
> Andre
> 
>> 
>> Best regards,
>>  
>> -
>>Luca Morandini
>>GIS Consultant
>> [EMAIL PROTECTED]
>>   +39 0744 59  85  1 Office
>>   +39 0335 681 02 12 Mobile
>> http://utenti.tripod.it/lmorandini/index.html
>> -
>> 
>> 
>> 
>> 
>> -
>> Please check that your question has not already been answered in the
>> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>> 
>> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>> For additional commands, e-mail: <[EMAIL PROTECTED]>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Re: C1 to C2

2001-07-12 Thread Andre Juffer



Luca Morandini wrote:

>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
>> Juffer
>> Sent: giovedì 12 luglio 2001 15.11
>> To: [EMAIL PROTECTED]
>> Subject: Re: C1 to C2
>> 
>> 
>> Luca Morandini wrote:
>> 
>>>> -Original Message-
>>>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>>> 
>> Behalf Of Andre
>> 
>>>> Juffer
>>>> Sent: giovedì 12 luglio 2001 13.35
>>>> To: [EMAIL PROTECTED]
>>>> Subject: Re: C1 to C2
>>>> 
>>> 
>>> Hmmm... why you would like to start a different context ?
>>> I assumed you wanted just to put you application in a
>> 
>> directory other than
>> 
>>> \webapps\cocoon... am I wrong ?
>> 
>> 
>> You are entirely correct. That is exactly what I have in mind. I should
>> say that all static html (normally in public_html in user's
>> subdirectories, as is common under Unix) are still served directly by
>> the Apache webserver. Nothing of that is going through cocoon. Under
>> cocoon1, one uses tomcat where files with the extension .xml where
>> served by tomcat and ultimately by cocoon1. I was under the impression
>> that things with cocoon2 were done in a similar way, but maybe
>> everything should be served by cocoon2 first (including these html
>> files) and the sitemap would than start the appropriate pipelines? (That
>> would explain the word sitemap). So, cocoon2 would control the complete
>> website (both static and dynamic files). Is the Apache webserver in fact
>> still required to run on the server?
>> 
> 
> 
>   No, you could dispense with Apache and run everything on Tomcat, though it
> seems an overkill to me (and less stable, too).
> 
>   Talking about C2, there is no need to start another Cocoon context, far
> from it... you should just tell Cocoon to find your files where they are.
>   The mechanism to do that is to modify the sitemap (the one I've named
> "general sitemap" in my previous message) in order to mount the sub-sitemap
> correctly.
> 
>   The odd thihg about this is that you may find your site only by referring
> to an URI with "cocoon" in it, like <...>\cocoon\cru\index.xml.
> 
>   Next step is to tell Apache to redirect everything from "cru" to
> "coocon\cru" (provided, of course, "cru" is the name of you application);
> I've used the rewrite engine of Apache, adding the following to httpd.conf:
> 
> RewriteEngine On
> RewriteLog "C:/apps/apache/logs/rewrite.log"
> RewriteLogLevel 0
> RewriteRule cru/(.*) /cocoon/cru/$1 [PT]
> 
>   It works, but it took me half a day to figure it out the whole process :(



So, apparently it is not possible to have something like 
mydomain.com/Foo/foo, and one must always use something like 
mydomain.com/cocoon/Foo/foo, if I understood you correctly. That is too 
bad, since it was certainly possible with cocoon1. There must (should) 
be a way around it.


Andre

> 
> Best regards,
>  
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>   +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
> 
> 
> 
> 
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> 
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>


-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
 the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW: http://www.biochem.oulu.fi/research.html


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-12 Thread Luca Morandini

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
> Juffer
> Sent: giovedì 12 luglio 2001 15.11
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>
>
> Luca Morandini wrote:
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Andre
> > > Juffer
> > > Sent: giovedì 12 luglio 2001 13.35
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: C1 to C2
> > >
> >
> > Hmmm... why you would like to start a different context ?
> > I assumed you wanted just to put you application in a
> directory other than
> > \webapps\cocoon... am I wrong ?
>
>
> You are entirely correct. That is exactly what I have in mind. I should
> say that all static html (normally in public_html in user's
> subdirectories, as is common under Unix) are still served directly by
> the Apache webserver. Nothing of that is going through cocoon. Under
> cocoon1, one uses tomcat where files with the extension .xml where
> served by tomcat and ultimately by cocoon1. I was under the impression
> that things with cocoon2 were done in a similar way, but maybe
> everything should be served by cocoon2 first (including these html
> files) and the sitemap would than start the appropriate pipelines? (That
> would explain the word sitemap). So, cocoon2 would control the complete
> website (both static and dynamic files). Is the Apache webserver in fact
> still required to run on the server?
>

No, you could dispense with Apache and run everything on Tomcat, though it
seems an overkill to me (and less stable, too).

Talking about C2, there is no need to start another Cocoon context, far
from it... you should just tell Cocoon to find your files where they are.
The mechanism to do that is to modify the sitemap (the one I've named
"general sitemap" in my previous message) in order to mount the sub-sitemap
correctly.

The odd thihg about this is that you may find your site only by referring
to an URI with "cocoon" in it, like <...>\cocoon\cru\index.xml.

Next step is to tell Apache to redirect everything from "cru" to
"coocon\cru" (provided, of course, "cru" is the name of you application);
I've used the rewrite engine of Apache, adding the following to httpd.conf:

RewriteEngine On
RewriteLog "C:/apps/apache/logs/rewrite.log"
RewriteLogLevel 0
RewriteRule cru/(.*) /cocoon/cru/$1 [PT]

It works, but it took me half a day to figure it out the whole process :(

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-




-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: C1 to C2

2001-07-12 Thread Luca Morandini

> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Andre
> Juffer
> Sent: giovedì 12 luglio 2001 13.35
> To: [EMAIL PROTECTED]
> Subject: Re: C1 to C2
>

> Let me see if I understand you correctly. The GENERAL sitemap is the
> sitemap located in the cocoon subdirectory (webapps/cocoon) <..> ?

Yes, I added "general" to be sure you didn't mistake it with sub-sitemap.

> The idea of a sub-sitemap below is clear to me. Still, the request
> localhost/Foo/foo goes through the Apache webserver, which passes it on
> to Tomcat. But Tomcat will try to read webapps/Foo and not
> webapps/cocoon, because the configuration of Tomcat was set up like
> that.  Should I possibly include in the configuration file of tomcat
> something like
>
> ---
>
> Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon
>
>
> so that /Foo would correspond to /cocoon as well? In combination with
> the sub-sitemap as you suggested, the correct pipeline would start.
>
> Is the above correct?


Hmmm... why you would like to start a different context ?
I assumed you wanted just to put you application in a directory other than
\webapps\cocoon... am I wrong ?

Best regards,
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-



-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




Re: C1 to C2

2001-07-12 Thread Andre Juffer

Hi Luca,

thank you for your response.

Let me see if I understand you correctly. The GENERAL sitemap is the
sitemap located in the cocoon subdirectory (webapps/cocoon), or are you
referring to another sitemap?

The idea of a sub-sitemap below is clear to me. Still, the request
localhost/Foo/foo goes through the Apache webserver, which passes it on
to Tomcat. But Tomcat will try to read webapps/Foo and not
webapps/cocoon, because the configuration of Tomcat was set up like
that.  Should I possibly include in the configuration file of tomcat
something like

--- 

Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon

---

so that /Foo would correspond to /cocoon as well? In combination with
the sub-sitemap as you suggested, the correct pipeline would start.

Is the above correct?


Thanks you again,
Andre.



Luca Morandini wrote:
> 
> Andre,
> 
> have you modifed the general sitemap to tell Cocoon you're not under the
> cocoon  context ?
> 
> For instance, when I wanted a sub-sitemap of mine to be relocated to the
> c:\cru directory, I modified the general sitemap as follows:
> 
> 
> 
>  check-reload="yes"
> reload-method="synchron"/>
> 
> 
> 
> I hope this helps...
> 
> -
>Luca Morandini
>GIS Consultant
> [EMAIL PROTECTED]
>   +39 0744 59  85  1 Office
>   +39 0335 681 02 12 Mobile
> http://utenti.tripod.it/lmorandini/index.html
> -
> 
> > -Original Message-
> > From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> > Sent: mercoledì 11 luglio 2001 21.19
> > To: [EMAIL PROTECTED]
> > Subject: C1 to C2
> >
> >
> > Hi,
> >
> > just recently I have posted a question about having cocoon2 recognizing
> > my own context under tomcat/webapp. This may be a tomcat problem, still
> > I had cocoon1.8.2, together with the apache web server and tomcat,
> > working just fine with my own context. Obviously, I would like to be
> > able to do the same with cocoon2, but I could not get it going.
> >
> > I have removed everything that had something to do with cocoon1 and got
> > cocoon2 installed. No problem, I could read cocoon/welcome and try some
> > of the examples. I did not make any modifications in the existing
> > configuration files. So, I continued and made a very simple sitemap in
> > webapps/cocoon that simply transforms foo.xml into some html. Worked
> > without problem in webapps/cocoon, but, after transferring the relevant
> > files to webapps/Foo and restarting tomcat and apache, I got error
> > messages. If I request localhost/Foo, the content of my context is
> > displayed, but it fails to start the pipeline associated with the
> > transformation (localhost/Foo/foo). I get the following error:
> >
> > 
> > type resource-not-found
> >
> > message Resource not found
> >
> > description The requested URI "/Foo/foo" was not found.
> >
> > sender org.apache.cocoon.servlet.CocoonServlet
> >
> > source Cocoon servlet
> >
> > request-uri
> >
> > /Foo/foo
> >
> > path-info
> >
> > foo
> >
> > 
> >
> > foo is the pattern that should start the pipeline. This works perfectly
> > all right when carried out in the cocoon context
> > (http://localhost/cocoon/foo). So, it must be a context setup problem.
> >
> > It seems that tomcat properly sees my context:
> >
> > 
> >
> > 2001-07-11 07:50:34 - ContextManager: Adding context Ctx( /Foo )
> >
> > 
> >
> > Is there anything special that I may need to do so that
> > tomcat/apache/cocoon2 work nicely together?
> >
> > This is the content of a configuation file that is included into the
> > apache httpd.conf file (the same I have used before with cocoon1):
> >
> > 
> >
> > LoadModule jserv_module libexec/mod_jserv.so
> > ApJServManual on
> > ApJServDefaultProtocol ajpv12
> > ApJServSecretKey DISABLED
> > ApJServMountCopy on
> > ApJServLogLevel notice
> >
> > ApJServDefaultHost localhost
> > ApJServDefaultPort 8007
> >
> > AddType test/jsp .jsp
> > AddHandler jserv-servlet .jsp
> > AddType text/xml .xml
> > AddHandler jserv-servlet .xml
> >
> > Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon
> > 
> >  Options In

RE: C1 to C2

2001-07-11 Thread Luca Morandini

Andre,

have you modifed the general sitemap to tell Cocoon you're not under the
cocoon  context ?

For instance, when I wanted a sub-sitemap of mine to be relocated to the
c:\cru directory, I modified the general sitemap as follows:







I hope this helps...
 
-
   Luca Morandini
   GIS Consultant
    [EMAIL PROTECTED]
  +39 0744 59  85  1 Office
  +39 0335 681 02 12 Mobile
http://utenti.tripod.it/lmorandini/index.html
-


> -Original Message-
> From: Andre Juffer [mailto:[EMAIL PROTECTED]]
> Sent: mercoledì 11 luglio 2001 21.19
> To: [EMAIL PROTECTED]
> Subject: C1 to C2
>
>
> Hi,
>
> just recently I have posted a question about having cocoon2 recognizing
> my own context under tomcat/webapp. This may be a tomcat problem, still
> I had cocoon1.8.2, together with the apache web server and tomcat,
> working just fine with my own context. Obviously, I would like to be
> able to do the same with cocoon2, but I could not get it going.
>
> I have removed everything that had something to do with cocoon1 and got
> cocoon2 installed. No problem, I could read cocoon/welcome and try some
> of the examples. I did not make any modifications in the existing
> configuration files. So, I continued and made a very simple sitemap in
> webapps/cocoon that simply transforms foo.xml into some html. Worked
> without problem in webapps/cocoon, but, after transferring the relevant
> files to webapps/Foo and restarting tomcat and apache, I got error
> messages. If I request localhost/Foo, the content of my context is
> displayed, but it fails to start the pipeline associated with the
> transformation (localhost/Foo/foo). I get the following error:
>
> 
> type resource-not-found
>
> message Resource not found
>
> description The requested URI "/Foo/foo" was not found.
>
> sender org.apache.cocoon.servlet.CocoonServlet
>
> source Cocoon servlet
>
> request-uri
>
> /Foo/foo
>
> path-info
>
> foo
>
> 
>
> foo is the pattern that should start the pipeline. This works perfectly
> all right when carried out in the cocoon context
> (http://localhost/cocoon/foo). So, it must be a context setup problem.
>
> It seems that tomcat properly sees my context:
>
> 
>
> 2001-07-11 07:50:34 - ContextManager: Adding context Ctx( /Foo )
>
> 
>
> Is there anything special that I may need to do so that
> tomcat/apache/cocoon2 work nicely together?
>
> This is the content of a configuation file that is included into the
> apache httpd.conf file (the same I have used before with cocoon1):
>
> 
>
> LoadModule jserv_module libexec/mod_jserv.so
> ApJServManual on
> ApJServDefaultProtocol ajpv12
> ApJServSecretKey DISABLED
> ApJServMountCopy on
> ApJServLogLevel notice
>
> ApJServDefaultHost localhost
> ApJServDefaultPort 8007
>
> AddType test/jsp .jsp
> AddHandler jserv-servlet .jsp
> AddType text/xml .xml
> AddHandler jserv-servlet .xml
>
> Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon
> 
>  Options Indexes FollowSymLinks
> 
> ApJServMount /cocoon /cocoon
> 
>  AllowOverride None
>  deny from all
> 
>
> Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/Foo
> 
>  Options Indexes FollowSymLinks
> 
> ApJServMount /Foo /Foo
> 
>  AllowOverride None
>  deny from all
> 
>
> 
>
>
> Thank you for any suggestion you may have to resolve this matter,
>
> --
> Andre H. Juffer  | Phone: +358-8-553 1683
> The Biocenter and| Fax: +358-8-553-1141
>  the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
> University of Oulu, Finland  | WWW:
> http://www.biochem.oulu.fi/tutkimus/Biocomputing/
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




C1 to C2

2001-07-11 Thread Andre Juffer

Hi,

just recently I have posted a question about having cocoon2 recognizing 
my own context under tomcat/webapp. This may be a tomcat problem, still 
I had cocoon1.8.2, together with the apache web server and tomcat, 
working just fine with my own context. Obviously, I would like to be 
able to do the same with cocoon2, but I could not get it going.

I have removed everything that had something to do with cocoon1 and got 
cocoon2 installed. No problem, I could read cocoon/welcome and try some 
of the examples. I did not make any modifications in the existing 
configuration files. So, I continued and made a very simple sitemap in 
webapps/cocoon that simply transforms foo.xml into some html. Worked 
without problem in webapps/cocoon, but, after transferring the relevant 
files to webapps/Foo and restarting tomcat and apache, I got error 
messages. If I request localhost/Foo, the content of my context is 
displayed, but it fails to start the pipeline associated with the 
transformation (localhost/Foo/foo). I get the following error:


type resource-not-found

message Resource not found

description The requested URI "/Foo/foo" was not found.

sender org.apache.cocoon.servlet.CocoonServlet

source Cocoon servlet

request-uri

/Foo/foo

path-info

foo



foo is the pattern that should start the pipeline. This works perfectly 
all right when carried out in the cocoon context 
(http://localhost/cocoon/foo). So, it must be a context setup problem.

It seems that tomcat properly sees my context:



2001-07-11 07:50:34 - ContextManager: Adding context Ctx( /Foo )



Is there anything special that I may need to do so that 
tomcat/apache/cocoon2 work nicely together?

This is the content of a configuation file that is included into the 
apache httpd.conf file (the same I have used before with cocoon1):



LoadModule jserv_module libexec/mod_jserv.so
ApJServManual on
ApJServDefaultProtocol ajpv12
ApJServSecretKey DISABLED
ApJServMountCopy on
ApJServLogLevel notice

ApJServDefaultHost localhost
ApJServDefaultPort 8007

AddType test/jsp .jsp
AddHandler jserv-servlet .jsp
AddType text/xml .xml
AddHandler jserv-servlet .xml

Alias /cocoon /usr/local/jakarta-tomcat-3.2.1/webapps/cocoon

 Options Indexes FollowSymLinks

ApJServMount /cocoon /cocoon

 AllowOverride None
 deny from all


Alias /Foo /usr/local/jakarta-tomcat-3.2.1/webapps/Foo

 Options Indexes FollowSymLinks

ApJServMount /Foo /Foo

 AllowOverride None
 deny from all





Thank you for any suggestion you may have to resolve this matter,

-- 
Andre H. Juffer  | Phone: +358-8-553 1683
The Biocenter and| Fax: +358-8-553-1141
 the Dep. of Biochemistry | Email: [EMAIL PROTECTED]
University of Oulu, Finland  | WWW: 
http://www.biochem.oulu.fi/tutkimus/Biocomputing/


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




Re: [C1 to C2] Big difference in XSP !! Why ?

2001-06-10 Thread Samuel ARNOD-PRIN

I have also discovered a big bug then :

suppose you want to use this :



..


String selected = (true) ? "yes" : "";


selected
ValueX



..



Well...  is unfortunately equivalent in html to
 and 

...


I have then to write this piece of code like this :




String selected = (true) ? "yes" : "";

if (selected.equals("")) {
hh
} else {
hh
}




it is not very elegant...

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




[C1 to C2] Big difference in XSP !! Why ?

2001-06-10 Thread Samuel ARNOD-PRIN

Hello,

Using C2 attributes are evaluated before the tags.

That's why :



if (true) {



} else {
String toto = "hello";


toto

}

My tage body...


... works well with C1... but with C2... mytag has no attributes !!! For
the attribute 'att2.. it does not compile with C2 because toto is not
yet defined ... ;o(

Is it a bug in C2 (the xsp parser)... ??? Or should I have never used it
at all ?


If it could work, it would make my xsp files cleaner !!

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: upgrade my beans from c1 to c2

2001-06-05 Thread Ramesh Vejendla

Hi ALL
  Here i'm trying to return record set object from java class.
but i'm facing this problem how do i solve this .plz any one can help me
out.

"java.lang.StackOverflowError"

thanks.






***Confidential Notice

This e-mail communication may contain information that is
confidential and privileged. The information is intended
to be for the use of the addressee only. If you are not the
named addressee you should not disseminate, distribute or
copy this e-mail: to do so could be a breach of confidence.

Kshema Technologies Ltd.,
# 33/1, Lalbagh Road, Bangalore 560027, INDIA. 
Tel: (91) 80- 2995114/5/6
Fax: (91) 80 2272933 

**

-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: upgrade my beans from c1 to c2

2001-06-01 Thread Antonio Parolini

> I'm not that familiar with C1 but I think you have to use bridge uility
> methods to convert your Nodes into SAX events. Have a look at the class
> org.apache.cocoon.xml.dom.DOMStreamer.

But I fear a performance problem doing so...

If I upgrade my objects ot return a sax event like ContentHandler instead of
a DOM Node, is this going to work in Cocoon2 ?

thanks,

- tony

> > So is the org.w3c.dom.Node Interface still supported in Cocoon
> 2 as a bean
> > return value ?


-
Please check that your question has not already been answered in the
FAQ before posting. 

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




RE: upgrade my beans from c1 to c2

2001-05-31 Thread giacomo

On Wed, 30 May 2001, Antonio Parolini wrote:

> Sorry if this was a stupid question... but i'll be gald if someone could
> help me out on this, even if it's to tell me to read de faq.
> :)

I'm not that familiar with C1 but I think you have to use bridge uility
methods to convert your Nodes into SAX events. Have a look at the class
org.apache.cocoon.xml.dom.DOMStreamer.

Giacomo

>
> So is the org.w3c.dom.Node Interface still supported in Cocoon 2 as a bean
> return value ?
>
> - Tony
>
> > -Original Message-
> > From: Antonio Parolini [mailto:[EMAIL PROTECTED]]
> > Sent: segunda-feira, 28 de maio de 2001 12:51
> > To: [EMAIL PROTECTED]
> > Subject: upgrade my beans from c1 to c2
> >
> >
> > Hi there,
> >
> > In Cocoon 1.8.x, my application use beans that return a DOM Node Object.
> >  public Node foo(){..};) and I call them from my XSP page like
> > mybean.foo()
> >
> > Now I would like to upgrade this for Cocoon 2, but I'm not sure whether
> > Cocoon2 will support this Node interface, since I'm avare that it uses the
> > Sax document model.
> >
> > Do I need to create a new class that supports the XML Frament
> > interface for
> > this and  return it insteed of Dom nodes ?
> >
> > thanks,
> >
> > - tony
> >
> >
> >
> >
> >
> > -
> > Please check that your question has not already been answered in the
> > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
> >
> > To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> > For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
>
>
>
>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




RE: upgrade my beans from c1 to c2

2001-05-30 Thread Antonio Parolini

Sorry if this was a stupid question... but i'll be gald if someone could
help me out on this, even if it's to tell me to read de faq.
:)

So is the org.w3c.dom.Node Interface still supported in Cocoon 2 as a bean
return value ?

- Tony

> -Original Message-
> From: Antonio Parolini [mailto:[EMAIL PROTECTED]]
> Sent: segunda-feira, 28 de maio de 2001 12:51
> To: [EMAIL PROTECTED]
> Subject: upgrade my beans from c1 to c2
>
>
> Hi there,
>
> In Cocoon 1.8.x, my application use beans that return a DOM Node Object.
>  public Node foo(){..};) and I call them from my XSP page like
> mybean.foo()
>
> Now I would like to upgrade this for Cocoon 2, but I'm not sure whether
> Cocoon2 will support this Node interface, since I'm avare that it uses the
> Sax document model.
>
> Do I need to create a new class that supports the XML Frament
> interface for
> this and  return it insteed of Dom nodes ?
>
> thanks,
>
> - tony
>
>
>
>
>
> -
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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




upgrade my beans from c1 to c2

2001-05-28 Thread Antonio Parolini

Hi there,

In Cocoon 1.8.x, my application use beans that return a DOM Node Object.
 public Node foo(){..};) and I call them from my XSP page like
mybean.foo()

Now I would like to upgrade this for Cocoon 2, but I'm not sure whether
Cocoon2 will support this Node interface, since I'm avare that it uses the
Sax document model.

Do I need to create a new class that supports the XML Frament interface for
this and  return it insteed of Dom nodes ?

thanks,

- tony





-
Please check that your question has not already been answered in the
FAQ before posting. 

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