You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Alasdair Nottingham <no...@apache.org> on 2010/10/25 23:39:29 UTC
Utility for making a Bundle look like a ClassLoader
It appears that we have multiple classes which basically create a
ClassLoader that delegates to a Bundle. Ones I know of are:
/blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
/util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
/jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
There may be others. I was wondering if it would make sense to try to
common these up into one place?
Thoughts?
Alasdair
--
Alasdair Nottingham
not@apache.org
Re: Utility for making a Bundle look like a ClassLoader
Posted by Alasdair Nottingham <no...@apache.org>.
One of the implementations I pointed to is in the util project
already, so I would probably start from there. It is common and util
is already used by several different sub projects.
Alasdair
On 26 October 2010 12:09, Timothy Ward <ti...@hotmail.com> wrote:
>
> Hi,
>
> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>
> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>
> Regards,
>
> Tim
>
> ----------------------------------------
>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>> From: vmahrwald@googlemail.com
>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>> To: aries-dev@incubator.apache.org
>>
>> + 1
>>
>> I think those were duplicated for short-term convenience more than anything else.
>>
>> Valentin
>>
>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>
>> > It appears that we have multiple classes which basically create a
>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>> >
>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>> >
>> > There may be others. I was wondering if it would make sense to try to
>> > common these up into one place?
>> >
>> > Thoughts?
>> > Alasdair
>> >
>> > --
>> > Alasdair Nottingham
>> > not@apache.org
>>
>
--
Alasdair Nottingham
not@apache.org
Re: Utility for making a Bundle look like a ClassLoader
Posted by Guillaume Nodet <gn...@gmail.com>.
You can assign an issue to several components afaik.
On Tue, Oct 26, 2010 at 14:59, Alasdair Nottingham <no...@apache.org> wrote:
> I have a couple of cross component Jira's assigned to me. Should I
> reassign these from no component to Util? They aren't really Util
> related, although they will touch on Util?
>
> Thanks
> Alasdair
>
> On 26 October 2010 13:51, Jeremy Hughes <hu...@apache.org> wrote:
>> On 26 October 2010 13:49, Alasdair Nottingham <no...@apache.org> wrote:
>>> OK,
>>>
>>> I have created ARIES-468 which is to create a common proxy
>>> implementation, but since two of these classes relate to the various
>>> proxy runtimes we have (one for JNDI and one for blueprint). I will
>>> add the commoning up of this to ARIES-468, since it would just involve
>>> adding an extra change to JPA.
>>>
>>> Any chance of getting a "Common" or "Util" component created in util
>>> for this kind of cross component work?
>>
>> I've added "Util" to mirror what we have in SVN.
>>
>>>
>>> Thanks
>>> Alasdair
>>>
>>> On 26 October 2010 13:33, Lin Sun <li...@gmail.com> wrote:
>>>> Hi
>>>>
>>>> Yes, +1 for moving to util. Also agree that some of the generic osgi
>>>> tools move to util like manifest processing related. I know it can be
>>>> used at least in subsystems, besides the current application project.
>>>>
>>>> Thanks
>>>>
>>>> Lin
>>>>
>>>> On Tue, Oct 26, 2010 at 7:09 AM, Timothy Ward <ti...@hotmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>>>>>
>>>>> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Tim
>>>>>
>>>>> ----------------------------------------
>>>>>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>>>>>> From: vmahrwald@googlemail.com
>>>>>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>>>>>> To: aries-dev@incubator.apache.org
>>>>>>
>>>>>> + 1
>>>>>>
>>>>>> I think those were duplicated for short-term convenience more than anything else.
>>>>>>
>>>>>> Valentin
>>>>>>
>>>>>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>>>>>
>>>>>> > It appears that we have multiple classes which basically create a
>>>>>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>>>>>> >
>>>>>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>>>>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>>>>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>>>> >
>>>>>> > There may be others. I was wondering if it would make sense to try to
>>>>>> > common these up into one place?
>>>>>> >
>>>>>> > Thoughts?
>>>>>> > Alasdair
>>>>>> >
>>>>>> > --
>>>>>> > Alasdair Nottingham
>>>>>> > not@apache.org
>>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Alasdair Nottingham
>>> not@apache.org
>>>
>>
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Utility for making a Bundle look like a ClassLoader
Posted by Alasdair Nottingham <no...@apache.org>.
I have a couple of cross component Jira's assigned to me. Should I
reassign these from no component to Util? They aren't really Util
related, although they will touch on Util?
Thanks
Alasdair
On 26 October 2010 13:51, Jeremy Hughes <hu...@apache.org> wrote:
> On 26 October 2010 13:49, Alasdair Nottingham <no...@apache.org> wrote:
>> OK,
>>
>> I have created ARIES-468 which is to create a common proxy
>> implementation, but since two of these classes relate to the various
>> proxy runtimes we have (one for JNDI and one for blueprint). I will
>> add the commoning up of this to ARIES-468, since it would just involve
>> adding an extra change to JPA.
>>
>> Any chance of getting a "Common" or "Util" component created in util
>> for this kind of cross component work?
>
> I've added "Util" to mirror what we have in SVN.
>
>>
>> Thanks
>> Alasdair
>>
>> On 26 October 2010 13:33, Lin Sun <li...@gmail.com> wrote:
>>> Hi
>>>
>>> Yes, +1 for moving to util. Also agree that some of the generic osgi
>>> tools move to util like manifest processing related. I know it can be
>>> used at least in subsystems, besides the current application project.
>>>
>>> Thanks
>>>
>>> Lin
>>>
>>> On Tue, Oct 26, 2010 at 7:09 AM, Timothy Ward <ti...@hotmail.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>>>>
>>>> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>>>>
>>>> Regards,
>>>>
>>>> Tim
>>>>
>>>> ----------------------------------------
>>>>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>>>>> From: vmahrwald@googlemail.com
>>>>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>>>>> To: aries-dev@incubator.apache.org
>>>>>
>>>>> + 1
>>>>>
>>>>> I think those were duplicated for short-term convenience more than anything else.
>>>>>
>>>>> Valentin
>>>>>
>>>>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>>>>
>>>>> > It appears that we have multiple classes which basically create a
>>>>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>>>>> >
>>>>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>>>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>>>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>>> >
>>>>> > There may be others. I was wondering if it would make sense to try to
>>>>> > common these up into one place?
>>>>> >
>>>>> > Thoughts?
>>>>> > Alasdair
>>>>> >
>>>>> > --
>>>>> > Alasdair Nottingham
>>>>> > not@apache.org
>>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
>
--
Alasdair Nottingham
not@apache.org
Re: Utility for making a Bundle look like a ClassLoader
Posted by Jeremy Hughes <hu...@apache.org>.
On 26 October 2010 13:49, Alasdair Nottingham <no...@apache.org> wrote:
> OK,
>
> I have created ARIES-468 which is to create a common proxy
> implementation, but since two of these classes relate to the various
> proxy runtimes we have (one for JNDI and one for blueprint). I will
> add the commoning up of this to ARIES-468, since it would just involve
> adding an extra change to JPA.
>
> Any chance of getting a "Common" or "Util" component created in util
> for this kind of cross component work?
I've added "Util" to mirror what we have in SVN.
>
> Thanks
> Alasdair
>
> On 26 October 2010 13:33, Lin Sun <li...@gmail.com> wrote:
>> Hi
>>
>> Yes, +1 for moving to util. Also agree that some of the generic osgi
>> tools move to util like manifest processing related. I know it can be
>> used at least in subsystems, besides the current application project.
>>
>> Thanks
>>
>> Lin
>>
>> On Tue, Oct 26, 2010 at 7:09 AM, Timothy Ward <ti...@hotmail.com> wrote:
>>>
>>> Hi,
>>>
>>> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>>>
>>> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>>>
>>> Regards,
>>>
>>> Tim
>>>
>>> ----------------------------------------
>>>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>>>> From: vmahrwald@googlemail.com
>>>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>>>> To: aries-dev@incubator.apache.org
>>>>
>>>> + 1
>>>>
>>>> I think those were duplicated for short-term convenience more than anything else.
>>>>
>>>> Valentin
>>>>
>>>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>>>
>>>> > It appears that we have multiple classes which basically create a
>>>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>>>> >
>>>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>> >
>>>> > There may be others. I was wondering if it would make sense to try to
>>>> > common these up into one place?
>>>> >
>>>> > Thoughts?
>>>> > Alasdair
>>>> >
>>>> > --
>>>> > Alasdair Nottingham
>>>> > not@apache.org
>>>>
>>>
>>
>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Utility for making a Bundle look like a ClassLoader
Posted by Alasdair Nottingham <no...@apache.org>.
OK,
I have created ARIES-468 which is to create a common proxy
implementation, but since two of these classes relate to the various
proxy runtimes we have (one for JNDI and one for blueprint). I will
add the commoning up of this to ARIES-468, since it would just involve
adding an extra change to JPA.
Any chance of getting a "Common" or "Util" component created in util
for this kind of cross component work?
Thanks
Alasdair
On 26 October 2010 13:33, Lin Sun <li...@gmail.com> wrote:
> Hi
>
> Yes, +1 for moving to util. Also agree that some of the generic osgi
> tools move to util like manifest processing related. I know it can be
> used at least in subsystems, besides the current application project.
>
> Thanks
>
> Lin
>
> On Tue, Oct 26, 2010 at 7:09 AM, Timothy Ward <ti...@hotmail.com> wrote:
>>
>> Hi,
>>
>> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>>
>> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>>
>> Regards,
>>
>> Tim
>>
>> ----------------------------------------
>>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>>> From: vmahrwald@googlemail.com
>>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>>> To: aries-dev@incubator.apache.org
>>>
>>> + 1
>>>
>>> I think those were duplicated for short-term convenience more than anything else.
>>>
>>> Valentin
>>>
>>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>>
>>> > It appears that we have multiple classes which basically create a
>>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>>> >
>>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>> >
>>> > There may be others. I was wondering if it would make sense to try to
>>> > common these up into one place?
>>> >
>>> > Thoughts?
>>> > Alasdair
>>> >
>>> > --
>>> > Alasdair Nottingham
>>> > not@apache.org
>>>
>>
>
--
Alasdair Nottingham
not@apache.org
Re: Utility for making a Bundle look like a ClassLoader
Posted by Lin Sun <li...@gmail.com>.
Hi
Yes, +1 for moving to util. Also agree that some of the generic osgi
tools move to util like manifest processing related. I know it can be
used at least in subsystems, besides the current application project.
Thanks
Lin
On Tue, Oct 26, 2010 at 7:09 AM, Timothy Ward <ti...@hotmail.com> wrote:
>
> Hi,
>
> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>
> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>
> Regards,
>
> Tim
>
> ----------------------------------------
>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>> From: vmahrwald@googlemail.com
>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>> To: aries-dev@incubator.apache.org
>>
>> + 1
>>
>> I think those were duplicated for short-term convenience more than anything else.
>>
>> Valentin
>>
>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>
>> > It appears that we have multiple classes which basically create a
>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>> >
>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>> >
>> > There may be others. I was wondering if it would make sense to try to
>> > common these up into one place?
>> >
>> > Thoughts?
>> > Alasdair
>> >
>> > --
>> > Alasdair Nottingham
>> > not@apache.org
>>
>
Re: Utility for making a Bundle look like a ClassLoader
Posted by Alasdair Nottingham <no...@apache.org>.
Hi,
I would too, the problem is if we don't override loadClass the class
loader adapter will be able to see classes that will not be available
to the Bundle. By default it delegates to the system class loader and
if we don't override loadClass it will defer to that classloader
first, so classes not visible to the bundle because they haven't been
imported and aren't in the boot delegation property will be visible.
I don't know how much of an issue it is, but it is why I would stick
with loadClass for now.
Alasdair
On 26 October 2010 12:09, Timothy Ward <ti...@hotmail.com> wrote:
>
> Hi,
>
> I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
>
> I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
>
> Regards,
>
> Tim
>
> ----------------------------------------
>> Subject: Re: Utility for making a Bundle look like a ClassLoader
>> From: vmahrwald@googlemail.com
>> Date: Tue, 26 Oct 2010 07:36:07 +0100
>> To: aries-dev@incubator.apache.org
>>
>> + 1
>>
>> I think those were duplicated for short-term convenience more than anything else.
>>
>> Valentin
>>
>> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>>
>> > It appears that we have multiple classes which basically create a
>> > ClassLoader that delegates to a Bundle. Ones I know of are:
>> >
>> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>> >
>> > There may be others. I was wondering if it would make sense to try to
>> > common these up into one place?
>> >
>> > Thoughts?
>> > Alasdair
>> >
>> > --
>> > Alasdair Nottingham
>> > not@apache.org
>>
>
--
Alasdair Nottingham
not@apache.org
RE: Utility for making a Bundle look like a ClassLoader
Posted by Timothy Ward <ti...@hotmail.com>.
Hi,
I would also be +1 for this, but I'd prefer the implementation not to override loadclass().
I think that at the same time we should move some of the other generic OSGi tools such as the ManifestHeaderProcessor. The function there would be great for JPA and for blueprint, but at the moment they would have to import from the application utils bundle which would bloat the dependency graph.
Regards,
Tim
----------------------------------------
> Subject: Re: Utility for making a Bundle look like a ClassLoader
> From: vmahrwald@googlemail.com
> Date: Tue, 26 Oct 2010 07:36:07 +0100
> To: aries-dev@incubator.apache.org
>
> + 1
>
> I think those were duplicated for short-term convenience more than anything else.
>
> Valentin
>
> On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
>
> > It appears that we have multiple classes which basically create a
> > ClassLoader that delegates to a Bundle. Ones I know of are:
> >
> > /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
> > /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
> > /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
> >
> > There may be others. I was wondering if it would make sense to try to
> > common these up into one place?
> >
> > Thoughts?
> > Alasdair
> >
> > --
> > Alasdair Nottingham
> > not@apache.org
>
Re: Utility for making a Bundle look like a ClassLoader
Posted by Valentin Mahrwald <vm...@googlemail.com>.
+ 1
I think those were duplicated for short-term convenience more than anything else.
Valentin
On 25 Oct 2010, at 22:39, Alasdair Nottingham wrote:
> It appears that we have multiple classes which basically create a
> ClassLoader that delegates to a Bundle. Ones I know of are:
>
> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>
> There may be others. I was wondering if it would make sense to try to
> common these up into one place?
>
> Thoughts?
> Alasdair
>
> --
> Alasdair Nottingham
> not@apache.org
Re: Utility for making a Bundle look like a ClassLoader
Posted by Guillaume Nodet <gn...@gmail.com>.
I don't really see the semantic difference between common and util but
it maybe because i'm not a native english ...
On Tue, Oct 26, 2010 at 12:03, Jeremy Hughes <hu...@apache.org> wrote:
> On 26 October 2010 10:30, Guillaume Nodet <gn...@gmail.com> wrote:
>> Itsn't the util project a good location for that ?
>
> As long, IMHO, as we use submodules with sensible names. Util could
> turn into a dumping ground otherwise. If the util modules is turning
> into a 'commons' then shouldn't we just call it commons as is the way
> with other Apache projects, and then people coming to the project will
> know we're trying to fit into the 'commons' pattern.
>
>>
>> On Tue, Oct 26, 2010 at 10:24, Jeremy Hughes <hu...@apache.org> wrote:
>>> On 25 October 2010 22:39, Alasdair Nottingham <no...@apache.org> wrote:
>>>> It appears that we have multiple classes which basically create a
>>>> ClassLoader that delegates to a Bundle. Ones I know of are:
>>>>
>>>> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>>> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>>> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>>
>>>> There may be others. I was wondering if it would make sense to try to
>>>> common these up into one place?
>>>>
>>>> Thoughts?
>>>
>>> Good idea. I was wondering where you might put this. Since you use the
>>> word 'common' I think an 'aries commons' module would be a good place
>>> to put this. Something like trunk/commons/cl ?
>>>
>>>> Alasdair
>>>>
>>>> --
>>>> Alasdair Nottingham
>>>> not@apache.org
>>>>
>>>
>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> Open Source SOA
>> http://fusesource.com
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Utility for making a Bundle look like a ClassLoader
Posted by Jeremy Hughes <hu...@apache.org>.
On 26 October 2010 10:30, Guillaume Nodet <gn...@gmail.com> wrote:
> Itsn't the util project a good location for that ?
As long, IMHO, as we use submodules with sensible names. Util could
turn into a dumping ground otherwise. If the util modules is turning
into a 'commons' then shouldn't we just call it commons as is the way
with other Apache projects, and then people coming to the project will
know we're trying to fit into the 'commons' pattern.
>
> On Tue, Oct 26, 2010 at 10:24, Jeremy Hughes <hu...@apache.org> wrote:
>> On 25 October 2010 22:39, Alasdair Nottingham <no...@apache.org> wrote:
>>> It appears that we have multiple classes which basically create a
>>> ClassLoader that delegates to a Bundle. Ones I know of are:
>>>
>>> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>
>>> There may be others. I was wondering if it would make sense to try to
>>> common these up into one place?
>>>
>>> Thoughts?
>>
>> Good idea. I was wondering where you might put this. Since you use the
>> word 'common' I think an 'aries commons' module would be a good place
>> to put this. Something like trunk/commons/cl ?
>>
>>> Alasdair
>>>
>>> --
>>> Alasdair Nottingham
>>> not@apache.org
>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: Utility for making a Bundle look like a ClassLoader
Posted by Guillaume Nodet <gn...@gmail.com>.
Also, I'm working on a similar kind of utility project in felix which
is not supposed to be a bundle, but simply a jar containing several
packages that have to be embedded in bundles that want to use those.
That could be a good location too, as I'm planning to release a new
version of it in the very near future.
On Tue, Oct 26, 2010 at 11:30, Guillaume Nodet <gn...@gmail.com> wrote:
> Itsn't the util project a good location for that ?
>
> On Tue, Oct 26, 2010 at 10:24, Jeremy Hughes <hu...@apache.org> wrote:
>> On 25 October 2010 22:39, Alasdair Nottingham <no...@apache.org> wrote:
>>> It appears that we have multiple classes which basically create a
>>> ClassLoader that delegates to a Bundle. Ones I know of are:
>>>
>>> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>>> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>>> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>>
>>> There may be others. I was wondering if it would make sense to try to
>>> common these up into one place?
>>>
>>> Thoughts?
>>
>> Good idea. I was wondering where you might put this. Since you use the
>> word 'common' I think an 'aries commons' module would be a good place
>> to put this. Something like trunk/commons/cl ?
>>
>>> Alasdair
>>>
>>> --
>>> Alasdair Nottingham
>>> not@apache.org
>>>
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Utility for making a Bundle look like a ClassLoader
Posted by Guillaume Nodet <gn...@gmail.com>.
Itsn't the util project a good location for that ?
On Tue, Oct 26, 2010 at 10:24, Jeremy Hughes <hu...@apache.org> wrote:
> On 25 October 2010 22:39, Alasdair Nottingham <no...@apache.org> wrote:
>> It appears that we have multiple classes which basically create a
>> ClassLoader that delegates to a Bundle. Ones I know of are:
>>
>> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
>> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
>> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>>
>> There may be others. I was wondering if it would make sense to try to
>> common these up into one place?
>>
>> Thoughts?
>
> Good idea. I was wondering where you might put this. Since you use the
> word 'common' I think an 'aries commons' module would be a good place
> to put this. Something like trunk/commons/cl ?
>
>> Alasdair
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Utility for making a Bundle look like a ClassLoader
Posted by Jeremy Hughes <hu...@apache.org>.
On 25 October 2010 22:39, Alasdair Nottingham <no...@apache.org> wrote:
> It appears that we have multiple classes which basically create a
> ClassLoader that delegates to a Bundle. Ones I know of are:
>
> /blueprint/blueprint-core/src/main/java/org/apache/aries/blueprint/utils/BundleDelegatingClassLoader.java
> /util/src/main/java/org/apache/aries/util/BundleToClassLoaderAdapter.java
> /jpa/jpa-container/src/main/java/org/apache/aries/jpa/container/unit/impl/BundleDelegatingClassLoader.java
>
> There may be others. I was wondering if it would make sense to try to
> common these up into one place?
>
> Thoughts?
Good idea. I was wondering where you might put this. Since you use the
word 'common' I think an 'aries commons' module would be a good place
to put this. Something like trunk/commons/cl ?
> Alasdair
>
> --
> Alasdair Nottingham
> not@apache.org
>