I'm trying to integrate a CAS 2.0.12 release with the newest Confluence 3.0.1
on Red Hat Enterprise Linux Server release 5.3 with the 0.5.3 Soulwing.org
client.
It looks like all the software is talking to each other but I'm get an error
page out of Confluence after the authentication.
org.soulwing.cas.client.ProtocolViolationException:
org.jdom.input.JDOMParseException: Error on line 1: The prefix "cas" for
element "cas:serviceResponse" is not bound.
at
org.soulwing.cas.client.jdom.JdomProtocolHandlerImpl.getJdomDocument(JdomProtocolHandlerImpl.java:93)
caused by: org.jdom.input.JDOMParseException: Error on line 1: The prefix "cas"
for element "cas:serviceResponse" is not bound.
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:468)
caused by: org.xml.sax.SAXParseException: The prefix "cas" for element
"cas:serviceResponse" is not bound.
at
org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
Following the stack trace shows that the error is not caused in the soulwing
code but down in the xerces code and looks to be a config issue with CAS.
What causes an element prefix not bound error?
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
