Can you explain this precisely ? My portlet included all the tomahawk and myfaces jars in the WEB-INF/lib directory. Which js I have to add and how ? I thought by now that's enough when I include the libs and the images for the tree.
Daniel Gradecak-2 wrote: > > you probably do not have the javascript files needed by that component > included on your page. > > opfau wrote: >> Hi, >> >> I have tried it and my tree2 is rendered. But clicks in the portlet have >> no >> result. I can not open the root node. It seems that all user clicks on >> the >> tree2 and a commandLink are not evalutaed. Any idea ? >> >> >> >> >> Rogerio Pereira wrote: >> >>> Wiki this please. >>> >>> 2006/8/16, David Chandler <[EMAIL PROTECTED]>: >>> >>>> I'm running Tree2 from Tomahawk 1.1.3 in Jetspeed2 with server-side >>>> expansion so as not to require JavaScript. The ExtensionsFilter is >>>> therefore >>>> needed only to serve up the image resources needed by Tree2, and image >>>> requests are handled through the Faces Servlet, not the portal, so the >>>> ExtensionsFilter will run as normal for these requests. However, >>>> Tomahawk >>>> 1.1.3 checks to see if the ExtensionsFilter has been configured, which >>>> fails in the portal context, but you can disable the check with a >>>> web.xmlcontext param. >>>> >>>> So to summarize, you can use Tree2 1.1.3 in a portal without any of the >>>> MYFACES-434 patches if >>>> >>>> 1) You use server-side toggle >>>> 2) You configure ExtensionsFilter as normal for the Faces Servlet >>>> 3) You disable the ExtensionsFilter configuration check as follows in >>>> web.xml: >>>> >>>> <context-param> >>>> >>>> <param-name>*org*.*apache*.*myfaces*.*CHECK_EXTENSIONS_FILTER*</param-name> >>>> >>>> <param-value>false</param-value> >>>> </context-param> >>>> >>>> /dmc >>>> David Chandler >>>> blog: http://turbomanage.wordpress.com >>>> >>>> On 8/14/06, Dave Brondsema <[EMAIL PROTECTED]> wrote: >>>> >>>>> Marcus Smith wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I tried to run Tomahawk components (which require Javascript) like >>>>>> >>>>> InputCalendar or tree2 in a Portlet on the Liferay Portal without >>>>> >>>> success. >>>> >>>>>> On portlet deployment Exceptions are thrown regarding to the >>>>>> >>>>> ExtensionFilter. >>>>> >>>>>> I know there is a JIRA entry about this issues and many patches are >>>>>> >>>>> available. ( http://issues.apache.org/jira/browse/MYFACES-434). >>>>> >>>>>> Can somebody tell me how to apply which patch to the myfaces src? >>>>>> >>>>>> Has anybody successful deployed portlets using Tomahawk components? >>>>>> >>>>>> >>>>> I use some tomahawk components that do not use javascript, but that >>>>> doesn't really help you. The MYFACES-434 patches are probably >>>>> out-of-date from the current development code and need some tweaking >>>>> before they can be used easily. >>>>> >>>>> We really need a MyFaces developer who works with portlets. >>>>> >>>>> >>>>> FWIW, I use the popup calendar from http://www.jenia.org/ which works >>>>> fine with no filter. >>>>> >>>>> -- >>>>> Dave Brondsema >>>>> Software Developer >>>>> Cornerstone University >>>>> >>>>> >>>>> >>>>> >>>>> >>> -- >>> Yours truly (Atenciosamente), >>> >>> Rogério (_rogerio_) >>> >>> >>> >> >> > > > -- View this message in context: http://www.nabble.com/Potlets-with-Tomahawk-in-Liferay-tf2089812.html#a6034395 Sent from the MyFaces - Users forum at Nabble.com.
