You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Marcus Smith <sa...@gmx.net> on 2006/08/11 12:14:20 UTC
Potlets with Tomahawk in Liferay
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?
Thanks,
Marcus
--
Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit!
"Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl
Re: Potlets with Tomahawk in Liferay
Posted by Daniel Gradecak <da...@gradecak.com>.
Hi,
I am also working with Liferay and trying to use Myfaces/Tomahawk and
Sandbox ...
You probably know that the first portlet specification does not include
servlet filters, and also it is not possible for a portlet to change
anything in the head of the portal page ...
So I am managing to use all that by setting the CHECK_EXTENSIONS_FILTER
to false and as the scripts will not be included in the page I am doing
it manually so right now I am trying to use Ajax stuffs from the sandbox
and I can integrate it in liferay portlets by adding to my jsp page the
next scripts ...
<script type="text/javascript" src="/my_webapp_root/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11568423/prototype.PrototypeResourceLoader/prototype.js"><!--
//--></script>
/faces/myFacesExtensionResource/ is the url mapping configured in your ExtensionFilter
but what you can do is load your page outside the portal and then you will be able to see all the scripts your component need ...
Good luck,
Daniel
opfau wrote:
> 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 <tu...@gmail.com>:
>>>>
>>>>
>>>>> 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 <da...@brondsema.net> 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_)
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
Re: Potlets with Tomahawk in Liferay
Posted by opfau <ol...@siemens.com>.
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 <tu...@gmail.com>:
>>>
>>>> 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 <da...@brondsema.net> 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.
Re: Potlets with Tomahawk in Liferay
Posted by Daniel Gradecak <da...@gradecak.com>.
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 <tu...@gmail.com>:
>>
>>> 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 <da...@brondsema.net> 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_)
>>
>>
>>
>
>
Re: Potlets with Tomahawk in Liferay
Posted by opfau <ol...@siemens.com>.
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 <tu...@gmail.com>:
>>
>> 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 <da...@brondsema.net> 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#a6034172
Sent from the MyFaces - Users forum at Nabble.com.
Re: Potlets with Tomahawk in Liferay
Posted by Rogerio Pereira <ro...@gmail.com>.
Wiki this please.
2006/8/16, David Chandler <tu...@gmail.com>:
>
> 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 <da...@brondsema.net> 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_)
Re: Potlets with Tomahawk in Liferay
Posted by David Chandler <tu...@gmail.com>.
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.xml context
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 <da...@brondsema.net> 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
>
>
>
>
Re: Potlets with Tomahawk in Liferay
Posted by Dave Brondsema <da...@brondsema.net>.
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