What is the Java EE Service Engine?
The Java EE Service Engine acts as a bridge between GlassFish and the JBI environment for web service providers and web service consumers deployed in GlassFish.
- EJBs/Servlets packaged as web services and deployed on GlassFish are transparently exposed as service providers in JBI Enviroment
- Java EE Components - EJBs/Servlets can consume services exposed in JBI enviroment using the Java EE service engine without being aware of the underlying binding/protocol such as SOAP, JMS etc exposing the web service.
- In-process communication between components of application server and JBI components to increase request processing speed.
- Any component that is plugged into ESB can directly communicate with Java EE applications. For example, clients of various bindings such as SOAP or JMS can communicate with web services developed using Java EE via open-esb because of Java EE Service Engine.
Using the EE SE
Please post questions on the OpenESB mailing list
. File bugs in the OpenESB issue tracker and
in the GlassFish issue tracker. Put all the problem information in one issue, and create a placeholder issue in the other issue tracker. Reference the issue from the placeholder issue. Use the EESE category.
Evolution of the EE SE
The EE SE is feature complete, and no new changes have been planned.
- Girish Patil
- Vikas Awasthi
- Bhavanishankara Sapaliga
- Roderico Cruz
- Edward Chou
Developing the EE SE
Sources are in the GlassFish repository