[JBoss Seam] - Re: slink join and conversationID
by jacob.orshalick
"vanyatka" wrote : When I link a page to itself with s:link propagation="begin", then a new long-running conversation is created, but it has the different conversationID to the original one
If by the original one you mean the conversation that existed on the last page rendering, this behavior is expected. This is because as I said, Seam creates a temporary conversation on each request that only exists for the duration of the request. So, once the response is rendered, unless that conversation has been promoted to long-running, it will no longer be maintained (which is why you are seeing this behavior). The conversationId you are seeing in the outputText is gone (unless it was promoted).
On the next request (s:link propagation="begin") another temporary conversation is created (with the new id) and this conversation is promoted to long-running. It sounds like you should begin the long-running conversation the first time the page is accessed if you want to carry the SMPC. This can be accomplished in several ways: @Begin, through pages.xml action, etc.
I hope this helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088434#4088434
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088434
18 years, 7 months
[JBoss jBPM] - Re: Task list of specified actor
by kukeltje
for those of you who want a shorter (jbpm api and java api) and jbpm 3.2 compliant version (the example above is 3.1)
| String currentUser = getUser(request).getUsername();
|
| IdentityService is = jbpmContext.getServices().getIdentityService();
| org.jbpm.identity.User jbpmUser = is.getUserByName(currentUser);
|
| //create list of possible id's (this includes groups) that
| //the current user is a member of.
| List actorsList = new ArrayList(jbpmUser.getMemberships());
|
| // add user in case he is the sole pooled actor not via a group
| actorsList.add(user);
| List pooledTaskInstances = jbpmContext.getGroupTaskList(actorsList);
| List userTaskInstanceList = jbpmContext.getTaskList(currentUser);
| userTaskInstanceList.addAll(pooledTaskInstances);
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088433#4088433
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088433
18 years, 7 months
[JBoss Seam] - Re: Layering the code in Seam
by Grandfatha
If you create the EntityManager in the presentation layer and pass it down to the DAO layer, then I dont see no difference to invoking the method of EntityManager right inside you presentation bean.
Truely layered code would mean that you business code would not even know about an Entity Manager let alone your presentation code. Truely layered means, that the presentation bean calls a business method and gets a result and does not care about how this result is produced.
In my view, only the DAO class should have a dependency to the EntityManager IF you want to truely structure your code into independent layers. Thats great for maintenance and testing since each layer can swapped out or replaced by a different implementation without breaking e.g. the layers above.
But this flexibility in the long term is bought by a higher complexity and more code in the short term. Maybe you will even have to deal with "LazyInitializationException" again depending on how you work with the Entitymanager/Seam components.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088429#4088429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088429
18 years, 7 months
[JBoss Seam] - Re: slink join and conversationID
by vanyatka
"jacob.orshalick" wrote : Ok, so did you begin a long-running conversation with cid 1? By default, Seam is always going to create a conversation for the processing of a request, but you must promote that conversation to long-running if you want it to continue. join=true will start a long-running conversation if there is no long-running conversation to join.
The issue is that I'm not being able to promote a "regular" conversation to a long-running one while keeping the ID of the original conversation. When I link a page to itself with s:link propagation="begin", then a new long-running conversation is created, but it has the different conversationID to the original one, so I presume this means that it's become a different conversation, and what particularly worries me is that SMPC of the original conversation is lost.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088425#4088425
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088425
18 years, 7 months
[JBoss jBPM] - Re: write a web service to invoke a process
by burrsutter
This not specifically a web service for command API of jBPM but...
the JBoss ESB has implemented core jBPM 3.2.x which means you can expose jBPM APIs (deploy, create/start, signal, update vars) as JBoss ESB Services. JBoss ESB Services can be exposed to the outside world as JMS, FTP, File drop, WS, etc.
So for example, you can start a new process instance via an FTP event (e.g a new order arrives on our FTP server), signal the process instance via a WS and update the process vars via a JMS message. At least this is the goal and the code is in place, just requires more feedback from users.
Burr
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088424#4088424
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088424
18 years, 7 months