Although I think I am going off an a tangent because it doesn’t prevent subsystem
controlled imports. As longs as subsystems add the imports to all deployment types things
are fine. I agree as well that we should be splitting all of these up.
On Feb 7, 2014, at 4:23 PM, Jason Greene <jason.greene(a)redhat.com> wrote:
Part of the problem we run into is that the spec says that all java
ee APIs
are supposed to be available everywhere. We find situations were like people
use a JSF API inside of a CDI initializer or an EJB initializer.
On Feb 7, 2014, at 3:23 PM, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
> I think it was just expedience honestly. I agree it would be better to
> selectively include API modules by subsystem. Aggregate modules seem to
> just cause problems in practice.
>
> On 02/07/2014 03:14 PM, Bill Burke wrote:
>> Chris sent me this rant on overriding built in Resteasy. I replied how
>> to fix it on his blog. The biggest problem is javaee.api which sucks in
>> every EE API. Is there a reason you don't trust the subsystems to suck
>> in the EE APIs they need?
>>
>>
>> -------- Original Message --------
>> Subject: dzone rant on resteasy/modules
>> Date: Fri, 07 Feb 2014 13:49:02 -0500
>> From: Chris Bredesen <cbredesen(a)redhat.com>
>> To: Bill Burke <bburke(a)redhat.com>
>>
>> Just saw this by accident, have fun!
>>
>>
http://java.dzone.com/articles/jboss-modules-suck-it%E2%80%99s
>>
>> -CB
>>
>
>
> --
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Jason T. Greene
WildFly Lead / JBoss EAP Platform Architect
JBoss, a division of Red Hat