Skip to Main Content

Application Development Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

beehive-netui-config.xml and Ampersand problem

LBROCKSOct 29 2008 — edited Nov 11 2008
<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.>
This post has been answered by 669641 on Nov 11 2008
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Dec 9 2008
Added on Oct 29 2008
2 comments
1,158 views