You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Matthias Fischer <Ma...@doubleSlash.de> on 2006/08/01 16:18:22 UTC

Re: is there a way to pull a session scope variable directly into a jsf tag?

Hm, that's right. what I had in mind when I answered Tom's question was
that session.foo contains an action binding string. But then you would
have to call
#{${session.foo}} - if that works at all.

If that is what Tom intended it does make sense to me:
A button that leads to a different action depending on a session attribute.
For example you could think of a list where you can select items.
Depending on user input of previous dialogues the session attribute foo
would be set to an action that is to be performed on the selected items
when the button is pressed.
I am not sure whether this works but that would allow you to reuse view
in different workflows.


> It may work... can I ask why you are designing things this way? It
> seems a bit odd to me to add another level of abstraction on page
> navigation: an expression that resolve to a string that is matched
> against navigation rules that finally defines a view (!)
>
> Cosma
>
> 2006/7/31, Matthias Fischer <Ma...@doubleslash.de>:
>>
>> > I think that the problem is that, if EL is found in the action
>> > attribute, JSF tries to use it as an action method (it attemps to
>> > "call" it)..
>> That's what I suppose. So JSTL EL should solve it as we have no method
>> bindings here...
>>
>>
>>
>>


-- 
Schützen Sie das was Ihnen wichtig ist !
http://iam-solution.de
Weitere Details verrate ich Ihnen gerne am Telefon. Einfach anrufen! 

-----------------------------------------------------------------
Matthias Fischer                  Fon: +49-7541-6047-148
Dipl. Informatiker (FH)           Fax: +49-7541-6047-111
doubleSlash Net-Business GmbH     matthias.fischer@doubleSlash.de
Müllerstr. 12 B                   http://doubleSlash.de
88045 Friedrichshafen


Re: is there a way to pull a session scope variable directly into a jsf tag?

Posted by Cosma Colanicchia <co...@gmail.com>.
This is a common problem.. you should look at the Shale Dialog
Manager: http://shale.apache.org/features-dialog-manager.html, it
tries to address this very exact problems.

Cosma

2006/8/1, Thomas_Perry@putnam.com <Th...@putnam.com>:
>
>
>
>
>
>
> Thank you all for your responses. It's been a great help and very
> interesting reading.
>
> We have a shared jsp page; there are three paths to it.  Navigation has to
> return to
> the jsp that took the user to this particular page.
>
> So we set a 'context' variable in session and wanted to use this for
> navigation;
> it would have one of three values and would invoke the jsp where the user
> began.
>
> James gave me a syntax that pulled the variable from sessionScope, but in
> fact
> that did not work in an action button; it does work with other tags, but
> the button
> tag wanted a method when I used a binding tag.  I haven't tried a jstl
> expression.
>
> In any case, we have a method that returns the session scope variable and
> are
> using that with the action button of the shared jsp, and this controls
> navigation ok.
>
> If anyone has resolved this problem in another way, I'd love to read about.
>
> Thanks again to everyone.
> Tom
>
>
>
>
>              "Cosma
>              Colanicchia"
>              <cosmacol@gmail.c                                          To
>              om>                       "MyFaces Discussion"
>                                        <us...@myfaces.apache.org>
>              08/01/2006 10:36                                           cc
>              AM
>                                                                    Subject
>                                        Re: is there a way to pull a
>              Please respond to         session scope variable directly
>                  "MyFaces              into a   jsf tag?
>                 Discussion"
>              <users@myfaces.ap
>                  ache.org>
>
>
>
>
>
>
>
> You can always write an action method, and return different outcomes,
> if you want to reuse the view.
>
> Cosma
>
> 2006/8/1, Matthias Fischer <Ma...@doubleslash.de>:
> >
> > Hm, that's right. what I had in mind when I answered Tom's question was
> > that session.foo contains an action binding string. But then you would
> > have to call
> > #{${session.foo}} - if that works at all.
> >
> > If that is what Tom intended it does make sense to me:
> > A button that leads to a different action depending on a session
> attribute.
> > For example you could think of a list where you can select items.
> > Depending on user input of previous dialogues the session attribute foo
> > would be set to an action that is to be performed on the selected items
> > when the button is pressed.
> > I am not sure whether this works but that would allow you to reuse view
> > in different workflows.
> >
> >
> > > It may work... can I ask why you are designing things this way? It
> > > seems a bit odd to me to add another level of abstraction on page
> > > navigation: an expression that resolve to a string that is matched
> > > against navigation rules that finally defines a view (!)
> > >
> > > Cosma
> > >
> > > 2006/7/31, Matthias Fischer <Ma...@doubleslash.de>:
> > >>
> > >> > I think that the problem is that, if EL is found in the action
> > >> > attribute, JSF tries to use it as an action method (it attemps to
> > >> > "call" it)..
> > >> That's what I suppose. So JSTL EL should solve it as we have no method
> > >> bindings here...
> > >>
> > >>
> > >>
> > >>
> >
> >
> > --
> > Schützen Sie das was Ihnen wichtig ist !
> > http://iam-solution.de
> > Weitere Details verrate ich Ihnen gerne am Telefon. Einfach anrufen!
> >
> > -----------------------------------------------------------------
> > Matthias Fischer                  Fon: +49-7541-6047-148
> > Dipl. Informatiker (FH)           Fax: +49-7541-6047-111
> > doubleSlash Net-Business GmbH     matthias.fischer@doubleSlash.de
> > Müllerstr. 12 B                   http://doubleSlash.de
> > 88045 Friedrichshafen
> >
> >
>
>
>
>
>
> This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction.  Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail.   All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice.  Any comments or statements made herein do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates.  If you are not the intended recipient of this e-mail, please delete the e-mail.
>

