[
https://issues.jboss.org/browse/RF-12896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilia Vassilev updated RF-12896:
-------------------------------
Attachment: modules.zip
> Richfaces TopicsContext.lookup() returns null after redeployment when
> Richfaces is deployed as a module in JBoss EAP 6
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-12896
> URL: https://issues.jboss.org/browse/RF-12896
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2.3.Final
> Reporter: Ilia Vassilev
> Attachments: jboss-as-helloworld-rf.war, modules.zip, RichBean.java
>
>
> Our application uses Richfaces push functionality and makes a call to
> lookup the TopicsContext in the constructor of one of a backing bean. The
> code looks like this below. This works fine when Richfaces is packaged in the
> war, however when we extract the richfaces jars into a module and have our
> applications declare a module dependency, there is an issue when we redeploy
> the application. It works fine when JBoss is first started, but if we
> redeploy the application while JBoss is running, we are getting a
> NullPointerException in our application because TopicsContext.lookup() is
> returning null.
> @PostConstruct
> public void postContruct() {
> TopicsContext topicsContext = TopicsContext.lookup();
> if(topicsContext == null)
> log(" - topicsContext is NULL");
> pushTK = new TopicKey(PUSH_TOPIC);
> // this will fail if topicsContext is null (NPE)
> topicsContext.getOrCreateTopic(pushTK);
> }
--
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
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
