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

[Brian Stansberry]

We already have that -- if they include the jar in the war.

The ee subsystem also has a "global-modules" attribute where users can 
configure the names of modules that should be available to all apps. So 
that could be used if for some reason they want to put the jar in the 
modules/ dir and not in their apps. Or if they don't want it exposed to 
all apps on a server, but still want a module they could create the 
module and then use configuration in the app's deployment descriptors.

On 4/10/13 5:00 PM, Fernando Nasser wrote:
> Can we leave the integration code in and require the user to include the JAR if they want to use it?
>
> --Fernando
>
>
>>
>> I say that we should leave it out.
>>
>> Unless the user wants the exact version of Groovy that we are
>> shipping
>> it may not actually be helpful anyway.
>>
>> There are lots of things that we could ship that 'could be useful to
>> some users' (e.g. Spring, pretty much every java web framework),
>> however
>> unless there is a compelling reason to include them I think we should
>> just let the user package the exact version they want in their jars.
>>
>> Stuart
>>
>> 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
>>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>


-- 
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat