shale session vs ejb 3.0 statefule session beans / jboss seam

[numpsy beelzebub <nu...@gmail.com>]

hello,
i want to developed an application using shale and ejb 3.0 (within container
jboss).
primary i used stateless session beans for access to the entity beans -
persistenz-layer is ok and how to work with it

as session i will declare a managed bean with an application scope "session"
and save my data in it.
i thought it is the fastest and easiest way, but in comparing to stateful
session beans it is not the only possible solution.

in addition to this a few questions:

1. i'm fit in clay and know how to access normally ejb 3.0 from shale's
application-logic (building context etc)
 but how is it possible to access stateful session bean from view etc.
(normally i have direct access, if it is declared as managed bean)
2. i have to initalize context for access ejb, so i thought maybe declare a
interface as managed bean which gives access to stateful session bean
   does exist a method in shale except init(), that would be called for
every request, so that i can initialize my access-context
3. if i want to use stateful-session ejb 3.0 - how is it possible out from
session to define when access of specific user ends.
   maybe saving access to stateful-session ejb 3.0 into some kind of state
bean in shale declared as managed bean with session scope -> but if i do it
so it seems strange
  i save access to a ejb, but i could save the data also direct
 4. generally problem - session in shale is only a javabean with the session
scope
    <-> stateful session bean is server side component (differences are
clear, but what is best to use - where lies advantages)

it is also a problem because jboss seam gives possibilities for my problems
http://www.javaworld.com/javaworld/jw-05-2006/jw-0515-jsf-p3.html

maybe i need some impressions of developer with some kind of more
experience, including th developers of shale

thx so much