December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3698) Error during rendering of an EMail in an event listener causes failure in rendering of next page

by Wayne Bagguley (JIRA)

Error during rendering of an EMail in an event listener causes failure in rendering of next page ------------------------------------------------------------------------------------------------ Key: JBSEAM-3698 URL: https://jira.jboss.org/jira/browse/JBSEAM-3698 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.0.SP1 Environment: Windows XP, Java 6, 2GB RAM, JBoss 4.2.2.GA Reporter: Wayne Bagguley Assignee: Pete Muir I have a method that is defined as a listener like this : @Observer(JpaIdentityStore.EVENT_USER_CREATED) This attempts to send an email to the user when he registers but if the email rendering fails for some reason the exception is caught and the method returns normally. However, instead of the next page being rendered, the original page gets rendered incorrectly, with parts of the form in the wrong place. The failure of rendering the EMail should not affect the progress of the rendering of the next page if the exception is caught. -- 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, 1 month

8
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3056) JPDL navigation and seam

by Florian Keusch (JIRA)

JPDL navigation and seam ------------------------ Key: JBSEAM-3056 URL: http://jira.jboss.com/jira/browse/JBSEAM-3056 Project: Seam Issue Type: Task Components: BPM Reporter: Florian Keusch hi In our applications we have a navigation menu. When we use seam and some jpdl pageflows we have the following problem: if we leave the pageflow with a <s:link propagation="end"> (e.g. clicking on the menu), then the pageflow conversation is ended but also an illegal navigation exception is thrown. This issue was described on the seam framework: http://www.seamframework.org/Community/ProblemWithJPDLIllegalNavigation but I could not find it in this Jira. It's not solved. In the code (PageFlow.java) there's a TODO where the illegal navigation ecxeption is thrown: //now check that the restored view id matches what we expect //from the pageflow node //TODO: we need some way to disable this check, since users // might want some adhoc nav in and out of a pageflow? String viewId = Pages.getViewId(facesContext); if ( !viewId.equals( getPage().getViewId() ) ) { illegalNavigationError(); } If we use <s:link propagation="none"> in our menu navigation then this will not cause a illegal navigation exception, but in the background the conversations are still there not ended. fke -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3699) Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes

by Pete Muir (JIRA)

Slow hot deployment - Seam scans and builds component tree each time to check for hot deploy changes ---------------------------------------------------------------------------------------------------- Key: JBSEAM-3699 URL: https://jira.jboss.org/jira/browse/JBSEAM-3699 Project: Seam Issue Type: Bug Components: Core Reporter: Pete Muir Priority: Blocker Fix For: 2.1.1.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, 1 month

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2232) Reduce debug log level for events

by Christian Bauer (JIRA)

Reduce debug log level for events --------------------------------- Key: JBSEAM-2232 URL: http://jira.jboss.com/jira/browse/JBSEAM-2232 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Christian Bauer Priority: Critical Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for org.jboss.seam.Component, you get thousands of these: 12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events 12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

9
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2690) Websphere on Windows JPA reference guide example throws a ClassCastException

by Jay Balunas (JIRA)

Websphere on Windows JPA reference guide example throws a ClassCastException ---------------------------------------------------------------------------- Key: JBSEAM-2690 URL: http://jira.jboss.com/jira/browse/JBSEAM-2690 Project: JBoss Seam Issue Type: Bug Components: Documentation Issues, Platform interoperability Affects Versions: 2.1.0.A1, 2.0.1.GA Environment: Webspher 6.1 on Windows Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor Several users have reported that on windows following the reference guide JPA example results in a ClassCastException. The issue you are seeing "java.lang.ClassCastException: org.jboss.seam.persistence.EntityManagerFactory incompatible with javax.persistence.EntityManagerFactory:" Following the forum link a user suggests a solution to the issue on windows. Need to verify websphere windows error, and test user fix. Then update document as needed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3151) SpringTransaction : error when using events.raiseTransactionSuccessEvent

by Gonzalez Adrian (JIRA)

