“Everything should be as simple as it is, but not simpler.” Albert Einstein
“Everything should be as simple as it is, but not simpler.” Albert Einstein
Originally posted by matt mcgrillis:
somehow lock down the access to them only to other EJBs within the same JAR? Would this be possible?
“Everything should be as simple as it is, but not simpler.” Albert Einstein
Originally posted by matt mcgrillis:
BTW, Had a look at the Spring option, and whilst you are totally correct in saying that would solve the problem of being able to use annotation to inject the PersistenceContext within POJOs... it will add a lot of extra time to implement, just for the sake of being able to keep the DAOs as POJOs. There's got to be a simpler solution... as mentioned before... perhaps by locking down access of the EJB DAOs to within the JAR or something similar???)
“Everything should be as simple as it is, but not simpler.” Albert Einstein
Independent Consultant — Author, EJB 3 in Action — Expert Group Member, Java EE 6 and EJB 3.1
I knew I would regret that burrito. But this tiny ad has never caused regrets:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|