You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by giacomo <gi...@apache.org> on 2001/04/28 11:31:00 UTC

Namespace issues with aggregation

Hi all

I'll try to find the bugs concerning namespaces with the aggregation at
the sitemap level.

I see that the following

  <map:match pattern="single">
    <map:generate src="doc.xml"/>
    <map:serialize type="xml"/>
  </map:match>

should be equivalent to

  <map:match pattern="aggregated-single">
    <map:aggregate element="page">
      <map:part src="single" strip-root="yes"/>
    </map:aggregate>
    <map:serialize type="xml"/>
  </map:match>

if the root element of the doc.xml file is <page>, right?

Could some namespace specialist compose such a doc.xml file for test
with all possible namespace problems in it?

This test scenario can be applied to the transparent xinclude mechanism
as well.

Giacomo



---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Re: Namespace issues with aggregation

Posted by giacomo <gi...@apache.org>.

On Mon, 30 Apr 2001, Sylvain Wallez wrote:

>
>
> giacomo a �crit :
> >
> > Hi all
> >
> > I'll try to find the bugs concerning namespaces with the aggregation at
> > the sitemap level.
> >
> > I see that the following
> >
> >   <map:match pattern="single">
> >     <map:generate src="doc.xml"/>
> >     <map:serialize type="xml"/>
> >   </map:match>
> >
> > should be equivalent to
> >
> >   <map:match pattern="aggregated-single">
> >     <map:aggregate element="page">
> >       <map:part src="single" strip-root="yes"/>
> >     </map:aggregate>
> >     <map:serialize type="xml"/>
> >   </map:match>
> >
> > if the root element of the doc.xml file is <page>, right?
> >
> > Could some namespace specialist compose such a doc.xml file for test
> > with all possible namespace problems in it?
> >
> > This test scenario can be applied to the transparent xinclude mechanism
> > as well.
> >
> > Giacomo
> >
> I can do it, but not before wednesday...

Cool :)

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Re: Namespace issues with aggregation

Posted by Sylvain Wallez <sy...@anyware-tech.com>.

giacomo a écrit :
> 
> Hi all
> 
> I'll try to find the bugs concerning namespaces with the aggregation at
> the sitemap level.
> 
> I see that the following
> 
>   <map:match pattern="single">
>     <map:generate src="doc.xml"/>
>     <map:serialize type="xml"/>
>   </map:match>
> 
> should be equivalent to
> 
>   <map:match pattern="aggregated-single">
>     <map:aggregate element="page">
>       <map:part src="single" strip-root="yes"/>
>     </map:aggregate>
>     <map:serialize type="xml"/>
>   </map:match>
> 
> if the root element of the doc.xml file is <page>, right?
> 
> Could some namespace specialist compose such a doc.xml file for test
> with all possible namespace problems in it?
> 
> This test scenario can be applied to the transparent xinclude mechanism
> as well.
> 
> Giacomo
> 
I can do it, but not before wednesday...

-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org