I attached an updated sample to the ticket that has some inheritance support. Rather than a patch, it is a zip file that you should be able to unzip and double-click the schema.xml (in IE or Firefox, at least) to view the transformed result. It does show inheritance or overriding of attributes -- although only the "weight" field has both -- but it does not expect analyzers or any child node to be overriden, only attributes. Let me know if this assumption is correct, as well as any other thoughts on the sample.
Thanks, Greg On 12/11/06, Greg Ludington <[EMAIL PROTECTED]> wrote:
> : What about creating an xml report (using a the live index searcher) > : and transforming that with XSLT to add look&feel? > > yeah ... i think you've really got something totally usable as is right > now, os don't feel like you have to start over. when i first typed up I do not have any real preference about starting over -- it would probably take the same amount of time to figure out the ugly parts of the XSL as it would to just do it all as straight JSP. As you both have suggested, I can generate intermediate XML from the IndexSchema to avoid doing the really ugly things in XSLT (which, of course, would also take some time). However, I was thinking more in terms of trade-offs on future work: Pro-XSLT: Using the Config utility methods, very easy for somebody to swap in their own version in $SOLR/conf/ in order to get their own look and feel. Pro-JSP: Easier for maintenance, and more approachable for new contributors, as JSP tends to be less impenetrable than XSLT. I should be able to finish it either way; however, I have an emerging crisis in my day job, so I may not be able to respond for a few days. Thanks, Greg
