Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 88788 invoked from network); 20 Jan 2004 01:44:50 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Jan 2004 01:44:50 -0000 Received: (qmail 75439 invoked by uid 500); 20 Jan 2004 01:44:25 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 75416 invoked by uid 500); 20 Jan 2004 01:44:25 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: users@cocoon.apache.org Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 75403 invoked from network); 20 Jan 2004 01:44:25 -0000 Received: from unknown (HELO sccrmhc11.comcast.net) (204.127.202.55) by daedalus.apache.org with SMTP; 20 Jan 2004 01:44:25 -0000 Received: from jianlzr6w353h3 (c-24-6-217-57.client.comcast.net[24.6.217.57]) by comcast.net (sccrmhc11) with SMTP id <2004012001443201100j9ih0e>; Tue, 20 Jan 2004 01:44:32 +0000 From: "Jian Dai" To: Subject: RE: Ask help for "Cinclude" implement Date: Tue, 20 Jan 2004 05:46:26 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <400C7F2B.9030206@gmx.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, Joery: 1. There is no error message. The system just treated them as normal xml tag. In my example, xmlns:cinclude="http://apache.org/cocoon/include/1.0"> > >> XMLURI >> >> >> paraone >> ValueforParaOne >> >> ............................. >> >> I would get a string like "XMLURL paraone ValueforParaOne". Just like I simply put there. 2. I use Cocoon 2.0.3. I have checked the source codes for cinclude transformer under my version. It does have those attributes. 3. I did use in my code. Sorry for the mistype here Here is a clue from that document. It said "this is currently not supported by the caching cinclude transformer". Do you know the difference between "caching" and "not caching" cinclude transformer and how to change them? Thanks a lot. Jack -----Original Message----- From: Joerg Heinicke [mailto:joerg.heinicke@gmx.de] Sent: Monday, January 19, 2004 5:07 PM To: users@cocoon.apache.org Subject: Re: Ask help for "Cinclude" implement On 20.01.2004 13:25, Jian Dai wrote: > Hi, Joery: > > I am sorry that I did not make my problem more clearer. No problem, that's communication :) > As you mentioned, my problem is that my cinclude transformer COULD NOT > understand the notation for the first alternative but I cannot figure > out the reason why. I see. Do you get an error message or does it "just not work"? > I have read the articile you mentioned(As the matter of face, I just > get the idea from there) but still haven't a clue. Do you have any idea > about that. Can it be the version problem? Of course it can. So it's interesting to know your exact version of Cocoon. You only wrote 2.0, but I guess you are not using 2.0, but any 2.0.x. BTW, related to the documentation (the link I sent, I never used the extended notation myself) it must be instead of simple as you wrote below. Might be only here in the mail, but maybe you have a closer look again. Joerg > -----Original Message----- > From: Joerg Heinicke [mailto:joerg.heinicke@gmx.de] > > > On 20.01.2004 12:25, Jian Dai wrote: > > >>Hi, all: >> >>I am tring to use cinclude to include some xml frags in main page and I > > want > >>to pass some >>parameter to that frag. I was learned that I could use cinclude in > > following > >>format >> >> > xmlns:cinclude="http://apache.org/cocoon/include/1.0"> > >> XMLURI >> >> >> paraone >> ValueforParaOne >> >> ............................. >> >> >> >>When I added this code frag into xsp for main page, the included XML could >>not be called. My >>xsp page simple treated thoese tag as normal xml tag instead of the >>attributes for "cinclude" >>transformer. >> >>But if I use a normal cinlude format like >> >>Then, the included XML can be called without problem. > > > If I understand you correctly you have two alternatives to use cinclude > and tried them by putting them into XSP. The output of XSP is of course > that what you add to it in XML tags form. Nothing will happen or will be > changed with it until you add a cinclude transformer to the pipeline. So > the only question is whether the cinclude transformer understands both > different notations. Following the documentation both should work: > http://cocoon.apache.org/2.0/userdocs/transformers/cinclude-transformer.html > . > > The problem I have with your error description is that you don't say > what does not work exactly and that you write "the included XML > can/could not be called" - what ever that means. > > Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org For additional commands, e-mail: users-help@cocoon.apache.org