Hi
They are not used for internal applications, I have a standalone client
that talks remote EJBs to a web server. But the information now passed
back orginates from a web service, hence the question regarding JavaBean
artifacts been generated using wsimport to implement Serialization
interface. The data cannot be passed using remote EJBs as then don't
implement Serialization/Externalizable interfaces. And I don't want to
modify the artifacts directly.
Glen
-----Original Message-----
From: glassfish_at_javadesktop.org [mailto:glassfish_at_javadesktop.org]
Sent: 29 August 2007 23:56
To: users_at_glassfish.dev.java.net
Subject: Re: EJB RMI serialization vs JAX WS serialization
No benchmarks, but XML is most certainly going to be more expensive than
RMI.
If you implement the Externalizable interface, RMI is even faster.
It makes more sense to facade your EJBs with a middle layer to handle
any specific web service demand you may have, but I wouldn't use web
services as a generic RPC mechanism, especially for internal
applications.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=233181
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
For additional commands, e-mail: users-help_at_glassfish.dev.java.net