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

[Snjezana Peco (JIRA)]

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

Snjezana Peco resolved JBIDE-4937.
----------------------------------

    Resolution: Done


I have fixed the issues described in https://jira.jboss.org/jira/browse/JBIDE-4937?focusedCommentId=12487667#action_12487667

I have also created a new project https://anonsvn.jboss.org/repos/jbosstools/workspace/snjeza/JBossBirtIntegration
It is a pure Maven project that contains two modules:
- birttag
which creates jboss-seam-birt.jar and depends on JSF libraries
- birtservlet 
which creates jboss-birt-servlet.jar and depends on BIRT libraries.
The BIRT 2.3.2 version is used because the JBoss repository doesn't contain the 2.5.x version which is irrelevant since these libraries are used only at compile time.

The project doesn't depend on Seam.

> 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