Validation Problem W/ DOCTYPE?!?

so I'm using W3C's validator to try and get the bugs out of
my web page, but I keep getting a message that says: "No Character
Encoding Found! Falling back to windows-1252", "Unable to Determine
Parse Mode!", and "No DOCTYPE found! Checking with default HTML
4.01 Transitional Document Type."
thenorthgate.org
This is what my page DOCTYPE looks like.
Any and all help would be greatly appreciated!
Thank you!

> so I'm using W3C's validator to try and get the bugs out
of my web page,
> but I
> keep getting a message that says: "No Character Encoding
Found! Falling
> back
> to windows-1252", "Unable to Determine Parse Mode!", and
"No DOCTYPE
> found!
> Checking with default HTML 4.01 Transitional Document
Type."
I don't get those errors at
http://validator.w3.org.
Just change each instance of this -
<style type="text/css">

</style>
to this -
</style>
and all but your Flash errors will go away.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"L0WRIDE" <[email protected]> wrote in
message
news:gqiihd$bus$[email protected]..
> so I'm using W3C's validator to try and get the bugs out
of my web page,
> but I
> keep getting a message that says: "No Character Encoding
Found! Falling
> back
> to windows-1252", "Unable to Determine Parse Mode!", and
"No DOCTYPE
> found!
> Checking with default HTML 4.01 Transitional Document
Type."
>
>
http://thenorthgate.org
>
> This is what my page DOCTYPE looks like.
>
> Any and all help would be greatly appreciated!
> Thank you!
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
> "
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="
http://www.w3.org/1999/xhtml">
> <head>
> <title>Welcome to the NorthGate!</title>
> <meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
>

Similar Messages

Weblogic Portal: Error While Deploying: VALIDATION PROBLEMS WERE FOUND

Hello friends
I am getting following error while deploying EAR on server.
“Module named 'MyEAR' failed to deploy. See Error Log view for more detail.”
Steps I followed:
1: Created one portal domain successfully and was able to start the serve after thatr.
2: Created one Portal EAR Project and added it on server.
Now when I am restarting the server, getting following error/log
**“weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND**
**problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>”**
Exception stack Trace:
java.lang.Exception: Exception received from deployment driver. See Error Log view for more detail.
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper$DeploymentProgressListener.watch(WlsJ2EEDeploymentHelper.java:1566)
at oracle.eclipse.tools.weblogic.server.internal.WlsJ2EEDeploymentHelper.deploy(WlsJ2EEDeploymentHelper.java:470)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishWeblogicModules(WeblogicServerBehaviour.java:1346)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishToServer(WeblogicServerBehaviour.java:803)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publishOnce(WeblogicServerBehaviour.java:623)
at oracle.eclipse.tools.weblogic.server.internal.WeblogicServerBehaviour.publish(WeblogicServerBehaviour.java:516)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:193)
at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:245)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:231)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:155)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:301)
at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:178)
as it is ‘brand new ‘ – IDE generated application, weblogic-application.xml is untouched.
Thanks & Regards

I have seen this problem also. To be clear, this occurs straight out of the box. In other words - launch eclipse, create a new workspace, create a new portal EAR project with the wizard, and then try to deploy it without touching anything. In fact, try changing the portal's facets to anything, plain EAR, 11g default, Portal EAR - it doesn't matter. It will not deploy. Either you get this error or you get deployment errors complaining about missing library references in the weblogic-application.xml. Then - you have to do surgery just to get an 'out of the box' portal to run. Very frustrating.

Migration from weblogic 8 to 10.3. Validation Problem

