I don't know. Would the enhancement workers allow you to enhance a field like that, though? I can see where putting it on a method would be fairly straight-forward, but a field might be a bit tricky.
On 3/13/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
It's not for the casual visitor of course, but the "integrated" way to do it would be using the enhancement workers. http://tapestry.apache.org/tapestry4.1/tapestry-framework/hivedoc/module/tapestry.enhance.html On 3/8/07, Bastian Voigt <[EMAIL PROTECTED]> wrote: > Hi *, > > in Suns EJB tutorials all EJB calls are made via annotations like so: > > @EJB private MyBeanInterface myBean; > . > . > void someMethod() > { > myBean.callEJBMethod(); > } > . > . > > > In Tapestry (4.0.2) Page and Component classes this annotation does not > seem to work (NullPointerException) although it gives no compiler errors > or anything like that. Can someone tell me why it does not work this > way? How can I efficiently access EJB3s via their local interface from a > tapestry application? > > The problem is that glassfish supports only remote interfaces when using > JNDI lookup. But I would rather like to use local interfaces as this > should be faster. > > Thank you very much for your help... > > Regards, > Bastian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
