[JBoss Seam] - Re: Beginning conversations in @Factory methods
by petemuir
anonymous wrote :
| My problem is that the next action after a list is displayed is often displaying a selection from the list. As I understand things, on a postback the DataTable component will reaccess the DataModel through EL variable resolution, then indicate the row selected. If the DataModel exists in a long running conversation, that will be returned and it'll work great. If the conversation wasn't started when the original DataModel was generated I'd imagine a new DataModel will be created on the postback (through the @Factory method) and it could be different from what was rendered to the user. Does that make sense?
|
Yes, but if it's in PAGE scope then on 'postback' the datamodel will be available through EL so won't be recreated. Your scenario is a big reason for PAGE scope :)
anonymous wrote :
| 2.1.3. Page context
|
| The page context allows you to associate state with a particular instance of a rendered page. You can initialize state in your event listener, or while actually rendering the page, and then have access to it from any event that originates from that page. This is especially useful for functionality like clickable lists, where the list is backed by changing data on the server side. The state is actually serialized to the client, so this construct is extremely robust with respect to multi-window operation and the back button.
|
A page action would work as well I think. Remember you can disable conversation propogation for actions and therefore @Begin would start a new conversation. This is equivalent to to your 'stripping the conversation Id'.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957473#3957473
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957473
20 years, 2 months
[JBoss jBPM] - Web console failing
by brado
I have deployed the jbpm.sar and jbpm.war built from the jbpm 3.1.1 starter's kit (along with required libraries to my best knowledge) into JBoss 4.0.4. JBoss starts up without any errors. When I access the webapp at http://localhost:8080/jbpm, I receive the normal home page fine, without any errors. However, if I try to click on the "Home", "Administration", or "Monitoring" links on the left hand side, I get a 500 response, with an ugly stack trace. Checking in the jboss log, I see the following error:
2006-07-12 11:40:18,078 ERROR [javax.faces.webapp.UIComponentTag] Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml.
| 2006-07-12 11:40:18,125 DEBUG [org.jbpm.JbpmContext] closing JbpmContext
| 2006-07-12 11:40:18,125 DEBUG [org.jbpm.svc.Services] closing service 'authentication': org.jbpm.security.authentication.DefaultAuthenticationService@723c42
| 2006-07-12 11:40:18,125 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jbpm].[jsp]] Servlet.service() for servlet jsp threw exception
| java.lang.NullPointerException
| at javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:615)
| at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:217)
| at org.apache.myfaces.taglib.core.ViewTag.doStartTag(ViewTag.java:71)
| at org.apache.jsp.home_jsp._jspx_meth_f_view_0(home_jsp.java:102)
| at org.apache.jsp.home_jsp._jspService(home_jsp.java:76)
| at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
| at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
| at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.AuthenticationFilter.doFilter(AuthenticationFilter.java:55)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.web.JbpmContextFilter.doFilter(JbpmContextFilter.java:83)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jbpm.webapp.filter.LogFilter.doFilter(LogFilter.java:59)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| 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.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.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)
|
I noticed that the "Select User:" drop down which asks you to log in is empty, containing no users. So I checked my database, and noticed that there were no users, groups, or permissions in the database. Perhaps this is fine, but I wasn't sure, so I thought I'd mention it.
Anyway, does anyone have any idea why this error is occurring, and how to rectify it? And also, what is the generally accepted way to populate the users, groups, and permissions tables -- is this something typically done in the web console (I can't tell because I haven't gotten it to work completely yet), or is this initially done by manually putting values in the database?
Thanks for your help.
Brad
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957465#3957465
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957465
20 years, 2 months