|
Hello Is there a way to identify a JSF page by its URL? Or is there a way to modify the urls for the JSF pages? Currently they look like this: /ivy/faces/instances/147C4D28F14CC8CC/MainWindow.xhtml What I would like to do is to have something like this: /ivy/faces/instances/custom-part/147C4D28F14CC8CC/MainWindow.xhtml Or: /ivy/faces/instances/ivy-project-name/147C4D28F14CC8CC/MainWindow.xhtml Is there a way to do this in ivy or in tomcat?
This question is marked "community wiki".
|
|
With version 7.3 it's possible to have static JSF pages. These pages have to be inside of the webContent folder and are reachable over:
For more informations have a look at: Designer Guide |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 12.08.2014 at 15:15
Seen: 4,992 times
Last updated: 18.03.2019 at 10:12
I asked the ivyTeam the same question at 2nd of July 2014, Request-No. 33872. The answer I recieved, was that there is no possibility to do that. Except, you set up two different IvyServer with different URIs.
Yes per default this is not possible. But may be it helps if you give us your use-case may we can then provide an solution.
We have some pages in our application that need to be public. We've created a "public" project. There is a proxy in front of the ivy-server that the request needs to go through. This proxy can be configured to allow unauthenticated users to go through based on an url pattern like /ivy/public/. The problem is that /ivy/faces/instances/* requires an authenticated user by the proxy and there is no way to distinguish between public and private pages.
We thought about the following solution sometimes: It should be possible to have static jsf pages (like jsp is already possible) in the webcontent folder (without processes). Would that solve your problem? you could then use different supfolders for public and non-public.