[pabloc2112]

I basically copied the entire example from the richfaces contextMenu demo page...

.....
<h:panelGrid columns="1" columnClasses="cent">

<h:outputText value="Perform right-click on the picture to call the menu" style="font-weight:bold" id="label"/>

<h:panelGroup id="picture">
<h:graphicImage value="/images/jeremias.jpg" id="pic"/>
<rich:contextMenu event="oncontextmenu" attached="true" submitMode="none">
<rich:menuItem value="Zoom In" onclick="enlarge();" id="zin"></rich:menuItem>
<rich:menuItem value="Zoom Out" onclick="decrease();" id="zout"></rich:menuItem>
</rich:contextMenu>
</h:panelGroup>

</h:panelGrid>
.....

I forgot to mention that when I use the ALL LoadScriptStrategie I get a js when loading the page. The contextMenu does not work at all at this time.
When using DEFAULT, I see the contextMenu popingup and at that point I get the js error.

Regards
Pablo

[fabmars]

3.1.3 is a real great release guys, works perfectly for me and new components are kickass !
Keep up the good work

[ilya_shaikovsky]

"pabloc2112" wrote:
I basically copied the entire example from the richfaces contextMenu demo page...

.....
<h:panelGrid columns="1" columnClasses="cent">

<h:outputText value="Perform right-click on the picture to call the menu" style="font-weight:bold" id="label"/>

<h:panelGroup id="picture">
<h:graphicImage value="/images/jeremias.jpg" id="pic"/>
<rich:contextMenu event="oncontextmenu" attached="true" submitMode="none">
<rich:menuItem value="Zoom In" onclick="enlarge();" id="zin"></rich:menuItem>
<rich:menuItem value="Zoom Out" onclick="decrease();" id="zout"></rich:menuItem>
</rich:contextMenu>
</h:panelGroup>

</h:panelGrid>
.....

I forgot to mention that when I use the ALL LoadScriptStrategie I get a js when loading the page. The contextMenu does not work at all at this time.
When using DEFAULT, I see the contextMenu popingup and at that point I get the js error.

Regards
Pablo

My page is

<h:panelGroup id="panel">
 <h:graphicImage value="/pages/arkansas_large.gif"/>
 <rich:contextMenu attached="true">
 <rich:menuItem value="test"/>
 </rich:contextMenu>
 </h:panelGroup>

and web.xml contains

<context-param>
 <param-name>org.richfaces.LoadStyleStrategy</param-name>
 <param-value>ALL</param-value>
 </context-param>
 <context-param>
 <param-name>org.richfaces.LoadScriptStrategy</param-name>
 <param-value>ALL</param-value>
 </context-param>

And the menu rendered just fine :/

[pabloc2112]

<h:panelGroup id="panel">
<h:graphicImage value="/pages/arkansas_large.gif"/>
<rich:contextMenu attached="true">
<rich:menuItem value="test"/>
</rich:contextMenu>
</h:panelGroup>

Maybe I have some issues with other libraries. Are you using facelets? if so what version? Could it be that my versions of myfaces/facelets/seam are causing the error?

Regards
Pablo

[cyberanto]

I had troubles too when using the new LoadStrategies; setting ALL caused the suggestionbox to stop working (no call to server, no choice menu, no update of value in the input field even when typing the value in, but no error message neither on server nor browser ...) after a redeploy to server.

Simply removing it from web.xml solved the problem. Did not have time to check the behaviour of other settings. (DEFAULT, NONE). Maybe it has to do with a session spanning across the reload - have quite a few "artefacts" with JSF on that issue.

[steven.whatmore]

We also experienced problmes the the new LoadStrategies; and as previously posted the problems went away when we removed the new configuration settings from the web.xml file.

Cheers

Whatty

[vrigdon]

We've had issues as will with the ALL load strategy for scripts. Firebug pops up a couple of errors as does WebTest. Reverting to DEFAULT fixes the errors.

[sergeysmirnov]

do you see the same error at richfaces live demo where the ALL is turned ON?

[sergeysmirnov]

Ok. We have found the case. Make sure you turn the js compression off if you use ALL.

<context-param>
 <param-name>org.ajax4jsf.COMPRESS_SCRIPT</param-name>
 <param-value>false</param-value>
</context-param>

P.S. The article is corrected to mentioned this issue.

[vrigdon]

That fixed it. Thanks!