[JBoss Seam] - Re: Seam and IceFaces problem
by jmiguel77
Hi:
I used the embedded example from the Seam 1.0.1/examples and now, at least there are no exceptions thrown in the page
But i am facing a new problem (i am really starting to dissapoint about this icefaces thing)
I have this page:
<!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"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:s="http://jboss.com/products/seam/taglib"
xmlns:ice="http://www.icesoft.com/icefaces/component"
template="../template/global.xhtml">
<ui:define name="content">
<h:outputText value="#{messages['user.label.list']}" />
<ice:dataTable value="#{userList}" var="user" width="100%">
<h:column id="userIdColumn">
<f:facet name="header">Id</f:facet>
<ice:outputText value="#{user.userId}"/>
</h:column>
<h:column id="userNameColumn">
<f:facet name="header">Name</f:facet>
<ice:outputText value="#{user.userName}"/>
</h:column>
<h:column id="userRoleColumn">
<f:facet name="header">Role</f:facet>
<ice:outputText value="#{user.role.roleName}"/>
</h:column>
<h:column id="actionColumn">
<f:facet name="header">Actions</f:facet>
<s:link id="editSeamLink" value="#{messages['common.label.edit']}" action="#{securityManager.selectUser}"/>
<s:link id="deleteSeamLink" value="#{messages['common.label.delete']}" action="#{securityManager.deleteUser}"/>
</h:column>
</ice:dataTable>
</ui:define>
</ui:composition>
it is really a simple page right ??? I have tried the same page with the same components (the session beans and stuff) without icefaces and everything worked fine
But with the ice:dataTable i get no values in the id, name and role columns once the page is loaded. If i click in the edit link, i get a bean in the edit page, but when i return to the list page, that loaded bean is present in the entire list
The number of rows in the table is ok, but the data i all jammed.
What can it be ???
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996551#3996551
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996551
18 years, 10 months
[JBoss Seam] - Re: Problems with Validator and Seam when submit form
by fabio.ita04
Cayo,
I spent some time with an error like yours. Simple validation (like that in Hibernate Validator) worked fine even after first submission (failed due to required constraints), but complex validation (using some business logic, like verify if a login field is unique) don't. The JSF code:
| <div class="entry">
| <s:decorate>
| <label>#{messages['user.login']}</label>
| <h:inputText id="login" value="#{user.login}">
| <a:support event="onblur" reRender="loginError" />
| </h:inputText>
| <a:outputPanel id="loginError">
| <s:message />
| <c:if test="#{userManager.loginInUse}">
| #{messages['user.login.in.use']}
| </c:if>
| </a:outputPanel>
| </s:decorate>
| </div>
|
where #{userManager.loginInUse} is a Session Bean method that was supposed to perform validation (verify if login is unique) at ajax rerendering.
The reason of the fails: the backing bean wasn't properly populated, probably because "required" constraints returned page before that. So, a method like user.getLogin (invoked at #{userManager.loginInUse}) returned null, even when the field was typed in the form.
So, I decided to move this validation to not be executed at ajax events. Instead, placed it in the action method that is invoked on form submission. If validation fails, add a message in FacesMessages with Fatal Severity, and return.
| FacesMessages.instance().addFromResourceBundle(
| FacesMessage.SEVERITY_FATAL, "login.already.in.use");
|
All Fatal errors are displayed as Global Errors at the top of the form:
| <span>
| <h:messages infoClass="success" fatalClass="globalErrors" errorStyle="display: none" />
| </span>
|
This way, business logic validation is executed at the very begining of action method (grant simple validation and proper population of backing bean).
Hope it helps.
Fábio.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996549#3996549
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996549
18 years, 10 months
[JBoss Seam] - Re: Jetbrains IntelliJ and seam (and maybe seam-gen)?
by atzbert
Ok,
i created some sort of plain seam project which was originally created by seam-gen and has been a little bit "enriched". You'll find an IntelliJ project file in the base directory along with 3 module files (ear/war/jar). Just open the project and do some minor adjustments:
-edit the project jdk
-adjust the testproject-ds.xml / jboss-beans.xml to match your db
-edit the {basedir}/build.properties and set the jboss home accordingly
If you want to use the seam gen tasks (which I have slightly modified and reduced to the file generators) then you should edit the {basedir}/seamgen/generator.properties file and make it matching your paths.
That should be it.
I added two ant build files, the upper one (called testproject) deploys/builds the application. Use "explode" to explode it to the jboss deploy dir and "restart" to touch the deployment descriptor in order to redeploy the app.
The other one is the "reduced to file generators" - seam gen. Pretty useful I think.
Have fun, and let me know if there are any further problems.
Tino
ps: download it here: http://pluggable.de/download/testproject.tar.gz ;P
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996544#3996544
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996544
18 years, 10 months
[JBoss Seam] - Re: Could not instantiate Seam component error
by hstang
If you provide a no-args constructor, the exception dealing with instantiation will be gone. This is the only way Seam can construct your seam components properly. Yes, as you suggested, use the @Create to initialize other important properties pertaining to the class. The annotated method is called once Seam has fully initialize the component.
As for @DataModel, this will outject the annotated property to the scope of the owning component. In your case, the conversation.
And for @DataModelSelection, this will inject the selected model object, if it's successfully look up in the contexts. You have to ensure that the conversation is long-running, just long enough though, so that @DataModelSelection object can be successfully be retrieved through the @DataModel property.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3996541#3996541
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3996541
18 years, 10 months