SpringTransaction : error when using events.raiseTransactionSuccessEvent ------------------------------------------------------------------------ Key: JBSEAM-3151 URL: http://jira.jboss.com/jira/browse/JBSEAM-3151 Project: Seam Issue Type: Bug Components: Spring Affects Versions: 2.0.2.SP1 Reporter: Gonzalez Adrian This issue happens when using the patch http://jira.jboss.com/jira/browse/JBSEAM-2662. Spring/Jta Status code are converted fine, but I run now in a bug whenever I call events.raiseTransactionSuccessEvent when using Spring transactionManager. To reproduce it, just run spring sample and change in HotelBookingAction the line events.raiseEvent("bookingConfirmed") with events.raiseTransactionSuccessEvent("bookingConfirmed"). You'll have the following stackTrace [1] when you confirm a booking. This is because it's buggy to call data access code in Spring TransactionSynchronization.afterCompletion(). Quote from Spring javadoc (http://static.springframework.org/spring/docs/2.5.x/api/org/springframewo...) : NOTE: The transaction will have been committed already, but the transactional resources might still be active and accessible. As a consequence, any data access code triggered at this point will still "participate" in the original transaction, allowing to perform some cleanup (with no commit following anymore!), unless it explicitly declares that it needs to run in a separate transaction. Hence: Use PROPAGATION_REQUIRES_NEW for any transactional operation that is called from here. I've modified Seam's SpringTransaction synchronization logic to correct this issue. Instead of using Spring extension points (TransactionSynchronization), I've just replicated UTTransaction logic (just using seam's Synchronizations). [1] [07/07/08 11:34:03:468 CEST] 00000026 SystemOut O ERROR [TransactionSynchronizationUtils ] user= - TransactionSynchronization.afterCompletion threw exception org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is java.lang.IllegalStateException: Already value [org.springframework.orm.jpa.EntityManagerHolder@4c464c46] for key [org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean@16e616e6] bound to thread [WebContainer : 0] Caused by: java.lang.IllegalStateException: Already value [org.springframework.orm.jpa.EntityManagerHolder@4c464c46] for key [org.jboss.seam.ioc.spring.SeamManagedEntityManagerFactoryBean@16e616e6] bound to thread [WebContainer : 0] at org.springframework.transaction.support.TransactionSynchronizationManager.bindResource(TransactionSynchronizationManager.java:163) at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:359) at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:350) at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:262) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:102) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:166) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:630) at org.jboss.seam.example.spring.BookingService$$EnhancerByCGLIB$$df01af10.findBookingsByUsername(<generated>) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:50) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.example.spring.BookingService_$$_javassist_3.findBookingsByUsername(BookingService_$$_javassist_3.java) at org.jboss.seam.example.spring.BookingListAction.getBookings(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at org.jboss.seam.example.spring.BookingListAction_$$_javassist_4.getBookings(BookingListAction_$$_javassist_4.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.Component.callComponentMethod(Component.java:2092) at org.jboss.seam.core.Events.raiseEvent(Events.java:84) at org.jboss.seam.async.AsynchronousEvent.call(AsynchronousEvent.java:27) at org.jboss.seam.async.Asynchronous.executeInContexts(Asynchronous.java:76) at org.jboss.seam.async.Asynchronous.execute(Asynchronous.java:45) at org.jboss.seam.async.TransactionSuccessEvent.afterCompletion(TransactionSuccessEvent.java:24) at Rev7677SpringTransaction$JtaSpringSynchronizationAdapter.afterCompletion(Unknown Source) at org.springframework.transaction.support.TransactionSynchronizationUtils.invokeAfterCompletion(TransactionSynchronizationUtils.java:133) at org.springframework.transaction.support.AbstractPlatformTransactionManager.invokeAfterCompletion(AbstractPlatformTransactionManager.java:904) at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:879) at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:707) at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:632) at Rev7677SpringTransaction.commit(Unknown Source) at org.jboss.seam.jsf.SeamPhaseListener.commitOrRollback(SeamPhaseListener.java:603) at org.jboss.seam.jsf.SeamPhaseListener.handleTransactionsAfterPhase(SeamPhaseListener.java:341) at org.jboss.seam.jsf.SeamPhaseListener.afterServletPhase(SeamPhaseListener.java:241) at org.jboss.seam.jsf.SeamPhaseListener.afterPhase(SeamPhaseListener.java:192) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:280) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:989) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:930) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.java:68) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:141) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:281) at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:766) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:674) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:498) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:464) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:90) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1455) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:113) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:454) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:383) at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:102) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:195) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:743) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:873) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3850) begin-conversation flush-mode="MANUAL" doesn't actualy apply MANUAL flushMode

by Uros Majeric (JIRA)

begin-conversation flush-mode="MANUAL" doesn't actualy apply MANUAL flushMode ----------------------------------------------------------------------------- Key: JBSEAM-3850 URL: https://jira.jboss.org/jira/browse/JBSEAM-3850 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: Seam 2.1.0.SP1 JBoss AS 4.2.2 Java 6 Reporter: Uros Majeric Priority: Critical If I put <begin-conversation join="true" flush-mode="MANUAL"/> in some.page.xml it starts me a conversation but flushMode isn't MANUAL. I tried with <action execute="#{actionBean.startConversation}"/> wich is anotated with: @Begin(join = true, flushMode = FlushModeType.MANUAL). In that case ti work's fine. -- 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, 1 month

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2809) s:inputPassword

by Pete Muir (JIRA)

s:inputPassword --------------- Key: JBSEAM-2809 URL: http://jira.jboss.com/jira/browse/JBSEAM-2809 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Reporter: Pete Muir Assigned To: Pete Muir Fix For: 2.1.0.BETA1 Extension of h:inputSecret. Renders two input fields. Attaches a validator by default that checks both fields are the same. Use like <s:inputPassword value="#{identity.password}" /> Advantages: No backing bean logic required, validation done at correct point -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

7
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2436) Session-scoped SFSB which holds entities leaks memory

by Susanne Jarl (JIRA)

Session-scoped SFSB which holds entities leaks memory ----------------------------------------------------- Key: JBSEAM-2436 URL: http://jira.jboss.com/jira/browse/JBSEAM-2436 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Environment: Suse Linux, JBoss 4.2.2.GA, Java 1.6.03, PostgreSQL 8.2 Reporter: Susanne Jarl Session-scoped SFSB which has entities in an object does not get destroyed. It leads to memory leak in production. Please read: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126542 The problem appeared after upgrading to Seam 2.0.0.GA. My code worked fine in Seam 1.2.1. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

7
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3603) Progressbar example is broken

by Jozef Hartinger (JIRA)

Progressbar example is broken ----------------------------- Key: JBSEAM-3603 URL: https://jira.jboss.org/jira/browse/JBSEAM-3603 Project: Seam Issue Type: Bug Components: Examples, Remoting Affects Versions: 2.1.0.GA Environment: JDK 5, 6 JBoss AS 4.2.3.GA Reporter: Jozef Hartinger After pressing go button progressbar starts to run but after several steps it stops and does not continue. After a while "Action complete" message is displayed. -- 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, 2 months

4
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008