Mixing EJB3 and POJO

[smithbstl]

Is it wise to mix the two when developing Seam applications? I have situations where I need to create components that do nothing but perform database queries for me. A SFSB is not really necessary (results will be passed to a SFSB from the querying component) and SLSB in Seam seem to be sort of pointless. Can I create a simple POJO for this? Can I use a TransactionalSeamPhaseListener with EJBs since I think I can only define one Phase Listener or the other to get a Persistence Context injected.

Or do I need to stick to a purely EJB3 application or purely POJO (J2EE)?

Thanks

-Brian

[pmuir]

Mix them to your hearts content :)

[stu2]

You might also take a look at the wiki example, which demonstrates this extensively. Its dao layer is pojos and the pattern works extremely well.

[smithbstl]

Thanks Pete,

I did not see any examples of this in the reference apps so I didn't know if this was frowned upon as a bad architecture or was simply not possible.

So you are saying I can use the TransactionalSeamPhaseListener in an EJB container? I know the transactions are dealt with a little differently, but I should not notice a difference from my standpoint?

[christian.bauer]

Please don't take the DAOs in the wiki example as a reference :) They have been done very quick and dirty and will be replaced at some point when I know how many/which DAO methods I really need.

[christian.bauer]

The SeamTransactionalPhaseListener works everywhere, transactional EJB methods join the transaction.

[pmuir]

Yes definitely. The TSPL isn't to do with whether you use POJO/EJB

[smithbstl]

Thanks stu, can you point me to where i can find this example? Is it one of the example within Seam or somewhere else?

Thanks

[smithbstl]

Ok, scratch the wiki example I guess, Lol, was typing before I saw Christian's posts.