|
I fully endorse what James is saying about thinking about always using remote interfaces. I don't know if all appservers do this but I can definitely vouch for jboss. I have even verified in the debugger that jboss intelligently optimizes for in-the-same-jvm calls.
Ashish.
On 12/13/06, James Carman <james@xxxxxxxxxxxxxxxxxxxx> wrote:
Or, as one of the comments points out, you could avoid local
interfaces altogether and just access it via the remote interface.
The app server will take care of optimizing the call if it's really a
local call.
On 12/13/06, Keshav Kode <keshav.kode@xxxxxxxxx> wrote:
> As I see it you have 3 potential options:
>
> 1) use something like xdoclet to generate interfaces
> 2) move to EJB3
> 3) use 'Business Interface' pattern
> (
http://www.theserverside.com/patterns/thread.tss?thread_id=12363)
>
> Hope this helps.
> Keshav Kode
>
>
>
>
> On 12/11/06, Edward Sumerfield <
esumerfd@xxxxxxxxxxxxxx> wrote:
> > Anyone have any fancy ways of removing the duplication between these
> > two interfaces? One needs to throw the RemoteException and the local
> > does not. Makes sence in theory but it means duping every method in
> > every bean.
> >
> > I could go code generation, copy from EJBObject to EJBLocalObject and
> > filter out the "throws RemoteException" string. Should be a simple ant
> > task but someone must have solved this inefficiency already?
> >
> > --
> > Ed
> >
> > ---------
> > You may unsubscribe from this mailing list
> > by sending a blank email addressed to:
> >
users-unsubscribe@xxxxxxxxxx
> >
> > --
> > Find additional help by sending a blank email
> > addressed to:
> > users-help@xxxxxxxxxx
> >
> >
>
>
>
> --
> Thank you,
> Keshav Kode
> Keshav.Kode@xxxxxxxxx
---------
You may unsubscribe from this mailing list
by sending a blank email addressed to:
users-unsubscribe@xxxxxxxxxx
--
Find additional help by sending a blank email
addressed to:
users-help@xxxxxxxxxx
|