[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4937) birt - Seam component always null with birt embed

[Gonzalez Adrian (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gonzalez Adrian updated JBIDE-4937:
-----------------------------------

    Attachment: JBIDE-4937-3.zip


This test case allows us to test :
- character encoding problem in embed mode.
- postback problem in embed mode.

And for the last : 'p:param parameters and the other tag attributes are not propagated' - there's no such bug (my fault, sorry !)

To install test case :
1. create a new Seam Web project (with BIRT reporting facet) with package org.domain.sample.session.
2. unzip JBIDE-4937-3.zip into project
this copies components.xml, birttests.xhtml, testbirtembed.xhtmln EncodingHome + EncodingHome.properties, testencoded.xhtml + testencoded.rptdesign + testencodedembed.xhtml, pages.xml
3. update jboss birt libs
. remove jboss-seam-birt.jar and jboss-birt-servlet.jar and replace them with http://fisheye.jboss.org/browse/~raw,r=17773/JBossTools/trunk/birt/plugins/org.jboss.tools.birt.core/resources/jboss-seam-birt.jar and http://fisheye.jboss.org/browse/~raw,r=17709/JBossTools/trunk/birt/plugins/org.jboss.tools.birt.core/resources/jboss-birt-servlet.jar

To reproduce encoding problem :
1. use your browser on http://localhost:8080/ /birttests.seam
    you should see a page with 5 links to birt reports and the output 'this is the euro character : €'
2. execute link Test Encoded Birt.
    The pdf should display the euro character.
3. execute link Test Encoded Birt Embed.
    The embeded html doesn't display correctly the euro character.

To reproduce postback problem :
1. use your browser on http://localhost:8080/ /birttests.seam
2. execute link Test Postback Birt Embed.
    The report should diplay fine (modulo euro character pb).
3. click button Test Postback.
    You should see the message Post Not Supported.

For the question about utf-8 encoding, I think (but not sure - don't know how to activate debug mode in osgi bundles) - that birt always use utf-8 encoding to output reports in HTML format).
See in org.eclipse.birt.report.engine.emitter.html_2.3.2.r232_20090202.jar class org.eclipse.birt.report.engine.emitter.html.HTMLReportEmitter, method
start(IReportContent report) :
    public void start(IReportContent report)
    {
        logger.log(Level.FINE, "[HTMLReportEmitter] Start emitter.");
        this.report = report;
        writer.open(out, "UTF-8");
        ReportDesignHandle designHandle = null;
        Report reportDesign = null;




> birt - Seam component always null with birt embed
> -------------------------------------------------
>
>                 Key: JBIDE-4937
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4937
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: birt
>            Reporter: Gonzalez Adrian
>            Assignee: Snjezana Peco
>             Fix For: 3.1.0.M4
>
>         Attachments: JBIDE-4937-1.zip, JBIDE-4937-2.zip, JBIDE-4937-3.zip, JBIDE-4937-patch1.zip, UIDocument.java
>
>
> I'm using a Seam component in birt report (from a scripted datasource).
> Seam component is in conversation (or even session scope - same result).
> When I try to access a Seam Component from a birt report and when I use embed mode(designType="embed"), Seam component is always null (I'm accessing seam component with Component.getInstance("sampleReportList", false);).
> When I use designType="run", or frameset everything works fine. 
> Tthe issue is due to the session that isn't propagated in embed mode.
> UIDocument class creates a new URLConnection to call JBossBirtServlet without propagating session cookie JSESSIONID (or the session id parameter if session is propagated with url rewriting).
> JBossBirtServlet then calls birt engine, but in a new session context.
> So the scripted source in birt engine cannot get a reference to any object stored in the original session.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira