On Fri, May 29, 2009 at 10:05 AM, Pete Muir <pmuir@bleepbleep.org.uk> wrote:
This bridge stuff is basically a stinking pile of poo IMO, and needs to go away ;-) It's a lazy way of achieving stuff

Stellar. Well, I wanted to get somewhere with Seam and whatever the official solution is becomes an easy drop-in replacement anyway.
, which if we think properly about the problem domain, we can get around.

Great. I await ideas. I just need to get the reference somehow. The impl in the jndi-bridge folder does a JNDI lookup, btw, so that at least is a generic approach. I'd like to see something suggested in the spec or WB ref doc. Clearly the Seam project is not the only thing that will need to solve this problem.

Actually, Gavin, this is something that would be useful to expose via the BeanManager:

public ELResolver getELResolver()


Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action


NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters.  Please don't hesitate to resend a message if
you feel that it did not reach my attention.