Re: Issue with BundleListener/Resolved events

2016-01-13 Thread Thomas Draier 
Hi,
It's not about classes (which are correctly loaded by the framework and
fully available when i get in there), but about custom
resources/capabilities that I register in the listener. So yes, it fails,
as the listener cannot load the resources it depends on, which should have
been registered earlier by the same listener. As a workaround I could keep
track of the bundles inside the listener when they have unresolved
dependencies, and register them only when the listener has been called on
all dependencies - but that's quite ugly and risk-prone. I would have
preferred to rely on the fact that events are sent in order - that would be
much more clean and simple.
Thomas

On Tue, Jan 12, 2016 at 6:45 PM Richard S. Hall 
wrote:

>
> On 1/12/16 11:59 , Thomas Draier wrote:
> > On Tue, Jan 12, 2016 at 5:45 PM Richard S. Hall 
> > wrote:
> >
> >> So, are you saying that when you get a resolved event for some arbitrary
> >> bundle, you are running into issues because some of its dependencies are
> >> not yet treated as if they are resolved? What is the symptom you see?
> >>
> > Well, I just did receive the resolved event for the dependencies (Y,Z)
> > after receiving the event for the bundle having the dependencies (X),
> > instead of the opposite. Of course, it's not always the case, it happens
> > for some bundles only, as the order is random. But yes, all of them are
> > marked as resolved when I get the first event, and all events will
> > eventually be sent.
>
> What I'm trying to get at is, why is this problematic for you if you get
> them out of order? Are you try to load a class and it fails, for
> example. Or does it just make you uncomfortable?
>
> -> richard
>
> >
> >
> >> Yes, that's the reverse order, not that this terminology is super
> >> important.
> >>
> > Ok, whatever, just to be sure we were talking of the same order.
> >
> > Thomas
> >
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>
> --
*Thomas Draier*
Chief Software Architect & Co-Founder

T +33 1 44 79 37 86
8 rue du Sentier | 75002 Paris | France
*jahia.com *
SKYPE | VCARD 


> JOIN OUR COMMUNITY  to evaluate, get trained and
to discover why Jahia is a leading User Experience Platform (UXP) for
Digital Transformation.

Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread Milen Dyankov 
Lets say I have a UI bundle that renders a button from template. The
template is just a text file(s) inside UI bundle. Clicking the button calls
a service (for the purpose of this example say one with the highest rank).

The requirement is: change both the service that is called and the button
in consistent manner.

The first part is easy:
 - To change the service one can simply provide a new bundle (call it S)
containing the new service implementation (with higher rank or whatever
else it takes to make it the one that service registry will give to the UI
bundle).
 - To change the button (or even replace it with something else) one can
provide a fragment bundle (call it FB) with updated template file(s).

