anonymous wrote :
| Wouldn't this be enough information for creating the client interface:
|
Um, with Intellij or Eclipse, its really easy to extract an interface. So
instead of typing @LocalMethod, just let your ide create an interface for you.
Easier, less typing.
View the original
anonymous wrote :
| Sounds like you'd just like an XDoclet-esque step for generating Java
source before compilation?
|
Yeah, sounds like it. I hoped that there would be no need for XDoclet anymore
with EJB3, but it seems there actually is. I guess 'my imaginary' annoatations
would in th
Sure...but wouldn't the generated interfaces have to be created at pre-compile
time? And annotations provide metadata that's part of the compiled code...
anonymous wrote : Of course FooBean does not implement an interface now
anymore, but invocations could be handled by some sort of dynamic prox
Sure, I understand that the client only gets a proxy to some interfaces and the
bean implementation has of course to stay on the server. What I don't
understand is why this interfaces could not be generated dynamically.
For example using some imaginary annoations here:
@Stateful
| @Local (i
The EJB3 spec eliminated the "Home" interfaces for obtaining a reference to a
bean's proxy invoker.
The reason that the Remote and Local interfaces are required is because clients
of an EJB3 Bean obtain a reference to (and invoke methods on) this proxy
object, generated by the container, whic
