Funny, just got around to watching this JSF video..

[Rick Reumann <ri...@gmail.com>]

I just got around to watching this JSF presentation with Ed Burns..
http://event.on24.com/eventRegistration/EventLobbyServlet?target=lobby.jsp&eventid=25412&sessionid=1&partnerref=atssc_sitepost_01_16_07&key=1C3610AF899E09A2EFD26F0FD6B7875E&eventuserid=9113781
(the transcript you can view also). What is funny is this exact
master-detail-situation is one of the things I found so frustrating
about JSF (at least he admits it should be made easier). Almost all
the tutorials (back when I was looking at JSF) always seemed to skip
the "basic" CRUD concepts which really annoyed me. Why not show
examples of what 99% of the developers are going to need to do with
the framework?

<transcirpt snippet>

18. TSS.com: I am sure it will be. Also looking around the educational
efforts, the patterns and the blueprints around JSF, tend to avoid a
lot of fairly simple patterns such as a simple master detail. It
certainly shows lists, but not actually doing the crud around…

Ed Burns: Right.

19. TSS.com: … master detail. Why -- I mean shouldn't that be normal for --?

Ed Burns: I agree. The master-detail pattern is something that is a
core thing, you most web apps do that. And as it turns out, I think
one of the most difficult -- one of the reasons why it's not included
so much is the lack of a conversation scope. With master-detail, you
often have one page that's your master page and then a separate page,
that's your detail page. You need to convey that information what have
I chosen to drill down on and the absence of the conversation scope
where you can say, okay, I am going to put this here and I want this
to exist for the next request, what we have in the JSF Extensions
Project I am working on is a simple Flash Ruby on Rails style Flash
thing, where you put data in the Flash and it exists for the next
request only and once you have that master-detail is simple and
trivial, so…

20. TSS.com: So master-detail is not simple and trivial now or --?

Ed Burns: Well, there are some other ways to do it now. You have to
use an F: parameter tag to attach the value to a component. So -- but
it's not as easy as it should be.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

EJB 3 + Struts ....delegate/ facade question

[papo <pa...@antcor.com>]

Hello everyone!

I am doing some EJB3 related project, all seems to work ok, though I now 
at the level of adding the web layer to the overall image! I have used 
struts before with EJB2.1 and we had some sort of delegates / facades / 
service locators in order to give us access to the Session Beans ..etc etc.

I guess I have to go to the same route, again in order to give access 
from the web - struts layer to the EJB3 business layer.

Struts 2.0 will support any kind of IoC for that stuff  - not targeted 
though for EJB3?


thanks in advance



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

Re: Funny, just got around to watching this JSF video..

[Mitchell James <jm...@apache.org>]

Ya, don't EVEN get me started on some of the hacks I've had to do in  
the last 8 months to get our JSF app to behave....sheeesh!


--
James Mitchell
678.910.8017




On Jan 16, 2007, at 11:34 PM, Rick Reumann wrote:

> I just got around to watching this JSF presentation with Ed Burns..
> http://event.on24.com/eventRegistration/EventLobbyServlet? 
> target=lobby.jsp&eventid=25412&sessionid=1&partnerref=atssc_sitepost_0 
> 1_16_07&key=1C3610AF899E09A2EFD26F0FD6B7875E&eventuserid=9113781
> (the transcript you can view also). What is funny is this exact
> master-detail-situation is one of the things I found so frustrating
> about JSF (at least he admits it should be made easier). Almost all
> the tutorials (back when I was looking at JSF) always seemed to skip
> the "basic" CRUD concepts which really annoyed me. Why not show
> examples of what 99% of the developers are going to need to do with
> the framework?
>
> <transcirpt snippet>
>
> 18. TSS.com: I am sure it will be. Also looking around the educational
> efforts, the patterns and the blueprints around JSF, tend to avoid a
> lot of fairly simple patterns such as a simple master detail. It
> certainly shows lists, but not actually doing the crud around…
>
> Ed Burns: Right.
>
> 19. TSS.com: … master detail. Why -- I mean shouldn't that be  
> normal for --?
>
> Ed Burns: I agree. The master-detail pattern is something that is a
> core thing, you most web apps do that. And as it turns out, I think
> one of the most difficult -- one of the reasons why it's not included
> so much is the lack of a conversation scope. With master-detail, you
> often have one page that's your master page and then a separate page,
> that's your detail page. You need to convey that information what have
> I chosen to drill down on and the absence of the conversation scope
> where you can say, okay, I am going to put this here and I want this
> to exist for the next request, what we have in the JSF Extensions
> Project I am working on is a simple Flash Ruby on Rails style Flash
> thing, where you put data in the Flash and it exists for the next
> request only and once you have that master-detail is simple and
> trivial, so…
>
> 20. TSS.com: So master-detail is not simple and trivial now or --?
>
> Ed Burns: Well, there are some other ways to do it now. You have to
> use an F: parameter tag to attach the value to a component. So -- but
> it's not as easy as it should be.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org