There's a lot of back end plumbing
happening here when we use SimpleRemoteStatelessSessionProxyFactoryBean,
courtesy of the Spring AOP framework. The POJO bean definition creates a proxy for
the remote stateless EJB, which implements the business method interface. The EJB
remote home is cached on startup, so there's only a single JNDI lookup. Each time
the EJB is invoked, the proxy invokes the corresponding business method on the
EJB. All the context details necessary for contacting the server are retrieved from the
previous jndiTemplate bean.
Once our POJO bean is ready, it is just a matter of wrapping that up in the
servicemix-jsr181 as shown in the configuration above. When you configure the
jsr181:endpoint, you can also specify the serviceInterface. This will hold the
class name of the interface to expose as a service and this abstraction will help the
binding to be exposed in standard ways (using WSDL), which we will explore shortly.
We will appreciate the fact that EJB components are remotable, but they normally
expose binary interfaces. Binary protocols are not platform agonistic, nor are they
firewall-friendly.
Pages:
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225