If the XML failures are in TCK tests that relate to modules not included in the minimal assemblies, then what would we be breaking by removing Xerces/Xalan?

I was just hoping that we could keep them out of the minimal assemblies if they are not needed, since some users will want to use Java 5 and others are wanting Java 6 support, which both provide their own implementations at different feature levels....


-Donald


Kevan Miller wrote:

On May 22, 2007, at 11:38 AM, Donald Woods wrote:

Can we put the addition of Xerces/Xalan in geronimo-boilerplate-jee5 instead of geronimo-boilerplate-minimal, which adds unnecessary bloat back into the minimal assemblies again?

We could consider it. Putting them back into boilerplate-minimal was consistent with our G 1.1 and 1.2 structure. I certainly wouldn't call it "unecessary" and could do without painting the issue with words like "bloat". I could similarly describe your proposal as -- "could we remove Xerces/Xalan from the minimal server, so that we can break xml processing in that environment?

Good chance that we'll be pulling the xalan jar out, for other reasons. Since xalan is the biggest jar, I assume this helps?

--kevan


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to