[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856198#action_12856198
]
DK commented on PORTLETBRIDGE-127:
----------------------------------
* I use session scope, here is how beans are configured in Spring
applicationContext.xml:
<bean id="hibernatePersistenceService"
class="gov.ed.fsa.riatpoc.persistence.hibernate.HibernatePersistenceService"
scope="singleton" />
<bean id="app" class="gov.ed.fsa.riatpoc.Application" scope="session">
<property name="persistenceService">
<ref local="hibernatePersistenceService" />
</property>
</bean>
<bean id="key" class="gov.ed.fsa.riatpoc.ApplicationKey" scope="session"/>
* I confirm that this is an issue in compatibility with Spring IoC 2.5.6.SEC01.
I rolled back bean configuration to pure JSF and that resolved the issue.
* I did have a code workaround, so I am not in a dire need of solution. If you
want me to investigate this problem further, I can do a debugging exercise with
Spring. It would probably make sense to upgrade to the latest, 3.0.2 Spring
release since 2.5.6 is history. It would take me some time to upgrade and then
do this exercise, especially given the fact that I've finished this project and
I'll be doing it in my spare time.
>
> FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove()
> does not seem to work wth the bridge
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-127
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-127
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Affects Versions: 1.0.0-beta
> Environment: WebSphere Portal 6.1.5 running on Windows XP Pro
> MyFaces Portal Bridge 1.0.0.beta2
> Reporter: DK
> Attachments: Thread Dumps.log
>
>
> I've been working on a POC application with PrimeFaces, deploying as a web
> app first, and then portalizing it and deploying to WebSphere Portal.
> When deployed as a web app, the following method removing JSF managed bean
> worked fine:
> public static void discardManagedObject(String objName) {
>
> FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove(objName);
> }
> It also seemed to work on the previous iteration of this app with IBM JWL
> Portlet Bridge 3.1.3.
> When deployed as a portlet with MyFaces Bridge 1.0.0.beta2, this does not
> seem to work anymore and the logic in code had to be changed as a workaround.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
