[
https://issues.jboss.org/browse/JBSEAM-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600075#comment-12600075
]
Alberto Fernández commented on JBSEAM-4806:
-------------------------------------------
Sorry but the patch has a bug, storing in a ThreadLocal variable causes some
problems to check if an app has ben initialized. It solves deploy issue but
it's necessary to rewrite Lifecycle.isApplicationInitialized(). I'll try next
week,
> failed to load multiple apps with jboss-seam.jar in global classpath
> --------------------------------------------------------------------
>
> Key: JBSEAM-4806
> URL: https://issues.jboss.org/browse/JBSEAM-4806
> Project: Seam 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.2.2.Final
> Environment: Java 1.6.23, Glasshfis v 2.1.1, Solaris 9 and Windows XP.
> Reporter: Alberto Fernández
> Labels: core, lifecycle, seam
> Attachments: lifecycle_multithread.patch, lifecycle_multithread2.patch
>
>
> We have a special setup with seam jars in global classpath on server (some
> tweak needed). WEB-INF/lib is empty in this setup.
> When loading multiple apps on the server, it fails on server restarts because
> the apps are loaded simultaneously with various threads and the class
> org.jboss.seam.contexts.Lifecycle have an static variable "application"
> shared for all threads. The solution: transform the "application" variable to
> a ThreadLocal variable (patch attached)
--
This message is automatically generated by JIRA.
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
