To be honest I have trouble understanding exactly what you are trying to do.
You talk about changing navigation at some point though.
If you want navigation to be more dynamic, e.g. let the user go to
different pages depending on some state information, you can simply
make the action attribute of your <h:commandXXX tags point to a method
which returns a string with the right navigation rule.
Example:
In your faces config file you define a managed bean, myBean with the
following method:
public String goSomeWhere {
if (somethingIsTrue) {
return "goToPageOne";
} else if (someThingElse) {
return "goToPageTwo";
}
//When everything else fails
return "goToPageThree";
}
goToPageOne
goToPageTwo
goToPageThree
Are all defined in the faces config like:
<navigation-rule>
<navigation-case>
<from-outcome>goToPageOne</from-outcome>
<to-view-id>/pageOne.jsp</to-view-id>
</navigation-case>
</navigation-rule>
etc.
In you jsp page you have a command, eg. a link:
<h:commandLink value="GotoSomePage" action="#{myBean.goSomeWhere}"/>
Hope that helps
Mads
On 8/13/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi,
>
> thanks for this nice explanation.
>
> Craig McClanahan wrote:
> If I had configuration settings that I wanted to make changeable, I'd
> set them up as application scope attributes, not web.xml settings.
>
> Well, how can be look a workaround for myfaces that will change the
> faces-config.xml or tiles.xml?
> That would be very interesting, not only for me.
> I read the Javadoc API, but cant suggest, where i can make the web.xml
> settings dynamic.
> My approach is that i use the FacesContext to handle that...
>
> Can someone give an idea?
>
> Thanks!
>
> Udo Krass
>
> Ihr Traumpartner ist nur einen Klick entfernt. 1 Million Singles warten auf
> Sie in
> Deutschlands beliebtester Partnerboerse:
> http://singles.freenet.de/index.html?pid=11512
>
>
