[jboss-dev-forums] [Design of Management Features on JBoss] - Re: Using xinclude in config files

[adrian@jboss.org]

"snacker" wrote : It's not working...
  | 
  | I couldn't find any command/env properties to set, so I created a dummy DocumentBuilderFactory class which sets namespaceaware and xincludeaware to true then proxies all calls to org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.
  | 

I've got no idea why it's not working. Ask the Apache Xerces project.
There is likely some nuance they can explain.

THIS IS NOT A JBOSS ISSUE, so there's little point trying to guess here.

I even tried hacking the configuration properties but that doesn't work either:

  | package test;
  | 
  | public class MyXmlParserConfig extends org.apache.xerces.parsers.XIncludeAwareParserConfiguration
  | {
  |    public MyXmlParserConfig()
  |    {
  |       setFeature(NAMESPACES, true);
  |       setFeature(XINCLUDE_FEATURE, true);
  |    }
  | 
  | // OR Even more belt and braces:
  | 
  |    public boolean getFeature(String featureId) throws org.apache.xerces.xni.parser.XMLConfigurationException
  |    {
  |       
  |       if (featureId.equals(NAMESPACES) || featureId.equals(XINCLUDE_FEATURE))
  |          return true;
  |       return super.getFeature(featureId);
  |    }
  | }
  | 

Neither works.

There's not point testing jboss5-Beta2. The SARDeployer where you report
your stacktrace uses a plain SAXParser not JBossXB.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106413#4106413

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106413