Scott, Executor is apart of the backport.util.concurrrent.jar, as James referred to in a previous posting.
For more information regarding the back port, feel free to check out: http://www.mathcs.emory.edu/dcl/util/backport-util-concurrent/ Andrew -----Original Message----- From: Scott Luttenberg [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 8:22 AM To: [email protected] Subject: RE: [servicemix-user] JBI Client Example Help? Got that included. Found a few others that I needed (ActiveMQ, and Jenks) but now I run into: EDU/oswego/cs/dl/util/concurrent/Executor Am I doing something wrong? Should this be so painful? It would VERY helpful to have all of these jars packaged up into a single Servermix Client API jar file! I am trying to make a list of all the things I encountered. This might be helpful to those who want to use the JBI API to invoke messages in SM. Scott -----Original Message----- From: James Strachan [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 08, 2005 8:05 AM To: [email protected] Subject: Re: [servicemix-user] JBI Client Example Help? On 8 Nov 2005, at 13:49, Scott Luttenberg wrote: > OK - past that one. How about > edu/emory/mathcs/backport/java/util/concurrent/atomic/AtomicBoolean ? backport.util.concurrrent.jar James ------- http://radio.weblogs.com/0112098/ --------------------------------------------------------------------------------------------------------- This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited. All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment. ---------------------------------------------------------------------------------------------------------
