[jboss-as7-dev] JSF Groovy support in AS8?

[ssilvert at redhat.com]

On 4/10/2013 1:15 PM, Brian Stansberry wrote:
> On 4/10/13 11:27 AM, ssilvert at redhat.com wrote:
>> On 4/10/2013 12:02 PM, Brian Stansberry wrote:
>>> Data point: 6MB would be a 4.9% increase in download size vs EAP
>>> 6.1.0.Alpha1.
>>>
>>> Does this groovy integration involve any integration code?
>> A few lines just to add the module to the deployment unit.  Yes.
>>> I assume so
>>> (to make the module visible), otherwise users would have to declare
>>> module dependencies, which for many may be harder than just packaging
>>> the jar.
>> Right.  We wouldn't ask them to do that.
>>> Do we intend to formally support this over the long run?
>> I don't know.  Perhaps it would be better as an unsupported layered product?
> Unsupported Add-On features would be one way to deal with things like 
> this. IMO we should not be producing unsupported Layered Distributions. 
> (See 
> https://community.jboss.org/wiki/LayeredDistributionsAndModulePathOrganization 
> for the definition of these terms.)
>
> For a feature to work as an add-on, it needs to somehow be integrated. 
> Currently that would have to be via an extension/subsystem.
That's way too much trouble because it takes a lot of effort to create a
new subsystem versus 2 lines of code to add it to the existing one. 

How are things going with simplifying subsystem development?
>
>>> If not, any
>>> integration will need to be ripped out at the start of productization.
>>>
>>> On 4/10/13 10:37 AM, ssilvert at redhat.com wrote:
>>>> On 4/10/2013 10:26 AM, Jaikiran Pai wrote:
>>>>> Resending - this time replying to the list.
>>>>>
>>>>> Does it have to be a module that we ship? Or would it work if users
>>>>> added it as a simple Java EE library to their application
>>>>> (.war/WEB-INF/lib for example)?
>>>> Adding it to your WAR is something you can do today.
>>>>
>>>> I'm asking for opinions on shipping it with AS so that JSF apps have
>>>> this capability by default.
>>>>
>>>> I won't really argue either way.  It's trivial to add and very, very
>>>> trivial to leave out.
>>>>
>>>>> -Jaikiran
>>>>>
>>>>> On Wednesday 10 April 2013 05:56 PM, ssilvert at redhat.com wrote:
>>>>>> Mojarra has supported Groovy for quite some time now.  It's kind of neat
>>>>>> because you can prototype JSF artifacts with Groovy and achieve dynamic
>>>>>> reloading of these artifacts during development.  Here is the original
>>>>>> introduction to this feature from way back in 2008.
>>>>>> https://blogs.oracle.com/rlubke/entry/groovy_mojarra
>>>>>>
>>>>>> Today, if you want to use this feature with AS you have to download
>>>>>> Groovy and package it with your WAR.
>>>>>>
>>>>>> I have the code already written to add Groovy support to AS8 and it
>>>>>> works well.  The only downside is that it introduces a module for
>>>>>> groovy-all.jar, which is about 6MB.
>>>>>>
>>>>>> Any thoughts?
>>>>>>
>>>>>> Stan
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>> _______________________________________________
>>>>> jboss-as7-dev mailing list
>>>>> jboss-as7-dev at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>