Hello everyone, Thinking about using camel inside JEE container. Breaking JEE compliance with regard to thread management, writing to disk &c. invalidates the JBOSS EAP support contract available to the project I'm working on.
For example, would it be possible to integrate the camel-core and camel-cdi into an EAR file, creating the camel routes in the camel context while maintaining JEE compliance, and moving built-in or custom components which may not be JEE compliant into resource adaptors? So transport based components would typically not be JEE compliant and could use a JEE WorkManager to request threads, whereas components doing data transformations, could be run within an EJB-JAR and could be implemented via stateless session beans for example. Moving everything including camel into a resource adapter means, that any components created need to worry about solving concurrency and scalability problems themselves rather than utilizing the container solutions for these things. Any guidance on this would be much appreciated. -- View this message in context: http://camel.465427.n5.nabble.com/Is-camel-cdi-component-JEE-compliant-tp5743179.html Sent from the Camel - Users mailing list archive at Nabble.com.
