Forum Stats

  • 3,873,424 Users
  • 2,266,570 Discussions
  • 7,911,532 Comments

Discussions

beehive-netui-config.xml and Ampersand problem

LBROCKS
LBROCKS Member Posts: 34
edited Nov 11, 2008 2:07PM in WebLogic Portal
<url-config>
<url-encode-urls>false</url-encode-urls>
<html-amp-entity>false</html-amp-entity>
</url-config>

I have added the following lines into beehive-netui-config.xml, but getting these errors saying invalid entries, we are using WLP 10.2, Any help on this much appreciated


java.lang.IllegalStateException: Could not initialize from /WEB-INF/beehive-netui-config.xml
at org.apache.beehive.netui.pageflow.internal.PageFlowInitialization.performInitializations(PageFlowInitialization.java:95)
at org.apache.beehive.netui.pageflow.PageFlowContextListener.contextInitialized(PageFlowContextListener.java:47)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:458)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
Truncated. see log file for complete stacktrace
org.apache.beehive.netui.util.config.ConfigInitializationException: Validation errors occurred parsing the config file "/WEB-INF/beehive-netui-config.xml". Cause: org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'url-config'. No child element is expected at this point.
at org.apache.beehive.netui.util.config.parser.NetUIConfigParser$3.error(NetUIConfigParser.java:171)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:175)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
Truncated. see log file for complete stacktrace
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'url-config'. No child element is expected at this point.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
Truncated. see log file for complete stacktrace


th<Oct 28, 2008 9:40:50 PM PDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1225255174548' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:975)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'url-config'. No child element is expected at this point.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
Truncated. see log file for complete stacktrace


<Oct 28, 2008 9:40:50 PM PDT> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 9 task for the application 'PortalEar'.>
<Oct 28, 2008 9:40:50 PM PDT> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating redeploy task for application 'PortalEar'.>
<Oct 28, 2008 9:40:50 PM PDT> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:975)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
Truncated. see log file for complete stacktrace
org.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'url-config'. No child element is expected at this point.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:316)
at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:429)
Truncated. see log file for complete stacktrace


<Oct 28, 2008 9:40:51 PM PDT> <Warning> <Deployer> <BEA-149252> <No deployment 'PortalEar' found for Operation stop.>

Best Answer

  • 669641
    669641 Member Posts: 6
    Answer ✓
    It looks like you've added the url-config entry in the wrong place in the config file, so it fails to parse. Looking at the beehive-netui-config schema, elements within the netui-config element need to be in the following sequential order:

    <xsd:element name="expression-languages" type="netui:expression-languages" minOccurs="1" maxOccurs="1"/>
    <xsd:element name="pageflow-action-interceptors" type="netuiageflow-action-interceptors" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-handlers" type="netuiageflow-handlers" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-config" type="netuiageflow-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-factories" type="netuiageflow-factories" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="default-shared-flow-refs" type="netuiefault-shared-flow-refs" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="type-converters" type="netui:type-converters"minOccurs="0" maxOccurs="1"/>
    <xsd:element name="jsp-tag-config" type="netui:jsp-tag-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="url-config" type="netui:url-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="iterator-factories" type="netui:iterator-factories" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="request-interceptors" type="netui:request-interceptors" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="prefix-handlers" type="netuirefix-handlers" minOccurs="0" maxOccurs="1" />
    <xsd:element name="catalog" type="netui:catalog" minOccurs="0" maxOccurs="1"/>

    So, 'url-config' needs to come before 'iterator-factories' and after 'jsp-tag-config' in the config file.

    Jeff

Answers

  • 665334
    665334 Member Posts: 40
    Tried it on 10.3... I get the same exception. The schema file in the distribution seems to be ok. Workshop is not validating the file correctly, though: doesn't recognize the proper schema elements and doesn't complain when I add a <foobar> element under <netui-config>.
  • 669641
    669641 Member Posts: 6
    Answer ✓
    It looks like you've added the url-config entry in the wrong place in the config file, so it fails to parse. Looking at the beehive-netui-config schema, elements within the netui-config element need to be in the following sequential order:

    <xsd:element name="expression-languages" type="netui:expression-languages" minOccurs="1" maxOccurs="1"/>
    <xsd:element name="pageflow-action-interceptors" type="netuiageflow-action-interceptors" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-handlers" type="netuiageflow-handlers" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-config" type="netuiageflow-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="pageflow-factories" type="netuiageflow-factories" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="default-shared-flow-refs" type="netuiefault-shared-flow-refs" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="type-converters" type="netui:type-converters"minOccurs="0" maxOccurs="1"/>
    <xsd:element name="jsp-tag-config" type="netui:jsp-tag-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="url-config" type="netui:url-config" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="iterator-factories" type="netui:iterator-factories" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="request-interceptors" type="netui:request-interceptors" minOccurs="0" maxOccurs="1"/>
    <xsd:element name="prefix-handlers" type="netuirefix-handlers" minOccurs="0" maxOccurs="1" />
    <xsd:element name="catalog" type="netui:catalog" minOccurs="0" maxOccurs="1"/>

    So, 'url-config' needs to come before 'iterator-factories' and after 'jsp-tag-config' in the config file.

    Jeff
This discussion has been closed.