----- Original Message ----- From: "Steve Loughran" <[EMAIL PROTECTED]>
> I am -1 to putting it in. If we could put stuff in there are usefult things > I'd want to add, like <hostname>, changes to <csc> and generally add ages > to the schedule. > > we have been feature complete since beta-1 + selectors, lets stay that way I hope to add more mess this week end and remove the outputtype for <style>. 1) remove the outputtype from the liaison 2) add an <outputproperty> in xsltprocess and the corresponding method to the traxliaison (will do nothing for the other just like the xmlcatalog) btw can someone explain why the xml catalog stuff in xsltprocess is done via reflection ? what's the reason rather than casting to a (TraXLiaison) and call the method ? What should go into 1.6: Requested feature about <style> is factory specific use for TraX (if you have both xalan and saxon you may use directly the implementation factory rather than the default lookup mechanism of JAXP). Another one is processor specific properties (optimize or such for example) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
