----- Original Message ----- From: "Vadim Gritsenko" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "'Nicola Ken Barozzi'" <[EMAIL PROTECTED]> Sent: Monday, January 07, 2002 7:31 PM Subject: RE: Allowed Sitemap Constructs
> <map:select>
> <map:when test="XX">
> <map:generate/>
> </map:when>
> <map:when test="YY">
> <map:generate/>
> </map:when>
> <map:otherwise>
> <map:generate/>
> </map:otherwise>
> </map:select>
> <map:serialize/>
>
> Try to convert to matchers - you will fail :)
This fails? :-o ;-)
<map:match>
<map:match pattern="XX">
<map:generate/>
</map:match>
<map:match pattern="YY">
<map:generate/>
</map:match>
<map:match pattern="**">
<map:generate/>
</map:match>
</map:match>
<map:serialize/>
I haven't tried it, so I don't know if it really fails, but it seems there
is an overlap between matchers and selectors which is dangerous IMHO.
With no overlap it's easy to decide what to use, but they seem so similar
it's difficult to really see how to use them. Actions complicate this matter
too, because they can have nested elements.
I suggest we have only atomic actions.
Then flow can be done with a selector that can select based on what the
Action has done to the objectModel.
Is there a need for non-atomic Actions?
It also seems matchers are before sitemap gen-trans-ser while selectors can
be intermingled.
Which makes me think thar matchers seem to belong to flowmaps while
selectors to sitemaps.
But on the other hand selectors are needed for atomic actions, which makes
them go into the flowmap.
I think that overlap should be avoided if possible.
So what I would like to know is:
- why are there matchers and selectors?
- are they unitable in a single selection component?
- must Actions have nested elements? It pollutes the selection concept.
Ken
--
Nicola Ken Barozzi [EMAIL PROTECTED]
These are the days of miracle and wonder...
...so don't cry baby, don't cry...
Paul Simon
smime.p7s
Description: application/pkcs7-signature
