if they are still
>>>> monitoring. As Jeff recommended I’m including the private@ list for PMC
>>>> folks that may not be paying as much attention to the dev@ list.
>>>>
>>>>> Before we dump the project I suggest we start with an analysis of where
>>>>> we are right now.
>>>>>
>>>>> What about starting look into
>>>>> .) Who is still active and willing to continue Geronimo as a ee-commons
>>>>> project?
>>>> So far I’ve not really seen anyone over the past days of communication
>>>> about this. But we’ll see.
>>>>
>>>> —jason
>>>>
>>>>
>>>>
>>>>> .) Which project parts of the project are of some shared interest and
>>>>> might be good to get some maintenance love and some realistic chance that
>>>>> this is gonna happening?
>>>> I can’t speak for the others, but I have zero interested in putting any
>>>> love in to any of what is presently here.
>>>>
>>>> I will defer to others to explain if they feel otherwise, though I do
>>>> recall some chatter on private@ but will probably need those folks to
>>>> re-post to dev@ to include that discussion.
>>>>
>>>> —jason
>>>>
>>>
>>>
>>
>
--
Clebert Suconic
imited in time ATM so happy to let
> it be done but can help a bit in 1 or 2 weeks if needed.
>
>>
>> LieGrue,
>> strub
>>
>>
>>
>>
>>
>> > On Tuesday, 23 August 2016, 17:42, Clebert Suconic
>> > wrote:
>> > >> Not sure I
> Not always. Will be true until something else has a reference to the
> classloader, like a provider Class for instance.
> In other words it can just prevent the whole webapp to be garbage collected.
A provider class Is not supposed to hold an explicit reference to the
classLoader.
That would be
> Not sure I get you there, commons clearly doesn't take in charge any of that
> but some containers can force some cleanup (not the other way around) - at
> least for beansutils for instance.
With a WeakHashmap, the cache will be removed once the classLoader is
released, right? Which is what I am
with the registry I proposed and enhance/fix it on
> demand? Sounds like a compromise
>
I guess I don't understand your proposal.
--
Clebert Suconic
On Tue, Aug 23, 2016 at 10:55 AM, Romain Manni-Bucau
wrote:
>
> 2016-08-23 16:51 GMT+02:00 Clebert Suconic :
>>
>> TBH: I don't expect the implementation to ever change on a given
>> classLoader.
>>
>
> So you accept to not work for tomcat, tomee, geron
> wrote:
>>
>>
>> >
>> >
>> >Just need to copy it from other spec. I have nothing against it.
>> > Alternative is in johnzon to return an impl instead of using the provider
>> > again. Maybe sthg to investigate
>> >
>
I Will be back from vacations on Tuesday. I could do some of this
weakhashmap per classloader but I don't want to waste time if you wouldn't
merger it anyways. Let me know what you think.
On Friday, August 19, 2016, Romain Manni-Bucau
wrote:
> Le 19 août 2016 18:54, "Cle
on only using the context
classloader.
On Friday, August 19, 2016, Romain Manni-Bucau
wrote:
> Le 19 août 2016 18:06, "Clebert Suconic" > a écrit :
> >
> > I would rather fix the framework in one place than force everybody to
> not use the factory. (The code Change
point that the fix is trivial and
> there is no actual performance issue once correctly coded so not sure it is
> a real issue.
>
>
>> LieGrue,
>> strub
>>
>> PS: this seems to be a complex topic. Each spec does it different. And
>> each of them has achileus
o help resolve that.
>>
>> https://github.com/apache/geronimo-specs/pull/4
>>
>> John
>>
>
--
Clebert Suconic
clebert suconic created GERONIMO-6548:
-
Summary: Bump geronimo-jms_2.0_spec to 1.0.final
Key: GERONIMO-6548
URL: https://issues.apache.org/jira/browse/GERONIMO-6548
Project: Geronimo
Is it possible someone make a cut of the JMS 2.0 spec jar?
We need a new release cut to fix this version:
https://issues.apache.org/jira/browse/ARTEMIS-148
[
https://issues.apache.org/jira/browse/GERONIMO-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587137#comment-14587137
]
clebert suconic commented on GERONIMO-6455:
---
This should be closed as
14 matches
Mail list logo
