[jbosstools-issues] [JBoss JIRA] Commented: (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:comment-tabpanel&focusedCommentId=12487076#action_12487076 ] 

Gonzalez Adrian commented on JBIDE-4937:
----------------------------------------

Attachment JBIDE-4937-patch1.zip includes a proposed patch.

To test it, install test case JBIDE-4937-2.zip in order to have a sample :
1. remove WebContent/WEB-INF/lib/jboss-seam-birt.jar
2. add in src/main/ :
	. UIDocument from JBIDE-4937-patch1.zip 
	. UIParameter from JBIDE-4937-patch1.zip 
3. add in src/main/META-INF :
	faces-config.xml from JBIDE-4937-patch1.zip 
	seam-birt.taglib.xml from JBIDE-4937-patch1.zip 
3. restart

Please note that I've changed more than needed in UIDocument class :
- JBossBirtServlet content is included in streaming mode (not copied in a buffer as before).
- I've moved all the logic from encodeBegin to encodeEnd.
- UIDocument restoreState and saveState where modified as per JBIDE-4842.


> 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-patch1.zip
>
>
> 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