You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "DK (JIRA)" <de...@myfaces.apache.org> on 2010/05/23 04:18:16 UTC
[jira] Issue Comment Edited: (PORTLETBRIDGE-127)
FacesContext.getCurrentInstance().getExternalContext().getSessionMap().remove()
does not seem to work wth the bridge
[ https://issues.apache.org/jira/browse/PORTLETBRIDGE-127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848171#action_12848171 ]
DK edited comment on PORTLETBRIDGE-127 at 5/22/10 10:16 PM:
------------------------------------------------------------
I should have mentioned from the beginning that beans are managed via Spring IoC. That was not an issue in the previous scenarios I described - a) pure web app, b) portlet deployed with IBM JWL Portlet Bridge 3.1.3, but I guess it might be a root cause (?).
Do you still want me to dump thread stack?
EL on the first ("login") page looks like this:
<ui:composition template="/templates/page.xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:p="http://primefaces.prime.com.tr/ui"
xmlns:this="http://fsa.ed.gov/riatpoc">
<ui:define name="body">
<p:panel id="wizard" styleClass="wizard">
<f:facet name="header">
<h:outputText value="#{app.step.stepTitle}" />
</f:facet>
<h:panelGrid rowClasses="s1row" columns="2" columnClasses="wfcol1,wfcol2,wfcol3">
<this:text prompt="The student's Social Security Number (9 digits):"
id="ssn" field="#{key.ssn}"
required="true"
regExp="\\d{9}" regExpMessage="Please provide SSN in 9 digit format" />
<this:text prompt="The student's full last name:"
id="lastName" field="#{key.lastName}"
required="true" />
<this:text prompt="The student's first name:"
id="firstName" field="#{key.firstName}"
required="true" />
<h:outputText value="* The student's Date of Birth (mm/dd/yyyy):" />
<h:panelGroup>
<p:calendar id="birthDate" value="#{key.birthDate}" readOnlyInputText="false"
required="true" requiredMessage="The student's Date of Birth (mm/dd/yyyy): required"
pattern="MM/dd/yyyy" converterMessage="Please provide date in mm/dd/yyyy format"
navigator="true"/>
 <p:message for="birthDate" />
</h:panelGroup>
<h:outputText value="* Your Password:" />
<h:panelGroup>
<h:inputSecret id="password" value="#{key.password}"
required="true" requiredMessage="Your Password: required" />
 <p:message for="password" />
</h:panelGroup>
<h:outputText value="* - required fields" />
</h:panelGrid>
<div class="navPanel">
<h:commandButton value="Next >>" action="#{app.onLogin}"
style="float:right" />
</div>
<br/> <!-- Add some white space at the panel bottom -->
</p:panel>
</ui:define>
</ui:composition>
was (Author: dkroot):
I should have mentioned from the beginning what beans are managed via Spring IoC. That was not an issue in the previous scenarios I described - a) pure web app, b) portlet deployed with IBM JWL Portlet Bridge 3.1.3, but I guess it might be a root cause (?).
Do you still want me to dump thread stack?
EL on the first ("login") page looks like this:
<ui:composition template="/templates/page.xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:p="http://primefaces.prime.com.tr/ui"
xmlns:this="http://fsa.ed.gov/riatpoc">
<ui:define name="body">
<p:panel id="wizard" styleClass="wizard">
<f:facet name="header">
<h:outputText value="#{app.step.stepTitle}" />
</f:facet>
<h:panelGrid rowClasses="s1row" columns="2" columnClasses="wfcol1,wfcol2,wfcol3">
<this:text prompt="The student's Social Security Number (9 digits):"
id="ssn" field="#{key.ssn}"
required="true"
regExp="\\d{9}" regExpMessage="Please provide SSN in 9 digit format" />
<this:text prompt="The student's full last name:"
id="lastName" field="#{key.lastName}"
required="true" />
<this:text prompt="The student's first name:"
id="firstName" field="#{key.firstName}"
required="true" />
<h:outputText value="* The student's Date of Birth (mm/dd/yyyy):" />
<h:panelGroup>
<p:calendar id="birthDate" value="#{key.birthDate}" readOnlyInputText="false"
required="true" requiredMessage="The student's Date of Birth (mm/dd/yyyy): required"
pattern="MM/dd/yyyy" converterMessage="Please provide date in mm/dd/yyyy format"
navigator="true"/>
 <p:message for="birthDate" />
</h:panelGroup>
<h:outputText value="* Your Password:" />
<h:panelGroup>
<h:inputSecret id="password" value="#{key.password}"
required="true" requiredMessage="Your Password: required" />
 <p:message for="password" />
</h:panelGroup>
<h:outputText value="* - required fields" />
</h:panelGrid>
<div class="navPanel">
<h:commandButton value="Next >>" action="#{app.onLogin}"
style="float:right" />
</div>
<br/> <!-- Add some white space at the panel bottom -->
</p:panel>
</ui:define>
</ui:composition>
> 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.
-
You can reply to this email to add a comment to the issue online.