[weld-issues] [JBoss JIRA] Commented: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object
[ https://issues.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591058#comment-12591058 ] John Ament commented on WELD-80: Pete, maybe this is the discrepancy. What if the EJB has no CDI beans in it, and is injected to the bean via @EJB? > Passivation of stateful session beans results in a loss of reference to > injected object > --- > > Key: WELD-80 > URL: https://issues.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 >Reporter: John Ament > Fix For: TBC > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-80) Passivation of stateful session beans results in a loss of reference to injected object
[ https://issues.jboss.org/browse/WELD-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589709#comment-12589709 ] Pete Muir commented on WELD-80: --- I don't think there is any spec issue here, a passivated EJB with CDI services should just work. All the spec could add would be "it should work". What were you thinking of explicitly? > Passivation of stateful session beans results in a loss of reference to > injected object > --- > > Key: WELD-80 > URL: https://issues.jboss.org/browse/WELD-80 > Project: Weld > Issue Type: Bug > Components: Scopes & Contexts > Environment: JBoss AS 5.1 >Reporter: John Ament > Fix For: TBC > > Attachments: statefulpassivate.zip > > > See forum post -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589699#comment-12589699 ] Ales Justin commented on WELD-833: -- We're planning a Weld 1.1.1 release in the next couple of days, which will include this (and other) fix(es). > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589696#comment-12589696 ] Vetle Roeim commented on WELD-833: -- This needs to be fixed in Glassfish 3.1 as well. > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589693#comment-12589693 ] ravi luthra commented on WELD-833: -- If it helps I've been using the patch for a while, no issues since I've done that. Please release a JBoss AS 6.0.1 that includes this! > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589678#comment-12589678 ] Jan Groth commented on WELD-833: Good point then. IMO this issue is blocking _any_ Weld application. Even HelloWorld crashes with ConcurrentModificationException as soon as you start some dedicated clicking - and there's no workaround but hand-patching the app server. Seems like (too) few people using Weld in productive environments. > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589655#comment-12589655 ] Vetle Roeim commented on WELD-833: -- Perhaps I should have been more specific: what I was asking for is a workaround that can be applied outside Weld, without upgrading Weld to an unreleased version. For various reasons it might be difficult to upgrade. > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Issue Comment Edited: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589650#comment-12589650 ] Jan Groth edited comment on WELD-833 at 3/22/11 9:47 AM: - Workaround: Just apply the patch or get the latest org.jboss.weld.context.AbstractConversationContext from github. was (Author: asiandub): Workaround: Just apply the patch.. > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-833) ConcurrentModificationException while deactivating conversations
[ https://issues.jboss.org/browse/WELD-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589650#comment-12589650 ] Jan Groth commented on WELD-833: Workaround: Just apply the patch.. > ConcurrentModificationException while deactivating conversations > > > Key: WELD-833 > URL: https://issues.jboss.org/browse/WELD-833 > Project: Weld > Issue Type: Bug > Components: Conversations >Affects Versions: 1.1.0.CR3, 1.1.0.Final, TBC >Reporter: Jan Groth >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: fix_deletion_of_conversations.patch > > > If a conversation gets deactivated, the code which actually iterates the map > of conversations in org.jboss.weld.context.AbstractConversationContext is > erroneous and easily runs into a ConcurrentModificationException if there is > more than one conversation. We consider this a pretty serious defect because > its not possible to use JBoss AS 6.0 GA for a real-world application. > See attached patch for a fix. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Resolved: (WELD-729) Servlet / listener / filter injection support for Jetty 7 and above
[
https://issues.jboss.org/browse/WELD-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ales Justin resolved WELD-729.
--
Resolution: Done
http://github.com/weld/core/compare/52d0bd6...a4effcc
> Servlet / listener / filter injection support for Jetty 7 and above
> ---
>
> Key: WELD-729
> URL: https://issues.jboss.org/browse/WELD-729
> Project: Weld
> Issue Type: Feature Request
> Components: Servlet Container Support
>Affects Versions: 1.1.0.Beta1
>Reporter: Dan Allen
>Assignee: Ales Justin
> Fix For: 1.2.0.Beta1
>
>
> Jetty changed it's packaging in version 7 when it moved to the Eclipse
> runtimes project. Therefore, the following required class check only works in
> earlier versions of Jetty.
> private static final String JETTY_REQUIRED_CLASS_NAME =
> "org.mortbay.jetty.servlet.ServletHandler";
> boolean jetty = true;
> try
> {
>Reflections.classForName(JETTY_REQUIRED_CLASS_NAME);
> }
> catch (IllegalArgumentException e)
> {
>jetty = false;
> }
> A second check should be performed for the class
> org.eclipse.jetty.servlet.ServletHandler.
> But then we have the issue that the WeldServletHandler extends a class only
> in Jetty 6. So we'll likely need a special classifier for weld-servlet that
> runs on jetty 7 and above.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Resolved: (WELD-784) Servlet / listener / filter injection support for Jetty 7.2
[ https://issues.jboss.org/browse/WELD-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-784. -- Resolution: Done > Servlet / listener / filter injection support for Jetty 7.2 > --- > > Key: WELD-784 > URL: https://issues.jboss.org/browse/WELD-784 > Project: Weld > Issue Type: Bug > Components: Servlet Container Support >Affects Versions: 1.1.0.CR1 >Reporter: Ben Sommerville >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: WeldConfiguration.java, WeldDecorator.java, > WeldWebAppDecorator.java > > > The fix committed for WELD-729 doesn't work under Jetty 7.2. It appears that > the Jetty API has changed between 7.1 and 7.2, which results in servlet/etc > injection not working. > I haven't tested under 8.0 but I notice that the fix refers to 8.0M0, I had > to update that dependency to 8.0M2 in order to get my changes for 7.2 to > compile, which meant I also had to change the jetty 8 support to fix those > compile errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Commented: (WELD-784) Servlet / listener / filter injection support for Jetty 7.2
[ https://issues.jboss.org/browse/WELD-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589631#comment-12589631 ] Ales Justin commented on WELD-784: -- @Ben: I've re-factored how web containers get used, so I didn't use your code at the end. But thanks anyway. Perhaps check what I've done and let me know if things are OK now. > Servlet / listener / filter injection support for Jetty 7.2 > --- > > Key: WELD-784 > URL: https://issues.jboss.org/browse/WELD-784 > Project: Weld > Issue Type: Bug > Components: Servlet Container Support >Affects Versions: 1.1.0.CR1 >Reporter: Ben Sommerville >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: WeldConfiguration.java, WeldDecorator.java, > WeldWebAppDecorator.java > > > The fix committed for WELD-729 doesn't work under Jetty 7.2. It appears that > the Jetty API has changed between 7.1 and 7.2, which results in servlet/etc > injection not working. > I haven't tested under 8.0 but I notice that the fix refers to 8.0M0, I had > to update that dependency to 8.0M2 in order to get my changes for 7.2 to > compile, which meant I also had to change the jetty 8 support to fix those > compile errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Assigned: (WELD-784) Servlet / listener / filter injection support for Jetty 7.2
[ https://issues.jboss.org/browse/WELD-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin reassigned WELD-784: Assignee: Ales Justin > Servlet / listener / filter injection support for Jetty 7.2 > --- > > Key: WELD-784 > URL: https://issues.jboss.org/browse/WELD-784 > Project: Weld > Issue Type: Bug > Components: Servlet Container Support >Affects Versions: 1.1.0.CR1 >Reporter: Ben Sommerville >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: WeldConfiguration.java, WeldDecorator.java, > WeldWebAppDecorator.java > > > The fix committed for WELD-729 doesn't work under Jetty 7.2. It appears that > the Jetty API has changed between 7.1 and 7.2, which results in servlet/etc > injection not working. > I haven't tested under 8.0 but I notice that the fix refers to 8.0M0, I had > to update that dependency to 8.0M2 in order to get my changes for 7.2 to > compile, which meant I also had to change the jetty 8 support to fix those > compile errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] Resolved: (WELD-601) Injection into servlet Listeners on Tomcat and Jetty
[ https://issues.jboss.org/browse/WELD-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ales Justin resolved WELD-601. -- Resolution: Done Re-factored web containers. > Injection into servlet Listeners on Tomcat and Jetty > > > Key: WELD-601 > URL: https://issues.jboss.org/browse/WELD-601 > Project: Weld > Issue Type: Feature Request > Components: Servlet Container Support >Affects Versions: 1.0.0.GA, 1.0.1.CR2 > Environment: Tomcat 6.0.24 standalone >Reporter: Matija Mazi >Assignee: Ales Justin > Fix For: 1.2.0.Beta1 > > Attachments: tests-injection-filter-listener.patch > > > I've written tests for injection into Filters and Listeners; the Filter > injection test passes but the Listener injection test fails on standalone > Tomcat 6.0.24. (I think injection into Listeners works on JBoss Web, though.) > The patch containing the tests is attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
