[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=12487327#action_12487327 ] 

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

JBIDE-4937-patch1.zip is really broken :
- included content in embed mode is now inserted in the wrong place [1]
- report name encoding pb now when using frameset mode.

[1] explanation from http://markmail.org/message/rordldae3h45xmwb
'JSF use own ResponseWriter, usualy buffered - since simple call RequestDispatcher.include will insert content in wrong place.
You need create own ResponseWrapper with using JSF ResponseWriter.'

I'll try to make some time next week to work more on it (but it becomes a bit difficult, I'm moving in other projects), and take code from here http://markmail.org/message/le3ijxha55kksnyp to replace the bugged EmbedHttpServletResponseWrapper with ResponseWrapper.

> 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