myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott O'Bryan" <>
Subject Re: Trinidad Chart
Date Mon, 19 Mar 2012 16:42:42 GMT
Well, liferay and ICEFaces have a tight coupling.  At one point they had
their own bridge, but I think now they use the bridge at Apache which was
written around Trin/Sun JSF examples.  I know Neil did a lot of work with
the ICEFaces/Liferay integration with the Apache Bridge so maybe he could
answer that further.  In any case, if liferay requires you to configure the
resources, you should be able to do that, although I'm not sure that's your
problem.  All of the Trin resources go through a special servlet which
aggregates our JavaScript content and is able to Steve it back to the
browser.  In other words, if the request can reach the servlet, the servlet
should be able to take over from there.

Sent from my iPhone

On Mar 19, 2012, at 10:32 AM, Christian Jurado <> wrote:

Liferay portlets require an additional configuration file, which contains
elements for defining where the JavaScript and css elements are for the
portlet application.  Since the JavaScript for these components is part of
their .jar, there’s no direct way to configure that.  Having said that, I
know ICEFaces works with Liferay 6 through the PortletFaces Bridge, so
somehow that bridge has a way to handle that problem, because it was
created with Liferay 6 in mind.  My understanding is that PortletFaces
Bridge may be tightly enough coupled to ICEFaces that it wouldn’t work with
another library like Trinidad, but I don’t know that for sure and finding
out is my next step.

*From:* Scott O'Bryan []
*Sent:* Monday, March 19, 2012 12:03 PM
*To:* MyFaces Development
*Subject:* Re: Trinidad Chart

Hmm.  Not really.  I'm wondering why liferay would prevent JavaScript from
loading though.

Sent from my iPhone

On Mar 19, 2012, at 9:38 AM, Christian Jurado <> wrote:

Hey Scott,

Thanks, I worded my question poorly but that’s the gist.

Actually, I found a new clue.  In looking at the page source for the
portlet when displayed in Liferay I’m seeing a tag in it saying:

<noscript>This page uses JavaScript and requires a JavaScript enabled
browser.Your browser is not JavaScript enabled.</noscript>

So it looks like that old Liferay 6 JavaScript conflict is rearing its
head.  I was thinking of trying to configure the portlet to point directly
to any script files in the Trinidad .jar files.  (Although I may need to
pull them out separately.)  Do you have any recommendations if I try that



*From:* Scott O'Bryan []
*Sent:* Monday, March 19, 2012 11:32 AM
*To:* MyFaces Development
*Subject:* Re: Trinidad Chart

I don't understand what your asking.  ExternalContextUtils is javadoc'd if
that's what you need.

Sent from my iPhone

On Mar 19, 2012, at 8:51 AM, Christian Jurado <> wrote:

Gotcha, thanks.

  I’ve been looking over the docs on the Trinidad components, such as
web.xml and Trinidad-config.xml options, and I don’t see a complete listing
of all the possible settings and context parameters.  For example, on the
configuration page in the dev guide ( it mentions
the org.apache.myfaces.trinidad.util.ExternalContextUtils.isPortlet, and
that’s how I learned of it.  I also have been using the Facelets with
Trinidad page in the wiki but that doesn’t seem like a fill listing
either.  Can you point me toward such a listing if it exists?



*From:* Scott O'Bryan []
*Sent:* Monday, March 19, 2012 10:46 AM
*To:* MyFaces Development
*Subject:* Re: Trinidad Chart

I did the initial portal compatability project for trin.  I don't remember
doing anything specific for the chart component.

Sent from my iPhone

On Mar 19, 2012, at 8:12 AM, Christian Jurado <> wrote:

Hey Scott,

  What sort of mods do you mean?  Something to make it work better with the


*From:* Scott O'Bryan []
*Sent:* Friday, March 16, 2012 8:23 PM
*To:* MyFaces Development
*Subject:* Re: Trinidad Chart

We don't use jquery, but instead have a homegrown system.  Most of the trin
components should work with the bridge, but I don't recall ever making mods
to the chart component.

Sent from my iPad

On Mar 16, 2012, at 12:53 PM, Christian Jurado <> wrote:

Hey Scott,

  Just as an update:  It works great as a stand-alone.  Will have to look
into the user agent.  Also, I know sometimes components that rely on JQuery
or other similar technologies sometimes have trouble in the Liferay 6


*From:* Scott O'Bryan []
*Sent:* Thursday, March 15, 2012 5:12 PM
*To:* MyFaces Development
*Subject:* Re: Trinidad Chart

No, I have no clue.  I know the chart component requires a valid user
agent.  Maybe that's not getting propagated by liferay?

Also, does your Portlet work As a stand-alone test case?

Sent from my iPhone

On Mar 15, 2012, at 2:58 PM, Christian Jurado <> wrote:


  I’m working on a portlet using MyFaces and Trinidad.  I have successfully
created a working hello world portlet using:

MyFaces 2.0

PortletBridge 3.0

Trinidad 2.0

The environment is

Liferay 6.0.6 running on Tomcat 6.0.29

The portlet installs and runs fine, displaying a simple outputText control,
but the Trinidad Chart control doesn’t display.  The value is set to a
backing bean that is being instantiated (debug statement in the constructor
outputs)  but no graphical display.

My faces-config.xml:

<?xml version=*"1.0"* encoding=*"UTF-8"*?>

<faces-config xmlns=*""*













My Trinidad-config.xml

<?xml version=*"1.0"*?>

<trinidad-config xmlns=*""*>

  <!-- Enable debug output -->



My view.xhtml:








      <trh:head />


                  <h:outputText value=*"BOOYAH!"*/>

                  <tr:chart id=*"chart"* rendered=*"true"* value=*
"#{chartBacking.chartModel}"* type=*"line"*/>



My web.xml:

<?xml version=*"1.0"* encoding=*"UTF-8"*?>

<web-app xmlns:xsi=*""*

      xmlns=*""* xmlns:web=*""*
















      <!-- This cannot be configured currently -->











            <!-- TrinidadFaceletViewHander must be the alternate view
handler if SessionChangeManager

                  is used -->




            <!--Unfortunately, *Facelets* provides no hook for plugging the

                  into the logic handling "facelets.VIEW_MAPPINGS". You
should leave "facelets.VIEW_MAPPINGS"

                  *unset* and use
"org.apache.myfaces.trinidad.FACELETS_VIEW_MAPPINGS" instead. -->




      <!--  More *Trinidad* Configuration -->















            <!-- This assumes that the FacesServlet has been registered -->

            <!-- under the name "faces" -->







I’m getting no errors of any kind, yet all I see in the portlet view is the
value of the h:outputText, and the debug statement in my backing bean
outputs, so at least I know everything else is working.

Any ideas?


View raw message