January 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMSERVLET-20) Upgrade to Seam Servlet Alpha 3

by Jozef Hartinger (JIRA)

Upgrade to Seam Servlet Alpha 3 ------------------------------- Key: SEAMSERVLET-20 URL: https://issues.jboss.org/browse/SEAMSERVLET-20 Project: Seam Servlet Issue Type: Task Affects Versions: 3.0.0.Alpha1 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Priority: Minor Reenable org.jboss.seam.rest.test.exceptions.CatchExceptionMappingTest.testUnhandledExceptionRethrown() once SEAMSERVLET-19 is fixed -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-39) @Handles parameter should be permitted in any parameter position

by Dan Allen (JIRA)

@Handles parameter should be permitted in any parameter position ---------------------------------------------------------------- Key: SEAMCATCH-39 URL: https://issues.jboss.org/browse/SEAMCATCH-39 Project: Seam Catch Issue Type: Bug Components: Core Implementation Affects Versions: 3.0.0.Alpha3 Reporter: Dan Allen Assignee: Jason Porter Fix For: 3.0.0.Alpha4 To be consist with CDI observers, the @Handles parameter should be allowed to be used in any position in the list of method arguments. The only restriction is that there is exactly one parameter annotated with @Handles (and it must be of type CaughtException). Here is the relevant section on observer methods for reference: "10.4.2. Declaring an observer method An observer method may be declared by annotating a parameter @javax.enterprise.event.Observes. That parameter is the event parameter. The declared type of the parameter is the observed event type. If a method has more than one parameter annotated @Observes, the container automatically detects the problem and treats it as a definition error." So we should allow: public void handle(BeanManager, @Handles CaughtException<Exception> ex) {} -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4758) Seam is allowing concurrent thread access to conversation components during conversation timeout

by Andrew Duckworth (JIRA)

