Return-Path: 
 <cocoon-users-return-43383-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 56058 invoked by uid 500); 3 Dec 2002 17:57:04 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 56045 invoked from network); 3 Dec 2002 17:57:04 -0000
Date: Tue, 3 Dec 2002 18:57:05 +0100
Subject: Re: Complicated setup
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v548)
From: leo leonid <tek@leonid.de>
To: cocoon-users@xml.apache.org
Content-Transfer-Encoding: 7bit
In-Reply-To: <9CCF89C4-06DF-11D7-9455-0003935AD2EE@media.demon.co.uk>
Message-Id: <A24564C6-06E8-11D7-8E38-003065A89D34@leonid.de>
X-Mailer: Apple Mail (2.548)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


On Tuesday, December 3, 2002, at 05:52 PM, Jeremy Quinn wrote:

>
> On Tuesday, Dec 3, 2002, at 15:31 Europe/London, leo leonid wrote:
>
>>
>> On Tuesday, December 3, 2002, at 03:34 PM, Jeremy Quinn wrote:
>>
>>> Hi All
>>>
>>> Can anyone advise me on getting this complicated setup right?
>
> <snip/>
>
>>>
>>> Many thanks for any help
>>
>>
>> I had a very similar situation, I solved it by regarding the suffix. 
>> In my Apache DocumentRoot are all directories with static content. I 
>> only mount the following
>>
>> JkMount /  worker2
>> JkMount /*.html  worker2
>> JkMount /*.xml  worker2
>>
>
> Is 'JK2' the best one to be using now?
> I am a bit confused between mod_webapp (warp) and JK[n] TBH.
>

I actually use JK1.2 ajp13 connector (works fine with Jetty, too)

I formerly used mod_webapp, which is simple to setup, but less flexible 
in managing the urispace. Apart from this it does not support 
load-balancing and has it has turned out to be not as stable as my 
current solution.

I experimented with jk2, too. Big advantage with jk2 is that you don't 
have to change the httpd.conf with every change in your mounts (you 
keep them in a separate file workers2.properties). But I had some very 
strange results with jk2, resources like images and css has been served 
in a random-like order after some hours with heavy load and my boring 
pages looked like artwork :-) maybe a cashing problem, never found the 
reason, so I switched back to jk1.2. (at that time jk2 was still alpha, 
maybe it is fine now, but AFAIK there is currently no solution with jk2 
and Jetty)


>> Sure you'll run into troubles if there are html files in the static 
>> directories, or you rename it to *.htm
>
> Can't change the urls ;)
>
>>
>> I you find a more flexible solution, please tell me.
>
> The problem here, is relying on suffixes ..... we cannot .....
>
>
> As I remember, mapping '/' to mod_webapp stopped Apache from serving 
> ANYTHING.
>

WebAppConnection warpConnection warp ministrant.leonid:8008
WebAppDeploy cocoon warpConnection /

this works, but now EVERYTHING is handled by cocoon. (That's maybe what 
you mean)


> But as you imply in your sample above, this is not the case with JK2?
>
> So I would be able to map a long list of folders to JK2 and have 
> everything else automatically handled by Apache?
>
> eg.
>
> JkMount / worker2
> JkMount /index worker2
> JkMount /index.* worker2
> JkMount /archive/* worker2
> JkMount /collaboration/* worker2
> JkMount /education/* worker2
> JkMount /general/* worker2
> JkMount /library/* worker2
> JkMount /news/* worker2
> JkMount /press/* worker2
> JkMount /publications/* worker2
> JkMount /season/* worker2
> JkMount /search/* worker2
> JkMount /x-space/* worker2
>
> Is this going to work?
>

Yes, this will work - with the drawback, that you probably have to 
update httpd.conf very often.
  It would be famous if the guys from jk would adopt the cocoon sitemap 
language. But at present the matching possibilities are very limited. 
*/dir/ or **/dir/* does not work :(



> Will Cocoon 'receive' the whole URL, or just the bit picked up by the 
> '*'?
>

yes, the whole URL

> Thanks for your help.
>
> regards Jeremy
>

/Leo


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

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