STATELESS components are created every time they are used, not EVENT components
:-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3966865#3966865
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3966865
__
And now I have my CountrySelect class working, I figured out that instead of
returning a Map, it needs to return a List of SelectItems. So I got that done.
Then I found out that, because I'm using an enum for my Country, I need to
write a Converter for that. Which turned out to be very easy t
Ah, I found out the problem.
In my entity class, I had a @Roles(...) annotation which gave role names and
scopes. I thought that would be enough to use the object. No! A @Name
annotation must be present, even if the given name is not used.
View the original post :
http://www.jboss.com/inde
And again, I'm back to "error during model data update". I assume that that
error is happening because the object is null. And yet the object has a
CONVERSATION scope, so it seems to me that it should always exist as long as
their is a conversation.
Is there some way to tell seam, "Please cre
I figured out a way to do it. I created a new class, called CountrySelect. I
gave it a name, and an Application scope, and one method, which is
getCountryMap. So that works now. I suppose if a class has APPLICATION scope,
only one instance of it is created?
View the original post :
http:/
This seems like a step backwards from JSP. Here's the problem I'm facing:
I have a signup form where users can select their country. There are about 200
countries, and a I have an enum that lists them all, and within that enum class
there is also a static member which is a Map that maps keys o
When the component is instantiated it will live in the event scope NOT the
component will be instantiated whenever the event scope is accessed. There is
no way (AFAIK) of doing this.
Beans are instantiated when they are accessed (via @In, @Out, accessed from a
JSF page etc.)
View the original