Seam is allowing concurrent thread access to conversation components during conversation timeout ------------------------------------------------------------------------------------------------ Key: JBSEAM-4758 URL: https://issues.jboss.org/browse/JBSEAM-4758 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.SP1 Reporter: Andrew Duckworth Our application is using Seam 2.0.2. During timeout processing for conversations, it appears that org.jboss.seam.core.Manager allows concurrent thread access to conversation scoped components and does not enforce normal conversation locking. This can cause major problems in components that expect single threaded behaviour and in our application that has some legacy Hibernate Session management, this can lead to multi-threaded access to the same HB session causing unpredictable results. I have verified the issue using a simple POJO and Seam Gen. The code for the POJO is as follows, (the large sleeps are to be able to easily reproduce the race condition): package org.domain.myseamwebproject.managertest; import java.text.SimpleDateFormat; import java.util.Date; import org.jboss.seam.ScopeType; import org.jboss.seam.annotations.Create; import org.jboss.seam.annotations.Destroy; import org.jboss.seam.annotations.Logger; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Observer; import org.jboss.seam.annotations.Scope; import org.jboss.seam.core.Conversation; import org.jboss.seam.log.Log; @Name("convScopedBean") @Scope(ScopeType.CONVERSATION) public class ConvScopedBean { int activeDestroyThreads = 0; int activeTimeoutThreads = 0; @Logger Log log; @Create public void create() { log.info("Bean created {0}", beanId()); } @Destroy public void destroy() { activeDestroyThreads++; log.info("Bean destroy starting on bean {0} in thread: {1} with {2} active destroy threads", beanId(), getCurrentThreadDetails(), activeDestroyThreads); try { Thread.sleep(10000); } catch (InterruptedException e) { e.printStackTrace(); } log.info("Bean destroy finished on bean {0} in thread: {1} with {2} active destroy threads", beanId(), getCurrentThreadDetails(), activeDestroyThreads); activeDestroyThreads--; } private String getCurrentThreadDetails() { return Thread.currentThread().getName() + " id:" + Thread.currentThread().getId(); } private String beanId() { return String.valueOf(System.identityHashCode(this)); } public String getConversationId() { return Conversation.instance().getId(); } public String getCurrentTime() { return (new SimpleDateFormat("hh:mm:ss")).format(new Date()); } @Observer("org.jboss.seam.conversationTimeout") public void conversationTimeout(String cid) { activeTimeoutThreads++; log.info("Conversation timeout starting on bean {0} in thread: {1} with {2} active timeout threads", beanId(), getCurrentThreadDetails(), activeTimeoutThreads); try { Thread.sleep(10000); } catch (InterruptedException e) { e.printStackTrace(); } log.info("Conversation timeout finished on bean {0} in thread: {1} with {2} active timeout threads", beanId(), getCurrentThreadDetails(), activeTimeoutThreads); activeTimeoutThreads--; } } On the xhtml page, I have an a4j:poll that polls getCurrentTime: <f:facet name="header">View Conversation</f:facet> <p>The current long running conversation is: #{convScopedBean.conversationId}</p> <p>The current time is: </p> <h:outputText id="currentTime" value="#{convScopedBean.currentTime}"/> <a4j:poll id="poll" interval="1000" enabled="true" reRender="poll,currentTime"/> <div class="actionButtons"> <s:button value="Go to Home" propagation="none" action="home"/> </div> As soon as the background expired conversation starts to get destroyed during a a4j:poll event, I click the s:button to generate a concurrent request to the same bean. The following log shows that the convScopedBean has multi-threaded access: 16:53:25,763 INFO [ConvScopedBean] Bean created 2923901 16:53:29,199 INFO [ConvScopedBean] Bean created 7938954 16:53:54,317 INFO [ConvScopedBean] Conversation timeout starting on bean 7938954 in thread: http-0.0.0.0-8080-3 id:79 with 1 active timeout threads 16:54:04,318 INFO [ConvScopedBean] Conversation timeout finished on bean 7938954 in thread: http-0.0.0.0-8080-3 id:79 with 1 active timeout threads 16:54:04,321 INFO [ConvScopedBean] Bean destroy starting on bean 12791208 in thread: http-0.0.0.0-8080-3 id:79 with 1 active destroy threads 16:54:14,322 INFO [ConvScopedBean] Bean destroy finished on bean 12791208 in thread: http-0.0.0.0-8080-3 id:79 with 1 active destroy threads 16:55:28,896 INFO [ConvScopedBean] Conversation timeout starting on bean 7938954 in thread: http-0.0.0.0-8080-3 id:79 with 1 active timeout threads 16:55:29,983 INFO [Manager] destroying conversation with garbage lock: 7 16:55:29,985 INFO [ConvScopedBean] Bean created 12033604 16:55:29,987 INFO [ConvScopedBean] Conversation timeout starting on bean 12033604 in thread: http-0.0.0.0-8080-2 id:78 with 1 active timeout threads 16:55:31,492 INFO [Manager] destroying conversation with garbage lock: 7 16:55:31,494 INFO [ConvScopedBean] Bean created 7531789 16:55:31,496 INFO [ConvScopedBean] Conversation timeout starting on bean 7531789 in thread: http-0.0.0.0-8080-1 id:77 with 1 active timeout threads 16:55:38,897 INFO [ConvScopedBean] Conversation timeout finished on bean 7938954 in thread: http-0.0.0.0-8080-3 id:79 with 1 active timeout threads 16:55:38,900 INFO [ConvScopedBean] Bean destroy starting on bean 2923901 in thread: http-0.0.0.0-8080-3 id:79 with 1 active destroy threads 16:55:39,988 INFO [ConvScopedBean] Conversation timeout finished on bean 12033604 in thread: http-0.0.0.0-8080-2 id:78 with 1 active timeout threads 16:55:39,991 INFO [ConvScopedBean] Bean destroy starting on bean 2923901 in thread: http-0.0.0.0-8080-2 id:78 with 2 active destroy threads 16:55:41,497 INFO [ConvScopedBean] Conversation timeout finished on bean 7531789 in thread: http-0.0.0.0-8080-1 id:77 with 1 active timeout threads 16:55:41,500 INFO [ConvScopedBean] Bean destroy starting on bean 2923901 in thread: http-0.0.0.0-8080-1 id:77 with 3 active destroy threads 16:55:48,901 INFO [ConvScopedBean] Bean destroy finished on bean 2923901 in thread: http-0.0.0.0-8080-3 id:79 with 3 active destroy threads 16:55:49,992 INFO [ConvScopedBean] Bean destroy finished on bean 2923901 in thread: http-0.0.0.0-8080-2 id:78 with 2 active destroy threads 16:55:50,041 INFO [ConvScopedBean] Bean destroy starting on bean 12033604 in thread: http-0.0.0.0-8080-2 id:78 with 1 active destroy threads 16:55:51,501 INFO [ConvScopedBean] Bean destroy finished on bean 2923901 in thread: http-0.0.0.0-8080-1 id:77 with 1 active destroy threads 16:55:51,536 INFO [ConvScopedBean] Bean destroy starting on bean 7531789 in thread: http-0.0.0.0-8080-1 id:77 with 1 active destroy threads 16:56:00,042 INFO [ConvScopedBean] Bean destroy finished on bean 12033604 in thread: http-0.0.0.0-8080-2 id:78 with 1 active destroy threads 16:56:01,538 INFO [ConvScopedBean] Bean destroy finished on bean 7531789 in thread: http-0.0.0.0-8080-1 id:77 with 1 active destroy threads Can someone tell me if this is a known issue and that @Destroy and @Observer(endConversation) need to manage their own synchronization ? I have looked at the 2.2.1 release and the same issue looks like it is still present. If it would be helpful to have the entire test application WAR, please let me know and I can send it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
5
0 / 0

