Yeah i know but tomee commiters are so Fast. Bases ON my experience
El 02/04/2014 12:37, "John Clingan" <john.clingan_at_oracle.com> escribió:
> The same applies with Apache TomEE or any community project. The time it
> takes to fix a bug depends on the bug itself. If you want want patches for
> a particular problem as being described, then go with commercial support -
> whether the product is based on open source license or not.
>
> On Apr 2, 2014, at 11:29 AM, José Luis Cetina <maxtorzito_at_gmail.com>
> wrote:
>
> Why not try apache tomee?
> El 02/04/2014 08:09, "John Clingan" <john.clingan_at_oracle.com> escribió:
>
>> You can also open up a jira issue. It may take hours, days, months, or
>> years to fix. It depends on the bug. It also helps if you can provide
>> sample code that can be run that exercises the bug. It helps even more if
>> you dig through the GlassFish code, locate the bug, and offer a fix.
>> Welcome to community :-)
>>
>>
>> On April 1, 2014 6:29:20 PM PDT, Reza Rahman <Reza.Rahman_at_oracle.com>
>> wrote:
>>>
>>> Generally you would do this via commercial support.
>>>
>>> On 4/1/2014 9:09 PM, Joshua Deacon wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>>
>>> For glassfish if we have a specific production issue, that doesn't
>>> require a new version or build of the open source software, can we request
>>> a patch fix from the relevant open source community?
>>>
>>>
>>>
>>>
>>> If so how long would this take?
>>>
>>> Thanks,
>>> Josh
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Joshua Deacon*
>>> *IBL (PMO)*
>>> M +61 447 667 961
>>> unico *smart IT solutions | practical outcomes* www.unico.com.au
>>> Technical Consulting | Solution Delivery | Tailored Support | Local
>>> Outsourcing
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>