[EMAIL PROTECTED] wrote: > > Hi Thomas, > > Perhaps you're right about JAXP, but even your example presupposes the > existence of TRAX. So to my mind we need to develop as good a grammar > caching API as possible, then work to ensure that anything JAXP comes up > with is compatible.
Yup, I'd agree that working out the details of a grammar caching API and implementation at apache first, would be useful. Then if the JAXP expert group thinks it's a useful feature, then it could be added to a future version. Updating JAXP is a heavier weight process so perhaps it could be developed the way TrAX was: independently at first and then incorporated into JAXP b/c it needed a home. BTW, I've already forwarded Thomas's email to the JAXP spec lead as a possible future feature addition. Thanks for the feedback. -Edwin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
