[JBoss Seam] - By clicking every row of dataTable, show Popup to edit it's
by dashti
I'm making an application with Jboss Seam , but now I have a problem.
I have a page that contains a dataTable and in every row of dataTable I have a link that selects that row and you can edit hat row when you click on it. (something like what seam-gen produces when you use generate-entities). and also making new records in the pop up window.
but now I don't like the navigation through pages and backing to the first page again, because my users may be confused.
now I want to pop up a window to do this approach.
I have 2 ways:
1. using the rich:ModalPanel but using this, I should make a modal panel for every row of dataTable and it increases the size of the page. (very bad !!)
but if I had a solution that could load the content of needed rich:ModalPanel at runtime , my problem will be solved. Is there a way to solve this?
and also, if I don't think about the page size, I don't know how to load the page I want, with my desired parameters.
2. using a pop up window, but the problem of this approach is, when popping up a windows, first I don't know how to tell that page to open with my parameters to edit the desired record. and second, I don't know how can I tell parent page, when the child page is closed and refresh some part of the page (maybe dataTable) when the edit is completed.
Please help me!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107398#4107398
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107398
18 years, 7 months
[EJB 3.0] - Re: ManyToMany relationship do not work properly
by fla83tn
Now I'm able to see the Exception..the problem occurs when I try to register a user to a source that does not exist yet. The Exception throwed is:
| javax.ejb.EJBTransactionRolledbackException: org.hibernate.HibernateException: this instance does not yet exist as a row in the database
| [java] at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87)
| [java] at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
| [java] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77)
| [java] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106)
| [java] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
| [java] at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:214)
| [java] at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:184)
| [java] at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:81)
| [java] at $Proxy203.createSources(Unknown Source)
| [java] at nc.session.facade.admin.AdminSessionFacadeBean.addSourceToUser(AdminSessionFacadeBean.java:191)
|
I also found a patch to this...I entered this lines in the code:
logger.debug("New Source (not found in Db): adding user to it");
| src=SourceAssembler.createSource(s);
| logger.debug("Source created: "+src.getSourceId()+", "+src.getUrl());
| manager.persist(src);
| manager.flush();
| list = new ArrayList<User>();
| list.add(user);
| src.setUsers(list);
| manager.persist(src);
|
However, why do I need to make the source persistent and synching with the database before adding user to it?? In all examples the persist method is called only once and without any flush!!
Any suggest?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107397#4107397
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107397
18 years, 7 months
[JBoss jBPM] - evaluation question: changing a running process and undo fun
by iamniche
Hello,
I am currently evaluating jbpm as a process workflow engine for a custom workflow involving many actors and actions.
my specific questions are:
a) Is it possible to change the process definition of a currently running process? If I re-deploy a process that has already started, what are the implications for a currently running process if i) a new task is added BEFORE the current node OR ii) a new task/action is added AFTER the current node
b) Is it possible to do a multiple 'Undo' function to roll-back to a certain point in the process (say, for example, if a mistake occurred in input earlier in the process)
c) Are there any examples of jbpm being used in the real-world scenarios?
d) Is it possible to accept input BY-REPLY i.e. from an email reply, if, for example, input is required from an actor. As I understand it, this would require some custom action code to parse an incoming email, use some kind of messaging system, then consume a JMS and update the process accordingly. I don't want to re-invent the wheel here!
Any replies to these queries would be most gratefully recieved.
Many thanks.
Cheerio,
Nic Hemley
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4107394#4107394
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4107394
18 years, 7 months