I think fox: should also be validated. It's, by
definition, part of FOP core, and can't be
added/adjusted to by anyone but us.
FOP Processor: XSL FO's + FOP (fox:) FO's.
RenderX Processor: XSL FO's + RenderX FO's.
AntennaHouse Processor: XSL FO's + AntennaHouse FO's.
Whether or not a particular FO supported by a
processor has been christened by the W3C is an
irrelevancy that shouldn't affect architecture.
Glen
--- [EMAIL PROTECTED] wrote:
> bckfnn 2004/09/08 13:25:55
>
> Modified: src/java/org/apache/fop/fo
> FOTreeBuilder.java
> Log:
> Disable the validation for extension elements.
> This is a temporary fix
> until a full validation framework that support
> extensions are in place.
>
> Revision Changes Path
> 1.49 +6 -4
>
xml-fop/src/java/org/apache/fop/fo/FOTreeBuilder.java
>
> Index: FOTreeBuilder.java
>
>
===================================================================
> RCS file:
>
/home/cvs/xml-fop/src/java/org/apache/fop/fo/FOTreeBuilder.java,v
> retrieving revision 1.48
> retrieving revision 1.49
> diff -u -r1.48 -r1.49
> --- FOTreeBuilder.java 6 Sep 2004 18:44:31 -0000
> 1.48
> +++ FOTreeBuilder.java 8 Sep 2004 20:25:55 -0000
> 1.49
> @@ -255,10 +255,12 @@
> "Error: First element must
> be fo:root formatting object"));
> }
> } else { // check that incoming node is
> valid for currentFObj
> - try {
> -
> currentFObj.validateChildNode(locator, namespaceURI,
> localName);
> - } catch (SAXParseException e) {
> - throw e;
> + if
> (namespaceURI.equals(FOElementMapping.URI)) {
> + try {
> +
> currentFObj.validateChildNode(locator, namespaceURI,
> localName);
> + } catch (SAXParseException e) {
> + throw e;
> + }
> }
> }
>
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
>
