Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (athena.apache.org: domain of simone.tripodi@gmail.com
 designates 209.85.219.209 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=NL6k+mWKW7FDY2MymfiIeZKzKMRoipg6i67K6kXv7PCE6bv9cjTXtyKdzDgT49vXUG
         +IW0C8v60QeTx9oJ4gOFp+oucMbB100/vU6mbx1ayV62Y5P+exqCc2ln0XOE9C7BSrTk
         MyLfoqgnlKi30maJTnkA6oi9PMe25OJSdms8M=
MIME-Version: 1.0
In-Reply-To: <1267697086.2517.4.camel@joske-laptop>
References: <1267517574.2511.5.camel@joske-laptop>
	 <4B8F54DB.6030901@apache.org> <1267697086.2517.4.camel@joske-laptop>
Date: Thu, 4 Mar 2010 12:34:23 +0100
Message-ID: <4173dc211003040334iec29879q20ca180cf9c5b46b@mail.gmail.com>
Subject: Re: Cocoon 3 XML serializer
From: Simone Tripodi <simone.tripodi@gmail.com>
To: users@cocoon.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Jos,
these classes are not committed because they're generated from JavaCC,
the JavaCC plugin should be invoked during the 'generate-source' maven
phase...
Doesn't it work for you?
Best,
Simo

http://people.apache.org/~simonetripodi/


On Thu, Mar 4, 2010 at 11:04 AM, Jos Snellings <Jos.Snellings@pandora.be> w=
rote:
> Hi!
>
> In the full checkout of the cocoon-3 SVN repository I am missing:
> org.apache.cocoon.sax.xpointer.XPointerFrameworkParser;
> org.apache.cocoon.sax.xpointer.ParseException;
>
> This prevents XIncludeTransformer from compiling. Any idea why?
>
> Jos
>
>
> On Thu, 2010-03-04 at 07:36 +0100, Reinhard P=C3=B6tz wrote:
>> Jos Snellings wrote:
>> > Hi,
>> >
>> > Is the hereunder described issue with XML serializers known?
>> >
>> > A sitemap having several xml serialization patterns:
>> >
>> > =C2=A0 <map:pipeline>
>> > =C2=A0 <map:match pattern=3D"showterm.xml">
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 <map:generate type=3D"term"/>
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 <map:serialize type=3D"xml"/>
>> > =C2=A0 </map:match>
>> > =C2=A0 =C2=A0<map:match pattern=3D"hierarchies">
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 <map:generate type=3D"topterms"/>
>> > =C2=A0 =C2=A0 =C2=A0 =C2=A0 <map:serialize type=3D"xml" />
>> > =C2=A0 =C2=A0</map:match>
>> >
>> > =C2=A0 =C2=A0...
>> >
>> > This pipeline is observed to have an 'eternal cache':
>> > whichever pattern is matched first gives the correct answer.
>> > All subsequent requests, whatever the URL, whatever the get-parameters
>> > return the contents of the cache.
>> >
>> > In order to get fresh results you need to destroy the caching stuff
>> > under work/... first.
>> >
>> > Is this known? I may as well get rid of it by checking out the very la=
st
>> > cocoon-3 version! Just asking.
>>
>> Could you create a JIRA issue please and attach a failing sample please?
>> =C2=A0Also add the version of C3 (release or SVN revision) that you use.
>>
>> Thanks!
>>
>
>
>
> ---------------------------------------------------------------------
> 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