December 2010 - weld-issues - Jboss List Archives

[JBoss JIRA] Created: (CDITCK-172) Tests needed for transactional observers that initiate, commit or rollback transactions

by David Allen (JIRA)

Tests needed for transactional observers that initiate, commit or rollback transactions --------------------------------------------------------------------------------------- Key: CDITCK-172 URL: https://jira.jboss.org/browse/CDITCK-172 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.1.0.CR1 Reporter: David Allen Priority: Minor Tests for the following assertion can be implemented and require the container to provide its own UserTransaction to prohibit the calls from succeeding: 10.5 (bd) An observer method may not directly initiate, commit or rollback JTA transactions. At the moment, the specification does not really specify what happens if an observer method does make these calls. -- 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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-73) Test abstract decorators functionally

by Marius Bogoevici (JIRA)

Test abstract decorators functionally ------------------------------------- Key: CDITCK-73 URL: https://jira.jboss.org/jira/browse/CDITCK-73 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA Reporter: Marius Bogoevici Fix For: 1.0.1.CR1 The current assertions for abstract decorators are just testing that abstract classes annotated with decorators can be enabled and are resolved correctly. However, no functionality test involving abstract decorators is carried out. The assertions should test that: a) abstract decorators can be applied at all (i.e. instantiated) b) methods which are not decorating methods of the decorated type cannot be abstract (DefinitionException) c) when abstract decorating method are called as part of the decorator chain, they are actually deferring the call to the injected delegate -- 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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-41) Remove lib/ directories, and instead provide maven goal that will generate lib/

by Pete Muir (JIRA)

Remove lib/ directories, and instead provide maven goal that will generate lib/ -------------------------------------------------------------------------------- Key: CDITCK-41 URL: https://jira.jboss.org/jira/browse/CDITCK-41 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.0.0.CR3 -- 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

12 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (CDITCK-52) Add all tests suitable for EEJB environment to "eejb" group

by Pete Muir (JIRA)

Add all tests suitable for EEJB environment to "eejb" group ----------------------------------------------------------- Key: CDITCK-52 URL: https://jira.jboss.org/jira/browse/CDITCK-52 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.1.0.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

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (CDITCK-61) Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar

by Santiago Pericas-Geertsen (JIRA)

Some tests have dependencies with jsr299-tck-api.jar and jsr299-tck-impl.jar ---------------------------------------------------------------------------- Key: CDITCK-61 URL: https://jira.jboss.org/jira/browse/CDITCK-61 Project: CDI TCK Issue Type: Bug Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.1.CR1 Environment: Solaris x86 / JDK 16u6 / GF v3 Reporter: Santiago Pericas-Geertsen We have found that certain TCK test load classes from jsr299-tck-api.jar and jsr299-tck-impl.jar, but these jars are not normally included in the generated application bundles. An example of such a test is: *.deployment.packaging.installedLibrary.WarInstalledLibraryTest.test which looks for: org/jboss/jsr299/tck/tests/deployment/packaging/installedLibrary/Bar This test fails with GF as these classes are not available to applications. Should jsr299-tck-api.jar and jsr299-tck-impl.jar be bundled with apps? (We can provide a complete list of tests that depend on these TCK jars if needed). -- 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

12 years, 10 months

3
8
0 / 0

[JBoss JIRA] Created: (CDITCK-64) Add test for abstract decorators.

by Marius Bogoevici (JIRA)

Add test for abstract decorators. --------------------------------- Key: CDITCK-64 URL: https://jira.jboss.org/jira/browse/CDITCK-64 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Affects Versions: 1.0.0.GA Reporter: Marius Bogoevici >From 8.1.3: "A decorator may be an abstract Java class, and is not required to implement every method of every decorated type." -- 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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (CDITCK-96) JAX-RS tests needed for CDI

by David Allen (JIRA)

JAX-RS tests needed for CDI --------------------------- Key: CDITCK-96 URL: https://jira.jboss.org/jira/browse/CDITCK-96 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.0.0.GA, 1.0.1.CR1 Reporter: David Allen Fix For: 1.1.0.CR1 It will be useful to test CDI contexts and injection within the context of JAX-RS services to fully test Java EE 6 containers. -- 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

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Created: (CDITCK-81) Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests

by Pete Muir (JIRA)

Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests ---------------------------------------------------------------------------------------- Key: CDITCK-81 URL: https://jira.jboss.org/jira/browse/CDITCK-81 Project: CDI TCK Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tests Reporter: Pete Muir Fix For: 1.1.0.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

12 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (CDITCK-98) Fix <scm> so that release plugin transforms properly

by Pete Muir (JIRA)

Fix <scm> so that release plugin transforms properly ---------------------------------------------------- Key: CDITCK-98 URL: https://jira.jboss.org/jira/browse/CDITCK-98 Project: CDI TCK Issue Type: Task Security Level: Public (Everyone can see) Components: Infrastructure Reporter: Pete Muir Fix For: 1.1.0.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

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (WELD-802) Specialization of Beans registered through portable extension does not work.

by Jozef Hartinger (JIRA)

Specialization of Beans registered through portable extension does not work. ---------------------------------------------------------------------------- Key: WELD-802 URL: https://issues.jboss.org/browse/WELD-802 Project: Weld Issue Type: Bug Affects Versions: 1.1.0.CR2 Reporter: Jozef Hartinger @ApplicationScoped public class SeamExceptionMapper implements ExceptionMapper<Throwable> { } @ApplicationScoped @Specializes public class CatchExceptionMapper extends SeamExceptionMapper { } both these beans are registered via a portable extension: event.addAnnotatedType(manager.createAnnotatedType(CatchExceptionMapper.class)); event.addAnnotatedType(manager.createAnnotatedType(SeamExceptionMapper.class)); The app fails to deploy with the following exception: 15:08:15,668 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=vfs:///home/jharting/jboss/Seam_3/jboss-6.0.0.20101110-CR1/server/default/deploy/seam-tasks.war_WeldBootstrapBean state=Create: org.jboss.weld.exceptions.DefinitionException: WELD-000047 Specializing bean must extend another bean: Managed Bean [class org.jboss.seam.rest.exceptions.CatchExceptionMapper] with qualifiers [@Any @Default] at org.jboss.weld.bean.ManagedBean.specialize(ManagedBean.java:530) [:6.0.0.20101110-CR1] at org.jboss.weld.bean.AbstractBean.initialize(AbstractBean.java:112) [:6.0.0.20101110-CR1] at org.jboss.weld.bean.AbstractClassBean.initialize(AbstractClassBean.java:172) [:6.0.0.20101110-CR1] at org.jboss.weld.bean.ManagedBean.initialize(ManagedBean.java:366) [:6.0.0.20101110-CR1] at org.jboss.weld.bootstrap.AbstractBeanDeployer.deploy(AbstractBeanDeployer.java:110) [:6.0.0.20101110-CR1] at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:216) [:6.0.0.20101110-CR1] at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:359) [:6.0.0.20101110-CR1] at org.jboss.weld.integration.deployer.env.helpers.BootstrapBean.boot(BootstrapBean.java:92) [:6.0.0.20101110-CR1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_23] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_23] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_23] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_23] at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:60) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:168) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66) [jboss-reflect.jar:2.2.0.Alpha9] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:257) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:125) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:202) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42) [jboss-kernel.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10] at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha8] at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha8] at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20101110-CR1] at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1] at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1] at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1] at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1] at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1] at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_23] at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_23] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) [:1.6.0_23] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_23] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_23] at java.lang.Thread.run(Thread.java:662) [:1.6.0_23] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

7
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

weld-issues December 2010