Sorry, I thought Seam looked up most of its components from the JNDI tree, not
just the EJB3 stuff. Again, I don't know much about how Seam works internally.
I do see how I could use the @Unwrap to take something bound in JNDI and
expose it though. The ultimate goal is simply to be able to ex
Turns out the seam component with an @Unwrap method doesn't work.
The component needs to depend on the "org.jboss.seam.core.ejb" component since
thats what is starting up the micro-container, however beans started up in the
EJB3 container are what requires the stuff we're trying to expose via th
Seam doesn't bind anything into JNDI. It only uses JNDI to lookup EJB3
components. If you have other things in JNDI, I think the best strategy is to
use an @Unwrap wrapper around your lookup code. If this were something that
people would generally want to do, I'm sure we could provide some so
Can you point me to some documents about where in the JNDI tree Seam binds
objects for the various contexts? It seems like a generic bean that could be
declared in the micro-container and bind beans to JNDI would be useful. Then
people could use the micro-container to setup and configure beans
Sorry - I read your message too quickly and didn't realize what you were
talking about. :)
Seam can't directly inject microcontainer components. I actually haven't used
the microcontainer, so I have no idea how you look up a component outside of
referencing a JNDI binding for it. It seems t
Sorry to be dense. I'm just not sure what the relation between beans created
by the micro-container config (jboss-beans) an those created/managed by Seam.
Will this use the instance configured in by the micro-container?
View the original post :
http://www.jboss.com/index.html?module=bb&op=vie
@In(create=true) will tell Seam to create the instance if it doesn't yet exist.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996771#3996771
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996771
___
