You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Berin Loritsch <bl...@apache.org> on 2002/04/25 18:20:51 UTC
C1 compatible sitemap??
Considering we have a number of people upgrading from C1 now that
we said that C2 is stable, we need to do something to ease that
migration.
If we do not do this, we risk alienating otherwise faithful users.
The C1 compatible sitemap follows the same rules as C1:
Assembles the pipeline from PIs, and reacts to *.xml in the root
directory.
It should be a completely separate sitemap, and should be relatively
easy to implement. The key issues to bear in mind are:
* this is a compatibility layer--no need to support new features
* the only feature upgrade should be speed/scalability
* the XSP engine has substantially changed--users of XSP should
upgrade to the official sitemap
* we only want simple File->XSLT->Serializer support
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: C1 compatible sitemap??
Posted by Berin Loritsch <bl...@apache.org>.
Vadim Gritsenko wrote:
>>From: Berin Loritsch [mailto:bloritsch@apache.org]
>>
<snip/>
>
>
> Why create the whole new sitemap? I feel this can be done by writing one
> transformer:
>
> ReactorTransformer, or C1Transformer
>
> It can be implemented similar to the LogicsheetCodeGenerator, building
> chain of the XSLT transformations on the fly.
>
> (I assume that PIs can appear only before root element. Am I right?)
You are right.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: C1 compatible sitemap??
Posted by Vadim Gritsenko <va...@verizon.net>.
> From: Berin Loritsch [mailto:bloritsch@apache.org]
>
> Considering we have a number of people upgrading from C1 now that
> we said that C2 is stable, we need to do something to ease that
> migration.
>
> If we do not do this, we risk alienating otherwise faithful users.
>
> The C1 compatible sitemap follows the same rules as C1:
>
> Assembles the pipeline from PIs, and reacts to *.xml in the root
> directory.
>
> It should be a completely separate sitemap, and should be relatively
> easy to implement. The key issues to bear in mind are:
>
> * this is a compatibility layer--no need to support new features
> * the only feature upgrade should be speed/scalability
> * the XSP engine has substantially changed--users of XSP should
> upgrade to the official sitemap
> * we only want simple File->XSLT->Serializer support
Why create the whole new sitemap? I feel this can be done by writing one
transformer:
ReactorTransformer, or C1Transformer
It can be implemented similar to the LogicsheetCodeGenerator, building
chain of the XSLT transformations on the fly.
(I assume that PIs can appear only before root element. Am I right?)
Vadim
> --
>
> "They that give up essential liberty to obtain a little temporary
safety
> deserve neither liberty nor safety."
> - Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org