[JBoss Seam] - Problem with seam and session invalidation.
by sreeraaman
Hi All,
>From a secured page, I am trying to logout a user by providing a Logout Button
| <h:commandButton id="logout" value="Logout" action="#{logoutAction.logout}"></h:commandButton>
|
The logoutAction Managed Bean is configured as follows in the faces-config.xml:
| <managed-bean>
| <managed-bean-name>logoutAction</managed-bean-name>
| <managed-bean-class>managedbeans.LogoutAction</managed-bean-class>
| <managed-bean-scope>session</managed-bean-scope>
| </managed-bean>
|
Inside the logout method, following is the code:
| public String logout(){
| String result ="reLogin";
| HttpServletRequest request= (HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest();
| Principal userPrincipal = request.getUserPrincipal();
| String userName = userPrincipal.getName();
| System.out.println("Current Logged In user is :" + userName) ;
| HttpSession session = (HttpSession)FacesContext.getCurrentInstance().getExternalContext().getSession(false);
| session.invalidate();
| return result;
| }
|
The navigation rule for the result "reLogin" is configured as follows in faces-config.xml:
| <navigation-case>
| <from-outcome>reLogin</from-outcome>
| <to-view-id>/TestLogout.jsp</to-view-id>
| <redirect />
| </navigation-case>
|
The application is configured for FORM authentication as follows:
| <error-page>
| <error-code>400</error-code>
| <error-code>404</error-code>
| <location>/index.jsp</location>
| </error-page>
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>Whole site</web-resource-name>
| <url-pattern>/secure/*</url-pattern>
| </web-resource-collection>
| <auth-constraint>
| <role-name>*</role-name>
| </auth-constraint>
| <user-data-constraint>
| <transport-guarantee>NONE</transport-guarantee>
| </user-data-constraint>
| </security-constraint>
|
|
| <login-config>
| <auth-method>FORM</auth-method>
| <realm-name>MyDomain</realm-name>
|
| <form-login-config>
| <form-login-page>/Login.seam</form-login-page>
| <form-error-page>/authorization-error.seam</form-error-page>
| </form-login-config>
|
| </login-config>
|
However, on clicking on the Logout button from the secured page, I get the following error:
2006-11-02 16:58:44,253 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/kr-intWeb].[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
java.lang.IllegalStateException: No active application scope
at org.jboss.seam.core.Init.instance(Init.java:48)
at org.jboss.seam.jsf.SeamNavigationHandler.handleNavigation(SeamNavigationHandler.java:29)
at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
at javax.faces.component.UICommand.broadcast(UICommand.java:106)
at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
Please Help.
regards
Sriraman.
anonymous wrote :
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982646#3982646
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982646
19Â years, 6Â months
[JBoss Seam] - JBoss seam Backbase integration
by dilshat
I have been trying hard to integrate the Backbase (AJAX) with JBoss seam with no success. I will be very grateful if you can give me a hint about solving the problem I have encountered.
I have copied all the necessary backbase jar files, and integrated the configuration content in the web.xml and faces-config.xml.
Due to the requirements of Backbase, I had to update the myfaces jar files in the jbossweb-tomcat55.sar\jsf-libs with those in the myfaces-1.1.4 (latest).
Then I added some backbase codes in the pages, hoping to see some results. However, Backbase tags in the pages are not rendered (ignored), and produced an empty content for the backbase code section in the page, although there is no any exception/error thrown.
So as the next option I can think of, I tried to run the Backbase example as they are. Because they are the jps files, I have to comment out the the following facelet configuration from the faces-config.xml (generated by jboss-gen)
| <application> <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
| </application>
|
And also I have commented out the following configuration from the web.xml:
|
| <context-param>
| <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
| <param-value>.xhtml</param-value>
| </context-param>
|
|
Then, when I tried to run the the following backbase example page
| <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
| <%@ taglib uri="http://www.backbase.com/bjs/core" prefix="bjs" %>
|
| <f:subview id="main">
| <bjs:view>
| <bjs:loadBundle basename="com.backbase.bjs.form.language" var="msg" />
|
| <bjs:window show="true" resize="all" label="#{msg.appTitle}"
| style="left:10%;top:40px;width:770px;height:44em;">
|
| <bjs:panelSet rows="2em *">
|
| <bjs:panelSet cols="90% *">
| <bjs:panel style="overflow:hidden"/>
| <bjs:panel style="overflow:hidden">
|
| <bjs:commandLink actionListener="#{locale.changeLocale}"
| action="#{locale.reloadMainPanel}" destinationId="index">
| <bjs:graphicImage url="#{msg.languageFlag}"/>
| </bjs:commandLink>
|
| </bjs:panel>
| </bjs:panelSet>
|
| <bjs:panel style="overflow:hidden">
|
| <bjs:navPanel style="width:100%">
| <bjs:navPanelItem itemLabel="#{msg.personaldetails}"
| url="billing.jsp" binding="#{panel.billing}"/>
| <bjs:navPanelItem itemLabel="#{msg.billingaddress}" disabled="true"
| url="billingaddress.jsp" binding="#{panel.billingaddress}"/>
| <bjs:navPanelItem itemLabel="#{msg.shipping}" disabled="true"
| url="shipping.jsp" binding="#{panel.shipping}"/>
| <bjs:navPanelItem itemLabel="#{msg.shippingaddress}" disabled="true"
| url="shippingaddress.jsp" binding="#{panel.shippingaddress}"/>
| <bjs:navPanelItem itemLabel="#{msg.shippingmethod}" disabled="true"
| url="shippingmethod.jsp" binding="#{panel.shippingmethod}"/>
| <bjs:navPanelItem itemLabel="#{msg.payment}" disabled="true"
| url="payment.jsp" binding="#{panel.payment}"/>
| <bjs:navPanelItem itemLabel="#{msg.send}" id="send-item" selectListener="#{panel.selectReview}"
| url="send.jsp" binding="#{panel.review}" />
| </bjs:navPanel>
|
| </bjs:panel>
| </bjs:panelSet>
| </bjs:window>
| </bjs:view>
| </f:subview>
|
|
When I tried to run the page, it produced the following exception:
| javax.servlet.ServletException: The absolute uri: http://java.sun.com/jsf/core cannot be resolved in either web.xml or the jar files deployed with this application
| org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:58)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
|
| root cause
|
| javax.servlet.ServletException: The absolute uri: http://java.sun.com/jsf/core cannot be resolved in either web.xml or the jar files deployed with this application
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:152)
| com.backbase.bjs.webapp.filter.UploadFilter.doFilter(Unknown Source)
| org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30)
| org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
|
| root cause
|
| javax.faces.FacesException: The absolute uri: http://java.sun.com/jsf/core cannot be resolved in either web.xml or the jar files deployed with this application
| org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:422)
| org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234)
| com.backbase.bjs.application.BackbaseViewHandler.renderView(Unknown Source)
| org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
| javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
| com.backbase.bjs.webapp.filter.UploadFilter.doFilter(Unknown Source)
| org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:30)
| org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:45)
| org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
|
|
|
I can see that that myfaces-impl-1.1.4.jar exist in the jbossweb-tomcat55.sar\jsf-libs directory, and it does contains myfaces_core.tld, which defines the taglib uri http://java.sun.com/jsf/core.
So I am really puzzled, do I need to copy that tld files into my web application and referenced it in my web.xml?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982639#3982639
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3982639
19Â years, 6Â months