><snip/>
> > What was the final functionality you were looking for?
>
>A way to dynamically choose/load skins and other config information that was
>particular to a client.
>
>Eventually that'll be driven from a session or cookie setting but I wanted
>to get the snippet in place first, so I thought I could do that all in the
>matcher itself.
>
>I've only just figured out that a better pattern is:
>
><map:resources>
> <map:resource name="clientconfig">
> <map:generate src="config/{client}.xml" type="file" />
> <map:serialize type="xml"/>
> </map:resource>
></map:resources>
>
><map:match pattern="mypage">
> <map:call resource="clientconfig">
> <map:parameter name="client" value="magnet" />
> </map:call>
></map:match>
>
>And next I'll try to change the matcher to something that'll give me the
>client value.
You should really take a look at Forrest. There's probably a lot you can use.
Check it out at xml.apache.org/forrest
Bert
>Per
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, email: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
