Re: jscookmenu problem

Thu, 22 Sep 2005 00:21:28 -0700

Simon, thank you for you advise. I read your email and you perfectly focus the problem (I had only one of the two required filter-mapping). Now my test properly works. 

Marco.



Simon Kitching wrote:

You might also find my reply to another recent email useful:
  http://www.mail-archive.com/users%40myfaces.apache.org/msg09082.html
I'm not claiming my reply is 100% correct though - I'm still learning myfaces! 

Martin Marinschek wrote:


You will need to include the ExtensionsFilter in your web.xml.

Best would be to copy a web.xml from a MyFaces example app and start
from this one!

regards,

Martin

On 9/21/05, Marco Barbi <[EMAIL PROTECTED]> wrote:


Hi,

I've been testing MyFaces (1.1.0) and Facelets (0.8) and I find problems
with JsCookMenu.
In detail, following the thread suggestions, I get the following html
code rendered:

...

<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> 
<title>Test Application</title>
<style type="text/css" xml:space="preserve"></style>
<script
src="/test/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11266487/JSCookMenu.js" 
type="text/javascript"></script>
<script
src="/test/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11266487/MyFacesHack.js" 
type="text/javascript"></script>
<script
src="/test/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11266487/ThemeOffice/theme.js" 
type="text/javascript"></script>
<link rel="stylesheet"
href="/test/faces/myFacesExtensionResource/navmenu.jscookmenu.HtmlJSCookMenuRenderer/11266487/ThemeOffice/theme.css" 
type="text/css"/>
</head>
<body>
<script type="text/javascript"><!--
var topMenu_menu =
[[null, 'File', null, 'linkDummyForm', null],
[null, 'Help', null, 'linkDummyForm', null]];
--></script>
<div id="topMenu_menu"></div>
<script type="text/javascript"><!--
cmDraw ('topMenu_menu', topMenu_menu, 'hbr', cmThemeOffice, 'ThemeOffice'); 
--></script>

</body>

...

Unluckly, the URL locations generated for the script tags don't match
any existing resource and, threfore, javascript errors rises.

Any suggestion?

Reply via email to