On Dec 10, 2007, at 3:08 PM, René Günther wrote:
In userForm.xhtml I needed an additional SelectItem component. To be
able to
reuse this component later I created a new ManagedBean. The value of
the
selectItem was a property of my new ManagedBean. The property has
not being
set after submit. Since it was a required field I got an error.
Additionally
to this error userForm.user.version was lost.
That’s part of the tag:
<h:selectOneMenu value="#{clientSI.selected}" id="client"
required="true"
disabled="#{userForm.user.version != null}">
After submit
clientSI.selected is lost.
Component isnt disabled anymore.
Then I tried the JSF Demo http://demo.appfuse.org/appfuse-jsf/userForm.html
,
switched off JavaScript (FireFox Web Developer), changed an user by
clearing
content of the field password hint. After submitting
userForm.user.version
was lost too: after the submit I got additional fields (roles, account
settings). Anyone got an idea why this is happening?
I don't know of any JSF applications that work well with JavaScript
disabled - do you? If your application is required to function w/ a
JavaScript-less browser, I'd suggest you don't use JSF.
With that being said, it's quite possible we have some bugs in
AppFuse's JSF implementation.
Matt
Additionally to this: in the JSF version ROLE_ADMIN is not allowed to
assign/delete roles of users.
I am really wondering whether anyone is using the JSF version of
appfuse 2
for real applications? Don’t you ever got problems with losing form
data? In
appfuse 1.8 I wasn’t able to build an application without using
t:saveState
Regards
René
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