Hi,
i encounter some problem while migrating to weblogic 10.3. I looked into the error but i do not know which file is causing the problem. Anyone encounter this problem before?
Thanks
<Dec 15, 2010 3:18:37 PM SGT> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\WEBLOGIC10_DEPLOYMENTS\project\Project/WEB-INF/weblogic.xml of module Project.
The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEM
problem: cvc-fractionDigits-valid: Decimal fractional digits (1) of value '0.5' does not match fractionDigits facet (0) for xsdIntegerType in namespace http://java.sun.com/xml/ns/javaee:<null>
C:\bea10\user_projects\domains\csurvey\<unknown>:103:2: problem: java.lang.NumberFormatException: For input string: ".5":<<unknown>>
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
at weblogic.servlet.internal.WebAppDescriptor.getWeblogicWebAppBean(WebAppDescriptor.java:170)
at weblogic.servlet.utils.WarUtils.getWlWebAppBean(WarUtils.java:107)
at weblogic.application.compiler.WARModule.processLibraries(WARModule.java:363)
at weblogic.application.compiler.WARModule.merge(WARModule.java:450)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:94)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:47)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createLazyDeployableObject(WebLogicDeployableObjectFactoryImpl.java:156)
at weblogic.deploy.api.tools.SessionHelper.inspect(SessionHelper.java:661)
at com.bea.console.actions.app.install.Flow$2.execute(Flow.java:463)
at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:4625)
at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:255)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:54)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.>*

Hi, would you please post how you solved the problem?
It would be really helpful for someone with the same problem.
Greetings!

Please help me with the digital signature validation problem?

Please help me with the digital signature validation problem?

Hi
Execute the program in the Debuggin mode.
In the Debugger Window
Select Breakpoint -> Break point at -> Breakpoint at source code Menu Item and enter the details of the program/include/line no..
Activate the System Debugger On from the Settings Menu.
Hope this would help you.
Murthy
Edited by: Kalyanam Seetha Rama Murthy on Jul 18, 2008 7:20 AM

Validation problem in Mapping

Hi,
I am getting this error when I am trying to validate the mapping
Source table is QMI
" VLD-1002: Mapping object QMI is not bound to a repository object.
All objects in a mapping must be bound to objects in the Design Repository. Unbound objects inherit the logical location of the module that owns the mapping. Warehouse Builder cannot generate the physical access specification (schema name and database link) for this unbound object. Perform a synchronization from QMI. "
Could, some body give me a solution for this validation problem.
Cheers,
Krishna,

Hi,
Thanks for your suggestions. I followed your steps and validating didnt returns any errors.
But, When I am trying to deploy I am getting a message
DEPLOYMENT STATUS : USE DEPLOYMENT
UNDO OR REDO BUTTONS TO CLOSE
WINDOW TO FINISH, PROCESSED : 0, ERRORS :0, WARNINGS :0.
I am able to deploy the mappings but not the source tables and target tables. I am getting deploy status failed in the control cetner.
The work process of my scenario is as follows:
1) I am having two tables from which I need to populate my target ( NEW table ) with some of the columns from those tables.
2) I created a two stage tables manually in the database for both of the source tables in two different mappings
source table 1 into stage table 1 in mapping 1
source table 2 into stage table 2 in mapping 2
3) I created a third table as the final target table where I can map these two stage tables into that .
stage table 1 and stage table 2 into target table in mapping 3 using a JOINER operator. I had given the join condidion as well.
4) All these stage tables and the final target table and the mappings are in the target module.
Is this is the way to work on these type of scenarios. Actually I need to JOIN 8 tables and pull some of the necessary columns into the target table based on the condition.
Intitially I had used a JOINER condition to JOIN those 8 tables in a single mapping.But it gave me the deployment error.
Could you guys please give me a hand by giving me some suggestion how to proceed in this scenario.
Last question : Are there any training centers in chennai or Hyderabad where I can get some trining over OWB 10g.
Cheers,
Krishna.

Xml schema validation problem

Hi All
How to tackle this xml schema validation problem
i am using the sample code provided by ORacle technet for xml
schema validation in the Oracle database(817).
The sample code works perfectly fine.
Sample as provided by http://otn.oracle.com/tech/xml/xdk_sample/archive/xdksample_093001.zip.
It works fine for normal xml files validated against
xml schema (xsd)
but in this case my validation is failing . Can you let me know why
I have this main schema
Comany.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.company.org"
xmlns="http://www.company.org"
elementFormDefault="qualified">
<xsd:include schemaLocation="Person.xsd"/>
<xsd:include schemaLocation="Product.xsd"/>
<xsd:element name="Company">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Person" type="PersonType" maxOccurs="unbounded"/>
<xsd:element name="Product" type="ProductType" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
================
which includes the following 2 schemas
Product.xsd
============
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="ProductType">
<xsd:sequence>
<xsd:element name="Type" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
==============
Person.xsd
===========
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xsd:complexType name="PersonType">
<xsd:sequence>
<xsd:element name="Name" type="xsd:string"/>
<xsd:element name="SSN" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
=================
now when i try to validate a xml file against Company.xsd
it throws an error saying unable to find Person.xsd.
no protocol error
Now where do i place these 2 schemas(.xsd files) Person & product
so that the java schemavalidation program running inside Oracle
database can locate these files
Rgrds
Sushant

