I inserted an explicit link into left.vm as you suggested but it still throws the same error when mixing VM & JSP.
Here are the links that I added. The first one works fine (.vm -> .vm). But the second one (.vm -> .jsp) throws the same error I described in my previous message. <a href="http://localhost:8080/jetspeed/portal/media-type/html/language/en/user/anon/page/default.psml/layout/default.vm/template/Page2.vm";> and <a href="http://localhost:8080/jetspeed/portal/media-type/html/language/en/user/anon/page/default.psml/layout/default.vm/template/Page3.jsp";> Looks to me like it's just a bit more involved. Because the JetspeedTemplatePage.doBuildAfterAction method calls both TemplateLocator.locateScreenTemplate & TemplateLocator.locateLayoutTemplate with the "screen template", including the extension. Then the TemplateLocator.locateLayoutTemplate strips the extension off the "screen template" to use in constructing the path for looking up the "layout". The problem is this depends on both the screen and layout having the same extension. To further explore the issue I thought it would be easy enough to extend the JetspeedTemplateLocatorService and tweak it (just for an experiment) to force it to only find the layout. So I did that and added the following snip to the beginning of MyTemplateLocatorService.locateLayoutTemplate() if (template.equal("Page3.jsp")) { template = "Page3.vm"; } Then change the service in the JR.p file to the use my new service. services.TemplateLocator.classname=org.apache.jetspeed.services.template.MyTemplateLocatorService This should force the locator service to find a VM Layout for the JSP Screen. And it did, but it fails later in the JetspeedJspLayout class where the code again seems to assume that the screens and layouts are both either VM or JSP but not mixed. So I don't think it's just a default extension issue nor does the issue seems to be encapsulated within the locator service. I appreciate your help. Thanks, Tom -----Original Message----- It should be extremely simple since the engine supports it and the issue looks to mainly be the use of default extensions. Firsft thing first, have you tried explicit extension naming like in: http://<portal>/jetspeed/portal/layout/default.jsp/template/test.vm It should work and prove that it's just the assumption that need fixing. Note that navigations should mix well too if you take care to suffix them with '.jsp' and '.vm' as required. If the above works, you can modify the default layout property and default template properties in your properties file to explicitely select the correct version and then use the full template name with extension in your links between screen templates. -- Rapha�l Luta - [EMAIL PROTECTED] Apache Portals - Enterprise Portal in Java http://portals.apache.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
