[
https://issues.jboss.org/browse/SOLDER-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lukaszewski updated SOLDER-338:
------------------------------------
Attachment: multi_ear_solder_3_1_0.zip
multi_ear_solder_3_1_1.zip
> Solder can't still inject HttpServletRequest
> --------------------------------------------
>
> Key: SOLDER-338
> URL: https://issues.jboss.org/browse/SOLDER-338
> Project: Solder
> Issue Type: Bug
> Components: Servlet
> Affects Versions: 3.1.0.Final
> Environment: JBoss 7.1.1
> Reporter: Adam Lukaszewski
> Labels: solder
> Attachments: multi_ear_solder_3_1_0.zip, multi_ear_solder_3_1_1.zip
>
>
> Executing identity.logout will cause an java.lang.IllegalStateException:
> Attempted to inject an HttpSession before it has been initialized.
> Before I go into more details I would like to describe some of the main
> findings on that issue and objectives that I want to establish. Since I am
> working on an bigger j2ee project, I decided to package the application as
> ear. One of the further claims was to include a web framework that can ease
> some of the repetitive tasks that developers are faced programming this kind
> applications. I have made my choice: Seam 3.x.x should be the one!
> With this ideas in mind I started to develop a small ear application with
> embedded seam (which should be the starting point of the adventure).
> Everything seams to work perfectly until I have been playing a little bit
> around with the seam-booking example. In order to understand seam and its
> opportunities better I have decided to port the seam-booking app into my ear
> structure. Everything worked very well until I started to implement the
> authentication mechanism. Logging out from the system causes the above
> exception.
> Although I have found a solder-issue (solder-311) and a forum post
> (https://community.jboss.org/message/735049) I could not find any solution
> (completely equal to my problem). The issue suggests to update to
> solder-3.1.1 which should fix the problem but it doesn't!
> Since I have got some deeper insights of packaging seam into an ear project I
> would like to share this intermediate results (maybe to come to a solution).
> Attached you will find two projects.
> multi_ear_solder_3_1_0.zip and multi_ear_solder_3_1_1.zip.
> Both projects are ear applications with some (unfinished) business logic from
> the seam-booking example. The difference, as you maybe expect, is the solder
> version I am using. Hitting the localhost:8080/multi-web should bring you to
> the app. Login as shane (password: 12345) and try to logout again by clicking
> the logout link, then you will see the error regardless which seam version
> you use.
> Although, I think that seam is a perfect artifact in that context my
> development progress stops through this problem. Does anyone have an idea how
> to figure this issue out? Do you think that the authentication module is only
> effected by this problem or will be there also some issues with the other
> modules (like remote, social, jsf,...)? I think the latter one is to be
> expected, isn't it?
> A appreciate any kind of help.
> Cheers,
> Adam L.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
