1 Reply Latest reply on Sep 18, 2006 9:58 AM by Adrian Brock

    JBossXB and security parsing

    Adrian Brock Master

      I'm also seeing this error which I haven't investigated:

      2006-09-16 15:23:11,036 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Configured: name=jboss.security:service=StandardLoginConfig state=Instantiated mode=Manual requiredState=Configured
      org.jboss.deployment.DeploymentException: Error configuring attribute PolicyConfig
       at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:52)
       at org.jboss.system.metadata.ServiceAttributeMetaData.getValue(ServiceAttributeMetaData.java:151)
       at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:132)
       at org.jboss.system.ServiceConfigurator.configure(ServiceConfigurator.java:102)
       at org.jboss.system.microcontainer.ConfigureAction.installAction(ConfigureAction.java:58)
      
      <snipped/>
      
      Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: No cursor for {urn:jboss:security-config:5.0}application-policy
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:154)
       at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:139)
       at org.jboss.system.metadata.ServiceJBXBValueMetaData.getValue(ServiceJBXBValueMetaData.java:75)
       at org.jboss.system.metadata.ServiceAttributeMetaData.getValue(ServiceAttributeMetaData.java:147)
       ... 31 more
      Caused by: org.jboss.xb.binding.JBossXBRuntimeException: No cursor for {urn:jboss:security-config:5.0}application-policy
       at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:277)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:299)
       at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
       at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
       at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
       at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
       at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
       at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
       at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:150)
       ... 34 more
      


        • 1. Re: JBossXB and security parsing
          Adrian Brock Master

          This was caused by the context classloader being that of the
          bootstrap. i.e. The NoAnnotationURLClassLoader.

          It couldn't find resource:.xml which is in jboss.jar

          Why this didn't fail in the old server as well?

          Whatever the reason, it obviously needs to use the MBean's classloader
          in case there are schemas in a scoped deployment.