ok, what i read is really nice. They throw the complete logic in sessionbeans
and let act them as componets for jsf (like actions is struts) and solve the
transation/lazy-fetching with different contexts and with something like an
action phase and render phase (like portlets with processAction a
http://docs.jboss.com/seam/reference/en/html/index.html
(See chapter 5.4 for relevant text.)
Note that Seam works with JSF, so this doesn't address your problem if you are
required to use Struts.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922941#3922941
or can perhaps someone explain in a few sentences how the handels it?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922896#3922896
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922896
---
thx for this hint.. is there any doucmentation about how seam handles
EntityManager lifecycle or "use the force use the source"?
Regards
Peter
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922873#3922873
Reply to the post :
http://www.jboss.com/index.htm
Have a look at JBoss Seam and how it handles EntityManager lifecycle
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922681#3922681
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922681
ok... that´s a option for a single application. But if you think
in context of portals where you want to make interfaces accessable to
portlets or modules where don´t even know the requirements
this is not flexibe enough.
One opinion would be to do without relations and only work with the
relation
Why not just have use cased base DAO methods.
OrderDOA {
Order getOrderSummary(...) //order with no line items but maybe a calc field of
how many lis there are? maybe customer/shipping info...
Order getOrderDetails(...) //order with line items
}
Passing other stuff moves your data layer up. Thi