A portal application will often divide the portal page into portlet areas, and one way to manage them is to make each portlet area be an HTML "div" element whose primary child is the results of a URL request.
Facelets can be used to tile a web page, but the tiles themselves will generally be div or table elements. Actually making them properly display results from multiple apps requires that the apps are written to render themselves in the limited space of the portal pane.
The easiest way to do that is to use a portal framework such as Apache Pluto. JSF does work quite well in a portlet environment.
Basically, if you want a portal-style system, you're a lot better off using a real portal sysem than trying to re-invent portals without being portals. Facelets xhtml files aren't designed to be referenced in a cross-application way, since they're compiled by their owning webapp to product an HTML page. Frames have problems of their own.
Loudly announcing something is true and finding out you're wrong makes you feel foolish.
Finding out you're wrong and refusing to admit it makes you LOOK foolish.
thank you for the response. We ware still using a portal, but are looking forward
to use other technologies. We are using only a few portal features and think it
could be better and easier to use other frameworks.
Currently I'm using facelets and try to ui:include my sub-urls ... without being successful
at the moment. My own ResourceResolver seems to work, but an weird exception occurs
when invoking my other application.
Maybe someone has other hints to realize this project, becaus big insurance-apps for example
use other technics and before the "portal" hype getting active I believe there were other
technologies for realizing a multi-app (war/ear) application.
Maybe I am wrong, I don't think you can include or reload other *.xhtml files from other wars.
But if you happen to use Maven to build your applications, the Maven overlays plugin is probably an option.
Basically, the whole idea is you extract the common web resources (such as template files, images) shared by
applications into a common artifact, and then allow maven to use this plugin to build this common resources into your wars.
As result, all wars built in this way will have the same style and layout.
Not sure if this can solve your problem. The plugin can be declared in POM.xml as follows: