| The SearchBean:
|
| @Stateless
| @Name(mitarbeiteruebersicht)
| @LoggedIn
| @Scope(ScopeType.STATELESS)
|
| public class MitarbeiterUebersichtBean
| implements MitarbeiterUebersicht {
| ...
| ...
| @In (required=false)
| @Out (required=false)
|
Please post the exception!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3980296#3980296
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3980296
___
jboss-user mailing list
2006-10-24 11:06:49,582 ERROR
[org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/weiterbildung].[Faces
Servlet]] Servlet.service() for servlet Faces Servlet threw exception
| javax.faces.FacesException: Cannot get value for expression
'#{varMitarbeiter.kostenstellen.name}'
|
petemuir wrote : ...
| I use a third bean for searching (stateless at the monent), and then use a
datamodel row selection to populate the edit bean.
| ...
Hi Pete!
I'm following the same pattern as you, but get a problem doing so.
I've also a Stateless SB for searching, including a
How do you 'get back to it'? The back button, or a link?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3979994#3979994
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3979994
___
I go back through a h:commandButton action=.../, calling a method in my
SLSB, which returns an outcome for faces-config.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3980028#3980028
Reply to the post :
I'm not sure what your exact problem. But I would guess that you are accessing
something that isn't in the stateless scope from your search page, and that
there is no persistence context available for it. So if you post some code it
will be easier to help ;)
View the original post :
This all very much depends on your desgin choices. Look at
http://blog.hibernate.org/cgi-bin/blosxom.cgi/Gavin%20King/stages-of-adoption.html
which quickly runs over various possible patterns.
My preferred technique is to use a conversation. I use a seperate backing bean
for create and edit
Stateless beans are only useful if you want to invoke one of their methods
without doing anything else with them.
But if you have a state that should be held (e.g. user filled in fields) you
need a STATEFUL bean. To distinguish between new and existing entities you can
call two different
As always with design there are a multitude of ways to do the same thing, some
of which are vastly different, some of which are very similar. It will be nice
when the EJB3/Seam patterns set is a bit more developed!
I would suggest using a Seam Managed Persistence Context rather than an
10 matches
Mail list logo
