[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-06-20 Thread [EMAIL PROTECTED]
We're looking into it. CVS builds fine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056091#4056091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056091 ___ jboss-user mail

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-06-20 Thread bsmithjj
the seam nightly builds are still 'stuck' on 06.14.2007 as the last build - any chance the nightly builds will resume being posted regularly? Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056002#4056002 Reply to the post : http://www.jboss.com

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-06-16 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : This is done in CVS, Brad, please try it out! Ok - it will take me a few days to review this issue and try this out. Thanks, Brad View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054957#4054957 Reply to the post : http://www.jboss

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-06-15 Thread [EMAIL PROTECTED]
This is done in CVS, Brad, please try it out! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4054935#4054935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4054935 ___ jboss-use

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-30 Thread avbentem
"petemuir" wrote : Then wire it up | | | | |... | | | | This works great for some process definitions, but I cannot get this to work with sub-processes. When I start some process that immediately delegates to some sub-process, then a ProcessInstance is injec

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-27 Thread avbentem
"kukeltje" wrote : afaik, jBPM 3.2 already is able to do something like autostart I could only find 16.4.8. task-node, which states: anonymous wrote : create-tasks - attribute - optional {yes|no|true|false}, default is true. Can be set to false when a runtime calculation has to determine which o

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread kukeltje
guys, what about jbpm being able to store a view-id in the processdefinition with a task? Currently jbpm has some forms.xml file which does kind of what is described here in the pages.xml. Besides that, afaik, jBPM 3.2 already is able to do something like autostart. I'll look into that tomorro

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread avbentem
"petemuir" wrote : Then wire it up | | | | |... | | | | Thanks, sounds good, I'll give it a try. "petemuir" wrote : In fact, can you create a JIRA issue for both a task selector and a way of auto-starting tasks - we can probably wrap it up in @CreateProcess /

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread petemuir
oic, sorry, I misread what you are doing. You should be able to wrap all this up on a page action - something like TaskFinder public String autoStart() { |TaskInstance taskInstance = getSingleTaskInstance(); |if (taskInstance != null) { | // Associate the task and process |

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread avbentem
"petemuir" wrote : assuming the actor has only one task assigned is a *big* one Of course, and indeed I'm not assuming an actor only has a single task assigned. So, for example, when a human actor logs into some website then indeed a list of tasks will often be very appropriate. However, when a

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread petemuir
I think the code for auto-starting tasks is an area which is extremely use-case specific (assuming the actor has only one task assigned is a *big* one) so should be implemented on a case-by-case basis. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030512#403

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-22 Thread avbentem
Actually, I think one day I also might want to start a task as soon as one assigns it to oneself, and show the appropriate page right away. In the DVD Store example the following is used: | : | | : | After clicking the button above, the new assigned task is listed in #{t

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-21 Thread avbentem
Ok, now that Gavin gave a nice combination of @StartTask and pages.xml, I wonder if something similar could be done using the value returned by @CreateProcess, somehow also forcing @StartTask to be triggered? Now, how to explain this... In the Todo example we've got: @CreateProcess(definition =

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : (1) Why not use the jbpmContext component, instead of creating your own context? | (2) Since you create the processInstance, you must associate it with the Seam contexts, by doing BusinessProcess.instance().setProcessId(...). | | I think if you do both of those,

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
"bsmithjj" wrote : "[EMAIL PROTECTED]" wrote : Of course, if you created it yourself via some other mechanism, *you* will have to associate it will the conversation using BusinessProcess.instance().setProcessId( processInstance.getId() ). | | | | Seam isn't magic. Seam only knows about

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
(1) Why not use the jbpmContext component, instead of creating your own context? (2) Since you create the processInstance, you must associate it with the Seam contexts, by doing BusinessProcess.instance().setProcessId(...). I think if you do both of those, things will work nicely View the or

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : Of course, if you created it yourself via some other mechanism, *you* will have to associate it will the conversation using BusinessProcess.instance().setProcessId( processInstance.getId() ). | | Seam isn't magic. Seam only knows about processes it creates or retr

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
In our application, a user may create a 1-N entities we call AccessRequests. In the SFSB method which is invoked by the user on submit, we create a loop to create each AccessRequest and create a ProcessInstance with that AccessRequest's id as a process variable. In this particular use case, w

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
Of course, if you created it yourself via some other mechanism, *you* will have to associate it will the conversation using BusinessProcess.instance().setProcessId( processInstance.getId() ). Seam isn't magic. Seam only knows about processes it creates or retrieves. If you get it yourself, by g

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
So how is it created. If it was created using @CreateProcess then it will be associated with the current conversation, and it will be available to the action handler. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030044#4030044 Reply to the post : http://w

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
Another EJB (yes a seam component) has created the process instance - then, based on certain business conditions, the process gets signaled through the tasks until we arrive at this particular state (node). On entry into the state, this ActionHandler fires (I posted the XML for this state node

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
What exactly is driving jBPM here? What causes the event to fire? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030039#4030039 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030039

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
Oops! My bad on the logger - I blindly accepted IDEA's suggestion to import commons logging. Anyway, what the heck is in scope when this fires? I thought that the ProcessInstance for which this ActionHandler is firing should be so, I injected ProcessInstance and apparently it's not... |

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread avbentem
"avbentem" wrote : import org.jboss.seam.log.Log; | | : | | @Logger | | private Log log; ...and you know you can then use: log.info("EntityManager (em) -> #0", em); Saves some String concatenation when the message is somehow suppressed by the logging setup. Arjan. View the origina

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread avbentem
"bsmithjj" wrote : Caused by: java.lang.IllegalArgumentException: Could not set field value by reflection: AutoProvisionerBean.log on: com.evergreen.accesscontrol.impl.AutoProvisionerBean with value: class org.jboss.seam.log.LogImpl | I guess your Java imports still refer to some non-Seam lo

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
This trial didn't go so well | | | | | | | | | | | @Local | public interface AutoProvisioner { | | String provisionAccess(); | | } | | @Stateless | @Name("autoProvisioner") | public class Au

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : anonymous wrote : It would be ideal if jBPM Handlers (ActionHandler, DecisionHandler, etc.) could be first class Seam components and have Seam intercept execute() invokations and @Inject/@Outject resources. | | What I'm saying is that any Seam component can be an

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : It would be ideal if jBPM Handlers (ActionHandler, DecisionHandler, etc.) could be first class Seam components and have Seam intercept execute() invokations and @Inject/@Outject resources. What I'm saying is that any Seam component can be an action handler or decision handler!

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread petemuir
"[EMAIL PROTECTED]" wrote : strange. there is an exact test case for this kind of expression evaluation. where the description doesn't start with #{ | | if there is any specific details on how i can reproduce. I was probably wrong ;) I can't reproduce, sorry :( anonymous wrote : it wou

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : anonymous wrote : No, it's not a Seam component (no @Name(...)) annotation - does that work? I mean if I put @Name on my custom ActionHandlers, DecisionHandlers, will Seam inject resources into them on invokation of the execute(ExecutionContext executionContext) metho

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread petemuir
"avbentem" wrote : But that might not be such a huge advantage at all: the jPDL XSD often accepts xsd:any, so probably allows for you additional viewId attribute without any changes. And one might also add Seam EL in the process definition, which makes them Seam-specific as well. I didn't have

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
"petemuir" wrote : The only issues I'm aware of are more JBPM than Seam | | * JBPM could do with better/more EL interpretation - for example you can't do as it only uses the EL interpreter if the string starts with #{ | strange. there is an exact test case for this kind of expression e

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread avbentem
"petemuir" wrote : I prefer to navigate to another page, and let that page set itself up (pages.xml or @Create) - fits the pages.xml style better imo. ...and earlier you wrote: "petemuir" wrote : I worked around this by extending task instance, and adding a viewId property. Then, in the startTas

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread petemuir
"[EMAIL PROTECTED]" wrote : I always assumed that you would typically need to write some code when starting work on a task, but I guess that's not necessarily true. I prefer to navigate to another page, and let that page set itself up (pages.xml or @Create) - fits the pages.xml style better imo

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
"bsmithjj" wrote : Oh yeah - thanks for the TaskSelector sample above - I think we can use one or more of those too! So maybe I should generalize it a bit and make it a built-in component. I always assumed that you would typically need to write some code when starting work on a task, but I gues

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : No, it's not a Seam component (no @Name(...)) annotation - does that work? I mean if I put @Name on my custom ActionHandlers, DecisionHandlers, will Seam inject resources into them on invokation of the execute(ExecutionContext executionContext) methods? No, of course not, Seam

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
Oh yeah - thanks for the TaskSelector sample above - I think we can use one or more of those too! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029903#4029903 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029903

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
anonymous wrote : Was this ActionHandler a Seam component? Again, I don't understand the scenario, nor why Seam was trying to close transactions that don't exist. Sounds very strange to me. No, it's not a Seam component (no @Name(...)) annotation - does that work? I mean if I put @Name on my

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread avbentem
Gavin, you type a lot faster than I do :-) I was ready to respond to your posts two times now, but each time you already replied again before I hit submit. Thanks! "[EMAIL PROTECTED]" wrote : What you want is to navigate from a list of *all kinds of tasks*, to the specific page for the task, wit

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : I also got stuck in a situation where some code I inherited, a jBPM ActionHandler, used Seam's ComponentgetInstance(...) to look up a SFSB and/or SLSB and invoke a method. In this case, we were regularly having issues with Seam trying to close managed resources - NO TRANSACTION

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : Easier to put custom variables on a task (this is currently a pita, you have to declare custom taskinstances, assginment handlers) Pete, I don't understand this one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029873#4029873 Reply to t

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
Oh, perhaps I understand now. What you want is to navigate from a list of *all kinds of tasks*, to the specific page for the task, without using multiple tasks lists. Is that all? Well, thats completely trivial: @Name("taskSelector") | public class TaskSelector | { | | @In TaskInst

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
anonymous wrote : our internal collective inexperience with JBoss I mean anonymous wrote : jBPM View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029866#4029866 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029866

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
"[EMAIL PROTECTED]" wrote : If you want the jBPM+Seam integration to improve, then you have to tell us exactly *what* limitations you are running into. I currently have only 9 open business process related issues in JIRA, most of which are definitely extremely minor, and only one of which came f

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : I need to show an actor a list of all owned processes, Define "owned". AFAIK, jBPM processes are not "owned" by an actor. If you mean all processes for which the actor has an open task, you can write a query to do this using: jbpmContext.getSession().createQuery() If you

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread petemuir
The only issues I'm aware of are more JBPM than Seam * JBPM could do with better/more EL interpretation - for example you can't do as it only uses the EL interpreter if the string starts with #{ * Easier to put custom variables on a task (this is currently a pita, you have to declare custom t

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
anonymous wrote : So: one cannot somehow use annotations or some configuration to specify what to do when a specific task is signaled by the actor, right? In other words: using annotations Seam can signal jBPM that a task is started or completed when some Java code is executed, but Seam has no m

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread [EMAIL PROTECTED]
If you want the jBPM+Seam integration to improve, then you have to tell us exactly *what* limitations you are running into. I currently have only 9 open business process related issues in JIRA, most of which are definitely extremely minor, and only one of which came from a user (you). In fact,

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
anonymous wrote : But you're still happily using Seam with jBPM? Happy? Honestly, I think the Seam + jBPM hype in the early days of Seam (winter-spring 2006) was a bit over hyped and I don't think it receives enough attention by the Seam team. I think part of the problem is a lot of the feat

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread avbentem
"bsmithjj" wrote : We've used jBPM and Seam a lot. [..] You'll probably find that you need to implement custom jBPM ActionHandler, DecisionHandler, etc. [..] figuring out and managing the resources (JbpmContext, EntityManager, etc.) shared between your custom jBPM code and your Seam components

[jboss-user] [JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?

2007-03-20 Thread bsmithjj
We've used jBPM and Seam a lot. It turns out the integration works great for the simplest cases, however, for issues like anonymous wrote : | So: one cannot somehow use annotations or some configuration to specify what to do when a specific task is signaled by the actor, right? You'll proba