The list has spoken...
 
OK, what I decided to do to in the end was place nested
matches at the inner level that match each possible * call
in the outer match.  These in turn call a map:act, each with
a different, but _fixed_ type attribute.  This is not ideal, as I
end up with the same code inside each of the actions, but
it seems the best compromise short of writing "meta action"
as suggested by Sylvain.  I really need to just finish off the
current assignment - of course, if anyone wants to try this
as an exercise, I'd be happy to help test it ;-)

>>> [EMAIL PROTECTED] 05/03/2003 10:51:58 >>>
Marco Rolappe wrote:

>hi derek,
>
>AFAIR the nodebuilder for <map:act> type nodes (and probably others) doesn't
>resolve those variable references for @type attributes. thus I think it's
>not possible.

>

Exactly. The "type" attribute on all map:xxx elements does not go
through the variable resolution mechanism.

Why so ? Because dynamically choosing the type of component doesn't
really make sense most of the time, and would complicate the
understanding of the sitemap.

Now, if you really want to do that, I suggest you write a "meta-action"
that calls an action whose type is given as a parameter.

Sylvain

--
Sylvain Wallez                                  Anyware Technologies
http://www.apache.org/~sylvain           http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
This message has been scanned for viruses and dangerous content by
MailScanner, and is believed to be clean.

"The CSIR exercises no editorial control over E-mail messages and/or
attachments thereto/links referred to therein originating in the
organisation and the views in this message/attachments thereto are
therefore not necessarily those of the CSIR and/or its employees.
The sender of this e-mail is, moreover, in terms of the CSIR's Conditions
of Service, subject to compliance with the CSIR's internal E-mail and
Internet Policy."

Reply via email to