Hi Jinyu
This is the java code loaded in the database using loadjava called by a wrapper oracle stored procedure
import oracle.xml.parser.schema.*;
import oracle.xml.parser.v2.*;
import java.net.*;
import java.io.*;
import org.w3c.dom.*;
import java.util.*;
import oracle.sql.CHAR;
import java.sql.SQLException;
public class SchemaUtil
public static String validation(CHAR xml, CHAR xsd)
throws Exception
//Build Schema Object
XSDBuilder builder = new XSDBuilder();
byte [] docbytes = xsd.getBytes();
ByteArrayInputStream in = new ByteArrayInputStream(docbytes);
XMLSchema schemadoc = (XMLSchema)builder.build(in,null);
//Parse the input XML document with Schema Validation
docbytes = xml.getBytes();
in = new ByteArrayInputStream(docbytes);
DOMParser dp = new DOMParser();
// Set Schema Object for Validation
dp.setXMLSchema(schemadoc);
dp.setValidationMode(XMLParser.SCHEMA_VALIDATION);
dp.setPreserveWhitespace (true);
StringWriter sw = new StringWriter();
dp.setErrorStream (new PrintWriter(sw));
try
dp.parse (in);
sw.write("The input XML parsed without errors.\n");
catch (XMLParseException pe)
sw.write("Parser Exception: " + pe.getMessage());
catch (Exception e)
sw.write("NonParserException: " + e.getMessage());
return sw.toString();
This is the code i used initially for validating a xml file against single xml schema (.xsd) file
In the above code could u tell how to specify the second schema validation code for the incoming xml.
say i create another Schemadoc for the 2nd xml schema.
something like this with another parameter(CHAR xsd1) passing to the method
byte [] docbytes1 = xsd1.getBytes();
ByteArrayInputStream in1 = new ByteArrayInputStream(docbytes1);
XMLSchema schemadoc1 = (XMLSchema)builder.build(in1,null);
DOMParser dp = new DOMParser();
How to set for the 2nd xml schema validation in the above code or can i combine 2 xml schemas.
How to go about it
Rgrds
Sushant

XML validation: how to check ALL validation problem for XHTML

I have a lot of documents in HTML format (not very good) that I would like to convert in XML (XHTML). I know it is not so easy and I would use this strategy in a Java program:
1. Try to check the well-formness and validation with a XML parser (SAX or Xerces)
2. If not valid: try to individuate ALL the problems the file has (*and not only the first one that halts the processing process*)
3. Try to transform the HTML to a validable XHTML with some approach: regular expression or other methods
So the questions I do to you are the following:
1. What XML parser do you think is the best for this purposes? SAX or Xerces?
2. How can I understand what are all the validation problems in the file and not only the first one (If I remember well XML parsers halt the parsing process at the first error...)?
3. How can I transform the HTML to a valid XHTML? I have only to use RegEx or is there other tools to do this for XHTML and HTML problem?
Thanks
r
Edited by: robertobat on Feb 21, 2009 7:09 PM

