[jira] [Created] (DELTASPIKE-408) WildFly test profile
Jozef Hartinger created DELTASPIKE-408: -- Summary: WildFly test profile Key: DELTASPIKE-408 URL: https://issues.apache.org/jira/browse/DELTASPIKE-408 Project: DeltaSpike Issue Type: Task Components: Tests Affects Versions: 0.4 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Fix For: 0.5 https://github.com/jharting/deltaspike/tree/wildfly -- 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
[jira] [Created] (DELTASPIKE-407) Tests for Servlet module incorrectly packaged
Jozef Hartinger created DELTASPIKE-407: -- Summary: Tests for Servlet module incorrectly packaged Key: DELTASPIKE-407 URL: https://issues.apache.org/jira/browse/DELTASPIKE-407 Project: DeltaSpike Issue Type: Bug Components: Servlet-Module Affects Versions: 0.4 Reporter: Jozef Hartinger Assignee: Christian Kaltepoth Fix For: 0.5 I am observing test classes being bundled twice in a test archive during Servlet module integration test run. For example in ServletContextEventsTest the ServletContextEventsObserver is packaged in the tested web archive twice: 1) in WEB-INF/classes of the test archive (expected) 2) in utils.jar - this is because utils.jar is built using Deployments.getTestSupportArchives() which adds all packages matching the "org.apache.deltaspike.test" prefix --> ServletContextEventsObserver is added here as well This bug causes test failures in WildFly -- 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
[jira] [Commented] (DELTASPIKE-405) producer for JsfMessage does not match CDI-1.1 rules
[
https://issues.apache.org/jira/browse/DELTASPIKE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754468#comment-13754468
]
Jozef Hartinger commented on DELTASPIKE-405:
I am sorry but I do not understand what you mean by:
{quote}
is NOT for the method but only for the class
{quote}
A parameterized type with a type variable is a legal bean type, no matter if it
is a managed bean or a producer method. See for example this part of the spec:
{quote}If the producer method return type is a parameterized type, it must
specify an actual type parameter or type variable for each type
parameter.{quote}
> producer for JsfMessage does not match CDI-1.1 rules
>
>
> Key: DELTASPIKE-405
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-405
> Project: DeltaSpike
> Issue Type: Bug
> Components: JSF-Module
>Affects Versions: 0.4
>Reporter: Mark Struberg
>Assignee: Mark Struberg
> Fix For: 0.5
>
>
> Some containers don't find the JsfMessageProducer as it is of a generic type
> .
--
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
[jira] [Commented] (DELTASPIKE-405) producer for JsfMessage does not match CDI-1.1 rules
[ https://issues.apache.org/jira/browse/DELTASPIKE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754461#comment-13754461 ] Mark Struberg commented on DELTASPIKE-405: -- exactly this very problem. But it seems we have no solution for cdi-1.1 at all. If we have an injection point of type JsfMessage and the producer is JsfMessage then according to the CDI-1.1 rules it does not resolve, as is NOT for the method but only for the class. If you read your cdi-1.1 rules then you would see that T is ONLY intended if the Producer Method itself extends SomeBaseClass in which case the producer would be for JsfMessage. Those rules seem bloody broken to me. > producer for JsfMessage does not match CDI-1.1 rules > > > Key: DELTASPIKE-405 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-405 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 0.4 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 0.5 > > > Some containers don't find the JsfMessageProducer as it is of a generic type > . -- 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
[jira] [Reopened] (DELTASPIKE-405) producer for JsfMessage does not match CDI-1.1 rules
[ https://issues.apache.org/jira/browse/DELTASPIKE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jozef Hartinger reopened DELTASPIKE-405: This resolution is wrong. It basically reverts what has been done as part of DELTASPIKE-295 and brings DS into conflict with CDI 1.1 again. (As long as injection point such as JsfMessage is expected to be injected) See for details DELTASPIKE-295 Could you expand on what problem this issue is addressing? > producer for JsfMessage does not match CDI-1.1 rules > > > Key: DELTASPIKE-405 > URL: https://issues.apache.org/jira/browse/DELTASPIKE-405 > Project: DeltaSpike > Issue Type: Bug > Components: JSF-Module >Affects Versions: 0.4 >Reporter: Mark Struberg >Assignee: Mark Struberg > Fix For: 0.5 > > > Some containers don't find the JsfMessageProducer as it is of a generic type > . -- 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
