September 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4589) ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans

by Sebastien Boutte (JIRA)

ManagedEntityWrapper wrap and deserialize with in-depth fields of Stateful Beans -------------------------------------------------------------------------------- Key: JBSEAM-4589 URL: https://jira.jboss.org/jira/browse/JBSEAM-4589 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.GA Reporter: Sebastien Boutte As it is said in documentation (Part : EJB Passivation and the ManagedEntityInterceptor) ; seam is capable of passivate SMPC (EntityManager with @In) and reattach all instances loaded at activation. For simple fields (Entities, Lists, Maps ...) , it works perfectly. For user defined fields (Wrapper with entity object, or more complex structure), this is not the case and cause a lazy exception later after activation. In class ManagedEntityWrapper, methods wrap and deserialize are not able to do in depth operations. -- 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

15 years, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4375) ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation

by Darryl Smith (JIRA)

ManagedEntityInterceptor destroys components in parent nested conversation, when ending a nested conversation ------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4375 URL: https://jira.jboss.org/jira/browse/JBSEAM-4375 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.2.0.GA Reporter: Darryl Smith setup: Parent (cid1) -> First Nested (cid2) ----> Second Nested (cid3) cid3: conversation.endAndRedirect(true); which calls setLongRunningConversation(false); FacesManager's redirect method tries to encode the page parameters of the parent view, which accesses a component created in cid2 the conversation we are returning to. This triggers ManagedEntityWrapper's switchToConversationContextOfComponent which switches the current conversation to cid2 after ManagedEntityWrapper wraps the component ManagedEntityWrapper's restorePreviousConversationContextIfNecessary method is called with oldCid = cid3 which triggers Contexts.getConversationContext().flush(); When flush is invoke the conversation (cid2) isn't long running, so flush removes all components created in cid2 -- 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

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMJMS-1) JmsSession should not be a qualifier

by Jordan Ganoff (JIRA)

JmsSession should not be a qualifier ------------------------------------ Key: SEAMJMS-1 URL: https://jira.jboss.org/browse/SEAMJMS-1 Project: Seam JMS Issue Type: Task Components: Injection Affects Versions: 3.0.0.Alpha1 Reporter: Jordan Ganoff Assignee: Jordan Ganoff JmsSession is currently a qualifier. Injection could be cleaner if it were made a simple annotation. See WELDX's @Category as an example. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
8
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-12) Change package name to org.jboss.seam

by Pete Muir (JIRA)

Change package name to org.jboss.seam ------------------------------------- Key: SEAMWICKET-12 URL: https://jira.jboss.org/jira/browse/SEAMWICKET-12 Project: Seam Wicket Issue Type: Task Affects Versions: 1.0.1.Final Reporter: Pete Muir Fix For: 1.0.2.CR1 -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMWICKET-13) Change build to use Seam group/build etc.

by Pete Muir (JIRA)

Change build to use Seam group/build etc. ----------------------------------------- Key: SEAMWICKET-13 URL: https://jira.jboss.org/jira/browse/SEAMWICKET-13 Project: Seam Wicket Issue Type: Task Reporter: Pete Muir Fix For: 1.0.2.CR1 -- 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

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4700) Hibernate Search 3.2 onwards is not properly detected by Seam 2

by Emmanuel Bernard (JIRA)

Hibernate Search 3.2 onwards is not properly detected by Seam 2 --------------------------------------------------------------- Key: JBSEAM-4700 URL: https://jira.jboss.org/browse/JBSEAM-4700 Project: Seam Issue Type: Bug Components: Search Affects Versions: 2.2.1.CR2 Reporter: Emmanuel Bernard Fix For: 2.2.1.CR3 HibernatePersistenceProvider incorrectly relies on the presence of the Version#VERSION field which is not present in Hibernate 3.2 onwards. This detection code was here to allow support for Hibernate Search 3.0 which we can safely ignore now. The code can be made much more straightforward by only keeping the code inside if (version != null) { } (and keep the try catch surrounding). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4649) HibernatePersistenceProvider has issues with Hibernate Search 3.2.0

by Tom Fank (JIRA)

HibernatePersistenceProvider has issues with Hibernate Search 3.2.0 ------------------------------------------------------------------- Key: JBSEAM-4649 URL: https://jira.jboss.org/jira/browse/JBSEAM-4649 Project: Seam Issue Type: Bug Components: Core, Search Affects Versions: 2.2.1.CR1, 2.2.1.CR2 Environment: JBoss AS 6.0.0.M2 Hibernate 3.5.1 Hibernate Search 3.2.0 Seam 2.2.1.CR1 Reporter: Tom Fank The new proxied persistence provider (introduced in Seam 2.2.1.CR1) needs some rework in order to be compatible with the current release candidate of Hibernate Search... 1) When org.jboss.seam.persistence.HibernatePersistenceProvider is trying to find out if HSearch is available it expects org.hibernate.search.Version to have some static VERSION field, but current release does not provide it. 2) The org.jboss.seam.persistence.HibernateSessionInvocationHandler does not seem to respect the org.hibernate.event.EventSource interface of the delegated Hibernate session. But the (legacy) implementation of FullTextSession still relies on it, so invocations of methods like 'getActionQueue()' need to be handled correctly. -- 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

15 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4697) SubscriptionRegistry.subscribe can cause thread to freeze

by Mark Torres (JIRA)

SubscriptionRegistry.subscribe can cause thread to freeze --------------------------------------------------------- Key: JBSEAM-4697 URL: https://jira.jboss.org/browse/JBSEAM-4697 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.1.2.GA Environment: ubuntu hardy, j2se 64-bit build 1.6.0_17-b04, jboss 4.2.3 Reporter: Mark Torres We ran into an issue where we got really high cpu usage on one instance of our application. Upon inspection in yourkit profiler, we found that the following threads we're consuming all the cpu(see stacktraces below). Upon googling, we saw several posts where concurrent access to hashmap can cause it to enter into an infinite loop. http://lightbody.net/blog/2005/07/hashmapget_can_cause_an_infini.html Subscription registry is using a HashMap and HashSet(for user tokens) below the covers, so I think this issue can be fixed by just using ConcurrentHashMap and ConcurrentHashSet respectively. Thread: ajp-172.17.8.20-8209-2 : priority:5, demon:true, threadId:228, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) Thread: ajp-172.17.8.20-8209-6 : priority:5, demon:true, threadId:279, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495) Thread: ajp-172.17.8.20-8209-10 : priority:5, demon:true, threadId:5336, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) Thread: ajp-172.17.8.20-8209-18 : priority:5, demon:true, threadId:10515, threadState:RUNNABLE, lockName:null java.util.HashMap.transfer(HashMap.java:527) java.util.HashMap.resize(HashMap.java:506) java.util.HashMap.addEntry(HashMap.java:810) java.util.HashMap.put(HashMap.java:416) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) Thread: ajp-172.17.8.20-8209-21 : priority:5, demon:true, threadId:10518, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) Thread: ajp-172.17.8.20-8209-26 : priority:5, demon:true, threadId:10523, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) Thread: ajp-172.17.8.20-8209-29 : priority:5, demon:true, threadId:16450, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) Thread: ajp-172.17.8.20-8209-35 : priority:5, demon:true, threadId:26542, threadState:RUNNABLE, lockName:null java.util.HashMap.put(HashMap.java:405) org.jboss.seam.remoting.messaging.SubscriptionRegistry.subscribe(SubscriptionRegistry.java:121) org.jboss.seam.remoting.messaging.SubscriptionRequest.subscribe(SubscriptionRequest.java:22) org.jboss.seam.remoting.SubscriptionHandler.handle(SubscriptionHandler.java:68) org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBSEAM-4709) Create a functional test for resource download link in UI example

by Martin Gencur (JIRA)

Create a functional test for resource download link in UI example ----------------------------------------------------------------- Key: JBSEAM-4709 URL: https://jira.jboss.org/browse/JBSEAM-4709 Project: Seam Issue Type: Feature Request Components: Examples Reporter: Martin Gencur Assignee: Martin Gencur Fix For: 2.2.1.CR3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4713) EntityConverter should allow empty String

by Cody Lerum (JIRA)

EntityConverter should allow empty String ----------------------------------------- Key: JBSEAM-4713 URL: https://jira.jboss.org/browse/JBSEAM-4713 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.2.1.CR2 Environment: seam 2.2.1CR2, PrimeFaces Reporter: Cody Lerum Fix For: 2.2.1.CR3 When using the <s:convertEntity /> tag along with a component such as primefaces autocomplete the EntityConverter will throw a NumberFormatException when it is passed an empty string as JSF is prone to do. <pf:autoComplete id="fromUserAC" value="#{emailTemplateData.fromUser}" widgetVar="fromUserAC" forceSelection="true" completeMethod="#{userLists.searchUsers}" var="_user" itemValue="#{_user}" itemLabel="#{_user.name}" selectListener="#{emailTemplateDataAddUtil.selectFromUser}" onSelectUpdate="fromUser" required="true"> <s:convertEntity /> </pf:autoComplete> The solution is to add a .isEmpty() check to the converter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2010