I found at least a solution to the issue described below:
In users.xhtml at
<h:commandLink
action="#{userForm.edit}" value="#{user.username}">
<f:param name="id"
value="#{user.id}" />
</h:commandLink>
Add
<f:param name="from"
value="list" />
But now there is still an issue. Just remove the validators in
userForm.xhtml and maybe also the onSubmit and onClick events. Edit a user
and clear content of a required field. Submit the form:
userForm.user.version is empty now.
If you login as admin and use the editProfile form, clear content of
required field, submit, then enter new data in that field, submit again you
lose all your roles and are not an admin any more ;-)
Regards
Rene
-----Ursprüngliche Nachricht-----
Von: René Günther [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 11. Dezember 2007 08:00
An: [email protected]
Betreff: AW: [appfuse-user] Problems with Server Roundtrips and Issue in JSF
Demo
In my application I didnt switch JavaScript off. I had to switch off the
JavaScript for the demo version to force a submit to the server since empty
required fields are caught on client side. The lost of userForm.user.version
will probably also occur if you delete the v:commonsValidator tags. But
without switching off JavaScript there is still the other issue (probably
related to problems with other parameters):
1. Login as admin
2. Go to http://demo.appfuse.org/appfuse-jsf/admin/users.html
3. Edit "user"
4. Resulting page is User Profile (no account settings/role assignments
changeable)
Regards
Rene
-----Ursprüngliche Nachricht-----
Von: Matt Raible [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 11. Dezember 2007 00:10
An: [email protected]
Betreff: Re: [appfuse-user] Problems with Server Roundtrips and Issue in JSF
Demo
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.
>
> Thats 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? Dont you ever got problems with losing form
> data? In
> appfuse 1.8 I wasnt 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]
---------------------------------------------------------------------
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]
