Experience with using Java EE Restlet's TaskService in an application server? <p>Has anyone used Restlet's TaskService in a Java EE app (deployed in Tomcat, GlassFish, etc)?</p> <p>Is using it going against Java EE's specifications? How does Restlet deal with it when the server/container maintains the thread pool and NOT go against the Java EE spec of not instantiating your own threads in a container managed application?</p> <p>Or are you forced to used Spring and/or interface with CommonJ's WorkManger interface for asynchronous processing?</p> <p>PS: FYI, TaskService basically wraps the ExecutorService of Java 6 - but it's suggested to not used that in an application server context. However, the Java EE version of Restlet does seem to have this service and was wondering if using it would violate the Java EE specs or is a strict no-no or is in fact doable or should one fallback to Spring/CommonJ</p>