[weld-issues] [JBoss JIRA] (WELD-1114) Remaining Weld references after WAR undeployement
Tomas Remes created WELD-1114:
-
Summary: Remaining Weld references after WAR undeployement
Key: WELD-1114
URL: https://issues.jboss.org/browse/WELD-1114
Project: Weld
Issue Type: Enhancement
Components: Bootstrap and Metamodel API
Affects Versions: 1.1.7.Final
Environment: JBoss AS 7.1.1.Final, JProfiler
Reporter: Tomas Remes
Attachments: weld-deployment-test.jps
I am not sure that this can be considered as issue, but when you run JBoss AS
in JProfiler and try to deploy and undeploy simple Weld Web application (for
example numberguess), you can find some referenced Weld classes in JProfiler
even after performing GC. For example WeldBootstrap class, which has incoming
references in following order:
{noformat}
... -> org.jboss.msc.service.ServiceControllerImpl ->
org.jboss.msc.value.ImmediateValue -> org.jboss.as.weld.service.WeldService ->
org.jboss.as.weld.WeldContainer -> org.jboss.weld.bootstrap.WeldBootstrap
{noformat}
JProfiler snapshot is in attachement. In JProfiler you can filter
org.jboss.weld.bootstrap classes and by right clicking you can show selection
in Heap Walker, where you can also find references graph or tree.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1114) Remaining Weld references after WAR undeployement
[
https://issues.jboss.org/browse/WELD-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Remes updated WELD-1114:
--
Attachment: weld-deployment-test.jps
> Remaining Weld references after WAR undeployement
> -
>
> Key: WELD-1114
> URL: https://issues.jboss.org/browse/WELD-1114
> Project: Weld
> Issue Type: Enhancement
> Components: Bootstrap and Metamodel API
>Affects Versions: 1.1.7.Final
> Environment: JBoss AS 7.1.1.Final, JProfiler
>Reporter: Tomas Remes
> Attachments: weld-deployment-test.jps
>
>
> I am not sure that this can be considered as issue, but when you run JBoss AS
> in JProfiler and try to deploy and undeploy simple Weld Web application (for
> example numberguess), you can find some referenced Weld classes in JProfiler
> even after performing GC. For example WeldBootstrap class, which has incoming
> references in following order:
> {noformat}
> ... -> org.jboss.msc.service.ServiceControllerImpl ->
> org.jboss.msc.value.ImmediateValue -> org.jboss.as.weld.service.WeldService
> -> org.jboss.as.weld.WeldContainer -> org.jboss.weld.bootstrap.WeldBootstrap
> {noformat}
> JProfiler snapshot is in attachement. In JProfiler you can filter
> org.jboss.weld.bootstrap classes and by right clicking you can show selection
> in Heap Walker, where you can also find references graph or tree.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1126) Arquillian tests fail using IPV6
Tomas Remes created WELD-1126: - Summary: Arquillian tests fail using IPV6 Key: WELD-1126 URL: https://issues.jboss.org/browse/WELD-1126 Project: Weld Issue Type: Bug Components: Testing Infrastructure (Mocks and Harness Integration) Affects Versions: 1.1.7.Final Reporter: Tomas Remes It is actually not problem of Weld functionality, but some problem of HtmlUnit used in tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1126) Arquillian tests fail using IPV6
[ https://issues.jboss.org/browse/WELD-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12689967#comment-12689967 ] Tomas Remes commented on WELD-1126: --- My git pull request is almost done for this, so if anyone can assign to me, it's not problem. > Arquillian tests fail using IPV6 > - > > Key: WELD-1126 > URL: https://issues.jboss.org/browse/WELD-1126 > Project: Weld > Issue Type: Bug > Components: Testing Infrastructure (Mocks and Harness Integration) >Affects Versions: 1.1.7.Final >Reporter: Tomas Remes > > It is actually not problem of Weld functionality, but some problem of > HtmlUnit used in tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1126) Arquillian tests fail using IPV6
[ https://issues.jboss.org/browse/WELD-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomas Remes updated WELD-1126: -- Git Pull Request: https://github.com/weld/core/pull/196 pull request sent > Arquillian tests fail using IPV6 > - > > Key: WELD-1126 > URL: https://issues.jboss.org/browse/WELD-1126 > Project: Weld > Issue Type: Bug > Components: Testing Infrastructure (Mocks and Harness Integration) >Affects Versions: 1.1.7.Final >Reporter: Tomas Remes > > It is actually not problem of Weld functionality, but some problem of > HtmlUnit used in tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1126) Arquillian tests fail using IPV6
[
https://issues.jboss.org/browse/WELD-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690056#comment-12690056
]
Tomas Remes commented on WELD-1126:
---
Run JBoss AS using IPV6 by:
{noformat}
${JBOSS_HOME/bin/standalone.sh -b=::1 -bmanagement=::1 -bunsecure=::1
-Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true
--server-config=standalone-full.xml
{noformat}
Update Weld by:
{noformat}
mvn clean verify -Pupdate-jboss-as -f jboss-as/jboss-as-7/pom.xml
{noformat}
Execute tests by:
{noformat}
mvn clean verify -Dincontainer-remote -Ptests -f tests-arquillian/pom.xml -U
-Dnode.address=::1
{noformat}
> Arquillian tests fail using IPV6
> -
>
> Key: WELD-1126
> URL: https://issues.jboss.org/browse/WELD-1126
> Project: Weld
> Issue Type: Bug
> Components: Testing Infrastructure (Mocks and Harness Integration)
>Affects Versions: 1.1.7.Final
>Reporter: Tomas Remes
>Assignee: Ales Justin
>
> It is actually not problem of Weld functionality, but some problem of
> HtmlUnit used in tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1268) Wrong version in as7-installer pom
Tomas Remes created WELD-1268 Wrong version in as7-installer pom Issue Type: Bug Affects Versions: 2.0.0.Beta1 Assignee: Unassigned Created: 29/Nov/12 4:32 AM Description: as7-installer/pom.xml uses 2.0.0-SNAPSHOT. This should be 2.0.0.Beta1 Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1271) Failing test Weld1234Test on AS7.1.1
Tomas Remes
created WELD-1271
Failing test Weld1234Test on AS7.1.1
Issue Type:
Bug
Affects Versions:
2.0.0.Beta1
Assignee:
Unassigned
Created:
29/Nov/12 9:44 AM
Description:
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertTrue(Assert.java:27)
at org.jboss.weld.tests.enterprise.weld1234.Weld1234Test.testRemovedEjbToString(Weld1234Test.java:61)
The proxy name doesn't contain string "REMOVED" when running with AS7.1.1.Final.
String toString = exceptionGenerator.toString();
assertTrue(toString.contains("REMOVED"));
Environment:
AS7.1.1.Final
Fix Versions:
2.0.0.Beta2
Project:
Weld
Priority:
Major
Reporter:
Tomas Remes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-308) Add missing tests for ProcessAnnotatedType event
Tomas Remes resolved CDITCK-308 as Done Add missing tests for ProcessAnnotatedType event Pushed with https://github.com/jboss/cdi-tck/commit/244e854c935b81c5ee4786ab5a1f7d801a81dbfa Change By: Tomas Remes (01/Feb/13 7:58 AM) Status: Open Resolved Fix Version/s: 1.1.0.Beta4 Resolution: Done This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1356) NPE when deploying intercepted bean, which cannot be proxyable
Tomas Remes created WELD-1356 NPE when deploying intercepted bean, which cannot be proxyable Issue Type: Bug Affects Versions: 2.0.0.Beta5 Assignee: Jozef Hartinger Created: 08/Mar/13 7:20 AM Description: When you try to deploy application with intercepted bean, which cannot be proxyable due to the following rule: classes which don’t have a non-private constructor with no parameters, you'll get following NPE instead of DefinitionException: jboss.deployment.unit."test.war".WeldStartService: Failed to start service at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] Caused by: java.lang.NullPointerException at org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedConstructorImpl.of(EnhancedAnnotatedConstructorImpl.java:57) at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.initEnhancedSubclass(SubclassedComponentInstantiator.java:63) at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.(SubclassedComponentInstantiator.java:56) at org.jboss.weld.injection.producer.SubclassedComponentInstantiator.(SubclassedComponentInstantiator.java:52) at org.jboss.weld.injection.producer.BeanInjectionTarget.initializeAfterBeanDiscovery(BeanInjectionTarget.java:108) at org.jboss.weld.injection.producer.InjectionTargetInitializationContext.initialize(InjectionTargetInitializationContext.java:42) at org.jboss.weld.injection.producer.InjectionTargetService.initialize(InjectionTargetService.java:57) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:470) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:62) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] ... 3 more Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1356) NPE when deploying intercepted bean, which cannot be proxyable
Tomas Remes updated WELD-1356 NPE when deploying intercepted bean, which cannot be proxyable Attaching reproducible war Change By: Tomas Remes (08/Mar/13 7:22 AM) Attachment: test.war This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-311) Align the tests for unproxyable bean types with the current wording of the spec
Tomas Remes resolved CDITCK-311 as Done Align the tests for unproxyable bean types with the current wording of the spec Resolved by https://github.com/jboss/cdi-tck/commit/55c1ff017f85693a0ee9d6fc020cdc12046e2d43 Change By: Tomas Remes (19/Mar/13 7:20 AM) Status: Open Resolved Resolution: Done This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1582) Initial request to previously deployed application fails
Tomas Remes
created WELD-1582
Initial request to previously deployed application fails
Issue Type:
Bug
Affects Versions:
2.1.1.Final
Assignee:
Jozef Hartinger
Created:
03/Jan/14 3:56 AM
Description:
Request fails with following exception:
09:42:38,459 ERROR [io.undertow.request] (default I/O-2) Blocking request failed HttpServerExchange{ GET /testapp/home.jsf}: java.lang.NullPointerException
at org.jboss.weld.context.http.HttpConversationContextImpl.getRequestAttribute(HttpConversationContextImpl.java:47)
at org.jboss.weld.context.http.HttpConversationContextImpl.getRequestAttribute(HttpConversationContextImpl.java:13)
at org.jboss.weld.context.AbstractConversationContext.copyConversationIdGeneratorAndConversationsToSession(AbstractConversationContext.java:177)
at org.jboss.weld.context.AbstractConversationContext.sessionCreated(AbstractConversationContext.java:185)
at org.jboss.weld.servlet.ConversationContextActivator.sessionCreated(ConversationContextActivator.java:187)
at org.jboss.weld.servlet.HttpContextLifecycle.sessionCreated(HttpContextLifecycle.java:122)
at org.jboss.weld.servlet.WeldInitialListener.sessionCreated(WeldInitialListener.java:107)
at io.undertow.servlet.core.ApplicationListeners.sessionCreated(ApplicationListeners.java:256)
at io.undertow.servlet.core.SessionListenerBridge.sessionCreated(SessionListenerBridge.java:36)
at io.undertow.server.session.SessionListeners.sessionCreated(SessionListeners.java:32)
at io.undertow.server.session.InMemorySessionManager.createSession(InMemorySessionManager.java:121)
at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:677)
at io.undertow.servlet.spec.ServletContextImpl.getSession(ServletContextImpl.java:691)
at io.undertow.servlet.handlers.SessionRestoringHandler.handleRequest(SessionRestoringHandler.java:110)
at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:56)
at io.undertow.server.handlers.NameVirtualHostHandler.handleRequest(NameVirtualHostHandler.java:53)
at io.undertow.server.handlers.error.SimpleErrorPageHandler.handleRequest(SimpleErrorPageHandler.java:76)
at io.undertow.server.handlers.CanonicalPathHandler.handleRequest(CanonicalPathHandler.java:43)
at io.undertow.server.handlers.ChannelUpgradeHandler.handleRequest(ChannelUpgradeHandler.java:158)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:164)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:142)
at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:46)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.2.0.Beta4.jar:3.2.0.Beta4]
at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:87) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
at org.xnio.nio.WorkerThread.run(WorkerThread.java:531) [xnio-nio-3.2.0.Beta4.jar:3.2.0.Beta4]
Environment:
WildFly 8.0.0.CR1
Project:
Weld
Priority:
Major
Reporter:
Tomas Remes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-is
[weld-issues] [JBoss JIRA] (WELD-1582) Initial request to previously deployed application fails
Tomas Remes updated WELD-1582 Initial request to previously deployed application fails Change By: Tomas Remes (03/Jan/14 3:56 AM) Attachment: testapp.war This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-397) Improve ApplicationScopeEventMultiWarTest by using Testable.archiveToTest()
Tomas Remes started work on CDITCK-397 Improve ApplicationScopeEventMultiWarTest by using Testable.archiveToTest() Change By: Tomas Remes (19/Mar/14 3:15 AM) Status: Open Coding In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1632) Cannot run numberguess on Jetty and execute ftests on embedded-tomcat
Tomas Remes created WELD-1632 Cannot run numberguess on Jetty and execute ftests on embedded-tomcat Issue Type: Bug Affects Versions: 2.2.0.Beta2 Assignee: Jozef Hartinger Components: Examples Created: 26/Mar/14 5:26 AM Description: Running "mvn war:inplace jetty:run -Pjetty" for numberguess produces: java.lang.ClassNotFoundException: org.jboss.weld.environment.servlet.Listener at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50) at org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:259) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:235) at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:227) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:430) at org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:383) at org.eclipse.jetty.server.handler.ContextHandler.loadClass(ContextHandler.java:1528) at org.eclipse.jetty.webapp.StandardDescriptorProcessor.visitListener(StandardDescriptorProcessor.java:1893) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.eclipse.jetty.webapp.IterativeDescriptorProcessor.visit(IterativeDescriptorProcessor.java:85) at org.eclipse.jetty.webapp.IterativeDescriptorProcessor.process(IterativeDescriptorProcessor.java:72) at org.eclipse.jetty.webapp.MetaData.resolve(MetaData.java:367) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1240) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:717) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:494) at org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:298) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:172) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95) at org.eclipse.jetty.server.Server.doStart(Server.java:282) at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:65) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64) at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:520) at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:365) at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:523) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555) at org.
[weld-issues] [JBoss JIRA] (CDITCK-396) Test non-trivial portable extensions configuration scenarios
Tomas Remes updated CDITCK-396 Test non-trivial portable extensions configuration scenarios Change By: Tomas Remes (01/Apr/14 4:51 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/55 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1647) Complete checks for lifecycle events invocation at runtime
Tomas Remes created WELD-1647 Complete checks for lifecycle events invocation at runtime Issue Type: Bug Affects Versions: 2.2.0.CR1 Assignee: Jozef Hartinger Components: Extensions Created: 04/Apr/14 9:52 AM Description: Basically it's to reflect all changes mentioned in CDI-425. Currently there are some checks for "write/add/set" methods mainly in BeforeBeanDiscovery, AfterTypeDiscovery and AfterBeanDiscovery AFAIK. There's need to expand these checks for all methods mentioned in the CDI issue - namely AfterDeploymentValidation, ProcessAnnotatedType, ProcessBean, ProcessBeanAttributes, ProcessInjectionPoint etc. I am not sure, if there's need for some extra check for situation -e.g when accessing PAT during ProcessBean event, but this should result to IllegalException as well. Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1647) Complete checks for lifecycle events invocation at runtime
Tomas Remes updated WELD-1647 Complete checks for lifecycle events invocation at runtime Change By: Tomas Remes (04/Apr/14 9:53 AM) Description: Basically it's to reflect all changes mentioned in CDI-425. Currently there are some checks for "write/add/set" methods mainly in BeforeBeanDiscovery, AfterTypeDiscovery and AfterBeanDiscovery AFAIK. There's need to expand these checks for all methods mentioned in the CDI issue - namely AfterDeploymentValidation, ProcessAnnotatedType, ProcessBean, ProcessBeanAttributes, ProcessInjectionPoint etc.I am not sure, if there's need for some extra check for situation -e.g when accessing PAT during ProcessBean event, but this should result to IllegalException IllegalStateException as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-405) Create tests for CDI-425
Tomas Remes updated CDITCK-405 Create tests for CDI-425 Change By: Tomas Remes (07/Apr/14 6:39 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/56 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1650) Weld SE boot time performance regression
Tomas Remes created WELD-1650 Weld SE boot time performance regression Issue Type: Bug Affects Versions: 2.2.0.CR2, 2.2.0.Alpha1 Assignee: Jozef Hartinger Components: Java SE Support, Performance and Scalability Created: 08/Apr/14 6:40 AM Description: There's significant performance regression in boot time of Weld SE. Test uses 1 annotated beans with default bean-discovery mode. This issue was introduced with 2.2.0.Alpha1 version. Numbers are following: Weld version boot time (s) 2.1.2.Final 34.73 2.2.0.Alpha1 41.85 I did commit bisect and it looks like it was introduced with this commit b5cb5e6904460d9cdbee6266ec789444c397b205. It needs further investigation. Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1650) Weld SE boot time performance regression
Tomas Remes updated WELD-1650 Weld SE boot time performance regression Change By: Tomas Remes (08/Apr/14 6:42 AM) Description: There's significant performance regression in boot time of Weld SE. Test uses 1 annotated beans with default bean-discovery mode (without jandex) . This issue was introduced with 2.2.0.Alpha1 version. Numbers are following:||Weld version|| boot time (s)||| 2.1.2.Final | 34.73 || 2.2.0.Alpha1 | 41.85 |I did commit bisect and it looks like it was introduced with this commit b5cb5e6904460d9cdbee6266ec789444c397b205. It needs further investigation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-406) Create tests for CDI-392
Tomas Remes updated CDITCK-406 Create tests for CDI-392 Change By: Tomas Remes (09/Apr/14 9:59 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/58 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1651) Specialization of generic beans throws inappropriate exception
Tomas Remes
created WELD-1651
Specialization of generic beans throws inappropriate exception
Issue Type:
Bug
Affects Versions:
2.2.0.CR2, 1.1.19.Final
Assignee:
Jozef Hartinger
Created:
10/Apr/14 4:54 AM
Description:
Having this e.g this class:
public class BeanDefaultextends AbstractClass> {
}
and its specialization like this:
@Specializes
public class BeanCustomextends AbstractClass> extends BeanDefault {
}
will result in:
Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-001511: Specializing bean Managed Bean [class mypackage.BeanCustom] with qualifiers [@Any @Default] does not have bean type class mypackage.BeanDefault of specialized bean Managed Bean [class mypackage.BeanDefault] with qualifiers [@Any @Default]
This is IMHO inappropriate since the type BeanDefault is present. CDI spec says just:
Formally, a bean X is said to specialize another bean Y if either:
...
Furthermore, X must have all the bean types of Y. If X does not have some bean type of Y, the container automatically de-
tects the problem and treats it as a definition error.
Project:
Weld
Priority:
Major
Reporter:
Tomas Remes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1651) Specialization of generic beans throws inappropriate exception
Tomas Remes commented on WELD-1651 Specialization of generic beans throws inappropriate exception Once the issue is fixed, test prepared at https://github.com/weld/core/pull/541 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1654) Update doc chapters about Tomcat and Jetty deployments
Tomas Remes created WELD-1654 Update doc chapters about Tomcat and Jetty deployments Issue Type: Bug Affects Versions: 2.2.0.CR2 Assignee: Jozef Hartinger Components: Documentation Created: 14/Apr/14 8:26 AM Description: There is need to update/rewrite following chapters: http://docs.jboss.org/weld/reference/latest/en-US/html_single/#tomcat http://docs.jboss.org/weld/reference/latest/en-US/html_single/#jetty Tomcat 6 is not supported. Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-278) Extends test coverage of InjectionTarget support for non-contextual components supporting injection
Tomas Remes assigned CDITCK-278 to Tomas Remes Extends test coverage of InjectionTarget support for non-contextual components supporting injection Change By: Tomas Remes (17/Apr/14 9:21 AM) Assignee: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-409) Create tests for not covered assertions for 11.4. Alternative metadata sources
Tomas Remes created CDITCK-409 Create tests for not covered assertions for 11.4. Alternative metadata sources Issue Type: Enhancement Assignee: Tomas Remes Created: 17/Apr/14 9:51 AM Description: Check assertions for this section and implements missing tests. Project: CDI TCK Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1660) Registering alternative during AfterTypeDiscovery event fails with NPE
Tomas Remes
created WELD-1660
Registering alternative during AfterTypeDiscovery event fails with NPE
Issue Type:
Bug
Assignee:
Jozef Hartinger
Created:
22/Apr/14 8:05 AM
Description:
Following code fails with NPE, because the priority is null in org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder#getGlobalAlternativeMap
public void afterTypeDiscovery(@Observes AfterTypeDiscovery event) {
event.getAlternatives().add(IntegerBean.class);
}
Stacktrace:
13:54:10,245 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC01: Failed to start service jboss.deployment.unit."4ded9a73-c1a8-48b2-b884-ec631181e7b3.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."4ded9a73-c1a8-48b2-b884-ec631181e7b3.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_45]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
Caused by: java.lang.NullPointerException: null value in entry: class org.jboss.cdi.tck.tests.definition.bean.custom.IntegerBean=null
at com.google.common.collect.CollectPreconditions.checkEntryNotNull(CollectPreconditions.java:33)
at com.google.common.collect.SingletonImmutableBiMap.(SingletonImmutableBiMap.java:39)
at com.google.common.collect.ImmutableBiMap.of(ImmutableBiMap.java:57)
at com.google.common.collect.ImmutableMap.of(ImmutableMap.java:80)
at com.google.common.collect.ImmutableMap.copyOf(ImmutableMap.java:292)
at org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder.getGlobalAlternativeMap(GlobalEnablementBuilder.java:193)
at org.jboss.weld.bootstrap.enablement.GlobalEnablementBuilder.createModuleEnablement(GlobalEnablementBuilder.java:236)
at org.jboss.weld.bootstrap.BeanDeployment.createEnablement(BeanDeployment.java:219)
at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:363)
at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
... 3 more
Project:
Weld
Priority:
Major
Reporter:
Tomas Remes
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1661) Consider possible code clean-up
Tomas Remes created WELD-1661 Consider possible code clean-up Issue Type: Enhancement Affects Versions: 2.2.0.SP1 Assignee: Jozef Hartinger Created: 22/Apr/14 9:01 AM Description: I've gone through the Weld code coverage report (including TCK, tests, arquillian tests) and discovered bunch of likely useless (not called) classes and some pieces of code. Classes are: org.jboss.weld.bootstrap.ExtensionBeanDeployerEnvironment org.jboss.weld.context.ForwardingWeldCreationalContext org.jboss.weld.context.beanstore.ForwardingNamingScheme org.jboss.weld.context.beanstore.http.LazyCyclicSessionBeanStore org.jboss.weld.exceptions.NullableDependencyException org.jboss.weld.executor.TaskPerItemTaskFactory org.jboss.weld.injection.ForwardingInjectionTarget org.jboss.weld.interceptor.util.InterceptorMetadataException org.jboss.weld.manager.RemoveMetadataWrapperFunction org.jboss.weld.resolution.ForwardingInterceptorResolvable org.jboss.weld.resources.SharedObjectFacade org.jboss.weld.serialization.NoopSerializableHolder org.jboss.weld.util.annotated.ForwardingAnnotatedConstructor org.jboss.weld.util.annotated.ForwardingAnnotatedField org.jboss.weld.util.annotated.ForwardingAnnotatedParameter org.jboss.weld.util.annotated.ForwardingWeldAnnotation org.jboss.weld.util.annotated.ForwardingWeldConstructor org.jboss.weld.util.annotated.ForwardingWeldField org.jboss.weld.util.annotated.ForwardingWeldMember (called, but only in classes mentioned in this list) org.jboss.weld.util.annotated.ForwardingWeldMethod org.jboss.weld.util.annotated.ForwardingWeldParameter org.jboss.weld.util.collections.ArrayListSupplier org.jboss.weld.util.collections.ArraySetSupplier org.jboss.weld.util.collections.ConcurrentHashSetSupplier org.jboss.weld.util.collections.CopyOnWriteArrayListSupplier org.jboss.weld.util.collections.DefaultValueMap org.jboss.weld.util.collections.SetView org.jboss.weld.util.dom.NodeListIterable org.jboss.weld.util.dom.NodeListIterator (called in the class above only) org.jboss.weld.util.reflection.ClassLoaderFunction Following pieces of code could be likely also removed: org.jboss.weld.injection.DynamicInjectionPoint#DynamicInjectionPoint(org.jboss.weld.injection.SLSBInvocationInjectionPoint, java.lang.String) org.jboss.weld.injection.DynamicInjectionPoint#readResolve org.jboss.weld.util.Beans#findInterceptorBindingConflicts - not sure but I guess the if statement is useless in for cycle org.jboss.weld.util.bean.WrappedBeanHolder - this class is used in static classes, which are not likely referenced anywhere. org.jboss.weld.util.bytecode.DescriptorUtils#descriptorStringToParameterArray org.jboss.weld.util.bytecode.DescriptorUtils#isWide(java.lang.Class) org.jboss.weld.util.bytecode.DescriptorUtils#getConstructorDescriptor org.jboss.weld.util.bytecode.DescriptorUtils#getMethodDescriptor(java.lang.reflect.Method) All changes are available https://github.com/tremes/core/commit/6e7a4595d8b1cf4eaf1dee9a8924c4f1ee9e0cd2, but I still need to test it properly. Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-410) some tests fail with Java8
Tomas Remes commented on CDITCK-410 some tests fail with Java8 Hey Mark. I was able to reproduce this issue only for the second test (DisposalMethodDefinitionTest). It seems to me unlikely to fail in ConditionalObserverTest, since there's rule one request context per one test method. In other words I don't think request context is active more than one test method, therefore I can't see any way how can asserts related to RecluseSpider bean (in this case) fail. On which container do you test? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1662) Not possible to use wrapped injectionTarget for many EE components
Tomas Remes created WELD-1662 Not possible to use wrapped injectionTarget for many EE components Issue Type: Bug Affects Versions: 2.2.0.SP1 Assignee: Jozef Hartinger Components: Extensions Created: 24/Apr/14 7:32 AM Description: It looks like that actually it is possible to use wrapped injectionTarget only for managed beans and implementations of ServletContextListener. This should be available also for: session bean servlet filter WS endpoint EJB interceptor tag handler Project: Weld Priority: Major Reporter: Tomas Remes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-278) Extends test coverage of InjectionTarget support for non-contextual components supporting injection
Tomas Remes updated CDITCK-278 Extends test coverage of InjectionTarget support for non-contextual components supporting injection Change By: Tomas Remes (24/Apr/14 7:33 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/62 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1662) Not possible to use wrapped injectionTarget for many EE components
Tomas Remes commented on WELD-1662 Not possible to use wrapped injectionTarget for many EE components TCK test available at https://github.com/cdi-spec/cdi-tck/pull/62 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1660) Registering alternative during AfterTypeDiscovery event fails with NPE
Tomas Remes commented on WELD-1660 Registering alternative during AfterTypeDiscovery event fails with NPE TCK test available at https://github.com/cdi-spec/cdi-tck/pull/63 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-410) some tests fail with Java8
Tomas Remes updated CDITCK-410 some tests fail with Java8 Here are some reasonable changes. However I'll strongly encourage to update testng to (at least) 5.10 in OWB. I've tried it and the failures magically disappeared at jdk8. Change By: Tomas Remes (25/Apr/14 10:55 AM) Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/63 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-412) Expand test for 11.5.2. AfterTypeDiscovery methods
Tomas Remes created CDITCK-412 Expand test for 11.5.2. AfterTypeDiscovery methods Issue Type: Enhancement Assignee: Tomas Remes Created: 29/Apr/14 2:27 AM Description: Expand these test to test adding alternatives/interceptors/decorators and update assertions to reflect CDI-434 changes. Project: CDI TCK Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1670) Not possible to wrap and replace observer method injection point
Title: Message Title Tomas Remes created an issue Weld / WELD-1670 Not possible to wrap and replace observer method injection point Issue Type: Bug Affects Versions: 2.2.0.SP1 Assignee: Jozef Hartinger Components: Extensions Created: 07/May/14 3:04 AM Priority: Major Reporter: Tomas Remes Having e.g. this: public void observerMilk(@Observes Milk milk, @Any Fruit fruit) and trying to wrap the second parameter fruit (injection point) will fail during validation in org.jboss.weld.annotated.enhanced.jlr.AbstractEnhancedAnnotatedCallable, because callable instance has only one parameter (injection point) and common java method has two parameters. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000614: Incorrect number of AnnotatedParameters 1 on AnnotatedMethod [UnbackedAnnotatedMethod] public org.jboss.cdi.tck.tests.extensions.alternative.metadata.Grocery.observerMilk(@Observes TropicalFruit). AnnotatedMethod has [[UnbackedAnnotatedParameter]
[weld-issues] [JBoss JIRA] (WELD-1670) Not possible to wrap and replace observer method injection point
Title: Message Title Tomas Remes resolved as Won't Fix Sorry wrongly implemented test Weld / WELD-1670 Not possible to wrap and replace observer method injection point Change By: Tomas Remes Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-413) Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml
Title: Message Title Tomas Remes created an issue CDI TCK / CDITCK-413 Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml Issue Type: Bug Assignee: Tomas Remes Created: 07/May/14 7:39 AM Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing
[weld-issues] [JBoss JIRA] (CDITCK-415) Fix possible concurrency issue in ApplicationScopeEventMultiWarTest
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-415 Fix possible concurrency issue in ApplicationScopeEventMultiWarTest Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/66 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-415) Fix possible concurrency issue in ApplicationScopeEventMultiWarTest
Title: Message Title Tomas Remes started work on CDITCK-415 Change By: Tomas Remes Status: Open Coding In Progress Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-415) Fix possible concurrency issue in ApplicationScopeEventMultiWarTest
Title: Message Title Tomas Remes stopped work on CDITCK-415 Change By: Tomas Remes Status: Coding In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-413) Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-413 Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-413) Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml
Title: Message Title Tomas Remes resolved as Done Resolved by: https://github.com/cdi-spec/cdi-tck/commit/61d277d14f12dbac8e104cd2a04ca66111657728 CDI TCK / CDITCK-413 Fix chapter ordering from 11.5.9 in tck-audit-cdi.xml Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1675) Wrapped typeClosure not used for session beans
Title: Message Title
Tomas Remes created an issue
Weld / WELD-1675
Wrapped typeClosure not used for session beans
Issue Type:
Bug
Affects Versions:
2.2.1.Final
Assignee:
Jozef Hartinger
Components:
Extensions
Created:
13/May/14 9:14 AM
Priority:
Major
Reporter:
Tomas Remes
Overriden method public Set getTypeClosure() is not used for session beans. For example this session bean still has Object, Pasta, ItalianFood types:
@Stateless
public class Pasta extends ItalianFood {}
however the overriden method returns set containing only Pasta, Object types.
[weld-issues] [JBoss JIRA] (WELD-1675) Wrapped typeClosure not used for session beans
Title: Message Title Tomas Remes commented on WELD-1675 Re: Wrapped typeClosure not used for session beans TCK test available in https://github.com/tremes/cdi-tck/compare/CDITCK-409 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-18) TCK should test both synchronous and asynchronous calls when verifying container requirements
Title: Message Title Tomas Remes resolved as Out of Date CDI TCK / CDITCK-18 TCK should test both synchronous and asynchronous calls when verifying container requirements Change By: Tomas Remes Status: Open Resolved Resolution: Out of Date Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-81) Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests
Title: Message Title Tomas Remes resolved as Rejected porting package can be used - see http://docs.jboss.org/cdi/tck/reference/latest/en-US/html_single/#porting-package CDI TCK / CDITCK-81 Switch to using specialized ObjectInputStream/ObjectOutputStream for serialization tests Change By: Tomas Remes Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-172) Tests needed for transactional observers that initiate, commit or rollback transactions
Title: Message Title Tomas Remes resolved as Out of Date We can open new issue, once is CDI-213 resolved. CDI TCK / CDITCK-172 Tests needed for transactional observers that initiate, commit or rollback transactions Change By: Tomas Remes Status: Open Resolved Resolution: Out of Date Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-330) Verify all AsyncListener tests are correct
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-330 Verify all AsyncListener tests are correct I've reviewed these mentioned tests and IMO it looks fine and meaningful. I also expanded AsyncListener tests for conversations - see PR. Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/67 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-417) BeanRegistrationByExtensionInEarLibraryTest is not portable
Title: Message Title Tomas Remes resolved as Done Resolved with commit eeb5df32a23ef4dcd3f8b4a5c6097fd70f0aa944 and 8dc20564dfd1a1936529fa0fa076c39d6bcbab60 CDI TCK / CDITCK-417 BeanRegistrationByExtensionInEarLibraryTest is not portable Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-419) Add sig files for Java SE 8 to CDI 1.0 and CDI 1.1 TCKs
Title: Message Title Tomas Remes assigned an issue to Tomas Remes CDI TCK / CDITCK-419 Add sig files for Java SE 8 to CDI 1.0 and CDI 1.1 TCKs Change By: Tomas Remes Assignee: Martin Kouba Tomas Remes Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-420) InterceptorModularityTest is not portable
Title: Message Title Tomas Remes created an issue CDI TCK / CDITCK-420 InterceptorModularityTest is not portable Issue Type: Bug Assignee: Martin Kouba Created: 22/May/14 1:28 AM Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) Tested EAR contains two WARs, which are not isolated. One is referencing the second one in its manifest. This fails on GF. Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-s
[weld-issues] [JBoss JIRA] (CDITCK-419) Add sig files for Java SE 8 to CDI 1.0 and CDI 1.1 TCKs
Title: Message Title Tomas Remes resolved as Done Sig files for jdk8 added - 1.0 branch aeb22c5c45fe5d91f6f8e7a39d53989facacf9f2 1.1 branch 8afb3db114b69acb59bb36299db1b9efa00b5d21 CDI TCK / CDITCK-419 Add sig files for Java SE 8 to CDI 1.0 and CDI 1.1 TCKs Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-409) Create tests for not covered assertions for 11.4. Alternative metadata sources
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-409 Create tests for not covered assertions for 11.4. Alternative metadata sources Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/70 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-421) Tests using security annotations are not portable
Title: Message Title Tomas Remes created an issue CDI TCK / CDITCK-421 Tests using security annotations are not portable Issue Type: Bug Affects Versions: 1.2.0.Final Assignee: Tomas Remes Created: 23/May/14 3:18 AM Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) Affected tests are: org.jboss.cdi.tck.interceptors.tests.contract.aroundInvoke.AroundInvokeAccessInterceptorTest org.jboss.cdi.tck.interceptors.tests.contract.aroundTimeout.AroundTimeoutInterceptorTest
[weld-issues] [JBoss JIRA] (CDITCK-310) Verify all JAX-WS-related tests are portable
Title: Message Title Tomas Remes resolved as Done Reviewed. JAX-WS related tests are passing on WildFly (except org.jboss.cdi.tck.tests.lookup.injection.non.contextual.WebServiceInjectionIntoNonContextualComponentTest - https://issues.jboss.org/browse/WFLY-3262) and GlassFish. CDI TCK / CDITCK-310 Verify all JAX-WS-related tests are portable Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-418) InterceptorEnvironmentJNDISessionBeanTest is not portable
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-418 InterceptorEnvironmentJNDISessionBeanTest is not portable Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-412) Expand test for 11.5.2. AfterTypeDiscovery methods
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-412 Expand test for 11.5.2. AfterTypeDiscovery methods Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/72 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-412) Expand test for 11.5.2. AfterTypeDiscovery methods
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-412 Expand test for 11.5.2. AfterTypeDiscovery methods Change By: Tomas Remes Fix Version/s: 2.0.0.Alpha1 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-423) RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface
Title: Message Title Tomas Remes created an issue CDI TCK / CDITCK-423 RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface Issue Type: Bug Affects Versions: 1.2.0.Final Assignee: Tomas Remes Created: 04/Jun/14 7:53 AM Fix Versions: 1.2.1.Final, 2.0.0.Alpha1 Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) Add Comment
[weld-issues] [JBoss JIRA] (CDITCK-423) RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface
Title: Message Title Tomas Remes resolved as Done Resolved with additional name mapping on EJBs. CDI TCK / CDITCK-423 RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-423) RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface
Title: Message Title Tomas Remes resolved as Done The use of mappedName() was reverted and additional remote interface was addded. CDI TCK / CDITCK-423 RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface Change By: Tomas Remes Status: Reopened Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-424) Revise tests where dependent beans are destroyed manually
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-424 Revise tests where dependent beans are destroyed manually Change By: Tomas Remes Fix Version/s: 2.0.0.Alpha1 Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/74 Add Comment This message was sent by Atlassian JIRA (v6.2.3#6260-sha1:63ef1d6) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-424) Revise tests where dependent beans are destroyed manually
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-424 Revise tests where dependent beans are destroyed manually Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-426) Some TransactionalObserverTest test methods are missing assertions
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-426 Some TransactionalObserverTest test methods are missing assertions Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-427) NormalSelfConsumingDependentProducer is illegal
Title: Message Title Tomas Remes commented on CDITCK-427 Re: NormalSelfConsumingDependentProducer is illegal I think this is legal and matches the tested assertion: The container is required to support circularities in the bean dependency graph where at least one bean participating in every circular chain of dependencies has a normal scope I guess incompletely initialized contextual instance is used in this case. Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-425) Revise org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionTarget.ContainerEventTest
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-425 Revise org.jboss.cdi.tck.tests.extensions.lifecycle.processInjectionTarget.ContainerEventTest Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1662) Not possible to use wrapped injectionTarget for some EE components
Title: Message Title Tomas Remes updated an issue Weld / WELD-1662 Not possible to use wrapped injectionTarget for some EE components Change By: Tomas Remes Summary: Not possible to use wrapped injectionTarget for many some EE components Affects Version/s: 2.2.2.Final It looks like that actually it is possible to use Using custom wrapped injectionTarget only for managed beans and implementations of ServletContextListener. This InjectionTarget should be available also for: session beanservletfilter WS endpointEJB interceptor tag handler Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1662) Not possible to use wrapped injectionTarget for some EE components
Title: Message Title Tomas Remes edited a comment on WELD-1662 Re: Not possible to use wrapped injectionTarget for some EE components In TCK test master branch there is available at https://github org . com/ jboss. cdi -spec/cdi- . tck /pull/62 .tests.extensions.lifecycle.processInjectionTarget.WrappedInjectionTargetTest Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-427) NormalSelfConsumingDependentProducer is illegal
Title: Message Title Tomas Remes commented on CDITCK-427 Re: NormalSelfConsumingDependentProducer is illegal Ok, true. I am going to remove the test. Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-427) NormalSelfConsumingDependentProducer is illegal
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-427 NormalSelfConsumingDependentProducer is illegal Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-428) org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.InterceptorLifeCycleTest.testInterceptorInstanceCreatedWhenTargetInstanceCreated assumes that
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-428 org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.InterceptorLifeCycleTest.testInterceptorInstanceCreatedWhenTargetInstanceCreated assumes that interception is implemented via subclassing Change By: Tomas Remes Fix Version/s: 2.0.0.Alpha1 Fix Version/s: 1.2.2.Final Affects Version/s: 1.2.1.Final Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-428) org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.InterceptorLifeCycleTest.testInterceptorInstanceCreatedWhenTargetInstanceCreated assumes that
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-428 org.jboss.cdi.tck.interceptors.tests.contract.interceptorLifeCycle.InterceptorLifeCycleTest.testInterceptorInstanceCreatedWhenTargetInstanceCreated assumes that interception is implemented via subclassing Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-424) Revise tests where dependent beans are destroyed manually
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-424 Revise tests where dependent beans are destroyed manually Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-417) BeanRegistrationByExtensionInEarLibraryTest is not portable
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-417 BeanRegistrationByExtensionInEarLibraryTest is not portable Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-423) RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-423 RemoteInterfaceNotInAPITypesTest - JNDI names collide on GlassFish for two EJBs with same remote interface Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-415) Fix possible concurrency issue in ApplicationScopeEventMultiWarTest
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-415 Fix possible concurrency issue in ApplicationScopeEventMultiWarTest Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-420) InterceptorModularityTest is not portable
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-420 InterceptorModularityTest is not portable Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-418) InterceptorEnvironmentJNDISessionBeanTest is not portable
Title: Message Title Tomas Remes closed an issue as Done CDI TCK / CDITCK-418 InterceptorEnvironmentJNDISessionBeanTest is not portable Change By: Tomas Remes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-429) CDI TCK custom AnnotatedTypes are often wrong
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-429 CDI TCK custom AnnotatedTypes are often wrong Change By: Tomas Remes Fix Version/s: 2.0.0.Alpha1 Fix Version/s: 1.2.2.Final Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-429) CDI TCK custom AnnotatedTypes are often wrong
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-429 CDI TCK custom AnnotatedTypes are often wrong Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/80 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-430) DecoratorResolutionTest - raw types not tested properly
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-430 DecoratorResolutionTest - raw types not tested properly Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/81 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-430) DecoratorResolutionTest - raw types not tested properly
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-430 DecoratorResolutionTest - raw types not tested properly Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-431) Test that ProcessBean event is fired for interceptors and decorators
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-431 Test that ProcessBean event is fired for interceptors and decorators Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/82 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-432) some TCK tests assume InjectionPoints in decorators and interceptors are working
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-432 some TCK tests assume InjectionPoints in decorators and interceptors are working Change By: Tomas Remes Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/83 Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-431) Test that ProcessBean event is fired for interceptors and decorators
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-431 Test that ProcessBean event is fired for interceptors and decorators Change By: Tomas Remes Status: Open Resolved Fix Version/s: 2.0.0.Alpha1 Fix Version/s: 1.2.2.Final Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-432) some TCK tests assume InjectionPoints in decorators and interceptors are working
Title: Message Title Tomas Remes resolved as Partially Completed Partially fixed. Disputable part with InjectionPoint was removed from 1.2.x branch and keep original test in master (2.0). CDI TCK / CDITCK-432 some TCK tests assume InjectionPoints in decorators and interceptors are working Change By: Tomas Remes Status: Open Resolved Fix Version/s: 1.2.2.Final Resolution: Partially Completed Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-431) Test that ProcessBean event is fired for interceptors and decorators
Title: Message Title Tomas Remes updated an issue CDI TCK / CDITCK-431 Test that ProcessBean event is fired for interceptors and decorators Change By: Tomas Remes Fix Version/s: 1.2.2.Final Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-429) CDI TCK custom AnnotatedTypes are often wrong
Title: Message Title Tomas Remes resolved as Done Annotated*Wrapper structure has been reworked in TCK. CDI TCK / CDITCK-429 CDI TCK custom AnnotatedTypes are often wrong Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-433) Create a test to verify a CDI interceptor is able to obtain metadata about the SESSION bean it intercepts
Title: Message Title Tomas Remes resolved as Done Test org/jboss/cdi/tck/tests/implementation/builtin/metadata/BuiltinMetadataBeanTest expanded to test intercepted and decorated session bean. CDI TCK / CDITCK-433 Create a test to verify a CDI interceptor is able to obtain metadata about the SESSION bean it intercepts Change By: Tomas Remes Status: Open Resolved Fix Version/s: 2.0.0.Alpha1 Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1705) Unable to inject @Intercepted Bean to interceptor of given SessionBean
Title: Message Title Tomas Remes created an issue Weld / WELD-1705 Unable to inject @Intercepted Bean to interceptor of given SessionBean Issue Type: Bug Assignee: Unassigned Created: 11/Jul/14 7:22 AM Priority: Major Reporter: Tomas Remes Security Level: Public (Everyone can see) This attempt fails with: Caused by: java.lang.IllegalArgumentException: Unable to inject Session bean [class org.jboss.cdi.tck.tests.implementation.builtin.metadata.FatYoghurt with qualifiers [@Any @Default]; local interfaces are [FatYoghurt] into [BackedAnnotatedField] @Inject private org.jboss.cdi.tck.tests.implementation.builtin.metadata.YoghurtInterceptor.interceptor at org.jboss.weld.bean.builtin.InterceptorMetadataBean.newInstance(InterceptorMetadataBean.java:53) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.bean.builtin.InterceptorMetadataBean.newInstance(InterceptorMetadataBean.java:41) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.bean.builtin.AbstractBuiltInMetadataBean.create(AbstractBuiltInMetadataBean.java:57) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:69) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:740) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.manager.BeanManagerImpl.getInjectableReference(BeanManagerImpl.java:831) [weld-core-impl-2.2.2.Final.jar:2014-06-27 08:57] at org.jboss.weld.
[weld-issues] [JBoss JIRA] (WELD-1705) Unable to inject @Intercepted Bean to interceptor of given SessionBean
Title: Message Title Tomas Remes updated an issue Weld / WELD-1705 Unable to inject @Intercepted Bean to interceptor of given SessionBean Change By: Tomas Remes Affects Version/s: 2.2.3.Final Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-330) Verify all AsyncListener tests are correct
Title: Message Title Tomas Remes assigned an issue to Tomas Remes CDI TCK / CDITCK-330 Verify all AsyncListener tests are correct Change By: Tomas Remes Assignee: Tomas Remes Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-330) Verify all AsyncListener tests are correct
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-330 Verify all AsyncListener tests are correct Change By: Tomas Remes Status: Open Resolved Fix Version/s: 2.0.0.Alpha1 Fix Version/s: TBD Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-409) Create tests for not covered assertions for 11.4. Alternative metadata sources
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-409 Create tests for not covered assertions for 11.4. Alternative metadata sources Change By: Tomas Remes Status: Open Resolved Fix Version/s: 2.0.0.Alpha1 Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-412) Expand test for 11.5.2. AfterTypeDiscovery methods
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-412 Expand test for 11.5.2. AfterTypeDiscovery methods Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-1392) Setup soak tests
Title: Message Title Tomas Remes resolved as Done Soak tests set up at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Weld/view/Weld%202%20Perf%20WF/ Weld / WELD-1392 Setup soak tests Change By: Tomas Remes Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-414) Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds
Title: Message Title Tomas Remes resolved as Done CDI TCK / CDITCK-414 Create tests regarding bean assignability of parameterized type with type variable(s) with multiple bounds Change By: Tomas Remes Status: Open Resolved Fix Version/s: 2.0.0.Alpha1 Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.2.6#6264-sha1:ee76422) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
