i think it is in my case. SFSB X is something like a Context (Application, Session, Request, Event) in Seam, so there will be a lot of them.
Y is a single DAO (per Entity one DAO) and i would have to include all of them. Why i need this: I cannot work with my DAOs, because each DAO has it's own ExtendedPersistenceContext. So if i have a unit-of-work i have to use more than one of them and so the changes are not atomar anymore. So i have to bind the lifecycle and PersistenceContext of my DAOs with something like a Context SFSB (in the example X) but this only works, if the DAOs are injected via Container and not fetched via JNDI. Unfortunatelly i can not use Seam for my application, because Seam uses a SFSB per Use-Case and in my modular-application the use-cases can not be foreknown. So i need a very dynamic and abstract facade which give out persistent and not detached object. Very simple Problem, but no simple solution (not any yet). Regards Peter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947816#3947816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947816 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