[JBoss JIRA] Closed: (SEAMFORGE-11) mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-11?page=com.atlassian.jira.plug... ] Lincoln Baxter III closed SEAMFORGE-11. --------------------------------------- Resolution: Cannot Reproduce Bug Thanks Michael! > mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030 > ----------------------------------------------------------------------------------------- > > Key: SEAMFORGE-11 > URL: https://issues.jboss.org/browse/SEAMFORGE-11 > Project: Seam Forge > Issue Type: Bug > Environment: * Maven 3.0.1 > * jdk1.6.0_21 > * Windows 7, 64bit > Reporter: Michael Schuetz > Assignee: Lincoln Baxter III > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-11) mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030

by Michael Schuetz (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-11?page=com.atlassian.jira.plug... ] Michael Schuetz commented on SEAMFORGE-11: ------------------------------------------ Hi Lincoln, yes you're right. After "git pull" and "mvn install -U" the problem disappeared. > mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030 > ----------------------------------------------------------------------------------------- > > Key: SEAMFORGE-11 > URL: https://issues.jboss.org/browse/SEAMFORGE-11 > Project: Seam Forge > Issue Type: Bug > Environment: * Maven 3.0.1 > * jdk1.6.0_21 > * Windows 7, 64bit > Reporter: Michael Schuetz > Assignee: Lincoln Baxter III > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-36) Add front matter to reference guide

by Dan Allen (JIRA)

Add front matter to reference guide ----------------------------------- Key: SEAMCATCH-36 URL: https://issues.jboss.org/browse/SEAMCATCH-36 Project: Seam Catch Issue Type: Task Components: Documentation Affects Versions: 3.0.0.Alpha3 Reporter: Dan Allen Assignee: Jason Porter Priority: Minor Fix For: 3.0.0.Alpha4 Add the front matter stuff like book_info.xml with the list of authors to the reference guide. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
7
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-18) <TAB> completion is inconsistent and buggy

by Lincoln Baxter III (JIRA)

<TAB> completion is inconsistent and buggy ------------------------------------------ Key: SEAMFORGE-18 URL: https://issues.jboss.org/browse/SEAMFORGE-18 Project: Seam Forge Issue Type: Bug Components: Shell Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Fix For: 1.0.0.Alpha1 This needs to be improved greatly. 1) show completion options for all --named parameters 2) don't add repeat parameters once all have been satisfied 3) don't crash 4) allow custom completers to be plugged in -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-12) JavaParser should be able to parse Enums and Interfaces

by Lincoln Baxter III (JIRA)

JavaParser should be able to parse Enums and Interfaces ------------------------------------------------------- Key: SEAMFORGE-12 URL: https://jira.jboss.org/browse/SEAMFORGE-12 Project: Seam Forge Issue Type: Feature Request Components: Java Parser Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
2
0 / 0

[JBoss JIRA] Commented: (SEAMFORGE-11) mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/SEAMFORGE-11?page=com.atlassian.jira.plug... ] Lincoln Baxter III commented on SEAMFORGE-11: --------------------------------------------- Hey Michael, any luck with this? Tried recently? > mvn clean install: Could not find artifact org.eclipse:osgi:jar:3.4.3.R34x_v20081215-1030 > ----------------------------------------------------------------------------------------- > > Key: SEAMFORGE-11 > URL: https://issues.jboss.org/browse/SEAMFORGE-11 > Project: Seam Forge > Issue Type: Bug > Environment: * Maven 3.0.1 > * jdk1.6.0_21 > * Windows 7, 64bit > Reporter: Michael Schuetz > Assignee: Lincoln Baxter III > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-17) Forge should <TAB>-complete defaultValues from Plugin Command Options

by Lincoln Baxter III (JIRA)

Forge should <TAB>-complete defaultValues from Plugin Command Options --------------------------------------------------------------------- Key: SEAMFORGE-17 URL: https://issues.jboss.org/browse/SEAMFORGE-17 Project: Seam Forge Issue Type: Feature Request Components: Brainstorming Reporter: Lincoln Baxter III Priority: Minor for example required="true + defaultValue = "something" Should autoCompletes with the default value if tabbing twice? Not sure if autocompeting the default value is the desired user experience, but worth considering. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2011