The question is, how to keep those consistent? That is, make sure that
either both S and FB are applied or none of them (lets assume S will
somehow ensure the service is registered or stop itself if it can't do so)!

It seams one needs to somehow declare a bidirectional dependency (I hate
the way it sounds, but that's what it in fact is, isn't it) between a
bundle and a fragment bundle. AFAIK this is not really possible as anything
specified in fragment is applied to the host! Has anyone faced similar
challenge before?


-- 
http://about.me/milen

org.osgi.framework.bsnversion=multiple

2016-01-13 Thread Malek Ben Salem 

Hi everyone,

I'm trying to start many instances of the same bundle in one OSGi. I 
have noticed that setting org.osgi.framework.bsnversion=multiple doesn't 
change anything. The install command returns the ID of the already 
installed bundle, no new bundle is installed, as specified in 4.4.3 of 
the OSGi Core Release 6 Spec:


"Every bundle is uniquely identified by its location string. If an 
installed bundle is using the specified
location, the installBundle methods must return the Bundle object for 
that installed bundle and not install a new bundle."


Yet the same section also says:

"If the to be installed bundle has a bundle symbolic name and version 
pair that is already installed in
the framework then the installation is only valid when the 
org.osgi.framework.bsnversion framework launching property is set to 
multiple or managed."


Section 10.1.15.49 (concerning org.osgi.framework.bsnversion=multiple) 
actually says this should be possible:
"Specifies the framework will allow multiple bundles to be installed 
having the same symbolic name and version."


So, is this a bug in the framework? I actually use my own build of the 
framework where I changed the installBundle method of 
org.apache.felix.framework.Felix.java to force this option to work. I 
still would like to know the better way to achieve this or to have the 
bug corrected.


Regards,
Malek.

--
aicas GmbH
Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
http://www.aicas.com   * Tel: +49-721-663 968-0

USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim
Geschäftsführer: Dr. James J. Hunt

Re: Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread Milen Dyankov 
Conceptually I guess you can put it that way, yes.

On Wed, Jan 13, 2016 at 2:43 PM, CLEMENT Jean-Philippe <
jean-philippe.clem...@fr.thalesgroup.com> wrote:

> Do you mean ensure that fragments and services are deployed as a single
> transaction?
>
> JP
>
> [@@ OPEN @@]
>
>
> -Message d'origine-
> De : Milen Dyankov [mailto:milendyan...@gmail.com]
> Envoyé : mercredi 13 janvier 2016 13:57
> À : users@felix.apache.org
> Objet : Re: Specifying dependency between a bundle and a fragment bundle
>
> Thank you for your thoughts regarding replacing the service. However that
> is not really my concern. There are 2 aspects in the picture - the service
> itself and the UI to communicate with it.
> In traditional layered architecture one would refer to those as service
> layer an UI layer. Both are developed independenty and in more complex
> scenarios there could be N bundles providing UIs for working with M bundles
> providing services. In non-OSGi environment if I start application having
> correct modules (jar files and resources on the classpath) at runtime, I am
> kind of guaranteed to have a consistent change in both layers. In OSGi (or
> any dynamic modular system I guess) one change can be applied and the other
> one not (due to configuration, resolve issues, removed dependencies, ...)
> which can lead to UI functionality not matching the actual underlying
> services providing it. So what I'm struggling with is finding a way to keep
> the changes consistent across both layers. As in this particular case the
> changes to the UI layer are applied via fragment bundles and the changes to
> the service layer are applied by providing "regular" bundles, I'm looking
> for a way to express the relationship between those. I guess using
> Requirements and Capabilities would be perfect but to my understanding you
> can not use it for fragments.
>
>
>
> On Wed, Jan 13, 2016 at 1:24 PM, CLEMENT Jean-Philippe <
> jean-philippe.clem...@fr.thalesgroup.com> wrote:
>
> > I'm not too sure what you need, but I would say first that you
> > consider what you have (a text file) rather than what you need (a
> > service or services). It seems you see things through the provider
> > instead of the consumer.
> >
> > So, you have a button which calls a service S. Fine. Then you want S
> > to be the best service. So you just have to implement a service S
> > which is a proxy to T services and which will forward calls to the best
> T service.
> >
> > You can even reuse S instead of another T service. So, S is a proxy to
> > other S services. The proxy has the better ranking in order the button
> > to "find it". The proxy has to exclude itself from S service candidates.
> >
> > ...just a quick thought...
> >
> > JP
> >
> > [@@ OPEN @@]
> >
> > -Message d'origine-
> > De : Milen Dyankov [mailto:milendyan...@gmail.com] Envoyé : mercredi
> > 13 janvier 2016 11:10 À : users@felix.apache.org Objet : Specifying
> > dependency between a bundle and a fragment bundle
> >
> > Lets say I have a UI bundle that renders a button from template. The
> > template is just a text file(s) inside UI bundle. Clicking the button
> > calls a service (for the purpose of this example say one with the
> highest rank).
> >
> > The requirement is: change both the service that is called and the
> > button in consistent manner.
> >
> > The first part is easy:
> >  - To change the service one can simply provide a new bundle (call it
> > S) containing the new service implementation (with higher rank or
> > whatever else it takes to make it the one that service registry will
> > give to the UI bundle).
> >  - To change the button (or even replace it with something else) one
> > can provide a fragment bundle (call it FB) with updated template file(s).
> >
> > The question is, how to keep those consistent? That is, make sure that
> > either both S and FB are applied or none of them (lets assume S will
> > somehow ensure the service is registered or stop itself if it can't do
> so)!
> >
> > It seams one needs to somehow declare a bidirectional dependency (I
> > hate the way it sounds, but that's what it in fact is, isn't it)
> > between a bundle and a fragment bundle. AFAIK this is not really
> > possible as anything specified in fragment is applied to the host! Has
> > anyone faced similar challenge before?
> >
> >
> > --
> > http://about.me/milen
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> > For additional commands, e-mail: users-h...@felix.apache.org
> >
>
>
>
> --
> http://about.me/milen
>
> -
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>



-- 
http://about.me/milen

Re: Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread Milen Dyankov 
Thank you for your thoughts regarding replacing the service. However that
is not really my concern. There are 2 aspects in the picture - the service
itself and the UI to communicate with it.
In traditional layered architecture one would refer to those as service
layer an UI layer. Both are developed independenty and in more complex
scenarios there could be N bundles providing UIs for working with M bundles
providing services. In non-OSGi environment if I start application having
correct modules (jar files and resources on the classpath) at runtime, I am
kind of guaranteed to have a consistent change in both layers. In OSGi (or
any dynamic modular system I guess) one change can be applied and the other
one not (due to configuration, resolve issues, removed dependencies, ...)
which can lead to UI functionality not matching the actual underlying
services providing it. So what I'm struggling with is finding a way to keep
the changes consistent across both layers. As in this particular case the
changes to the UI layer are applied via fragment bundles and the changes to
the service layer are applied by providing "regular" bundles, I'm looking
for a way to express the relationship between those. I guess using
Requirements and Capabilities would be perfect but to my understanding you
can not use it for fragments.



On Wed, Jan 13, 2016 at 1:24 PM, CLEMENT Jean-Philippe <
jean-philippe.clem...@fr.thalesgroup.com> wrote:

> I'm not too sure what you need, but I would say first that you consider
> what you have (a text file) rather than what you need (a service or
> services). It seems you see things through the provider instead of the
> consumer.
>
> So, you have a button which calls a service S. Fine. Then you want S to be
> the best service. So you just have to implement a service S which is a
> proxy to T services and which will forward calls to the best T service.
>
> You can even reuse S instead of another T service. So, S is a proxy to
> other S services. The proxy has the better ranking in order the button to
> "find it". The proxy has to exclude itself from S service candidates.
>
> ...just a quick thought...
>
> JP
>
> [@@ OPEN @@]
>
> -Message d'origine-
> De : Milen Dyankov [mailto:milendyan...@gmail.com]
> Envoyé : mercredi 13 janvier 2016 11:10
> À : users@felix.apache.org
> Objet : Specifying dependency between a bundle and a fragment bundle
>
> Lets say I have a UI bundle that renders a button from template. The
> template is just a text file(s) inside UI bundle. Clicking the button calls
> a service (for the purpose of this example say one with the highest rank).
>
> The requirement is: change both the service that is called and the button
> in consistent manner.
>
> The first part is easy:
>  - To change the service one can simply provide a new bundle (call it S)
> containing the new service implementation (with higher rank or whatever
> else it takes to make it the one that service registry will give to the UI
> bundle).
>  - To change the button (or even replace it with something else) one can
> provide a fragment bundle (call it FB) with updated template file(s).
>
> The question is, how to keep those consistent? That is, make sure that
> either both S and FB are applied or none of them (lets assume S will
> somehow ensure the service is registered or stop itself if it can't do so)!
>
> It seams one needs to somehow declare a bidirectional dependency (I hate
> the way it sounds, but that's what it in fact is, isn't it) between a
> bundle and a fragment bundle. AFAIK this is not really possible as anything
> specified in fragment is applied to the host! Has anyone faced similar
> challenge before?
>
>
> --
> http://about.me/milen
>
> -
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>



-- 
http://about.me/milen

RE: Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread CLEMENT Jean-Philippe 
Do you mean ensure that fragments and services are deployed as a single 
transaction?

JP

[@@ OPEN @@]


-Message d'origine-
De : Milen Dyankov [mailto:milendyan...@gmail.com] 
Envoyé : mercredi 13 janvier 2016 13:57
À : users@felix.apache.org
Objet : Re: Specifying dependency between a bundle and a fragment bundle

Thank you for your thoughts regarding replacing the service. However that is 
not really my concern. There are 2 aspects in the picture - the service itself 
and the UI to communicate with it.
In traditional layered architecture one would refer to those as service layer 
an UI layer. Both are developed independenty and in more complex scenarios 
there could be N bundles providing UIs for working with M bundles providing 
services. In non-OSGi environment if I start application having correct modules 
(jar files and resources on the classpath) at runtime, I am kind of guaranteed 
to have a consistent change in both layers. In OSGi (or any dynamic modular 
system I guess) one change can be applied and the other one not (due to 
configuration, resolve issues, removed dependencies, ...) which can lead to UI 
functionality not matching the actual underlying services providing it. So what 
I'm struggling with is finding a way to keep the changes consistent across both 
layers. As in this particular case the changes to the UI layer are applied via 
fragment bundles and the changes to the service layer are applied by providing 
"regular" bundles, I'm looking for a way to express the relationship between 
those. I guess using Requirements and Capabilities would be perfect but to my 
understanding you can not use it for fragments.



On Wed, Jan 13, 2016 at 1:24 PM, CLEMENT Jean-Philippe < 
jean-philippe.clem...@fr.thalesgroup.com> wrote:

> I'm not too sure what you need, but I would say first that you 
> consider what you have (a text file) rather than what you need (a 
> service or services). It seems you see things through the provider 
> instead of the consumer.
>
> So, you have a button which calls a service S. Fine. Then you want S 
> to be the best service. So you just have to implement a service S 
> which is a proxy to T services and which will forward calls to the best T 
> service.
>
> You can even reuse S instead of another T service. So, S is a proxy to 
> other S services. The proxy has the better ranking in order the button 
> to "find it". The proxy has to exclude itself from S service candidates.
>
> ...just a quick thought...
>
> JP
>
> [@@ OPEN @@]
>
> -Message d'origine-
> De : Milen Dyankov [mailto:milendyan...@gmail.com] Envoyé : mercredi 
> 13 janvier 2016 11:10 À : users@felix.apache.org Objet : Specifying 
> dependency between a bundle and a fragment bundle
>
> Lets say I have a UI bundle that renders a button from template. The 
> template is just a text file(s) inside UI bundle. Clicking the button 
> calls a service (for the purpose of this example say one with the highest 
> rank).
>
> The requirement is: change both the service that is called and the 
> button in consistent manner.
>
> The first part is easy:
>  - To change the service one can simply provide a new bundle (call it 
> S) containing the new service implementation (with higher rank or 
> whatever else it takes to make it the one that service registry will 
> give to the UI bundle).
>  - To change the button (or even replace it with something else) one 
> can provide a fragment bundle (call it FB) with updated template file(s).
>
> The question is, how to keep those consistent? That is, make sure that 
> either both S and FB are applied or none of them (lets assume S will 
> somehow ensure the service is registered or stop itself if it can't do so)!
>
> It seams one needs to somehow declare a bidirectional dependency (I 
> hate the way it sounds, but that's what it in fact is, isn't it) 
> between a bundle and a fragment bundle. AFAIK this is not really 
> possible as anything specified in fragment is applied to the host! Has 
> anyone faced similar challenge before?
>
>
> --
> http://about.me/milen
>
> -
> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> For additional commands, e-mail: users-h...@felix.apache.org
>



--
http://about.me/milen

-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org

RE: Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread CLEMENT Jean-Philippe 
I would have made this via services, but there might be other ways such as 
subsystems (?)

JP
 
[@@ OPEN @@]


-Message d'origine-
De : Milen Dyankov [mailto:milendyan...@gmail.com] 
Envoyé : mercredi 13 janvier 2016 14:49
À : users@felix.apache.org
Objet : Re: Specifying dependency between a bundle and a fragment bundle

Conceptually I guess you can put it that way, yes.

On Wed, Jan 13, 2016 at 2:43 PM, CLEMENT Jean-Philippe < 
jean-philippe.clem...@fr.thalesgroup.com> wrote:

> Do you mean ensure that fragments and services are deployed as a 
> single transaction?
>
> JP
>
> [@@ OPEN @@]
>
>
> -Message d'origine-
> De : Milen Dyankov [mailto:milendyan...@gmail.com] Envoyé : mercredi 
> 13 janvier 2016 13:57 À : users@felix.apache.org Objet : Re: 
> Specifying dependency between a bundle and a fragment bundle
>
> Thank you for your thoughts regarding replacing the service. However 
> that is not really my concern. There are 2 aspects in the picture - 
> the service itself and the UI to communicate with it.
> In traditional layered architecture one would refer to those as 
> service layer an UI layer. Both are developed independenty and in more 
> complex scenarios there could be N bundles providing UIs for working 
> with M bundles providing services. In non-OSGi environment if I start 
> application having correct modules (jar files and resources on the 
> classpath) at runtime, I am kind of guaranteed to have a consistent 
> change in both layers. In OSGi (or any dynamic modular system I guess) 
> one change can be applied and the other one not (due to configuration, 
> resolve issues, removed dependencies, ...) which can lead to UI 
> functionality not matching the actual underlying services providing 
> it. So what I'm struggling with is finding a way to keep the changes 
> consistent across both layers. As in this particular case the changes 
> to the UI layer are applied via fragment bundles and the changes to 
> the service layer are applied by providing "regular" bundles, I'm 
> looking for a way to express the relationship between those. I guess 
> using Requirements and Capabilities would be perfect but to my understanding 
> you can not use it for fragments.
>
>
>
> On Wed, Jan 13, 2016 at 1:24 PM, CLEMENT Jean-Philippe < 
> jean-philippe.clem...@fr.thalesgroup.com> wrote:
>
> > I'm not too sure what you need, but I would say first that you 
> > consider what you have (a text file) rather than what you need (a 
> > service or services). It seems you see things through the provider 
> > instead of the consumer.
> >
> > So, you have a button which calls a service S. Fine. Then you want S 
> > to be the best service. So you just have to implement a service S 
> > which is a proxy to T services and which will forward calls to the 
> > best
> T service.
> >
> > You can even reuse S instead of another T service. So, S is a proxy 
> > to other S services. The proxy has the better ranking in order the 
> > button to "find it". The proxy has to exclude itself from S service 
> > candidates.
> >
> > ...just a quick thought...
> >
> > JP
> >
> > [@@ OPEN @@]
> >
> > -Message d'origine-
> > De : Milen Dyankov [mailto:milendyan...@gmail.com] Envoyé : mercredi
> > 13 janvier 2016 11:10 À : users@felix.apache.org Objet : Specifying 
> > dependency between a bundle and a fragment bundle
> >
> > Lets say I have a UI bundle that renders a button from template. The 
> > template is just a text file(s) inside UI bundle. Clicking the 
> > button calls a service (for the purpose of this example say one with 
> > the
> highest rank).
> >
> > The requirement is: change both the service that is called and the 
> > button in consistent manner.
> >
> > The first part is easy:
> >  - To change the service one can simply provide a new bundle (call 
> > it
> > S) containing the new service implementation (with higher rank or 
> > whatever else it takes to make it the one that service registry will 
> > give to the UI bundle).
> >  - To change the button (or even replace it with something else) one 
> > can provide a fragment bundle (call it FB) with updated template file(s).
> >
> > The question is, how to keep those consistent? That is, make sure 
> > that either both S and FB are applied or none of them (lets assume S 
> > will somehow ensure the service is registered or stop itself if it 
> > can't do
> so)!
> >
> > It seams one needs to somehow declare a bidirectional dependency (I 
> > hate the way it sounds, but that's what it in fact is, isn't it) 
> > between a bundle and a fragment bundle. AFAIK this is not really 
> > possible as anything specified in fragment is applied to the host! 
> > Has anyone faced similar challenge before?
> >
> >
> > --
> > http://about.me/milen
> >
> > 
> > - To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
> > For additional commands, e-mail: users-h...@felix.apache.org
> >
>
>
>
>

RE: Specifying dependency between a bundle and a fragment bundle

2016-01-13 Thread CLEMENT Jean-Philippe 
I'm not too sure what you need, but I would say first that you consider what 
you have (a text file) rather than what you need (a service or services). It 
seems you see things through the provider instead of the consumer.

So, you have a button which calls a service S. Fine. Then you want S to be the 
best service. So you just have to implement a service S which is a proxy to T 
services and which will forward calls to the best T service.

You can even reuse S instead of another T service. So, S is a proxy to other S 
services. The proxy has the better ranking in order the button to "find it". 
The proxy has to exclude itself from S service candidates.

...just a quick thought...

JP

[@@ OPEN @@]

-Message d'origine-
De : Milen Dyankov [mailto:milendyan...@gmail.com] 
Envoyé : mercredi 13 janvier 2016 11:10
À : users@felix.apache.org
Objet : Specifying dependency between a bundle and a fragment bundle

Lets say I have a UI bundle that renders a button from template. The template 
is just a text file(s) inside UI bundle. Clicking the button calls a service 
(for the purpose of this example say one with the highest rank).

The requirement is: change both the service that is called and the button in 
consistent manner.

The first part is easy:
 - To change the service one can simply provide a new bundle (call it S) 
containing the new service implementation (with higher rank or whatever else it 
takes to make it the one that service registry will give to the UI bundle).
 - To change the button (or even replace it with something else) one can 
provide a fragment bundle (call it FB) with updated template file(s).

The question is, how to keep those consistent? That is, make sure that either 
both S and FB are applied or none of them (lets assume S will somehow ensure 
the service is registered or stop itself if it can't do so)!

It seams one needs to somehow declare a bidirectional dependency (I hate the 
way it sounds, but that's what it in fact is, isn't it) between a bundle and a 
fragment bundle. AFAIK this is not really possible as anything specified in 
fragment is applied to the host! Has anyone faced similar challenge before?


--
http://about.me/milen

-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org

Re: org.osgi.framework.bsnversion=multiple

2016-01-13 Thread Neil Bartlett 
Do you pass a unique location string each time you install?

Neil


> On 13 Jan 2016, at 12:12, Malek Ben Salem  wrote:
> 
> Hi everyone,
> 
> I'm trying to start many instances of the same bundle in one OSGi. I have 
> noticed that setting org.osgi.framework.bsnversion=multiple doesn't change 
> anything. The install command returns the ID of the already installed bundle, 
> no new bundle is installed, as specified in 4.4.3 of the OSGi Core Release 6 
> Spec:
> 
> "Every bundle is uniquely identified by its location string. If an installed 
> bundle is using the specified
> location, the installBundle methods must return the Bundle object for that 
> installed bundle and not install a new bundle."
> 
> Yet the same section also says:
> 
> "If the to be installed bundle has a bundle symbolic name and version pair 
> that is already installed in
> the framework then the installation is only valid when the 
> org.osgi.framework.bsnversion framework launching property is set to multiple 
> or managed."
> 
> Section 10.1.15.49 (concerning org.osgi.framework.bsnversion=multiple) 
> actually says this should be possible:
> "Specifies the framework will allow multiple bundles to be installed having 
> the same symbolic name and version."
> 
> So, is this a bug in the framework? I actually use my own build of the 
> framework where I changed the installBundle method of 
> org.apache.felix.framework.Felix.java to force this option to work. I still 
> would like to know the better way to achieve this or to have the bug 
> corrected.
> 
> Regards,
> Malek.
> 
> -- 
> aicas GmbH
> Haid-und-Neu-Straße 18 * D-76131 Karlsruhe * Germany
> http://www.aicas.com   * Tel: +49-721-663 968-0
> 
> USt-Id: DE216375633, Handelsregister HRB 109481, AG Mannheim
> Geschäftsführer: Dr. James J. Hunt
> 


-
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org