[JBoss-user] [JBoss Seam] - Re: Seam + Portal
I have committed the docs on how to deploy the example. Important to note my comments on the manual configuration needed after using the installer: http://jira.jboss.com/jira/browse/JBAS-3069 This issue is being addressed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936887#3936887 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936887 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
I just committed working portal support on Sunday eve. It is not yet documented. You have to use SeamPortletPhaseListener, not SeamPhaseListener to account for the differences in the JSF request lifecycle in a portal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936487#3936487 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936487 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
Actually, Here is some more details - it looks like the SeamPhaseListener doesn't get called for RESTORE_VIEW in the portlet case. It goes straight to RENDER_RESPONSE in portlet, but always through RESTORE_VIEW in the regular web page case. Is there similar behavior for the JSF based admin pages ? Is this a bug in MyFacesGenericPortlet ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936465#3936465 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936465 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
Guys, It seems that Portal's requests don't go through the org.jboss.seam.contexts.Lifecycle.class's beginRequest method. As a result, none of Seam's TLS caches get initialized with contexts. I don't know if this is a dependency on JSF that isn't compatible with JSR-168 (i.e. should this lifecycle processing happen in a portal ?) At any rate - Assuming I can find a portlet hook to do this initialization on, should I continue with this or do we know already that the Portal will not provide enough info to initialize the caches ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936462#3936462 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936462 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
Guys - the latest HEAD build I did has a dependency on portlet-api-lib.jar as it checks whether it is writing a portlet or servlet response (code to write conversation id in response). Looks like some good progress is being made in getting Seam and Portal to well together. All I can say is thank you. But I do have a couple of questions: - is portlet-api-lib.jar supposed to be packaged with or Seam applications ? Is it a prerequisite of the container ? I ask because I can't seem to get the classloader to pick it up when I package it in WEB-INF/lib of my Seam WAR file. My second question is - how can I help ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936060#3936060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936060 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
I will be showing Gavin what I have done, tomorrow. Then he can decide whether we roll the changes in to Seam or create a separate branch. I will update this post, once the decision has been made. I look forward to any help I can get from you in this. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934431#3934431 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934431 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
Mr. Russo, Is there a branch available for your change to Seam ? I'd like to recreate your work and assist the investigation if possible. Colin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934400#3934400 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934400 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
I have modified the SeamPhaseListener so every phase is entered only once by adding a ThreadLocal innerclass to preserve order and ignore dupe calls. So no need to uncomment the StartupServletContextblabla anymore - as it leads to an ugly trace on deploy anyway. Now, that allows everything to work nicely outside of the portal, when deployed alongside the portal. However, inside the portal, it is still failing and it appears all context objects are null: | 13:43:28,609 ERROR [MyFacesGenericPortlet] The portlet threw an exception | java.lang.IllegalStateException: No active session context | at org.jboss.seam.core.LocaleSelector.instance(LocaleSelector.java:119) | at org.jboss.seam.jsf.SeamViewHandler.calculateLocale(SeamViewHandler.java:24) | at org.apache.myfaces.application.jsp.JspViewHandlerImpl.createView(JspViewHandlerImpl.java:130) | at org.jboss.seam.jsf.SeamViewHandler.createView(SeamViewHandler.java:35) | at org.jboss.seam.jsf.SeamViewHandler.createView(SeamViewHandler.java:35) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:320) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:298) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:380) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) | at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:167) | at javax.portlet.GenericPortlet.render(GenericPortlet.java:407) | This is hapenning after the portal dispatched to myfacesportlet. Tracing the code, I see all context objects are null. The SeamPhaseListener is never hit, nor is the contexts.Lifecycle class. Obviously I'm missing some data on how Seam handles its context creation, and why inside a portal environment all of it is nulled. I was thinking it was the portal's redirect response, but it appears that not even the initial request is being processed correctly in Seam. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931699#3931699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3931699 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
Try to get a stack trace inside of the constructor and print it to the console. Simply create a new Exception and call printStackTrace(), you don't even need to throw it. Maybe that will help to identify the calls... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931596#3931596 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3931596 --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] [JBoss Seam] - Re: Seam + Portal
It is as I suspected that Tomcat deploys it the first time, and then the portal comes along and reads in the config again. This is normal and expected and happens with most JSF apps that have the portlet descriptors included. Normally, this is not a problem, but I suspect that having two SeamPhasListeners registered is indeed a causing issues on execute. As with the link I posted in the original post, theres usually not an issue with two instances of the same listener being registered, but Seam's case may differ. Now, taking Thomas' suggestions I did find a way to shortcircuit this behaviour, by commenting the myfaces StartupServletContextListener. Myfaces complains on deploy, but the seam app will still work outside of the portal with no problems. Inside of the portal, we fail: | 10:44:02,843 ERROR [MyFacesGenericPortlet] The portlet threw an exception | java.lang.IllegalStateException: No active session context | at org.jboss.seam.core.LocaleSelector.instance(LocaleSelector.java:119) | at org.jboss.seam.jsf.SeamViewHandler.calculateLocale(SeamViewHandler.java:24) | at org.apache.myfaces.application.jsp.JspViewHandlerImpl.createView(JspViewHandlerImpl.java:130) | at org.jboss.seam.jsf.SeamViewHandler.createView(SeamViewHandler.java:35) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:320) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.nonFacesRequest(MyFacesGenericPortlet.java:298) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.facesRender(MyFacesGenericPortlet.java:380) | at org.apache.myfaces.portlet.MyFacesGenericPortlet.doView(MyFacesGenericPortlet.java:266) | at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:167) | at javax.portlet.GenericPortlet.render(GenericPortlet.java:407) | at org.jboss.portal.portlet.PortletContainer.invokeRender(PortletContainer.java:552) | at org.jboss.portal.portlet.PortletContainer.dispatch(PortletContainer.java:464) | at org.jboss.portal.server.app.ComponentInvocation.dispatch(ComponentInvocation.java:79) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:142) | at org.jboss.portal.core.aspects.component.TransactionInterceptor.invoke(TransactionInterceptor.java:69) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.core.aspects.component.HeaderInterceptor.invoke(HeaderInterceptor.java:48) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.server.aspects.component.CacheInterceptor.invoke(CacheInterceptor.java:169) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.server.aspects.component.ModesInterceptor.invoke(ModesInterceptor.java:86) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.server.aspects.component.WindowStatesInterceptor.invoke(WindowStatesInterceptor.java:85) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.portlet.aspects.component.SessionPostDispatchInterceptor.invoke(SessionPostDispatchInterceptor.java:82) | at org.jboss.portal.server.app.ComponentInterceptor.invoke(ComponentInterceptor.java:37) | at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:132) | at org.jboss.portal.server.aspects.component.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:127) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.jboss.portal.server.servlet.CommandServlet.doGet(CommandServlet.java:101) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli
