Thanks Erelend, :-)
What I mean is the choice action listener versus action shouldn't have to be
a technical constraint...
Regards,
Zied
2007/6/22, Erlend Hamnaberg <[EMAIL PROTECTED]>:
Zied Hamdi wrote:
> Hello people there :-),
>
> I have a solution through the use of actionListener instead of action:
>
> public void updatePhoneType( ActionEvent event ) {
> UIData data = findComponent( UIData.class,
> "page:personForm:details:phoneListSubview:phones" );
> PhoneNumber number = (PhoneNumber) data.getRowData ();
> UIComponent component = event.getComponent();
> String type = (String) component.getAttributes().get( "phoneType" );
> number.setType( PhoneType.valueOf( type ) );
> }
>
> But using an action listener instead of an action isn't a very good
> solution since I loose control on redirecting the result to another
page.
(snip)
You can use an ActionListener AND an action.
The actionListener gets invoked first, then the action. So your
navigation will still work.
Regards
- Erlend
--
Erlend Hamnaberg
[EMAIL PROTECTED]
Student 3. dataingeniør AITeL HiST.
----------------------------------------
Tear down the walls
Wake up the world
Ignorance is not bliss
So fed up with second best
Our time is here and now
I am the enemy
I am the antidote
Watch me closely
I will stand up - now
*Arch Enemy - We will rise*
--
Zied Hamdi
zatreex.sourceforge.net
