On 8 Nov 2004, at 18:53, Jeremy Boynes wrote:
I think we may be in violent agreement here :-)
I think we should add some type of collective entity, I just hesitate
to call it a Group as that tends to be associated with a specific
model ( a relatively static set of users and other groups). Call it
Davanum Srinivas wrote:
Intro email already posted :)
http://marc.theaimsgroup.com/?l=incubator-general&m=109994773621556&w=2
sorry, people that was a typing mistake on my end, I didn't want to send
email :-)
--
Stefano.
smime.p7s
Description: S/MIME Cryptographic Signature
Intro email already posted :)
http://marc.theaimsgroup.com/?l=incubator-general&m=109994773621556&w=2
-- dims
On Mon, 08 Nov 2004 16:02:46 -0500, Stefano Mazzocchi
<[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >Date: 2004-11-08T07:09:12
> >Editor: SteveForsyth <[EMAIL PROTECTE
[EMAIL PROTECTED] wrote:
Date: 2004-11-08T07:09:12
Editor: SteveForsyth <[EMAIL PROTECTED]>
Wiki: Incubator Wiki
Page: ApolloProposal
URL: http://wiki.apache.org/incubator/ApolloProposal
no comment
New Page:
= PROJECT PROPOSAL =
Apollo: A WS-Resource``Framework Reference Implement
Please peruse the three project proposals below for your consideration
as candidates for entry into the Apache Incubator. The text of the full
proposals have been posted to the Incubator wiki - their URLs are
indicated below.
Here is a summary of the proposals:
Apollo (http://wiki.apache.org/incu
[EMAIL PROTECTED] wrote:
On 8 Nov 2004, at 15:58, Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could
On 8 Nov 2004, at 15:58, Jeremy Boynes wrote:
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could
perform - they then grab
[EMAIL PROTECTED] wrote:
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could perform
- they then grab one ('locking it') and then execute the task o
Its very common with people workflow to assign a task to a group of
users (or a role) rather than assigning it to a specific individual
user. Then a user sees a list of all available tasks they could perform
- they then grab one ('locking it') and then execute the task or
releasing it back into
In an attempt to comprehend what the bindings are and how they work for
static versus EL types (static appears to be read-only, rather than a
static expression) I hacked up this extra test case which might be
interesting for others...
Index: NodeContextImplTestCase.java
I've attached a patch which fixes up the Task insert so that when you
assign a task to a user you can capture the TaskID for the task.
It also avoids the hacky try/catch solution to try update first and
only insert if that fails.
Index: TaskServiceImpl.java
=
11 matches
Mail list logo
