December 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - fail to persiste taskinstance variables from xhtml page

by apdo

I initially post this to the jbpm forum but I think it is more related to the jboss seam forum. In the thread of the jbpm forum I have written to consider that entries closed since I planned to create this entry in the seam forum. I have modified the todo example to add an xhtml form for the todo task. The todoform.xhtml follows. When I submit the form with "Done command" button, the description of the taskinstance is persisted in the database but not the variable1. The variable1 is created in the jbpm_variableinstance table but there is no value set (null). So what I have done is to use the @In in the todolist component and then on the todolist.done method I save the variable using TaskInstance.instance().setVariable("variable1", comments); However, I don't think it is the way to do thing with jsf-seam-jbpm integration. That is why even if I have found a workaround I am asking the question. Do you have an answer for that? Thanks Phong Here is my xhtml file that is that save de taskintance.description but not the taskInstance.variables['variable1']. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:rich="http://richfaces.org/rich"> Todo List <f:view> <h:form id="list"> <h:messages/> id: <h:outputText value="#{taskInstance.id}"></h:outputText> name: <h:outputText value="#{taskInstance.name}"></h:outputText> description:<h:inputText value="#{taskInstance.description}" style="width: 400"/> summary:<h:inputText value="#{taskInstance.variables['variable1']}" style="width: 400"/> <h:commandButton value="Update Items" action="update"/> <h:commandButton value="Done command" action="#{todoList.done}"/> </h:form> </f:view> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113535#4113535 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113535

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Newbie Problem with Exception handling and pages.xml

by sheadley3228

I am new with seam and require a little bit of guidance. I am trying to handle application wide exceptions through the use of pages.xml and the <exception class> tags. If I forceably thow an exception in my application for testing purpose, with the following tag in my pages.xml: <end-conversation/> <redirect view-id="/views/admin/error.xhtml"> Database access failed I get the following view which is incorrect: 500 Internal Server Error Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details. If I then use the following in my web.xml: <error-page> <error-code>500</error-code> /views/admin/error.xhtml </error-page> I get the correct page displayed. Why is this happenning? How could I maintain one place for all exceptions to be handled which allows all my exception messages to be shown? My enviornment is OC4J, Seam, RichFaces. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113528#4113528 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113528

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: FlushModeType.MANUAL in conversation

by kai222

The question behind my problem is: How do other developers validate certain user input against the database within a long-running conversation? Does nobody else have problems with transaction handling? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113527#4113527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113527

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - What is the timeline for 2.0.1?

by cpopetz

This bug: http://jira.jboss.org/jira/browse/JBSEAM-2357 is preventing me from dropping our code, so I'm curious what the timeline is for a seam release that contains its fix, or if I should patch 2.0.0GA locally with this change: http://fisheye.jboss.com/changelog/JBoss/jboss-seam?cs=MAIN:nrichards:200... Thanks, -Clint P.S. I'd love to join a mailing list where someone from jboss could send out "Oh, we just discovered seam 2.0.0 isn't thread safe." I wouldn't have wasted the past three days isolating the above bug. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113526#4113526 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113526

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Server.log and large tables

by hispeedsurfer

Hi, in my application I can call a link to output a large table in a seperate browser window. When I call this link the server.log grows up from 3.65 MB to 45 MB. The table is build with richfaces datatabel and subtables and ~260 rows What the reason for this server.log growing on large table. I don't see any helpful entries in the log. here a short cutting from server.log 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.contexts.Contexts] found in session context: reportDisplay | 2007-12-17 20:13:41,299 DEBUG [org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor] ++++ LongLivedSessionPropagationInterceptor | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preSetVariable.reportDisplay | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postSetVariable.reportDisplay | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.this | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.this | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.method | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.method | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,299 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.parameters | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.parameters | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.preSetVariable.org.jboss.seam.component | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.core.events | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.core.Events] Processing event:org.jboss.seam.postSetVariable.org.jboss.seam.component | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] trying to inject with hierarchical context search: facesMessages | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: org.jboss.seam.faces.facesMessages | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] trying to inject with hierarchical context search: entityManager | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.contexts.Contexts] found in conversation context: entityManager | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] trying to inject with hierarchical context search: geoMapData | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.contexts.Contexts] found in session context: geoMapData | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] instantiating Seam component: org.jboss.seam.web.parameters | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] initializing new instance of: org.jboss.seam.web.parameters | 2007-12-17 20:13:41,309 DEBUG [org.jboss.seam.Component] done initializing: org.jboss.seam.web.parameters | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113525#4113525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113525

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Seam - Redhat Studio -- How to persist multiple databases?

