Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Difference between wlexpress and wlserver (config.xml)

0 views
Skip to first unread message

Moos Gabor

unread,
May 27, 2004, 7:41:54 AM5/27/04
to
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.UPAuthenticator' in
ClassDescriptor of SecurityType

at
org.exolab.castor.xml.UnmarshalHandler.startElement(UnmarshalHandler.java:97
3)

at
org.apache.xerces.parsers.SAXParser.startElement(SAXParser.java:1340)

at
org.apache.xerces.validators.common.XMLValidator.callStartElement(XMLValidat
or.java:1284)

at
org.apache.xerces.framework.XMLDocumentScanner.scanElement(XMLDocumentScanne
r.java:1806)

at
org.apache.xerces.framework.XMLDocumentScanner$ContentDispatcher.dispatch(XM
LDocumentScanner.java:1182)

at
org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanner.
java:381)

at
org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1098)

at
org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.java:463)

at
org.exolab.castor.xml.Unmarshaller.unmarshal(Unmarshaller.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.parseDomainTemplate(TemplateBuilder.j
ava:465)

at
com.bea.plateng.domain.TemplateBuilder.buildDomainTemplate(TemplateBuilder.j
ava:1163)

at
com.bea.plateng.domain.script.ScriptExecutor.readTemplate(ScriptExecutor.jav
a:344)

at
com.bea.plateng.domain.script.ScriptParser$StateMachine.processRead(ScriptPa
rser.java:536)

at
com.bea.plateng.domain.script.ScriptParser$StateMachine.execute(ScriptParser
.java:442)

at
com.bea.plateng.domain.script.ScriptParser.parseAndRun(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.RunScriptTask.execute(RunScriptTa
sk.java:214)

at
com.bea.plateng.wizard.silent.tasks.AbstractSilentTask.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!


Moos Gabor

unread,
May 27, 2004, 11:38:14 AM5/27/04
to
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" <gabor...@fathomtechnology.com> wrote in message
news:40b5d403$1@mktnews1...

0 new messages