UserList.xhtml as generated:
| !DOCTYPE composition PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN
|
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd;
|
|
| ui:composition xmlns=http://www.w3.org/1999/xhtml;
|
Strange because I am using the display template
I'm using the templates and views as generated by seam-gen and can't get it
working
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129569#4129569
Reply to the post :
I've exactly the same problem.
The default display decorator is used as generated by seam-gen.
A userLsit (entityQuery) is also generated by seam-gen.
I would like to search for a user by e-mail address, but validation is
performed (must be a well-formed email address) since there exists an
All sessionbean lists generated by seam-gen provide an implementation of an
EntityQuery class.
Why is the String[] of RESTRICTIONS marked as Static? as shown below:
| package web.session;
|
| import web.entity.user.*;
| import org.jboss.seam.annotations.Name;
| import
mars1412 wrote : IMO:
| it's static because you want to make it a class-variable (NOT instance
variable)
| it's final, because you will never change it
| anonymous wrote :
| | The only place currently reffering to this attribute is within the
class itself (getRestrictions).That's why
Hi,
I'm trying to use an abstract class for some stateful beans that use a lot of
similair functionality.
But I'm having a lot of trouble using in-/outjections in combination with
reflection.
My abstract class:
| package common.selectableMap;
|
| //imports
|
|
Where can i find more information about the entityQuery lifecycle?
What method is called when?
I would like to use the functionality of pagination for my resultlist (and
search option), but also want to add some functionality to add a
booleancheckbox for every item.
After selecting a checkbox
[EMAIL PROTECTED] wrote : You should upgrade to 2.0.1.CR2 and use the now
documented support for natural conversations.
Tanks a lot.
This is very usefull.
Chapter 6.6 Using an explicit conversation id should be updated because it is
still misleading.
View the original post :
I would like to use an explicit conversation id.
The Begin annotation API:
http://docs.jboss.com/seam/2.0.0.GA/api/org/jboss/seam/annotations/Begin.html
mentions the id attribute to be deprecated public abstract String idDeprecated.
use in pages.xml
|
| An EL expression for the conversation
