欢迎大家赞助一杯啤酒🍺 我们准备了下酒菜：Formal mathematics/Isabelle/ML, Formal verification/Coq/ACL2, C++/F#/Lisp
Java EE Service Engine
来自开放百科 - 灰狐
（版本间的差异）
| （未显示1个用户的1个中间版本） | |||
| 第1行： | 第1行： | ||
| − | Java EE Service Engine acts as a bridge between GlassFish and | + | Java EE Service Engine acts as a bridge between GlassFish and [[Open ESB]] environment for web service providers and web service consumers deployed in GlassFish. It provides numerous benefits including the following : |
[[Image:JBI-SE_Bridge.jpg|thumb|right|]] | [[Image:JBI-SE_Bridge.jpg|thumb|right|]] | ||
| 第9行： | 第9行： | ||
https://glassfish.dev.java.net/javaee5/jbi-se/ServiceEngine.html | https://glassfish.dev.java.net/javaee5/jbi-se/ServiceEngine.html | ||
| + | |||
| + | ==Documents== | ||
| + | *[http://weblogs.java.net/blog/bhavanishankar/archive/2007/01/servicemix_on_g_1.html ServiceMix on GlassFish - Java EE and JBI integration] | ||
2007年1月10日 (三) 10:47的最后版本
Java EE Service Engine acts as a bridge between GlassFish and Open ESB environment for web service providers and web service consumers deployed in GlassFish. It provides numerous benefits including the following :
- 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.
https://glassfish.dev.java.net/javaee5/jbi-se/ServiceEngine.html
[编辑] Documents
分享您的观点
