[weld-issues] [JBoss JIRA] (WELD-2479) List#remove(Object) does not work for lists returned by AfterTypeDiscovery
Title: Message Title Matej Novotny commented on WELD-2479 Re: List#remove(Object) does not work for lists returned by AfterTypeDiscovery Weld contains similar test as does TCK - org.jboss.weld.tests.extensions.lifecycle.atd.AfterTypeDiscoveryObserverAfterTypeDiscoveryObserver. We should modify that one to have it covered (uses iterators ATM). Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2474) Weld is still using CDI 2.0 literal implementations in several places
Title: Message Title Matej Novotny updated an issue Weld / WELD-2474 Weld is still using CDI 2.0 literal implementations in several places Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1806 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-611) DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA
Title: Message Title Matej Novotny updated CDITCK-611 CDI TCK / CDITCK-611 DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p
Title: Message Title Matej Novotny updated CDITCK-598 CDI TCK / CDITCK-598 org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-609) org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension
Title: Message Title Matej Novotny updated CDITCK-609 CDI TCK / CDITCK-609 org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-591) AlternativeMetadataTest createVegetables and destroyVegetables violate Type Closure rules
Title: Message Title Matej Novotny resolved as Rejected Looks like there are two problems which were discussed here. I'm going to reject this issue, but here is my reasoning why I'm doing so (apart from the fact that both, CDI TCK lead and CDI spec lead, agreed on the test being correct): Firstly, it was disputed that the test restricts the types of the producer in an incorrect way. The test itself does not make use of @Typed to restrict it, it instead replaces the whole AT. The method itself returns Carrot as it is and we only swapped the getTypeClosure() call, which is used to determine bean types of any kind of bean. Hence the producer still makes sense. One of the relevant parts of spec says: ...the container must: call Annotated.getBaseType() to determine the type of an injection point, event parameter or disposed parameter, call Annotated.getTypeClosure() to determine the bean types of any kind of bean, And secondly, in regards to Producer-Disposer matching problem - according to specification, the Annotated interface: getTypeClosure() returns all types to which the base type should be considered assignable. Changing this has direct effect on bean's assignability to injection points but also to disposer methods. This basically says that for every IP, you look at the getBaseType() and then try to match it against all beans' getClosureType() to see if you get a type match. Test changes getTypeClosure() for createVegetable() producer method to Carrot. The disposer method is altered in a similar way, via getBaseType() - again to Carrot. Hence you are now matching disposer's getBaseType() (Carrot) to producer's getTypeClosure() (Carrot) which is totally valid. I reckon that the bits and pieces of important information are scattered throughout the spec but putting them together, I can only see this test as valid, although not a common case for sure. CDI TCK / CDITCK-591 AlternativeMetadataTest createVegetables and destroyVegetables violate Type Closure rules Change By: Matej Novotny Status: Reopened Resolved
[weld-issues] [JBoss JIRA] (CDITCK-584) UnproxyableManagedBeanTest assumes detection at runtime, but the spec requires a 'deployment error'
Title: Message Title Matej Novotny resolved as Rejected Resolving as Rejected. With my TCK lead hat on, I see this test as a correct one and supported by spec. So did former TCK lead and so does CDI spec lead. If you need to dispute this further, please raise a CDI spec issue instead and reformulate respective parts "more clearly" there which could then lead to this test being changed. CDI TCK / CDITCK-584 UnproxyableManagedBeanTest assumes detection at runtime, but the spec requires a 'deployment error' Change By: Matej Novotny Status: Reopened Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
[weld-issues] [JBoss JIRA] (CDITCK-352) Interceptors spec - test the Priority annotation is ignored on interceptors bound using the Interceptors annotation
Title: Message Title Matej Novotny commented on CDITCK-352 Re: Interceptors spec - test the Priority annotation is ignored on interceptors bound using the Interceptors annotation The respective GH issues (since java.net was closed) are: INTERCEPTORS_SPEC-23 -> https://github.com/javaee/interceptors-spec/issues/23 (as of March 21 2018 - resolved) INTERCEPTORS_SPEC-24 -> https://github.com/javaee/interceptors-spec/issues/24 (as of March 21 2018 - still open) Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-598 org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs Change By: Matej Novotny Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/159, https://github.com/cdi-spec/cdi-tck/pull/160 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-598 org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs Change By: Matej Novotny Fix Version/s: 2.1.0.Final Fix Version/s: 2.0.4.Final Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-598) org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between p
Title: Message Title
Matej Novotny commented on CDITCK-598
Re: org.jboss.cdi.tck.tests.event.observer.context.enterprise.staticMethod.SessionBeanStaticObserverMethodInvocationContextTest failing due to discrepancy between platform and ejb specs
Joseph Snyder if the TCK test used module instead of comp would that fix it for you?
toner = (Toner) InitialContext.doLookup("java:module/Toner");
printer = (Printer) InitialContext.doLookup("java:module/Printer");
I see no reason why we couldn't alter the test that way and avoid the cross-spec issue. The test is focused around transactional observers so it shouldn't change a thing. Or is there something I am missing?
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
weld-issues@lists.jboss.org
[weld-issues] [JBoss JIRA] (WELD-2474) Weld is still using CDI 2.0 literal implementations in several places
Title: Message Title
Matej Novotny commented on WELD-2474
Re: Weld is still using CDI 2.0 literal implementations in several places
Back there I recall I was {{grep}}ing through the code and I left some of these in place for I thought them harmless (they were in tests for the most part). But I wonder how come all the tests pass with org.jboss.weld.util.Observers#isContainerLifecycleObserverMethod()) using CDI literals? This should be used in every OM check, right?
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-607) EnterpriseBeanDiscoveryTest assumes that AnnotatedType class must reflect the @Local interface, but this is not backed by the spec
Title: Message Title
Matej Novotny edited a comment on CDITCK-607
Re: EnterpriseBeanDiscoveryTest assumes that AnnotatedType class must reflect the @Local interface, but this is not backed by the spec
[~struberg] I am not sure I can see what it is you find disputable, please provide more details.Is it the expectation of { { AnnotatedType.getJavaClass()}} to return the implementation class of an EJB bean with {{@Local}} interface? The list of classes observed from PAT observer should contain all the classes anyway (impl and local interfaces), as spec mandates that you fire PAT for each of them.
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-609) org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #158 in GitHub CDI TCK / CDITCK-609 org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-607) EnterpriseBeanDiscoveryTest assumes that AnnotatedType class must reflect the @Local interface, but this is not backed by the spec
Title: Message Title
Matej Novotny commented on CDITCK-607
Re: EnterpriseBeanDiscoveryTest assumes that AnnotatedType class must reflect the @Local interface, but this is not backed by the spec
Mark Struberg I am not sure I can see what it is you find disputable, please provide more details. Is it the expectation of {AnnotatedType.getJavaClass()}} to return the implementation class of an EJB bean with @Local interface?
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-608) LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-608 LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown Change By: Matej Novotny Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-608) LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown
Title: Message Title Matej Novotny commented on CDITCK-608 Re: LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown Mark Struberg please provide more context for this. The test you pointed to works with Conversations and events for those are obtained by end end of servlet's service() method - e.g. after the request is done (and not session). So I do not really see any harm done with sessions not being invalidated. Not to mention all the sessions which can possibly linger on the server have their timeouts and after that, servlet should dispose of them. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-608) LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown
Title: Message Title Matej Novotny assigned an issue to Unassigned CDI TCK / CDITCK-608 LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-608) LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-608 LongRunningConversationLifecycleEventTest and others wrongly assume that Session get destroyed at shutdown Change By: Matej Novotny Issue Type: Bug Enhancement Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-609) org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-609 org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension Change By: Matej Novotny Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/157, https://github.com/cdi-spec/cdi-tck/pull/158 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-609) org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension
Title: Message Title Matej Novotny commented on CDITCK-609 Re: org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension This test does not necessarily need to "fail on an EE server" but it may intermittently fail with certain test ordering. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-611) DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #156 in GitHub CDI TCK / CDITCK-611 DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-609) org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-609 org.jboss.cdi.tck.tests.event.observer.priority.contextLifecycleEvent.ApplicationContextLifecycleEventObserverOrderingTest misses to package the TestExtension Change By: Matej Novotny Fix Version/s: 2.1.0.Final Fix Version/s: 2.0.4.Final Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-610) the CDI spec does not require Servlets to be interceptable
Title: Message Title Matej Novotny resolved as Rejected As was said, this is defined by EE spec therefore an expected behaviour. CDI TCK / CDITCK-610 the CDI spec does not require Servlets to be interceptable Change By: Matej Novotny Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-611) DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-611 DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA Change By: Matej Novotny Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/155, https://github.com/cdi-spec/cdi-tck/pull/156 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-611) DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA
Title: Message Title Matej Novotny created an issue CDI TCK / CDITCK-611 DefaultBeanDiscoveryModeTest should be implicit and contain at least one bean class with BDA Issue Type: Bug Affects Versions: 2.0.3.Final Assignee: Matej Novotny Created: 15/Mar/18 5:40 AM Fix Versions: 2.1.0.Final, 2.0.4.Final Priority: Major Reporter: Matej Novotny org.jboss.cdi.tck.tests.deployment.discovery.implicit.DefaultBeanDiscoveryModeTest creates an archive with beans.xml which have mode=annotated but have no version. According to spec, this would classify as explicit archive which is IMO unintended (class is in package named implicit). Also according to specification, an archive with no version has a default bean discovery mode of all. Another problem of the test is that it contains no valid bean class with BDA, only one extension which is disputable (it will effectively be a bean but when scanning the archive, it isn't a bean class with BDA). Adding one another bean class with BDA would solve this. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title
Matej Novotny edited a comment on WELD-2470
Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
[~andreas.r.], [~spanko], [~michid] I have updated the PRs, it now passes the more complex test with hierarchy attached to this JIRA.Feel free to try it out and report back how it works for your projects.FYI if you need to patch your WildFly with this version, then easy way to do so is:* [checkout the PR|https://help.github.com/articles/checking-out-pull-requests-locally/] & build it ({{mvn clean install -DskipTests}})* {{export JBOSS_HOME=/path/to/your/wfly}}* {{mvn clean package -Pupdate-jboss-as -f jboss-as/pom.xml}}** This will take the WildFly from {{JBOSS_HOME}} variable and patch the insides with your currently checkouted version of Weld (snapshot in this case)
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny commented on WELD-2470 Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor I have updated the PRs, it now passes the more complex test with hierarchy attached to this JIRA. Feel free to try it out and report back how it works for your projects. FYI if you need to patch your WildFly with this version, then easy way to do so is: checkout the PR & build it (mvn clean install -DskipTests) export JBOSS_HOME=/path/to/your/wfly mvn clean package -Pupdate-jboss-as -f jboss-as/pom.xml This will take the WildFly from JBOSS_HOME variable and patch the insides with your currently checkouted version of Weld (snapshot in this case) Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny commented on WELD-2470 Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Andreas R. thanks for quick clarification. I can see the problem, but I am unsure how to handle this ATM. One way would be to detect if the method is abstract but that might introduce some problems in combination with decorators. I'll have to think a bit harder on this. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny commented on WELD-2470 Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Hi, Sven Panko Would you be able to create and provide a reproducer for your case? Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny commented on WELD-2470 Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Andreas R. and Michael Düsterhus I proposed a change which fixes the scenario posted here but it would be really neat if you guys could try this fix with your project(s). Many of these proxy changes are very subtle and hard to test (you cannot really test all combinations). You would need to build Weld with that PR branch and use that snapshot version in your projects. PR for Weld 2.4 - https://github.com/weld/core/pull/1802 PR for Weld 3 - https://github.com/weld/core/pull/1801 Let me know if it works for you Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1802 in GitHub Weld / WELD-2470 NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny updated an issue Weld / WELD-2470 NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1801 , https://github.com/weld/core/pull/1802 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny updated an issue Weld / WELD-2470 NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1801 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2468) Uber JAR: weld throws massive amount of java.lang.ClassNotFoundException
Title: Message Title Matej Novotny closed an issue as Rejected But still it doesn't tell me why even jUnit is required here by Weld From what I know, Weld uses JUnit only as test dependency so I would say it's coming from other dependency and Weld is merely trying to load it first but it's missing on CP. I am total Gradle rookie, but from running gradlew dependencies I can see that JUnit 4.12 comes from org.spockframework:spock-core:1.1-groovy-2.4, so it's not Weld. Basically I would say your build.gradle is wrong in how it creates shaded JAR. I have seen some suggestions such as using this plugin. You want an uber JAR with its dependencies shaded (present inside that JAR) so that you don't need to add them to CP later on. Anyway, this isn't Weld bug, it's Gradle build issue in our code, so I'm closing this JIRA. Weld / WELD-2468 Uber JAR: weld throws massive amount of java.lang.ClassNotFoundException Change By: Matej Novotny Status: Open Closed Resolution: Rejected Add Comment
[weld-issues] [JBoss JIRA] (WELD-2470) NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor
Title: Message Title Matej Novotny commented on WELD-2470 Re: NPE Abortion - CDI-Bean / Inheritance / Generics / Interceptor Andreas R. thanks for the report and even more for a minimal reproducer (these constellations are rather difficult to blindly guess)! We'll see what we can do about it. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2468) Uber JAR: weld throws massive amount of java.lang.ClassNotFoundException
Title: Message Title Matej Novotny commented on WELD-2468 Re: Uber JAR: weld throws massive amount of java.lang.ClassNotFoundException I did manage to build it (master and feature branches both) but I had to download latest Gradle (4.6) and use Java 9. Looking at your uber jar: You are missing the classes your uber jar, hence the CNFE I checked some of those CNFE classes, such as org.apache.ivy.core.report.ResolveReport or even javax.servlet.http.HttpServlet You packaging is hence wrong and you either need to fix the uber jar, or run java command and add missing libs on classpath/module-path Many entries inside that uber jar are duplicated property files, beans xsd files, module-info even... You may want to clear this up before going any further Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #75 in GitHub Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Matej Novotny updated an issue Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1797 , https://github.com/weld/api/pull/75 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Matej Novotny updated an issue Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1797 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Matej Novotny updated an issue Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Change By: Matej Novotny Fix Version/s: 3.0.4.Final Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Matej Novotny created an issue Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Issue Type: Task Affects Versions: 3.0.3.Final Assignee: Unassigned Created: 23/Feb/18 4:54 AM Priority: Minor Reporter: Matej Novotny JBoss version of common annotations 1.3 was released - we should switch to it. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
[weld-issues] [JBoss JIRA] (WELD-2465) Switch to JBoss version of commons annotation 1.3
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2465 Switch to JBoss version of commons annotation 1.3 Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-606) org.jboss.cdi.tck.tests.deployment.discovery.enterprise.annotated.EnterpriseDefaultBeanDiscoveryModeTest should fail because of ambiguous beans
Title: Message Title Matej Novotny resolved as Rejected This test verifies just the discovery of producer/disposer/observer method and producer field on an EJB, not injection itself. So we have one injection point (Apple) but... There is no injection point in that test. Hence there is no AmbiguousResolutionException. Note that for disposer methods, the parameter annotated @Disposes is not an injection point. Looking at spec 3.4.2: Declaring disposer method: A disposer method may be declared by annotating a parameter @javax.enterprise.inject.Disposes. That parameter is the disposed parameter. Qualifiers may be declared by annotating the disposed parameter And a bit further it adds: In addition to the disposed parameter, a disposer method may declare additional parameters, which may also specify qualifiers. These additional parameters are injection points. One of the reasons, why it cannot be an IP is (spec link): A disposer method may resolve to multiple producer methods or producer fields declared by the bean class CDI TCK / CDITCK-606 org.jboss.cdi.tck.tests.deployment.discovery.enterprise.annotated.EnterpriseDefaultBeanDiscoveryModeTest should fail because of ambiguous beans Change By: Matej Novotny Status: Open Resolved Resolution: Rejected
[weld-issues] [JBoss JIRA] (WELD-2462) Migrate from findbugs to spotbugs
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1787 in GitHub Weld / WELD-2462 Migrate from findbugs to spotbugs Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2462) Migrate from findbugs to spotbugs
Title: Message Title Matej Novotny updated an issue Weld / WELD-2462 Migrate from findbugs to spotbugs Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1786 , https://github.com/weld/core/pull/1787 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2462) Migrate from findbugs to spotbugs
Title: Message Title Matej Novotny updated an issue Weld / WELD-2462 Migrate from findbugs to spotbugs Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1786 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2462) Migrate from findbugs to spotbugs
Title: Message Title Matej Novotny created an issue Weld / WELD-2462 Migrate from findbugs to spotbugs Issue Type: Task Affects Versions: 2.4.6.Final, 3.0.2.Final Assignee: Unassigned Components: Infrastructure Created: 06/Feb/18 7:20 AM Priority: Major Reporter: Matej Novotny FindBugs is dead for some time and has problems with Java 9. Successor is SpotBugs - same code, different artifacts. It should be fairly easy to migrate it. We will need to change dependencies, profiles and properties. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2462) Migrate from findbugs to spotbugs
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2462 Migrate from findbugs to spotbugs Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2460) JDK 9 - reflection usage, multirelease jar, testing
Title: Message Title
Matej Novotny updated an issue
Weld / WELD-2460
JDK 9 - reflection usage, multirelease jar, testing
Change By:
Matej Novotny
We need to inspect and rework our calls to JDK internal libs - with JDK 9 this is permitted but throws warnings in logs. In JDK 10 this is to be forbidden and {{Handles}} anr/or {{Unsafe}} needs to be used. Once done, we will likely need to java a multirelease JARs as the new solution won't be available in JDK 8. Note that it does not matter whether you use classpath or module path. One such case of our reflection usage is the way we create proxies by calling {{ClassLoader.defineClass()}} (protected method on CL) in {{ClassFileUtils}}. This could instead be done via either {{Unsafe}} or {{Lookup}}.There might be some changes required in classfilewriter itself which is to be discovered (likely related to https://github . com/jbossas/jboss-classfilewriter/issues/14) Another part of this issue is to ensure we are continuously testing on JDK 9 (or 10, doesn't matter) as well as JDK 8.Goal is to be able to execute all our tests with JDK 9 without any WARN messages related to illegal access.
Add Comment
This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849)
[weld-issues] [JBoss JIRA] (WELD-2460) JDK 9 - reflection usage, multirelease jar, testing
Title: Message Title Matej Novotny updated an issue Weld / WELD-2460 JDK 9 - reflection usage, multirelease jar, testing Change By: Matej Novotny Labels: jdk9 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2460) JDK 9 - reflection usage, multirelease jar, testing
Title: Message Title Matej Novotny created an issue Weld / WELD-2460 JDK 9 - reflection usage, multirelease jar, testing Issue Type: Bug Affects Versions: 2.4.6.Final, 3.0.2.Final Assignee: Unassigned Created: 02/Feb/18 8:45 AM Priority: Major Reporter: Matej Novotny We need to inspect and rework our calls to JDK internal libs - with JDK 9 this is permitted but throws warnings in logs. In JDK 10 this is to be forbidden and Handles anr/or Unsafe needs to be used. Once done, we will likely need to java a multirelease JARs as the new solution won't be available in JDK 8. One such case of our reflection usage is the way we create proxies by calling ClassLoader.defineClass() (protected method on CL) in ClassFileUtils. This could instead be done via either Unsafe or Lookup. There might be some changes required in classfilewriter itself which is to be discovered. Another part of this issue is to ensure we are continuously testing on JDK 9 (or 10, doesn't matter) as well as JDK 8. Goal is to be able to execute all our tests with JDK 9 without any WARN messages related to illegal access. Add Comment
[weld-issues] [JBoss JIRA] (CDITCK-605) EJBObserverMethodRemoteBusinessMethod test and the Async counterpart are too strict
Title: Message Title Matej Novotny closed an issue as Rejected EJBObserverMethodRemoteBusinessMethod links to CDI spec 24.1 regarding observers on EJB. Which says: An observer method may also be a non-abstract method of an EJB session bean class. It must be either a business method exposed by a local business interface of the EJB or a static method of the bean class. This clearly disallows methods on remote interfaces to be observer methods - no conditions are stated. The test simply follows that. The intention of the original CDI clarification was to make clear that CDI events are not... That is not what the original issue says, please read up on issues/mail which lead up to this, including: https://issues.jboss.org/browse/CDI-545 https://issues.jboss.org/browse/CDITCK-497 and finally a mail conversation linked in the aforementioned CDI issue - http://lists.jboss.org/pipermail/cdi-dev/2015-July/006993.html Summing up, remote business methods were never intended to be observer methods, that's what the clarification was about. CDI TCK / CDITCK-605 EJBObserverMethodRemoteBusinessMethod test and the Async counterpart are too strict Change By: Matej Novotny Status: Open Closed Resolution: Rejected Add Comment
[weld-issues] [JBoss JIRA] (WELD-2458) OSGi - import javax.ejb optionally
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1785 in GitHub Weld / WELD-2458 OSGi - import javax.ejb optionally Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2458) OSGi - import javax.ejb optionally
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2458 OSGi - import javax.ejb optionally Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2458) OSGi - import javax.ejb optionally
Title: Message Title Matej Novotny updated an issue Weld / WELD-2458 OSGi - import javax.ejb optionally Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1784, https://github.com/weld/core/pull/1785 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2458) OSGi - import javax.ejb optionally
Title: Message Title Matej Novotny updated an issue Weld / WELD-2458 OSGi - import javax.ejb optionally Change By: Matej Novotny Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2458) OSGi - import javax.ejb optionally
Title: Message Title Matej Novotny created an issue Weld / WELD-2458 OSGi - import javax.ejb optionally Issue Type: Bug Affects Versions: 2.4.6.Final, 3.0.2.Final Assignee: Unassigned Components: OSGi support Created: 30/Jan/18 9:15 AM Environment: OSGi Priority: Major Reporter: Matej Novotny When using OSGi bundle outside of EE server, it is required to mandatory provide javax.ejb bundle as well. This is due to change in WELD-2430. It makes sense to make this dependency optional (similarly to what we have here) Add Comment
[weld-issues] [JBoss JIRA] (WELD-2430) EJB no-interface view, non-public method behaviour
Title: Message Title Matej Novotny commented on WELD-2430 Re: EJB no-interface view, non-public method behaviour Martin Kouba a penny for your thoughts^? Grzegorz Grzybek I think we provide OSGi bundle primarily because some EE servers consume it that way (for instance glassfish does that). But that doesn't mean we shouldn't look into this deeper. Sadly I am rather unfamiliar with OSGi in general, so I would need some nudge on how do we go about enabling this. Your point is still valid though and the EJB package should be there as optional import. I'll glance at those two issues you linked. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2430) EJB no-interface view, non-public method behaviour
Title: Message Title Matej Novotny commented on WELD-2430 Re: EJB no-interface view, non-public method behaviour Hi Grzegorz Grzybek Thanks for reporting that. I suppose this problem surfaces when you are running osgi bundle outside EE server? Because in EE server you should have EJB available anyway. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2443) Weld fails to invoke an observer method with a private access
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1767 in GitHub Weld / WELD-2443 Weld fails to invoke an observer method with a private access Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2447) Client proxy serialization support should be container agnostic
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2447 Client proxy serialization support should be container agnostic Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2447) Client proxy serialization support should be container agnostic
Title: Message Title Matej Novotny updated an issue Weld / WELD-2447 Client proxy serialization support should be container agnostic Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1765, https://github.com/weld/core/pull/1766 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2247) Allow to disable parallel container support enforcement
Title: Message Title Matej Novotny updated an issue Weld / WELD-2247 Allow to disable parallel container support enforcement Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1765, https://github.com/weld/core/pull/1766 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2247) Allow to disable parallel container support enforcement
Title: Message Title Matej Novotny updated an issue Weld / WELD-2247 Allow to disable parallel container support enforcement Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1765, https://github.com/weld/core/pull/1766 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2447) Client proxy serialization support should be container agnostic
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1765 in GitHub Weld / WELD-2447 Client proxy serialization support should be container agnostic Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2443) Weld fails to invoke an observer method with a private access
Title: Message Title Matej Novotny commented on WELD-2443 Re: Weld fails to invoke an observer method with a private access Stéphane Appercel I am trying to create a reproducer but it works for me. I am not using SE but standard Weld in embedded container one, but that shouldn't matter. You can take a peek at the reproducer I tried here (last commit). Maybe some of your classes have more complex hierarchy? Inherit some of the observer methods from abstract superclasses etc? What's the difference between your second class (crashing) and third class (working) - could you post the class declarations? (E.g. public class Foo extends Bar) Also forgot to ask, does your problem appear with JDK 9 only? Or JDK 8 as well? Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2445) beans_1_1.xsd is not in org.jboss.weld.xml.XmlSchema
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1764 in GitHub Weld / WELD-2445 beans_1_1.xsd is not in org.jboss.weld.xml.XmlSchema Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2443) Weld fails to invoke an observer method with a private access
Title: Message Title Matej Novotny edited a comment on WELD-2443 Re: Weld fails to invoke an observer method with a private access Hi [~steappe]Thanks for the report but we need to nail down the exact case to make a reproducer.So here are some additional questions:1) Does it work with older Weld? 3.0.1 or perhaps 3.0.0? - just out of curiosity, on which Weld 2.4 version did this work for you?2) Can you share the details about the class which has the private observer which fails? - these exceptions are often connected to a very special case so we need details - what kind of bean is it? What scope? An EJB bean? - whole class hierarchy - generics, all the interfaces and extended classes (and their generics) - if you cannot share your code, could you create a dummy structure similar to what you have there? 3) Any other detail that comes to your mind - especially differences from those private access observers which work for you Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2443) Weld fails to invoke an observer method with a private access
Title: Message Title Matej Novotny commented on WELD-2443 Re: Weld fails to invoke an observer method with a private access Hi Stéphane Appercel Thanks for the report but we need to nail down the exact case to make a reproducer. So here are some additional questions: 1) Does it work with older Weld? 3.0.1 or perhaps 3.0.0? just out of curiosity, on which Weld 2.4 version did this work for you? 2) Can you share the details about the class which has the private observer which fails? these exceptions are often connected to a very special case so we need details what kind of bean is it? What scope? An EJB bean? whole class hierarchy - generics, all the interfaces and extended classes (and their generics) if you cannot share your code, could you create a dummy structure similar to what you have there? Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-604) create a TCK test for alternative sterotype + @Priority on the class
Title: Message Title Matej Novotny updated CDITCK-604 Added a test for this with reference to two separate spec parts (stereotypes and enablement of alternatives via priority). Since it is a new test, it will be part of the future 2.1 TCK release. CDI TCK / CDITCK-604 create a TCK test for alternative sterotype + @Priority on the class Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org
[weld-issues] [JBoss JIRA] (CDITCK-604) create a TCK test for alternative sterotype + @Priority on the class
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-604 create a TCK test for alternative sterotype + @Priority on the class Change By: Matej Novotny Fix Version/s: 2.1.0.Final Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-604) create a TCK test for alternative sterotype + @Priority on the class
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #154 in GitHub CDI TCK / CDITCK-604 create a TCK test for alternative sterotype + @Priority on the class Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-604) create a TCK test for alternative sterotype + @Priority on the class
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-604 create a TCK test for alternative sterotype + @Priority on the class Change By: Matej Novotny Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/154 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2442) After Upgrade to 2.4.6 has NullPointerException in InterceptedSubclassFactory.java:272
Title: Message Title Matej Novotny commented on WELD-2442 Re: After Upgrade to 2.4.6 has NullPointerException in InterceptedSubclassFactory.java:272 Also your sample above shows the exception coming from proxy of AtributoProdutoConverterImpl, which isn't amongst the classes you described so I presume there is some piece missing? A reproducer would be lovely as this way I am just blindly shooting, trying to find that one faulty heirarchy where it will crashes. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2442) After Upgrade to 2.4.6 has NullPointerException in InterceptedSubclassFactory.java:272
Title: Message Title Matej Novotny commented on WELD-2442 Re: After Upgrade to 2.4.6 has NullPointerException in InterceptedSubclassFactory.java:272 Hi Leandro Kersting de Freitas Would you be able to provide minimal reproducer project? I am trying to re-create it from your description, but with no success so far (no NPE in my side so I must be missing something). These problems/errors often depend on a very peculiar class hierarchy and don't manifest themselves otherwise. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2440) Document WeldEvent and WeldInstance
Title: Message Title Matej Novotny updated an issue Weld / WELD-2440 Document WeldEvent and WeldInstance Change By: Matej Novotny Git Pull Request: https://github.com/weld/core/pull/1755, https://github.com/weld/core/pull/1756 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2440) Document WeldEvent and WeldInstance
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1755 in GitHub Weld / WELD-2440 Document WeldEvent and WeldInstance Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-497) Fix the corresponding tests with regarding to CDI-545
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-497 Fix the corresponding tests with regarding to CDI-545 Change By: Matej Novotny Fix Version/s: 1.2.10.Final Fix Version/s: 1.2.11.FiInal Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-497) Fix the corresponding tests with regarding to CDI-545
Title: Message Title Matej Novotny edited a comment on CDITCK-497 Re: Fix the corresponding tests with regarding to CDI-545 The relevant test should in fact be excluded even for TCK 1.2.CDI-545 clarifies that this behaviour was intended all along and hence the observer on an EJB with remote interface shouldn't be there at all. EDIT: Ignore my lack of caffeine, the test is already excluded there, just not linked to this issue. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-497) Fix the corresponding tests with regarding to CDI-545
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-497 Fix the corresponding tests with regarding to CDI-545 Change By: Matej Novotny Fix Version/s: 1.2.11.FiInal Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-497) Fix the corresponding tests with regarding to CDI-545
Title: Message Title Matej Novotny commented on CDITCK-497 Re: Fix the corresponding tests with regarding to CDI-545 The relevant test should in fact be excluded even for TCK 1.2. CDI-545 clarifies that this behaviour was intended all along and hence the observer on an EJB with remote interface shouldn't be there at all. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-603) Rework ConfiguratorAndSetMethodTest
Title: Message Title Matej Novotny updated CDITCK-603 CDI TCK / CDITCK-603 Rework ConfiguratorAndSetMethodTest Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-600) WrappedInjectionTargetTest assumes unspecified lifecycle behaviour
Title: Message Title Matej Novotny updated CDITCK-600 CDI TCK / CDITCK-600 WrappedInjectionTargetTest assumes unspecified lifecycle behaviour Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-599) Test that custom bean with isAlternative()=true is not automatically enabled
Title: Message Title Matej Novotny updated CDITCK-599 CDI TCK / CDITCK-599 Test that custom bean with isAlternative()=true is not automatically enabled Change By: Matej Novotny Status: Pull Request Sent Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2440) Document WeldEvent and WeldInstance
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2440 Document WeldEvent and WeldInstance Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2427) WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type
Title: Message Title Matej Novotny updated an issue Weld / WELD-2427 WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/69, https://github.com/weld/api/pull/72, https://github.com/weld/core/pull/1750 , https://github.com/weld/core/pull/1754 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2440) Document WeldEvent and WeldInstance
Title: Message Title Matej Novotny created an issue Weld / WELD-2440 Document WeldEvent and WeldInstance Issue Type: Enhancement Affects Versions: 2.4.5.Final, 3.0.1.Final Assignee: Unassigned Components: Documentation Created: 02/Nov/17 10:24 AM Priority: Minor Reporter: Matej Novotny This is follow-up issue on WELD-2427. We need to add some documentation about WeldInstance.select(Type) and newly introduced WeldEvent. This concerns both versions - 2.4 and 3.x. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2427) WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type
Title: Message Title Matej Novotny updated an issue Weld / WELD-2427 WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/69, https://github.com/weld/api/pull/72 , https://github.com/weld/core/pull/1750 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2427) WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type
Title: Message Title Matej Novotny updated an issue Weld / WELD-2427 WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/69, https://github.com/weld/api/pull/72 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2436) Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #1747 in GitHub Weld / WELD-2436 Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2436) Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API
Title: Message Title Matej Novotny updated an issue Weld / WELD-2436 Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/67, https://github.com/weld/api/pull/70, https://github.com/weld/core/pull/1743 , https://github.com/weld/core/pull/1747 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2436) Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API
Title: Message Title Matej Novotny updated an issue Weld / WELD-2436 Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/67, https://github.com/weld/api/pull/70 , https://github.com/weld/core/pull/1743 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2436) Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API
Title: Message Title Matej Novotny updated an issue Weld / WELD-2436 Move InterceptorMethodHandler.INTERCEPTOR_BINDINGS_KEY to API Change By: Matej Novotny Git Pull Request: https://github.com/weld/api/pull/67, https://github.com/weld/api/pull/70 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-603) Rework ConfiguratorAndSetMethodTest
Title: Message Title Issue was automatically transitioned when Matej Novotny created pull request #153 in GitHub CDI TCK / CDITCK-603 Rework ConfiguratorAndSetMethodTest Change By: Matej Novotny Status: Open Pull Request Sent Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-601) SpecializationModularity*Test should be in the JAVAEE_FULL group
Title: Message Title Matej Novotny resolved as Rejected Rejecting issue as the test group is present there on the methods, see my previous comment for link to code. CDI TCK / CDITCK-601 SpecializationModularity*Test should be in the JAVAEE_FULL group Change By: Matej Novotny Status: Open Resolved Resolution: Rejected Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-603) Rework ConfiguratorAndSetMethodTest
Title: Message Title Matej Novotny updated an issue CDI TCK / CDITCK-603 Rework ConfiguratorAndSetMethodTest Change By: Matej Novotny Git Pull Request: https://github.com/cdi-spec/cdi-tck/pull/152, https://github.com/cdi-spec/cdi-tck/pull/153 Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (CDITCK-603) Rework ConfiguratorAndSetMethodTest
Title: Message Title
Matej Novotny created an issue
CDI TCK / CDITCK-603
Rework ConfiguratorAndSetMethodTest
Issue Type:
Task
Affects Versions:
2.0.3.Final
Assignee:
Matej Novotny
Created:
30/Oct/17 5:53 AM
Fix Versions:
2.1.0.Final, 2.0.4.Final
Priority:
Major
Reporter:
Matej Novotny
As Mark pointed out on IRC, this test is currently @Test(groups = INTEGRATION) while it needn't be there. It can be easily reworked so that it can be just {{@Test} hence testable on a real container as well as embedded one. The above can be done without any change to test logic meaning this change can go to both streams - 2.0.x and future 2.1.x.
Add Comment
[weld-issues] [JBoss JIRA] (WELD-2427) WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type
Title: Message Title Matej Novotny assigned an issue to Matej Novotny Weld / WELD-2427 WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type Change By: Matej Novotny Assignee: Matej Novotny Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
[weld-issues] [JBoss JIRA] (WELD-2427) WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type
Title: Message Title Matej Novotny commented on WELD-2427 Re: WeldInstance - consider adding a select() method which accepts java.lang.reflect.Type Note - we should/will be adding Weld.select(Type type, Annotation... qualifiers) as well. Add Comment This message was sent by Atlassian JIRA (v7.5.0#75005-sha1:fd8c849) ___ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
