[
https://issues.apache.org/jira/browse/SHINDIG-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547493#comment-13547493
]
Ryan Baxter commented on SHINDIG-1892:
--------------------------------------
James I will close it for now and you can reopen it if you determine that it is
really shindig causing the problem.
> Shindig throws a ClassCastException in JBOSS over xercesImpl
> ------------------------------------------------------------
>
> Key: SHINDIG-1892
> URL: https://issues.apache.org/jira/browse/SHINDIG-1892
> Project: Shindig
> Issue Type: Bug
> Environment: Running the Liferay Portal on JBOSS EAP 5.1 and HSQL.
> Reporter: James Lefeu
> Priority: Blocker
> Attachments: shindig exception.txt
>
>
> For my development, I'm using the Shindig server.
> When I place the shindig-server-2.0.2.war file in the JBOSS deploy directory,
> for a hotdeploy of the server, I get an ClassCastException related to
> XercesImpl.
> I find similar issues documented here:
> http://xerces.apache.org/xerces2-j/faq-xni.html#faq-2
> http://www.ibm.com/developerworks/websphere/library/techarticles/0310_searle/searle.html
> The Liferay Portal does not throw exceptions as it has been configured like
> this:
> http://in.liferay.com/web/global.engineering/wiki/-/wiki/Quality+Assurance+Main/JBoss+EAP+Startup
> But, I'm wondering if there's a configuration needed for the Shindig server
> for it to work in JBOSS 5.1
> Or, is there a bug in Shindig?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
