Jeremy, Ok, having a brief look at the JCA work manager API, these are my thoughts
1. The high-level API are very similar, a manager and optional support for listeners for callbacks 2. There are subtle differences between the actual semantics of work allocation. JCA work manager supports both blocking (doWork), asynchronous (scheduleWork) , blocking start/asynchronous completion (startWork), whereas a JSR 237 it is always asynchronous (scheduleWork). JSR 237 supports a different semantic for blocking calls using wautForAll and waitForAny. Do you have any thoughts on what features you want to support in the API. Ta Meeraj -----Original Message----- From: Meeraj Kunnumpurath Sent: 07 July 2006 15:55 To: 'tuscany-dev@ws.apache.org' Subject: RE: Support for callbacks >> JSR-237 was not part of 1.4 True, I don't think it is part of JEE 5 either. Weblogic 9.1 does provide an implementation though. >> I don't think we should provide a full implementation of 237 I have an implementation that supports local work using concurrent utilities (Doug Lea), I can port it to use the Java 5 API. >> It would be good to make the API similar enough to javax.resource and 237 so that we can provide version that delegate through to implementations provided by a managed environment. I will have a look at the JCA work manager API and see what commonalities we can abstract. Ta Meeraj -----Original Message----- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: 07 July 2006 15:41 To: tuscany-dev@ws.apache.org Subject: Re: Support for callbacks On Jul 7, 2006, at 7:13 AM, Meeraj Kunnumpurath wrote: > > Also, we may find other use cases for using a work manager for > deferred executions. Do we have any view on how the runtime can use a > work manager from a managed environment when Tuscany is run in a > managed environment. I think app servers that support work managers, > may be making them available through the JNDI namespace or something > else. > It's going to depend on the app server :-( In J2EE1.4, app servers were required to provide a work manager to connectors through the javax.resource API; the one we are using from Geronimo is the one they use to support that. JSR-237 was not part of 1.4 although some of the major vendors did provide implementations; I am not sure how portable they are. I don't think we should provide a full implementation of 237 but something similar but lighter weight (for example, I don't think we will need remote work, we may not need transactional work). It would be good to make the API similar enough to javax.resource and 237 so that we can provide version that delegate through to implementations provided by a managed environment. -- Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message has been checked for all email viruses by MessageLabs. ***************************************************** You can find us at www.voca.com ***************************************************** This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX This message has been checked for all email viruses by MessageLabs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