by codemonkey010101

We are building a system with Redhat Studio in Seam on JBoss. The database backend is Postgres 8.1. We need to create multiple databases, all with the same entity structure, but housing individual client's data. So, theoretically, I would like to use the same set of entity classes and connect them to multiple databases; all of which match the entity classes. I am not finding a lot of help of the web surrounding this problem. Thanks in advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113524#4113524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113524

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Why is it that

by alllle

If I specify the following: | @In(create=true, scope=XXXX-any scope here) | private MyEntityClass bean; | I get a Seam exception that the "create=true" is not valid with the explicit scope. I don't understand the reasoning behind it. I am thinking it is common for the following scenario in a wep app: 1. The Action component is in the Conversation scope. 2. The Action component contains an component attribute, this attribute is needed for page scope only. 3. This component attribute need to be injected, its properties is updated via form post. Therefore, it's desirable having this component attribute auto created in the Page scope when the Action component is called. But the above mentioned problem prevent me from doing this. Any explanation? TIA. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113522#4113522 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113522

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Trouble W/ NullPointerException

by nathandennis

pete,, i apologize. i know you have to be tired of telling people that. i found the rest of what i needed in some of your other post. | ReturnServerLocal host = (ReturnServerLocal) Component.getInstance("returnServer"); | not only did instantiating the object correctly fix my NPE,,, if fixed the log not working mystery... which when i think about it now,, makes really good sense that it didnt work without being properly wrapped. i have to say after four days of beating around the bush trying to figure out something so simple,, that was the sweetest infinite loop i have hung my app server with in a while. post your donate button and i'll buy you a beer. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113518#4113518 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113518

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Why is Authenticator.authenticate() called twice if it r

by b.reeve

Isn't this referring to http://jira.jboss.org/jira/browse/JBSEAM-2165 and it says it is fixed in CVS. Is it out in 2.0.0.GA? I am still having this issue in 2.0.0.GA. Could anyone please clarify. Thanks ! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113516#4113516 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113516

18 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Identity.loggedIn and Session expiring

by b.reeve

Thank you for the answers. anonymous wrote : | Not yet implemented. This is the best way to do what you are AFAICS. | Does this mean that there are plans for adding this to future release? anonymous wrote : | Null in JSF means stay on the same page. | But I am getting the page navigated according to some rule (defined in pages.xml) when the return type is null. | 1. Also, Is there a way I can disable Seam from adding the default seam messages to FacesMessage apart from giving a value for that key in the resource bundle? | | 2. Is there some way to do something like, | | pages.xml | | | <page view-id="/login.xhtml" > | | <navigation from-action="#{identity.login}" > | | <rule if="#{identity.loggedIn} > | | <evaluate="#{loginBean.navigation}" > | | <rule if-outcome="pageA" > | | <redirect view-id="/pageA.xhtml" /> | | </rule> | | <rule if-outcome="pageB" > | | <redirect view-id="/pageB.xhtml" /> | | </rule> | | <rule if-outcome="landing" > | | <redirect view-id="/index.xhtml" /> | | </rule> | | </evaluate> | | </rule> | | </navigation> | | </page> | | | | so that my evaluate would be evaluated only if certain condition is met and not always. | | Thanks again for helping! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4113514#4113514 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4113514

18 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2007