<config>
<client>
<!– the login page the client will use –>
<login-page>/jsp/extension/login.jsp</login-page>
</client>
</config>
<config>
<client>
<!– the login page the client will use –>
<login-page>/jsp/extension/login.jsp</login-page>
<relogin-page>/jsp/extension/relogin.jsp</relogin-page>
</client>
</config>
<navigation-rule>
<from-view-id>/jsp/*</from-view-id>
<navigation-case>
<from-outcome>logout</from-outcome>
<to-view-id>/jsp/login.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>relogin</from-outcome>
<to-view-id>/jsp/relogin.jsp</to-view-id>
</navigation-case>
</navigation-rule>
Bonjour,
voici le pourquoi de vos derniers petits tracas, je pense que cela vous éclairera sur la bonne méthode de surcharge de règle de navigation :
http://wiki.alfresco.com/wiki/Packaging_And_Deploying_Extensions#JSF_configuration_files
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
<navigation-rule>
<description>
The decision rule used by the NavigationHandler to
determine which view must be displayed after the
current view, login.jsp is processed.
</description>
<from-view-id>/jsp/extension/login.jsp</from-view-id>
<navigation-case>
<description>
Indicates to the NavigationHandler that the browse.jsp
view must be displayed if the Action referenced by a
UICommand component on the login.jsp view returns
the outcome "success".
</description>
<from-outcome>success</from-outcome>
<to-view-id>/jsp/browse/browse.jsp</to-view-id>
</navigation-case>
</navigation-rule>
<!– rule to get back to the login page from anywhere –>
<navigation-rule>
<from-view-id>/jsp/*</from-view-id>
<navigation-case>
<from-outcome>logout</from-outcome>
<to-view-id>/jsp/extension/login.jsp</to-view-id>
</navigation-case>
<navigation-case>
<from-outcome>relogin</from-outcome>
<to-view-id>/jsp/extension/relogin.jsp</to-view-id>
</navigation-case>
</navigation-rule>
</faces-config>
faces-config.jar
– META-INF
– faces-config.xml
– MANIFEST.MF
jar.exe cvf [i]adresse_de_sortie\faces-config.jar[/i] [i]adresse de faces-config.xml[/i]
Il créera le fichier MANIFEST.MF automatiquement (voir http://www.siteduzero.com/tutoriel-3-30916-creer-une-archive-jar-executable.html)Content from pre 2016 and from language groups that have been closed.
Content is read-only.
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.