December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Martin Gencur commented on WELD-31: ----------------------------------- Yes, I can do that. The only thing I don't get from the comments is whether I should always update the Glassfish with Weld trunk or not. I can then set it up during the next week. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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] Assigned: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Pete Muir (JIRA)

[ https://issues.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.sy... ] Pete Muir reassigned WELD-31: ----------------------------- Assignee: Martin Gencur (was: Sahoo Sahoo) Martin, would you be able to set up the job sahoo describes in our hudson? > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://issues.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Martin Gencur > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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: (CDITCK-197) Non-contextual WebService injection test fails when deploying on JBoss AS 6.0 CR1

by Marius Bogoevici (JIRA)

Non-contextual WebService injection test fails when deploying on JBoss AS 6.0 CR1 --------------------------------------------------------------------------------- Key: CDITCK-197 URL: https://jira.jboss.org/browse/CDITCK-197 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Marius Bogoevici Priority: Blocker The test from org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest *deploying* on JBoss AS 6.0 CR1 with the following error: Deployment "vfs:///opt/jboss/jboss-6.0.0-SNAPSHOT/server/default/deploy/org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.InjectionIntoWebServiceEndPointTest.war" is in error due to the following reason(s): com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions Two classes have the same XML type name "{http://ws.contextual.non.injection.lookup.tests.tck.jsr299.jboss.org/}isSheepInjected". Use @XmlType.name and @XmlType.namespace to assign different names to them. this problem is related to the following location: at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.jaxws_asm.IsSheepInjected this problem is related to the following location: at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.IsSheepInjected at public org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.IsSheepInjected org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.ObjectFactory.createIsSheepInjected() at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.ObjectFactory Two classes have the same XML type name "{http://ws.contextual.non.injection.lookup.tests.tck.jsr299.jboss.org/}isSheepInjectedResponse". Use @XmlType.name and @XmlType.namespace to assign different names to them. this problem is related to the following location: at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.jaxws_asm.IsSheepInjectedResponse this problem is related to the following location: at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.IsSheepInjectedResponse at public org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.IsSheepInjectedResponse org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.ObjectFactory.createIsSheepInjectedResponse() at org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.ObjectFactory The assertions from the test are not exercised. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
5
0 / 0

[JBoss JIRA] Commented: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Sahoo Sahoo (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Sahoo Sahoo commented on WELD-31: --------------------------------- No, the hudson job will test latest glassfish builds only - whatever Weld version is integrated gets tested as part of that. That's exactly why we are expecting Weld team to run the aforementioned regression tests using Weld trunk/branch builds. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Pete Muir commented on WELD-31: ------------------------------- Sahoo, excellent news. Will this also include a job that has Weld trunk + last GF promoted build (so that we can see any problems we introduce to Weld as we go?) > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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] Issue Comment Edited: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Sahoo Sahoo (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Sahoo Sahoo edited comment on WELD-31 at 12/7/10 2:36 PM: ---------------------------------------------------------- The latest weekly promoted build of GF 3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/promoted/latest-glassfish.zip Similarly the latest nightly build of GF3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/nightly/latest-glassfish.zip Depending on whether you want to use weekly promoted build or nightly build, download the appropriate zip file and unzip it. It will create a directory structure like glassfish3/glassfish/... That's all it takes to install glassfish. In order to integrate a newer version of Weld, just copy your weld-osgi-bundle-${version}.jar to glassfish3/glassfish/modules/weld-osgi-bundle.jar and restart glassfish. I repeat, one must overwrite glassfish3/glassfish/weld-osgi-bundle.jar. As long as the SPIs and APIs are compatible, this should be enough. Instructions to run Glassfish CDI regression tests (GlassFish developer tests) are at: https://svn.java.net/svn/glassfish~svn/trunk/v2/appserv-tests/devtests/cd... The instruction to run the regression tests is in the section "To run all CDI developer tests" in the above README. We are in the process of setting up of a publicly viewable hudson job that runs the CDI developer tests against latest GlassFish, so that Weld team can compare their results with that of our hudson job. I will share that hudson job url as soon as it is ready. Our current test suite is not JUnit or TestNG based yet and can't be integrated into Weld suite suite directly. was (Author: sahoo): The latest weekly promoted build of GF 3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/promoted/latest-glassfish.zip Similarly the latest nightly build of GF3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/nightly/latest-glassfish.zip Depending on whether you want to use weekly promoted build or nightly build, download the appropriate zip file and unzip it. It will create a directory structure like glassfish3/glassfish/... That's all it takes to install glassfish. Instructions to run Glassfish CDI regression tests (GlassFish developer tests) are at: https://svn.java.net/svn/glassfish~svn/trunk/v2/appserv-tests/devtests/cd... The instruction to run the regression tests is in the section "To run all CDI developer tests" in the above README. We are in the process of setting up of a publicly viewable hudson job that runs the CDI developer tests against latest GlassFish, so that Weld team can compare their results with that of our hudson job. I will share that hudson job url as soon as it is ready. Our current test suite is not JUnit or TestNG based yet and can't be integrated into Weld suite suite directly. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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: (WELD-31) JBoss QE Runs WebBeans GlassFish Integration Tests

by Sahoo Sahoo (JIRA)

[ https://jira.jboss.org/browse/WELD-31?page=com.atlassian.jira.plugin.syst... ] Sahoo Sahoo commented on WELD-31: --------------------------------- The latest weekly promoted build of GF 3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/promoted/latest-glassfish.zip Similarly the latest nightly build of GF3.1 is always made available at: http://dlc.sun.com.edgesuite.net/glassfish/3.1/nightly/latest-glassfish.zip Depending on whether you want to use weekly promoted build or nightly build, download the appropriate zip file and unzip it. It will create a directory structure like glassfish3/glassfish/... That's all it takes to install glassfish. Instructions to run Glassfish CDI regression tests (GlassFish developer tests) are at: https://svn.java.net/svn/glassfish~svn/trunk/v2/appserv-tests/devtests/cd... The instruction to run the regression tests is in the section "To run all CDI developer tests" in the above README. We are in the process of setting up of a publicly viewable hudson job that runs the CDI developer tests against latest GlassFish, so that Weld team can compare their results with that of our hudson job. I will share that hudson job url as soon as it is ready. Our current test suite is not JUnit or TestNG based yet and can't be integrated into Weld suite suite directly. > JBoss QE Runs WebBeans GlassFish Integration Tests > -------------------------------------------------- > > Key: WELD-31 > URL: https://jira.jboss.org/browse/WELD-31 > Project: Weld > Issue Type: Feature Request > Components: GlassFish Integration > Environment: GlassFish V3 > Reporter: Roger Kitain > Assignee: Sahoo Sahoo > Fix For: TBC > > > JBoss QE Runs WebBeans / GlassFish integration tests. -- 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: (CDITCK-195) ExplicitConstructorSessionBean must have a no-arg constructor

by Marius Bogoevici (JIRA)

ExplicitConstructorSessionBean must have a no-arg constructor ------------------------------------------------------------- Key: CDITCK-195 URL: https://jira.jboss.org/browse/CDITCK-195 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.2.CR3 Reporter: Marius Bogoevici Fix For: 1.0.3.CR4 ExplicitConstructorSessionBean from org.jboss.jsr299.tck.tests.implementation.enterprise.definition.EnterpriseBeanDefinitionTest must have a no-arg constructor. While the intent of the test is to exercise the usage of the @Inject-annotated constructor, a session bean class must also have a no-arg constructor, as required by EJB 3.1 spec 4.9.2. This may also be a disconnect between the EJB 3.1 and CDI spec, since the no-arg constructor may not actually be used, however it is still a requirement of the specification. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-180) org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public

by Lance Andersen (JIRA)

org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard need to use public ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: CDITCK-180 URL: https://jira.jboss.org/browse/CDITCK-180 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.Final Reporter: Lance Andersen The following two classes are missing public in there declarations: org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard Specification version & section: The EJB Spec states the following in section "4.9.2 Session Bean Class": The class must be defined as public, must not be final, and must not be abstract. The class must be a top level class. This clearly violates that rule. These classes are not public. Tests Affected: testSpecializingBeanHasBindingsOfSpecializedAndSpecializingBean testSpecializingBeanHasNameOfSpecializedBean from org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.EnterpriseBeanSpecializationTest Output: [9/7/10 14:57:34:309 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Farmer does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract [9/7/10 14:57:34:312 CDT] 0000002f annotations E AbstractMergeAction merge An exception occurred while validating an annotation:com.ibm.wsspi.amm.validate.ValidationException: class org.jboss.jsr299.tck.tests.inheritance.specialization.enterprise.Yard does not define a valid enterprise bean; the class is either not declared public or is declared as either final or abstract -- 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

13 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (CDITCK-137) org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest

by Gurkan Erdogdu (JIRA)

org.jboss.jsr299.tck.tests.decorators.invocation.testChainedDecoratorInvocation.DecoratorInvocationTest ------------------------------------------------------------------------------------------------------- Key: CDITCK-137 URL: https://jira.jboss.org/jira/browse/CDITCK-137 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Gurkan Erdogdu Method : testChainedDecoratorInvocation In this test, TCK tests the injection points of the Decortor delegate. But it seems that this test is specific to Weld. In our case, we manage decorator stack via single delegate not via injection each decorator reference to DecoratorInvocationTest -- 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

13 years, 4 months

3
22
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010