Hello; When running TCK 1.0.1-Final with Web Profile Enabled, I have faced some issues. 1* org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest --> ServletTestRunner servlet mapping is not correct Must be mapped as "/*", but it is mapped as "/" · <servlet-mapping> · · <servlet-name>JBoss Test Harness Test Runner</servlet-name> · · <url-pattern>/</url-pattern> · </servlet-mapping> Therefore tests are getting 404 from server.

2* org.jboss.jsr299.tck.tests.context.ContextTest and org.jboss.jsr299.tck.tests.context.ContextDestroysBeansTest "Class MyContextual implements Bean<MySessionBean>" is a session scoped bean and must be passivation capable. To do this, it must implement "PassivationCapable" interface. But it does not implement it. Actually, this issue has been reported and resolved in CR2

Hi Pete, I have opened JIRA issues for them. https://jira.jboss.org/browse/CDITCK-187 https://jira.jboss.org/browse/CDITCK-188 Thanks; --Gurkan ----- Original Message ---- From: Pete Muir <pmuir(a)redhat.com&gt; To: Gurkan Erdogdu <gurkanerdogdu(a)yahoo.com&gt; Cc: weld-dev(a)lists.jboss.org Sent: Tue, October 26, 2010 7:34:04 PM Subject: Re: [weld-dev] TCK 1.0.1-Final Problems On 26 Oct 2010, at 17:20, Gurkan Erdogdu wrote: > Hello; > > When running TCK 1.0.1-Final with Web Profile Enabled, I have faced some > issues. > > 1* > org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ContainerEventTest > > --> ServletTestRunner servlet mapping is not correct > Must be mapped as "/*", but it is mapped as "/" > > · <servlet-mapping> > · · <servlet-name>JBoss Test Harness Test Runner</servlet-name> > · · <url-pattern>/</url-pattern> > · </servlet-mapping> > > Therefore tests are getting 404 from server. Ok, please file a TCK issue. > > 2* org.jboss.jsr299.tck.tests.context.ContextTest and > org.jboss.jsr299.tck.tests.context.ContextDestroysBeansTest > > "Class MyContextual implements Bean<MySessionBean>" is a session scoped bean > and must be passivation capable. > To do this, it must implement "PassivationCapable" interface. But it does not > implement it. Actually, this issue has been reported and resolved in CR2 Is this not on the exclude list for 1.0.1.Final?