RE: PhaseListener/SetFocus Question

Posted by Tom Innes <To...@allTiers.com>.
Thanks Mike,

I came to the same conclusion and have implemented it as you suggested. 

I am curious though if anybody knows how to determine which form was
submitting.  Unfortunately I don't have a debugger that I can easily use.

Tom

-----Original Message-----
From: Mike Kienenberger [mailto:mkienenb@gmail.com] 
Sent: Tuesday, August 01, 2006 3:59 PM
To: MyFaces Discussion
Subject: Re: PhaseListener/SetFocus Question

Yes, phase listener doesn't seem like the place to handle it.

How many submit buttons do the forms have?  It'd seem like you'd want
to do this in the action or actionListener for each of the UICommands
instead of in a phase listener.

If you're going to use a phase listener, you'll need to determine
which form was submitting.   Don't know how that's done off the top of
my head, but you could set a breakpoint on an action and see how
things got there.


On 8/1/06, Tom Innes <To...@alltiers.com> wrote:
> Thanks for the suggestion Matthias,
>
> Unfortunately that is exactly what I was doing.
>
> My suspicion is that since
>
> countryQBE is a Managed Property of countryForm and
> countryForm is a Managed Property of stateForm
>
> that all three Phase Listeners fire.  Unfortunately I don't see a way to
> distinguish between them. Does anybody know of a way?
>
> Tom
>
>
> -----Original Message-----
> From: Matthias Fischer [mailto:Matthias.Fischer@doubleSlash.de]
> Sent: Tuesday, August 01, 2006 1:06 PM
> To: MyFaces Discussion
> Subject: Re: PhaseListener/SetFocus Question
>
> JavaServerFaces in Action mentions on page 437 that you can register a
> phase listerner with a bean. The example shows a bean that refreshes a
> list before phase RENDER_RESPONSE. Maybe this helps:
>
> public class MyBean() {
>
> public MyBean() {
>
> LifecycleFactory lifecycleFactory = (LifecycleFactory)
> FactoryFinder.getFactory(FactoryFinder.LIFECYLE_FACTORY);
> Lifecycle lifecycle =
> lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
> lifecycle.addPhaseListener(
> new PhaseListener() {
>
>    public void beforePhase() {
>       refreshList();
>   }
>
>   public void afterPhase() {
>   }
>
>    publid PhaseId getPhaseId() {
>       return PhaseId.RENDER_RESPONSE;
>   }
> });
>
>  protected void refreshList() {
>  ...
> }
> ...
> }
>
>
> Tom Innes wrote:
> > I have a question on how best to handle focus when an error occurs.
> >
> > I am currently using the Sandbox focus component and have implemented a
> > PhaseListener on my backing beans to set focus to the first input
> component
> > that has a message associated with it. On each of my backing beans I
have
> a
> > setFocusId and a getFocusId Method.
> >
> > Consider the following Example
> >
> > Backing Bean
> > CountryQBE
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> > CountryForm
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> >
> > StateForm
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> > Say as a Result of Pressing a command button on the CountryForm an Error
> > occurs on the nameField.  When this happens the PhaseListener Fires on
all
> > three backing beans and sets the FocusId to the nameFieldId.
> >
> > Thus the CountryQBE, CountryForm and StateForm backing beans all have
> their
> > focusId property set to nameFieldId.
> >
> > Is there any way to limit the phase listener to only fire for the
current
> > form that it is processing?
> >
> > Tom
> >
> >
> >
> >
>
>
>


Re: PhaseListener/SetFocus Question

Posted by Mike Kienenberger <mk...@gmail.com>.
Yes, phase listener doesn't seem like the place to handle it.

How many submit buttons do the forms have?  It'd seem like you'd want
to do this in the action or actionListener for each of the UICommands
instead of in a phase listener.

If you're going to use a phase listener, you'll need to determine
which form was submitting.   Don't know how that's done off the top of
my head, but you could set a breakpoint on an action and see how
things got there.


On 8/1/06, Tom Innes <To...@alltiers.com> wrote:
> Thanks for the suggestion Matthias,
>
> Unfortunately that is exactly what I was doing.
>
> My suspicion is that since
>
> countryQBE is a Managed Property of countryForm and
> countryForm is a Managed Property of stateForm
>
> that all three Phase Listeners fire.  Unfortunately I don't see a way to
> distinguish between them. Does anybody know of a way?
>
> Tom
>
>
> -----Original Message-----
> From: Matthias Fischer [mailto:Matthias.Fischer@doubleSlash.de]
> Sent: Tuesday, August 01, 2006 1:06 PM
> To: MyFaces Discussion
> Subject: Re: PhaseListener/SetFocus Question
>
> JavaServerFaces in Action mentions on page 437 that you can register a
> phase listerner with a bean. The example shows a bean that refreshes a
> list before phase RENDER_RESPONSE. Maybe this helps:
>
> public class MyBean() {
>
> public MyBean() {
>
> LifecycleFactory lifecycleFactory = (LifecycleFactory)
> FactoryFinder.getFactory(FactoryFinder.LIFECYLE_FACTORY);
> Lifecycle lifecycle =
> lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
> lifecycle.addPhaseListener(
> new PhaseListener() {
>
>    public void beforePhase() {
>       refreshList();
>   }
>
>   public void afterPhase() {
>   }
>
>    publid PhaseId getPhaseId() {
>       return PhaseId.RENDER_RESPONSE;
>   }
> });
>
>  protected void refreshList() {
>  ...
> }
> ...
> }
>
>
> Tom Innes wrote:
> > I have a question on how best to handle focus when an error occurs.
> >
> > I am currently using the Sandbox focus component and have implemented a
> > PhaseListener on my backing beans to set focus to the first input
> component
> > that has a message associated with it. On each of my backing beans I have
> a
> > setFocusId and a getFocusId Method.
> >
> > Consider the following Example
> >
> > Backing Bean
> > CountryQBE
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> > CountryForm
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> >
> > StateForm
> >  - getCode
> >  - setCode
> >  - getName
> >  - setName
> >  - setFocusId
> >  - getFocusId
> >
> > Say as a Result of Pressing a command button on the CountryForm an Error
> > occurs on the nameField.  When this happens the PhaseListener Fires on all
> > three backing beans and sets the FocusId to the nameFieldId.
> >
> > Thus the CountryQBE, CountryForm and StateForm backing beans all have
> their
> > focusId property set to nameFieldId.
> >
> > Is there any way to limit the phase listener to only fire for the current
> > form that it is processing?
> >
> > Tom
> >
> >
> >
> >
>
>
>

RE: PhaseListener/SetFocus Question

Posted by Tom Innes <To...@allTiers.com>.
Thanks for the suggestion Matthias,

Unfortunately that is exactly what I was doing.

My suspicion is that since 

countryQBE is a Managed Property of countryForm and
countryForm is a Managed Property of stateForm 

that all three Phase Listeners fire.  Unfortunately I don't see a way to
distinguish between them. Does anybody know of a way?

Tom


-----Original Message-----
From: Matthias Fischer [mailto:Matthias.Fischer@doubleSlash.de] 
Sent: Tuesday, August 01, 2006 1:06 PM
To: MyFaces Discussion
Subject: Re: PhaseListener/SetFocus Question

JavaServerFaces in Action mentions on page 437 that you can register a
phase listerner with a bean. The example shows a bean that refreshes a
list before phase RENDER_RESPONSE. Maybe this helps:

public class MyBean() {

public MyBean() {

LifecycleFactory lifecycleFactory = (LifecycleFactory)
FactoryFinder.getFactory(FactoryFinder.LIFECYLE_FACTORY);
Lifecycle lifecycle =
lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
lifecycle.addPhaseListener(
new PhaseListener() {

   public void beforePhase() {
      refreshList();
  }

  public void afterPhase() {
  }

   publid PhaseId getPhaseId() {
      return PhaseId.RENDER_RESPONSE;
  }
});

 protected void refreshList() {
 ...
}
...
}


Tom Innes wrote:
> I have a question on how best to handle focus when an error occurs.  
>
> I am currently using the Sandbox focus component and have implemented a
> PhaseListener on my backing beans to set focus to the first input
component
> that has a message associated with it. On each of my backing beans I have
a
> setFocusId and a getFocusId Method.
>
> Consider the following Example
>
> Backing Bean
> CountryQBE
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
> CountryForm
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
>     
> StateForm
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
> Say as a Result of Pressing a command button on the CountryForm an Error
> occurs on the nameField.  When this happens the PhaseListener Fires on all
> three backing beans and sets the FocusId to the nameFieldId.
>
> Thus the CountryQBE, CountryForm and StateForm backing beans all have
their
> focusId property set to nameFieldId.
>
> Is there any way to limit the phase listener to only fire for the current
> form that it is processing? 
>
> Tom 
>
>  
>
>   



Re: PhaseListener/SetFocus Question

Posted by Matthias Fischer <Ma...@doubleSlash.de>.
JavaServerFaces in Action mentions on page 437 that you can register a
phase listerner with a bean. The example shows a bean that refreshes a
list before phase RENDER_RESPONSE. Maybe this helps:

public class MyBean() {

public MyBean() {

LifecycleFactory lifecycleFactory = (LifecycleFactory)
FactoryFinder.getFactory(FactoryFinder.LIFECYLE_FACTORY);
Lifecycle lifecycle =
lifecycleFactory.getLifecycle(LifecycleFactory.DEFAULT_LIFECYCLE);
lifecycle.addPhaseListener(
new PhaseListener() {

   public void beforePhase() {
      refreshList();
  }

  public void afterPhase() {
  }

   publid PhaseId getPhaseId() {
      return PhaseId.RENDER_RESPONSE;
  }
});

 protected void refreshList() {
 ...
}
...
}


Tom Innes wrote:
> I have a question on how best to handle focus when an error occurs.  
>
> I am currently using the Sandbox focus component and have implemented a
> PhaseListener on my backing beans to set focus to the first input component
> that has a message associated with it. On each of my backing beans I have a
> setFocusId and a getFocusId Method.
>
> Consider the following Example
>
> Backing Bean
> CountryQBE
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
> CountryForm
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
>     
> StateForm
>  - getCode
>  - setCode
>  - getName
>  - setName
>  - setFocusId
>  - getFocusId
>
> Say as a Result of Pressing a command button on the CountryForm an Error
> occurs on the nameField.  When this happens the PhaseListener Fires on all
> three backing beans and sets the FocusId to the nameFieldId.
>
> Thus the CountryQBE, CountryForm and StateForm backing beans all have their
> focusId property set to nameFieldId.
>
> Is there any way to limit the phase listener to only fire for the current
> form that it is processing? 
>
> Tom 
>
>  
>
>   


PhaseListener/SetFocus Question

Posted by Tom Innes <To...@allTiers.com>.
I have a question on how best to handle focus when an error occurs.  

I am currently using the Sandbox focus component and have implemented a
PhaseListener on my backing beans to set focus to the first input component
that has a message associated with it. On each of my backing beans I have a
setFocusId and a getFocusId Method.

Consider the following Example

Backing Bean
CountryQBE
 - getCode
 - setCode
 - getName
 - setName
 - setFocusId
 - getFocusId

CountryForm
 - getCode
 - setCode
 - getName
 - setName
 - setFocusId
 - getFocusId

    
StateForm
 - getCode
 - setCode
 - getName
 - setName
 - setFocusId
 - getFocusId

Say as a Result of Pressing a command button on the CountryForm an Error
occurs on the nameField.  When this happens the PhaseListener Fires on all
three backing beans and sets the FocusId to the nameFieldId.

Thus the CountryQBE, CountryForm and StateForm backing beans all have their
focusId property set to nameFieldId.

Is there any way to limit the phase listener to only fire for the current
form that it is processing? 

Tom 

 


Re: is there a way to pull a session scope variable directly into a jsf tag?

Posted by Th...@putnam.com.





Thank you all for your responses. It's been a great help and very
interesting reading.

We have a shared jsp page; there are three paths to it.  Navigation has to
return to
the jsp that took the user to this particular page.

So we set a 'context' variable in session and wanted to use this for
navigation;
it would have one of three values and would invoke the jsp where the user
began.

James gave me a syntax that pulled the variable from sessionScope, but in
fact
that did not work in an action button; it does work with other tags, but
the button
tag wanted a method when I used a binding tag.  I haven't tried a jstl
expression.

In any case, we have a method that returns the session scope variable and
are
using that with the action button of the shared jsp, and this controls
navigation ok.

If anyone has resolved this problem in another way, I'd love to read about.

Thanks again to everyone.
Tom



                                                                          
             "Cosma                                                       
             Colanicchia"                                                 
             <cosmacol@gmail.c                                          To
             om>                       "MyFaces Discussion"               
                                       <us...@myfaces.apache.org>         
             08/01/2006 10:36                                           cc
             AM                                                           
                                                                   Subject
                                       Re: is there a way to pull a       
             Please respond to         session scope variable directly    
                 "MyFaces              into a   jsf tag?                  
                Discussion"                                               
             <users@myfaces.ap                                            
                 ache.org>                                                
                                                                          
                                                                          
                                                                          




You can always write an action method, and return different outcomes,
if you want to reuse the view.

Cosma

2006/8/1, Matthias Fischer <Ma...@doubleslash.de>:
>
> Hm, that's right. what I had in mind when I answered Tom's question was
> that session.foo contains an action binding string. But then you would
> have to call
> #{${session.foo}} - if that works at all.
>
> If that is what Tom intended it does make sense to me:
> A button that leads to a different action depending on a session
attribute.
> For example you could think of a list where you can select items.
> Depending on user input of previous dialogues the session attribute foo
> would be set to an action that is to be performed on the selected items
> when the button is pressed.
> I am not sure whether this works but that would allow you to reuse view
> in different workflows.
>
>
> > It may work... can I ask why you are designing things this way? It
> > seems a bit odd to me to add another level of abstraction on page
> > navigation: an expression that resolve to a string that is matched
> > against navigation rules that finally defines a view (!)
> >
> > Cosma
> >
> > 2006/7/31, Matthias Fischer <Ma...@doubleslash.de>:
> >>
> >> > I think that the problem is that, if EL is found in the action
> >> > attribute, JSF tries to use it as an action method (it attemps to
> >> > "call" it)..
> >> That's what I suppose. So JSTL EL should solve it as we have no method
> >> bindings here...
> >>
> >>
> >>
> >>
>
>
> --
> Schützen Sie das was Ihnen wichtig ist !
> http://iam-solution.de
> Weitere Details verrate ich Ihnen gerne am Telefon. Einfach anrufen!
>
> -----------------------------------------------------------------
> Matthias Fischer                  Fon: +49-7541-6047-148
> Dipl. Informatiker (FH)           Fax: +49-7541-6047-111
> doubleSlash Net-Business GmbH     matthias.fischer@doubleSlash.de
> Müllerstr. 12 B                   http://doubleSlash.de
> 88045 Friedrichshafen
>
>





This message is intended for the recipient only and is not meant to be forwarded or distributed in any other format. This communication is for informational purposes only.  It is not intended as an offer or solicitation for the purchase or sale of any financial instrument, or security, or as an official confirmation of any transaction.  Putnam does not accept purchase or redemptions of securities, instructions, or authorizations that are sent via e-mail.   All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice.  Any comments or statements made herein do not necessarily reflect those of Putnam, LLC (DBA Putnam Investments) and its subsidiaries and affiliates.  If you are not the intended recipient of this e-mail, please delete the e-mail.

Re: is there a way to pull a session scope variable directly into a jsf tag?

Posted by Matthias Fischer <Ma...@doubleSlash.de>.
> You can always write an action method, and return different outcomes,
> if you want to reuse the view.
>

Yes, but different outcomes go to different VIEWS not to different
actions. So what you're doing then is to reuse the action, not the view!
What if I want one particular view to call different actions based on a
condition?

<h: commandButton action="#{${session.myActionBinding}}" ...

thus we could have an action mapping in myActionBinding and the command button would call different actions (maybe even in different beans).
Of course I can write a backing bean with an executeAction instead that - depending on the session attribute - calls the different actions in other beans and returns their outcomes.
But if the way described above works it is the easier way to go. In this case you do not need any additional Java code to call the target action. However as said I havent tried that yet.




Re: is there a way to pull a session scope variable directly into a jsf tag?

Posted by Cosma Colanicchia <co...@gmail.com>.
You can always write an action method, and return different outcomes,
if you want to reuse the view.

Cosma

2006/8/1, Matthias Fischer <Ma...@doubleslash.de>:
>
> Hm, that's right. what I had in mind when I answered Tom's question was
> that session.foo contains an action binding string. But then you would
> have to call
> #{${session.foo}} - if that works at all.
>
> If that is what Tom intended it does make sense to me:
> A button that leads to a different action depending on a session attribute.
> For example you could think of a list where you can select items.
> Depending on user input of previous dialogues the session attribute foo
> would be set to an action that is to be performed on the selected items
> when the button is pressed.
> I am not sure whether this works but that would allow you to reuse view
> in different workflows.
>
>
> > It may work... can I ask why you are designing things this way? It
> > seems a bit odd to me to add another level of abstraction on page
> > navigation: an expression that resolve to a string that is matched
> > against navigation rules that finally defines a view (!)
> >
> > Cosma
> >
> > 2006/7/31, Matthias Fischer <Ma...@doubleslash.de>:
> >>
> >> > I think that the problem is that, if EL is found in the action
> >> > attribute, JSF tries to use it as an action method (it attemps to
> >> > "call" it)..
> >> That's what I suppose. So JSTL EL should solve it as we have no method
> >> bindings here...
> >>
> >>
> >>
> >>
>
>
> --
> Schützen Sie das was Ihnen wichtig ist !
> http://iam-solution.de
> Weitere Details verrate ich Ihnen gerne am Telefon. Einfach anrufen!
>
> -----------------------------------------------------------------
> Matthias Fischer                  Fon: +49-7541-6047-148
> Dipl. Informatiker (FH)           Fax: +49-7541-6047-111
> doubleSlash Net-Business GmbH     matthias.fischer@doubleSlash.de
> Müllerstr. 12 B                   http://doubleSlash.de
> 88045 Friedrichshafen
>
>