XDoclet vs Vendor GUI

[Sondra Colagrossi]

I've been reading Ed Roman's Matering EJB 2.0 he talks about methods vendors us to achieve clustering. Two of the paradigms he mentions involve code manipulations in the home stub and the remote stub.
Now my understanding is the XDoclet package generates the Home and the Remote Stub. So to use Xdoclet and have the benefit of decoupling an application from its server, one must sacrifice the vendors ability to achieve clustering through these techniques.
Am I understanding this correctly?

[Chris Mathews]

Originally posted by Bob Fred:
Now my understanding is the XDoclet package generates the Home and the Remote Stub. So to use Xdoclet and have the benefit of decoupling an application from its server, one must sacrifice the vendors ability to achieve clustering through these techniques.

The Home and Remote interfaces of an EJB are just plain Java Interfaces. The Application Server is responsible for providing an implementation for these interfaces. The implementations of the Home and Remote interfaces are commonly referred to as the Home and Remote stubs. XDoclet saves you the hassle of writing these interfaces, it does not change how the Application Server uses them.