[
https://issues.apache.org/jira/browse/SHINDIG-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13547485#comment-13547485
]
James Lefeu commented on SHINDIG-1892:
--------------------------------------
Yes. Sorry about that.
This one should be public:
http://www.liferay.com/community/wiki/-/wiki/Main/JBoss+tips
Also, by manually putting the jboss-classes.xml in the war file of my portlet
(a portlet which wraps around Shindig) and putting a similar jboss-classes.xml
in the ROOT.war/WEB-INF directory, I was able to get it so that it didn't throw
the classCastException. But, It now fails to deploy with the following console
output:
22:47:46,713 INFO [TomcatDeployment] deploy, ctxPath=/opensocial-portlet
22:47:46,911 WARNING [config] Unable to process deployment descriptor for contex
t '/opensocial-portlet'
22:47:46,912 INFO [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/
opensocial-portlet'
Copying 1 file to K:\Dev\liferay\Git\CE\jboss-eap-5.1\jboss-as\server\default\
deploy\opensocial-portlet.war
Deleting directory C:\Users\JAMESL~1\AppData\Local\Temp\20130108224735453
22:49:54,640 WARN [loggerI18N] [com.arjuna.ats.internal.jta.recovery.xarecovery
1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAEx
ception: Error trying to connect to provider java:/DefaultJMSProvider, XAExcepti
on.XAER_RMERR
I've been inspecting my web.xml file in the *.war to see if something is wrong
there.
It deploys with no problem on Tomcat 7 though.
It's possible that this failure to deploy is not a problem with shindig, but a
problem with my portlet, though.
I originally thought it to be caused by Shindig because that output occurs when
I put the shindig-server-2.0.2.war file in the deploy directory of JBOSS 5.1
All my other applications are able to deploy without a problem, so I thought
that maybe this could be a shindig issue.
At this point, it's looking much less like a shindig issue and more like a
configuration issue.
If you want to cancel this ticket, or put it on hold for now, that's fine with
me.
I'm still debugging the issue and hope to come to a resolution soon.
> 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
