I finally found some time to take another look at this, and I figured
out the problem in about 30 seconds. :P
Seems the Crystal component needs to be inside both an f:view tag and an
h:form tag. Those had been accidentally omitted because this was a
conversion from the Cyrstal pure-JSP viewer, which requires there to be
nothing else on the page.
Unfortunately, I have immediately run into another problem with this
component, regarding serialization. (Message thread "Omit component from
serializeView()?")
In any case, Mike your comment did help a bit. It pointed me in the
direction of looking for a configuration screwup, rather than thinking
about incompatibilities. Thanks.
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
Mike Kienenberger wrote:
No, I'd say that it means that you've got it misconfigured somehow.
It's either missing a faces-config.xml entry or a view handler entry
or something.
On 9/14/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
Can someone please confirm the meaning of this error message for me.
Does this mean that the Crystal Reports JSF componenets are incompatible
with the MyFaces renderer?
---------
WARN [HtmlRenderKitImpl] Unsupported component-family/renderer-type:
javax.faces.ViewRoot/CrystalReports.ViewerHtmlRenderer
---------
I get that error when trying to view a page with the Crystal Reports
viewer tag. A blank page is displayed. There are several other similar
lines in the log, except they say "No Renderer found for component"...
My Page:
<%@ taglib
uri="http://www.businessobjects.com/jsf/crystalreportsviewers";
prefix="bocrv"%>
<bocrv:reportPageViewer reportSource="#{report.reportSource}"
parameterFields="#{report.fields}"
databaseLogonInfos="#{report.connections}"
displayGroupTree="false"
displayToolbarToggleTreeButton="false"
allowDatabaseLogonPrompting="false"
allowParameterPrompting="false"
displayToolbarLogo="false"
displayToolbarViewList="false"/>
Thanks for any response!
Regards,
Jeff Bischoff
Kenneth L Kurz & Associates, Inc.