>
1. Neither of them. (Disregarding the fact that SAX and Xerces aren't in the same category and don't cover all the possibilities.I would say SAX default implementation in JRE and SAX parser in Xerces.
2. I think you have "valid" and "well-formed" confused. And HTML isn't a dialect of XML so the idea of trying to use an XML parser to handle HTML isn't a good idea.I know very well what is the difference between valid and well-formed but I've used "validation" to represent all the conversion problem. But you are right. I'm convincing myself that using a XML parser as the first step is not a good idea.
3. Well, this is the real question, isn't it? Those other two were just a waste. Don't screw about with regex, for one thing it doesn't work well for hierarchical structures and for another you won't finish in a finite time. Just use an HTML parser which can produce a DOM, like TagSoup for example. Or run them through HTMLTidy. You could also submit them to one of the internet sites which will validate XHTML for you.I've seen Tidy and its capability to convert an HTML to a XHTML and I think it is better then TagSoup because I have to implement this mechanism in a production environment and I want to use only open source projects that have a very long story and that are strong. But I'll see TagSoup as you say.
I cannot use an Internet service to convert millions of private documents.

Weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND

I have a deploy application on the server [Weblogic 10], but when I try to assign a VirtualHost handing me the following error:
          weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
          problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
          problem: cvc-complex-type.2.4b: Element not allowed: dispatcher@http://java.sun.com/xml/ns/javaee in element filter-mapping@http://java.sun.com/xml/ns/javaee:<null>
          at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
          at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
          at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
          at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:292)
          at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:260)
          Truncated. see log file for complete stacktrace

<?xml version="1.0" encoding="UTF-8"?>
          <web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
          <display-name>portalUchileWeb</display-name>
          <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
          </welcome-file-list>
          <filter>
          <filter-name>PageFlowJspFilter</filter-name>
          <filter-class>org.apache.beehive.netui.pageflow.PageFlowJspFilter</filter-class>
          </filter>
          <filter>
          <filter-name>PageFlowForbiddenFilter</filter-name>
          <filter-class>org.apache.beehive.netui.pageflow.PageFlowForbiddenFilter</filter-class>
          <init-param>
          <param-name>response-code</param-name>
          <param-value>404</param-value>
          </init-param>
          </filter>
          <filter-mapping>
          <filter-name>PageFlowJspFilter</filter-name>
          <url-pattern>*.jsp</url-pattern>
          <dispatcher>FORWARD</dispatcher>
          <dispatcher>REQUEST</dispatcher>
          <dispatcher>INCLUDE</dispatcher>
          </filter-mapping>
          <filter-mapping>
          <filter-name>PageFlowJspFilter</filter-name>
          <url-pattern>*.jspx</url-pattern>
          <dispatcher>FORWARD</dispatcher>
          <dispatcher>REQUEST</dispatcher>
          <dispatcher>INCLUDE</dispatcher>
          </filter-mapping>
          <filter-mapping>
          <filter-name>PageFlowForbiddenFilter</filter-name>
          <url-pattern>*.java</url-pattern>
          <dispatcher>REQUEST</dispatcher>
          </filter-mapping>
          <filter-mapping>
          <filter-name>PageFlowForbiddenFilter</filter-name>
          <url-pattern>*.jsfb</url-pattern>
          <dispatcher>REQUEST</dispatcher>
          </filter-mapping>
          <filter-mapping>
          <filter-name>PageFlowForbiddenFilter</filter-name>
          <url-pattern>*.jpfs</url-pattern>
          <dispatcher>REQUEST</dispatcher>
          </filter-mapping>
          <listener>
          <listener-class>org.apache.beehive.netui.pageflow.PageFlowContextListener</listener-class>
          </listener>
          <listener>
          <listener-class>org.apache.beehive.netui.pageflow.HttpSessionMutexListener</listener-class>
          </listener>
          <servlet>
          <servlet-name>action</servlet-name>
          <servlet-class>org.apache.beehive.netui.pageflow.PageFlowActionServlet</servlet-class>
          <init-param>
          <param-name>config</param-name>
          <param-value>/_pageflow/struts-config.xml</param-value>
          </init-param>
          <init-param>
          <param-name>debug</param-name>
          <param-value>2</param-value>
          </init-param>
          <init-param>
          <param-name>detail</param-name>
          <param-value>2</param-value>
          </init-param>
          <load-on-startup>2</load-on-startup>
          </servlet>
          <servlet>
          <servlet-name>XmlHttpRequestServlet</servlet-name>
          <servlet-class>org.apache.beehive.netui.pageflow.xmlhttprequest.XmlHttpRequestServlet</servlet-class>
          </servlet>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.jpf</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>action</servlet-name>
          <url-pattern>*.do</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>XmlHttpRequestServlet</servlet-name>
          <url-pattern>*.xhr</url-pattern>
          </servlet-mapping>
          <servlet-mapping>
          <servlet-name>XmlHttpRequestServlet</servlet-name>
          <url-pattern>*.render</url-pattern>
          </servlet-mapping>
               <jsp-config>
          <taglib>
          <taglib-uri>render.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/render_taglib.jar</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/exesite.tld</taglib-uri>
          <taglib-location>/WEB-INF/exesite.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>netui-tags-template.tld</taglib-uri>
          <taglib-location>/WEB-INF/netui-tags-template.tld</taglib-location>
          </taglib>
               <taglib>
          <taglib-uri>netui-tags-databinding.tld</taglib-uri>
          <taglib-location>/WEB-INF/netui-tags-databinding.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>netui-tags-html.tld</taglib-uri>
          <taglib-location>/WEB-INF/netui-tags-html.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-bean.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-logic.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>/WEB-INF/struts-html.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/struts-adapter-html.tld</taglib-location>
          </taglib>
          <taglib>
          <taglib-uri>um.tld</taglib-uri>
          <taglib-location>/WEB-INF/lib/um_taglib.jar</taglib-location>
          </taglib>
          </jsp-config>
          </web-app>

Validation Problems Were Found

problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.>
<Aug 3, 2009 8:08:26 PM IST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean IMEAR. Error - weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>.
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>
<Aug 3, 2009 8:08:26 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249310306002' for task '0'. Error is: 'weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>'
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>
<Aug 3, 2009 8:08:26 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'IMEAR'.>
<Aug 3, 2009 8:08:26 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>
<Aug 3, 2009 8:08:27 PM IST> <Error> <J2EE> <BEA-160197> <Unable to load descriptor C:\shared\views\w108198_infomgt-1_0_new\col-ts_infomgt\infomgt\.metadata\.plugins\org.eclipse.core.resources\.projects\IMEAR\beadep\im_domain\IMEAR/META-INF/application.xml of module IMEAR. The error is weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.application.ApplicationDescriptor.getApplicationDescriptor(ApplicationDescriptor.java:311)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:174)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:72)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:88)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
.>
<Aug 3, 2009 8:08:27 PM IST> <Error> <Deployer> <BEA-149605> <Failed to create App/Comp mbeans for AppDeploymentMBean IMEAR. Error - weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>.
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>
<Aug 3, 2009 8:08:27 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249310306940' for task '1'. Error is: 'weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>'
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>
<Aug 3, 2009 8:08:27 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'IMEAR'.>
<Aug 3, 2009 8:08:27 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.management.DeploymentException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:189)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     Truncated. see log file for complete stacktrace
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
problem: cvc-complex-type.2.4c: Expected element 'module@http://java.sun.com/xml/ns/javaee' before the end of the content in element application@http://java.sun.com/xml/ns/javaee:<null>
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:234)
     at weblogic.descriptor.internal.MarshallerFactory$1.evaluateResults(MarshallerFactory.java:221)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:146)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:306)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     Truncated. see log file for complete stacktrace
>

