[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] (CDITCK-605) EJBObserverMethodRemoteBusinessMethod test and the Async counterpart are too strict
Title: Message Title Mark Struberg created an issue CDI TCK / CDITCK-605 EJBObserverMethodRemoteBusinessMethod test and the Async counterpart are too strict Issue Type: Bug Affects Versions: 2.0.3.Final Assignee: Matej Novotny Components: Tests Created: 01/Feb/18 7:00 AM Priority: Major Reporter: Mark Struberg Both those tests are too strict as they effectively dissalow any observer methods in @Remote beans. The intention of the original CDI clarification was to make clear that CDI events are not propagated over the network to the other side. But we of course still want CDI events in those beans on the target side. Add Comment
[weld-issues] [JBoss JIRA] (WELD-2459) Ignore module-info during discovery
Title: Message Title Martin Kouba created an issue Weld / WELD-2459 Ignore module-info during discovery Issue Type: Task Assignee: Unassigned Created: 01/Feb/18 6:06 AM Fix Versions: 3.0.3.Final Labels: jdk9 Priority: Major Reporter: Martin Kouba Weld currently logs an INFO message: INFO: WELD-000119: Not generating any bean definitions from module-info because of underlying class loading error: Type module-info is not a class because access_flag ACC_MODULE is set not found. If this is unexpected, enable DEBUG logging to see the full error.
[weld-issues] [JBoss JIRA] (WELD-2459) Ignore module-info during discovery
Title: Message Title Martin Kouba updated an issue Weld / WELD-2459 Ignore module-info during discovery Change By: Martin Kouba Fix Version/s: 2.4.7.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
