Difference between wlexpress and wlserver (config.xml) - Weblogic
This is a discussion on Difference between wlexpress and wlserver (config.xml) - Weblogic ; Hello,
com.bea.plateng.domain.TemplateBuilder's output seems to be interpreted
differently on WL Express, but WL Server is happy with it. The difference is
with the custom security providers. Any ideas?
2004-05-27 12:43:59,202 ERROR [runScript]
com.bea.plateng.domain.TemplateBuilder - unable to parse config.xml
org.xml.sax.SAXException: unable ...
-
Difference between wlexpress and wlserver (config.xml)
Hello,
com.bea.plateng.domain.TemplateBuilder's output seems to be interpreted
differently on WL Express, but WL Server is happy with it. The difference is
with the custom security providers. Any ideas?
2004-05-27 12:43:59,202 ERROR [runScript]
com.bea.plateng.domain.TemplateBuilder - unable to parse config.xml
org.xml.sax.SAXException: unable to find FieldDescriptor for
'com.encorus.pwm3.management.auth.userpass.UPAuthe nticator' in
ClassDescriptor of SecurityType
at
org.exolab.castor.xml.UnmarshalHandler.startElemen t(UnmarshalHandler.java:97
3)
at
org.apache.xerces.parsers.SAXParser.startElement(S AXParser.java:1340)
at
org.apache.xerces.validators.common.XMLValidator.c allStartElement(XMLValidat
or.java:1284)
at
org.apache.xerces.framework.XMLDocumentScanner.sca nElement(XMLDocumentScanne
r.java:1806)
at
org.apache.xerces.framework.XMLDocumentScanner$Con tentDispatcher.dispatch(XM
LDocumentScanner.java:1182)
at
org.apache.xerces.framework.XMLDocumentScanner.par seSome(XMLDocumentScanner.
java:381)
at
org.apache.xerces.framework.XMLParser.parse(XMLPar ser.java:1098)
at
org.exolab.castor.xml.Unmarshaller.unmarshal(Unmar shaller.java:463)
at
org.exolab.castor.xml.Unmarshaller.unmarshal(Unmar shaller.java:552)
at
com.bea.plateng.domain.DomainHelper.unmarshallXML( DomainHelper.java:691)
at
com.bea.plateng.domain.TemplateBuilder.parseConfig (TemplateBuilder.java:206)
at
com.bea.plateng.domain.TemplateBuilder.parseDomain Template(TemplateBuilder.j
ava:465)
at
com.bea.plateng.domain.TemplateBuilder.buildDomain Template(TemplateBuilder.j
ava:1163)
at
com.bea.plateng.domain.script.ScriptExecutor.readT emplate(ScriptExecutor.jav
a:344)
at
com.bea.plateng.domain.script.ScriptParser$StateMa chine.processRead(ScriptPa
rser.java:536)
at
com.bea.plateng.domain.script.ScriptParser$StateMa chine.execute(ScriptParser
..java:442)
at
com.bea.plateng.domain.script.ScriptParser.parseAn dRun(ScriptParser.java:171
)
at
com.bea.plateng.domain.script.ScriptParser.execute (ScriptParser.java:134)
at
com.bea.plateng.domain.script.ScriptParser.execute (ScriptParser.java:98)
at
com.bea.plateng.wizard.domain.silent.tasks.RunScri ptTask.execute(RunScriptTa
sk.java:214)
at
com.bea.plateng.wizard.silent.tasks.AbstractSilent Task.run(AbstractSilentTas
k.java:32)
at java.lang.Thread.run(Thread.java:536)
2004-05-27 12:43:59,202 ERROR [runScript]
com.bea.plateng.domain.TemplateBuilder - failed to parse the template!
-
Re: Difference between wlexpress and wlserver (config.xml)
Please disregard the post. The XML parser component of WL Server and WL
Express is different, and that was the cause of the problem we encountered.
(Using WL Server 8.1 SP2 and WL Express 8.1 SP1)
Might be a target for correction, however. 
Gabor
"Moos Gabor" wrote in message
news:40b5d403$1@mktnews1...
> Hello,
>
> com.bea.plateng.domain.TemplateBuilder's output seems to be interpreted
> differently on WL Express, but WL Server is happy with it. The difference
is
> with the custom security providers. Any ideas?
>
> 2004-05-27 12:43:59,202 ERROR [runScript]
> com.bea.plateng.domain.TemplateBuilder - unable to parse config.xml
>
> org.xml.sax.SAXException: unable to find FieldDescriptor for
> 'com.encorus.pwm3.management.auth.userpass.UPAuthe nticator' in
> ClassDescriptor of SecurityType
>
> at
>
org.exolab.castor.xml.UnmarshalHandler.startElemen t(UnmarshalHandler.java:97
> 3)
>
> at
> org.apache.xerces.parsers.SAXParser.startElement(S AXParser.java:1340)
>
> at
>
org.apache.xerces.validators.common.XMLValidator.c allStartElement(XMLValidat
> or.java:1284)
>
> at
>
org.apache.xerces.framework.XMLDocumentScanner.sca nElement(XMLDocumentScanne
> r.java:1806)
>
> at
>
org.apache.xerces.framework.XMLDocumentScanner$Con tentDispatcher.dispatch(XM
> LDocumentScanner.java:1182)
>
> at
>
org.apache.xerces.framework.XMLDocumentScanner.par seSome(XMLDocumentScanner.
> java:381)
>
> at
> org.apache.xerces.framework.XMLParser.parse(XMLPar ser.java:1098)
>
> at
> org.exolab.castor.xml.Unmarshaller.unmarshal(Unmar shaller.java:463)
>
> at
> org.exolab.castor.xml.Unmarshaller.unmarshal(Unmar shaller.java:552)
>
> at
> com.bea.plateng.domain.DomainHelper.unmarshallXML( DomainHelper.java:691)
>
> at
>
com.bea.plateng.domain.TemplateBuilder.parseConfig (TemplateBuilder.java:206)
>
> at
>
com.bea.plateng.domain.TemplateBuilder.parseDomain Template(TemplateBuilder.j
> ava:465)
>
> at
>
com.bea.plateng.domain.TemplateBuilder.buildDomain Template(TemplateBuilder.j
> ava:1163)
>
> at
>
com.bea.plateng.domain.script.ScriptExecutor.readT emplate(ScriptExecutor.jav
> a:344)
>
> at
>
com.bea.plateng.domain.script.ScriptParser$StateMa chine.processRead(ScriptPa
> rser.java:536)
>
> at
>
com.bea.plateng.domain.script.ScriptParser$StateMa chine.execute(ScriptParser
> .java:442)
>
> at
>
com.bea.plateng.domain.script.ScriptParser.parseAn dRun(ScriptParser.java:171
> )
>
> at
> com.bea.plateng.domain.script.ScriptParser.execute (ScriptParser.java:134)
>
> at
> com.bea.plateng.domain.script.ScriptParser.execute (ScriptParser.java:98)
>
> at
>
com.bea.plateng.wizard.domain.silent.tasks.RunScri ptTask.execute(RunScriptTa
> sk.java:214)
>
> at
>
com.bea.plateng.wizard.silent.tasks.AbstractSilent Task.run(AbstractSilentTas
> k.java:32)
>
> at java.lang.Thread.run(Thread.java:536)
>
> 2004-05-27 12:43:59,202 ERROR [runScript]
> com.bea.plateng.domain.TemplateBuilder - failed to parse the template!
>
>