It generally helps to include a little more in a question besides just the stack trace. Was it clear to you that this is reporting a problem with your "application.xml" file? The contents of this file would be very useful information.
The error message is saying that it expected to find a "module" element, and it didn't find it. Seeing as this is the principal element that is found in this file, I'm guessing you have almost nothing in this file.
You can see the schema for this file at [http://java.sun.com/xml/ns/javaee/application_5.xsd] (this is for JEE 5. I'm not sure whether the WebLogic version you're using (you've given no indication what version you're using) supports JEE 4 or JEE 5).

MBDOC Validation Problem

Dear all,
We are facing a problem regarding a customer record flow between SAP ECC and SAP CRM system.
Customer creation is taking place in ECC and downloading to SAP CRM system.
all customers created on yesterday have downloaded with out errors except 3 customer records.
I have checked in SMW01, it is showing the BUPA_MW_EXCHANGE010 error message with the MBDOC validation problem.
I don't know how to resolve this problem. all remaining customers are flowed perfectly where as these 3 customer records are only not flowing.
any of you please help me to resolve this problem, Your suggestions will be highly appreciated.
Thank you
Raghu ram.

Hi,
You are seeing the error because every BDoc brings Object data which gets validated using a validation FM in CRM Middleware.
Plz check if there is any info in the Bdoc regarding the incorrect entries ( data ) in your data ? If yes , plz maintain the entry in IMG using txn SPRO
To resolve this problem , plz recheck if you have imported all Customizting Objects correctly !!
Regards
Ritvij

XML validation problem

hi,
i am trying to validate an xml document against a schema document abnd am getting some strange validation errors. i am using xerces to parse. here are my java classes:-
//---------------------------------------- class Validation-------------------------------------------//
import org.apache.xerces.parsers.DOMParser;
public class Validation {
public static void main(String[] args)
try
DOMParser parser = new DOMParser();
parser.setFeature("http://xml.org/sax/features/validation", true);
parser.setProperty(
"http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation","country.xsd");
ErrorChecker errors = new ErrorChecker();
parser.setErrorHandler(errors);
parser.parse("country.xml");
} // end try
catch (Exception e)
System.out.print("Problem parsing the file.");
} // end catch
} // end main
} // end class Validation
//----------------------------------------- class ErrorHandler -----------------------------------------//
import org.xml.sax.*;
public class ErrorChecker implements ErrorHandler
public void warning(SAXParseException exception)
//Ignore warnings
public void error(SAXParseException e)
// A validity error.
System.out.println("Vaidation error: " + e.getMessage());
public void fatalError(SAXParseException e)
// A well-formedness error
System.out.println("Fatal error: " + e.getMessage());
} // end class ErrorChecker
and here is my xml document, called "country.xml":-
<?xml version="1.0"?>
<country
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="country.xsd">
<name>France</name>
<pop>59.7</pop>
</country>
and my schema, called "country.xsd":-
<?xml version="1.0"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="country">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string"/>
<xs:element name="pop" type="xs:decimal"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
and here are the validation errors that are caught when i try to parse the xml document:-
Vaidation error: Document is invalid: no grammar found.
Vaidation error: Document root element "country", must match DOCTYPE root "null".
could anyone please shed any light on these validation errors? any help much appreciated.
thanks,
ramsey

