Thanks, Nathan!
I have update the javadoc at
http://concurrency-ee-spec.java.net/javadoc/ to capture what we have
discussed so far. I have also included some minor corrections in this
update. Classes that were updated includes:
ContextService
LastExecution
ManagedExecutorService
ManagedExecutors
ManagedScheduledExecutorService
ManagedTask (replacing Identifiable)
SkippedException
Regards
Anthony
On 12/18/12 12:25 PM, Nathan Rauh wrote:
> I agree - affinity only makes sense at the level of the
> ManagedExecutorService.
> At the per-task level, DISTRIBUTABLE=true/false as you suggested is good.
>
> Nathan Rauh
> ____________________________________________
> Software Engineer, WebSphere Application Server
> IBM Rochester Bldg 002-2 C111
> 3605 Highway 52N
> Rochester, MN 55901-7802
>
>
>
> From: Anthony Lai <anthony.lai_at_oracle.com>
> To: jsr236-experts_at_concurrency-ee-spec.java.net
> Date: 12/18/2012 12:02 PM
> Subject: [jsr236-experts] Re: On ManagedTaskListener related APIs in
> MES and MSES
> ------------------------------------------------------------------------
>
>
>
> Thanks for pointing that out. :-)
>
> I was looking at this execution property and was wondering if
> DISTRIBUTABLE_WITH_AFFINITY hint applies to a single task. It applies to
> a MES or MSES so tasks submitted to the MES or MSES would be routed to
> the same application server process. But what does it mean on a task?
> Should a task simply provide hint saying whether it can be run in a
> remote process. So instead of having:
>
> Property name: RUN_LOCATION
> Possible values: LOCAL, DISTRIBUTABLE, DISTRIBUTABLE_WITH_AFFINITY
>
> Does it make sense to have this instead:
>
> Property name: DISTRIBUTABLE
> Possible values: "true", "false"
>
> Regards
> Anthony
>
> On 12/18/12 7:25 AM, frowe_at_us.ibm.com wrote:
> > I'm assuming that you'll correct the typo in
> > "DISRTIBUTABLE_WITH_AFFINITY
> > " when updating spec...
>
>