I am looking to use EJB 3.0 embeddable in a new project and wanted to validate some of my architectural assumptions before I recommend it. I am primarily interested in the constraints of the embeddable solution.
I am building a n tier based architecture with a thick Eclipse RCP based GUI, with an embeddable EJB 3.0 client component that handles communications/transactions/local persistence between the Eclipse GUI and the JEE server tier on the client machine.
RMI and JMS are the two current protocols we need, however, even the JMS communication would be serialized objects and not XML/SOAP messaging for now.
The communication between the GUI and the embedded container on the client machine would always be local, however, the embedded container would need to be able to pick messages off of JMS queues on a remote JMS server and communicate with remote EJBs on behalf of the client. Will I have any problems with this? I read somewhere that the micro container/embeddable EJB 3 container can't instantiate remote interfaces?
Also, am I confusing the micro-container and the embeddable EJB 3.0 container? Would appreciate some answers.