I managed to get it working with the DOM parser. Just in case anyone else has this problem in the future and checks this thread, here is the solution. The problem basically came down to me using
parser.setFeature("http://apache.org/xml/features/validation", true);
instead of
parser.setFeature("http://xml.org/sax/features/validation", true);
When you replace the word "xml" with "sax" in the above it seems to work. So, basically all you need is:-
// enable validation in pipeline
parser.setFeature("http://xml.org/sax/features/validation", true);
// set validator to schema validation
parser.setFeature("http://apache.org/xml/features/validation/schema", true);
And, if you haven't given the schema location inside the XML document itself, then you also need something like the following:-
// this feature needs to be set to true if the schema
// location is NOT hardcoded into the xml document
parser.setProperty("
http://apache.org/xml/properties/schema/external-noNamespaceSchemaLocation", "country.xsd");
Thanks for all your help dvohra09, you definitely pointed me in the right direction of looking into the setFeatures() method in more detail.

Problems with doctype

I found a problem where if a document is saved to a container with a doctype
using a public identifier it comes back using a system identifer that is the
same string as the public id. Here is what happens using an example from the
xhtml spec.
dbxml -V
Sleepycat Software: Berkeley DB XML 2.2.13: (December 19, 2005)
Sleepycat Software: Berkeley DB 4.3.29: (September 6, 2005)
dbxml> putdoc xhtml_1 '<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
</html>' s
Document added, name = xhtml_1
dbxml> get xhtml_1
1 documents found
dbxml> print
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html SYSTEM "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd" -//W3C//DTD XHTML 1.0 Strict//EN >
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
</html>
This happens on linux and windows.
Another problem seems to be that external access must be allowed even if the
container is not supposed to do validation. If external access is turned off
putting the document fails with an error saying that dbxml cannot resolve the
entity given by the DTD URL.
Let me know if I am doing something wrong or the answer is posted somewhere I missed.
Thanks for you help.
Jed Rifkin
[email protected]

Jed,
This is a known bug in 2.2.13. It's fixed in the development tree, but
there is no patch for 2.2.13. It can be worked around by using wholedoc
containers, if that's feasible.
Regards,
George

Xerces SAXParser validation problems

I'm using the Xerces 2 beta 3 SAXParser to validate an XML document but
it does not seem to raise a SAXParseException even though my XML is not valid.
Say I have the following DTD, example.dtd:
<?xml version='1.0' encoding='UTF-8' ?>
<!ELEMENT a (b)>
<!ELEMENT b (c)>
<!ELEMENT c (#PCDATA)>
Now, I have a well-formed XML document that is not valid because it clearly violates
the DTD above:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE class SYSTEM "example.dtd">
<a>
<c>Hello</c>
</a>
It is my understanding that the SAXParser validation should catch this invalid XML.
Why does it not raise any Exceptions?
From what I understood the only valid documents should contain 0 or more of the
following XML statements:
<c>Hello</c>
OR
<b>
<c>Hello</c>
</b
OR
<a>
<b>
<c>Hello</c>
</b>
</a>
Also, note that if I forget a tag, the parser behaves as expected and raises a SAXParseException that reads
'The element type "a" must be terminated by the matching end-tag "</a>'
i.e. <c>Hello
The only reason I mention this is to show that validation is set to true on the SAXParser.
Any help would be greatly appreciated. Thanks in advance.
KL

The problem I am have does not seem to be with the value of the
http://xml.org/sax/features/validation feature. I printed the value out after I set it and it is indeed set to true.
I was reading more about the feature (see below) and am now thinking the validation might not occur because the grammar might not be read in by the parser.
When that say "grammar" I assume they mean the DTD in my case. When they say "the document must specify a grammar," I assume that mean that my XML document must state the DTD to use in the DOCTYPE statement.
My XML document looks kind of like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE class SYSTEM "example.dtd" [
<!ENTITY % entities SYSTEM "7670Entities2.0.xml">
%entities;
]>
<a>
<b>
<c>Hello</c>
</b>
</a>
So have I specified the grammar correctly? Is there anyway to print out anything that will show that the grammar has indeed been read in?
http://xml.org/sax/features/validation
True:
Validate the document.
False:
Do not validate the document.
Default:
false
Access:
(parsing) read-only; (not parsing) read-write;
Note:
If this feature is set to true, the document must specify a
grammar. If this feature is set to false, the document may
specify a grammar and that grammar will be parsed but
no validation of the document contents will be performed.

AP Invoice Validation problem

Hi,
Invoice R12 (12.1.3)While trying to validate an AP Invoice getting the following error :
APP-SQL-10000: User-Defined Exception occurred in
AP_INVOICE_UTILITY_PKG.CALCULATE_VARIANCE<-AP_APPROVAL_MATC
HED_PKG.Exec_Matched_Variance_Checks<-AP_APPROVAL_PKG.Genera
te_Distributions<-AP_APPROVAL_PKG.Approval<-APXINWKB
with parameters (Distribution Id = 13113101)
while performing the following operations:
CALCULATE_VARIANCE - Close cursor invoice_dist_cursor
Hence, requesting if anyone of you have come cross this kind of problem in R12, AP invoice validation kindly post your valuable comments.
regards.
Arup

Hi,
Welcome to Communities.
Please review this note
R12: AP: Unable To Validate Freight Invoices Matched To Receipts Errors APP-SQL-10000 ORA:01403 (Doc ID 1350996.1)
Thanks
George

XML SAX dtd Validation Problem

Hi,
          I’m having problems getting an xml document to validate within Weblogic 8.1. I am trying to parse a document that references both a dtd and xsd. Both the schema and dtd reference need to be substituted so they use local paths. I specify the schema the parser should use and have created an entityResolver to change the dtd reference.
          When this runs as a standalone app from eclipse the file parses and validates without a problem. When deployed to the app server the process seems to be unable read the contents of the dtd. Its not that it cannot find the file (no FileNotFoundException is thrown but this can be created if I delete the dtd) rather it seems to find no declared elements.
          Initial thought was that the code didn’t have access to read the dtd from its location on disk, to check I moved the dtd to within the deployed war and reference as a resource. The problem still persists.
          Code Snippet:
          boolean isValid = false;
          try {
          // Create and configure factory
          SAXParserFactory factory = SAXParserFactoryImpl.newInstance();
          factory.setValidating(true);
          factory.setNamespaceAware(true);
          // To be notified of validation errors in the XML document,
          // add a custom error handler to the document builder
          PIMSFeedFileValidationHandler handler
          = new PIMSFeedFileValidationHandler();
          // Create and Configure Parser
          SAXParser parser = factory.newSAXParser();
          parser.setProperty(JAXP_SCHEMA_LANGUAGE, W3C_XML_SCHEMA);
          parser.setProperty(NAMESPACE_PROPERTY_KEY, getSchemaFilePath());
          // Set reader with entityResolver for dtd
          XMLReader xmlReader = parser.getXMLReader();
          xmlReader.setEntityResolver(new SAXEntityResolver(this.dtdPath));
          // convert file to URL, as it is a remote file
          URL url = super.getFile().toURL();
          // Open an input stream and parse
          InputStream is = url.openStream();
          xmlReader.setErrorHandler(handler);
          xmlReader.parse(new InputSource(is));
          is.close();
          // get the result of parsing the document by checking the
          // errorhandler's isValid property
          isValid = handler.isValid();
          if (!isValid) {
          LOGGER.warn(handler.getMessage());
          LOGGER.debug("XML file is valid XML? " + isValid);
          } catch (ParserConfigurationException e) {
          LOGGER.error("Error parsing file", e);
          } catch (SAXException e) {
          LOGGER.error("Error parsing file", e);
          } catch (IOException e) {
          throw new FeedException(e);
          return isValid;
          See stack trace below for a little more info.
          2005-01-28 10:24:09,217 [DEBUG] [file] - Attempting validation of file 'cw501205.wa1.xml' with schema at 'C:/pims-feeds/hansard/schema/hansard-v1-9.xsd'
          2005-01-28 10:24:09,217 [DEBUG] [file] - Entity Resolver is using DTD path file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/
          VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
          2005-01-28 10:24:09,227 [DEBUG] [file] - Creating InputSource at: file:C:/Vignette/runtime_services/8.1/install/common/nodemanager/VgnVCMServer/stage/pims-hansard/pims-hansard.war/WEB-INF/classes/com/morse/pims/cms/feed/sax/ISO-Entities.dtd
          2005-01-28 10:24:09,718 [WARN ] [file] - org.xml.sax.SAXParseException: Element type "Hansard" must be declared.
          org.xml.sax.SAXParseException: Element type "Session" must be declared.
          org.xml.sax.SAXParseException: Element type "DailyRecord" must be declared.
          org.xml.sax.SAXParseException: Element type "Volume" must be declared.
          org.xml.sax.SAXParseException: Element type "Written" must be declared.
          org.xml.sax.SAXParseException: Element type "WrittenHeading" must be declared.
          org.xml.sax.SAXParseException: Element type "Introduction" must be declared.
          … continues for all the elements in the doc
          2005-01-28 10:24:10,519 [DEBUG] [file] - XML file is valid XML? false
          2005-01-28 10:24:10,519 [WARN ] [file] - Daily Part file 'cw501205.wa1.xml' was not valid XML and was not processed.
          Has anybody seen this behavior before with weblogic and if so how have you resolved the issue.
          Thanks in Advance
          Adam

It looks like you clicked on "Post" before you got around to explaining your problem. I don't see any error messages or any description of what was supposed to happen and what happened instead.
Now, I don't know anything about XML Schema, but just guessing at how that unique name feature might be designed, and just guessing that your unique name is actually in the <userId> element, I would suggest that this:
<xsd:unique name="un_name">
<xsd:selector xpath="USER"/>
<xsd:field xpath="."/>
</xsd:unique> is at fault because it doesn't mention the <userId> element anywhere.

Validation Problem W/ DOCTYPE?!?

Similar Messages

Maybe you are looking for