[Opensource] how do you administer xsl mappings?

[Michael Rimov]

At 07:33 PM 8/14/2002 -0500, you wrote:
Mike,

Since nobody's replied to you so far, I'll give this a shot.

You're partially right in that I haven't personally used XSL mappings since 
Mike N. first created them so I can't fully comment on how complete they are.

However,

>- what's the difference between Match Number and Match Sequence


Looking at the code, I SUSPECT that Match Number should really be an 
auto-inc field.  Since sequence numbers CAN be duplicates depending on the 
Controller.  I can easily change it to such if nobody else is using it.

I do know that MatchSequence is the order you check for a matching regular 
expression so you can first check very specific versions of browsers and 
then further down the MatchSequence have more general matches.  Until you 
have one with MatchSequence='99' and BrowserPattern='*'


>- looking at the ControllerXSLMap code, it seems like there is no way to 
>wildcard or simply choose all User Groups - en entry has to exist for each 
>User Group?

As far as I can tell, you're right, so I did a one liner change so that it 
checks for the userGroup ="*" which is the same way the Expresso's Security 
Matrices work.

You'll see that in the 4.1 final since I consider that as a bug.

>- same as above for User Agent, which would mean that each netscape and ie 
>version would require a different record?

I checked the UserAgent table, and it has full support for Perl5 regular 
Expressions using the Jakarta ORO project.  [See the getMatch() function in 
ControllerXSLMap]


>- Additional Parameters seems to be required - what is this?

Have no idea... in fact did a grep on all the commercial projects as well 
as Expresso and never found any reference to it.  So I think switching it 
to 'allow null' would be appropriate here.

It's at least not used in the XMLViewHandler....

I've noticed that Werner just posted to the forums several fixes so I'll 
see if this helps.

Also, please know that I modified the code as of Expresso 4.1 (pre first 
ea) to cache the Perl5 expression parser results so you should see a 
significant performance improvement as of the final release.

HTH!
                                         -Mike