EZB OSGI without RMI

[ekke]

if I'm using Easybeans OSGI without RMI,
is it correct to do the following:

don't start CAROL bundle
change Manifest of easybeans.core and jotm:
imports from carol changed to optional

thanks for info

ekke

[David Alves-3]

Hi ekke

        Actually from a configuration standpoint all you should have to do
would be not to include the <rmi/> node in your configuration
(easybeans.xml), though I'm not entirely sure the RMI will not start if
you do this. If you do this you will still have the carol bundle there
but it will not be used, which I think is better than changing the
bundle imports for core.

Regards
David Alves


On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:

> if I'm using Easybeans OSGI without RMI,
> is it correct to do the following:
>
> don't start CAROL bundle
> change Manifest of easybeans.core and jotm:
> imports from carol changed to optional
>
> thanks for info
>
> ekke
>

[ekke]

hi david,
thanks...

I'll think about it..

changing the bundle imports of easybeans.core isn't problematic for me,
because I have to rebundle easybeans.core, because I dont't like those
bundles with so many many many jars in /dependencies.
this is problematic if you use those bundles in context with other
bundles also importing or requiring same packages.

I know its much work to break it into many small bundles, but thats
the way OSGI works better

ekke

David Alves schrieb:

> Hi ekke
>
> Actually from a configuration standpoint all you should have to do
> would be not to include the <rmi/> node in your configuration
> (easybeans.xml), though I'm not entirely sure the RMI will not start if
> you do this. If you do this you will still have the carol bundle there
> but it will not be used, which I think is better than changing the
> bundle imports for core.
>
> Regards
> David Alves
>
>
> On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
>> if I'm using Easybeans OSGI without RMI,
>> is it correct to do the following:
>>
>> don't start CAROL bundle
>> change Manifest of easybeans.core and jotm:
>> imports from carol changed to optional
>>
>> thanks for info
>>
>> ekke
>>
>
>

[Guillaume Sauthier]

ekke a écrit :

> hi david,
> thanks...
>
> I'll think about it..
>
> changing the bundle imports of easybeans.core isn't problematic for me,
> because I have to rebundle easybeans.core, because I dont't like those
> bundles with so many many many jars in /dependencies.
> this is problematic if you use those bundles in context with other
> bundles also importing or requiring same packages.
>
> I know its much work to break it into many small bundles, but thats
> the way OSGI works better

Ekke, dividing the easybeans big OSGi bundle is something we want to do.
If you've already done it, can you consider to contribute this work ?

Thanks
--Guillaume

>
> ekke
>
> David Alves schrieb:
>> Hi ekke
>>
>>     Actually from a configuration standpoint all you should have to do
>> would be not to include the <rmi/> node in your configuration
>> (easybeans.xml), though I'm not entirely sure the RMI will not start if
>> you do this. If you do this you will still have the carol bundle there
>> but it will not be used, which I think is better than changing the
>> bundle imports for core.
>>
>> Regards
>> David Alves
>>
>> On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
>>> if I'm using Easybeans OSGI without RMI,
>>> is it correct to do the following:
>>>
>>> don't start CAROL bundle
>>> change Manifest of easybeans.core and jotm:
>>> imports from carol changed to optional
>>>
>>> thanks for info
>>>
>>> ekke
>>>
>>
>>
>
>
>

[Guillaume_Sauthier.vcf]

---

begin:vcard
fn:Guillaume Sauthier
n:Sauthier;Guillaume
org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a>
adr:;;;;;;France
email;internet:guillaume.sauthier@...
title:<a href="http://jonas.ow2.org">JOnAS Application Server</a>
x-mozilla-html:TRUE
url:http://jonas.ow2.org
version:2.1
end:vcard

---

[ekke]

Guillaume Sauthier schrieb:

> ekke a écrit :
>> hi david,
>> thanks...
>>
>> I'll think about it..
>>
>> changing the bundle imports of easybeans.core isn't problematic for me,
>> because I have to rebundle easybeans.core, because I dont't like those
>> bundles with so many many many jars in /dependencies.
>> this is problematic if you use those bundles in context with other
>> bundles also importing or requiring same packages.
>>
>> I know its much work to break it into many small bundles, but thats
>> the way OSGI works better
>
> Ekke, dividing the easybeans big OSGi bundle is something we want to do.
> If you've already done it, can you consider to contribute this work ?
>

I'm working on it ;-)
step-by-step
ist not so easy

and: of course I'll contribute this

if you open easybeans.core as plugin project in eclipse, then the first
you see from PDE: "cycle detected". I think the problem is that some
packages are
a) defined as dependency by inmport
b) AND also included as jar from dependencies AND exported

ekke
btw: the logging is really problematic - would be really great if you
found a way that log4j can also used.
the current ow2 commons-logging package has in the internal commons
logging packages some classes less then the original commons.logging.
but for other packages you need the origin comons logging.
I'm using the bundles from springsource enterprise repository if possible

> Thanks
> --Guillaume
>
>>
>> ekke
>>
>> David Alves schrieb:
>>> Hi ekke
>>>
>>>     Actually from a configuration standpoint all you should have to do
>>> would be not to include the <rmi/> node in your configuration
>>> (easybeans.xml), though I'm not entirely sure the RMI will not start if
>>> you do this. If you do this you will still have the carol bundle there
>>> but it will not be used, which I think is better than changing the
>>> bundle imports for core.
>>>
>>> Regards
>>> David Alves
>>>
>>> On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
>>>> if I'm using Easybeans OSGI without RMI,
>>>> is it correct to do the following:
>>>>
>>>> don't start CAROL bundle
>>>> change Manifest of easybeans.core and jotm:
>>>> imports from carol changed to optional
>>>>
>>>> thanks for info
>>>>
>>>> ekke
>>>>
>>>
>>>
>>
>>
>>
>

[ekke]

David Alves schrieb:
> Hi ekke
>
> Actually from a configuration standpoint all you should have to do
> would be not to include the <rmi/> node in your configuration
> (easybeans.xml),

david,

at the moment I'm testing and evaluating and have used your built in
default configuration.

from the user guide I also know about the easybeans.xml,
but I didn't found an information where I have to place this file
in easybeans OSGI ?
a fragment bundle to easybeans.core ?
or are you using something like managed services ?

thx for info

ekke

though I'm not entirely sure the RMI will not start if

> you do this. If you do this you will still have the carol bundle there
> but it will not be used, which I think is better than changing the
> bundle imports for core.
>
> Regards
> David Alves
>
>
> On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
>> if I'm using Easybeans OSGI without RMI,
>> is it correct to do the following:
>>
>> don't start CAROL bundle
>> change Manifest of easybeans.core and jotm:
>> imports from carol changed to optional
>>
>> thanks for info
>>
>> ekke
>>
>
>

[David Alves-3]

Hi ekke

        You can include the config file wherever you want all you have to do is
set the directory as a system property. (I pass it as a command line
argument -Dorg.ow2.easybeans.osgi.conf.dir="./conf/".

David


On Fri, 2008-07-11 at 15:33 +0200, ekke wrote:

> David Alves schrieb:
> > Hi ekke
> >
> > Actually from a configuration standpoint all you should have to do
> > would be not to include the <rmi/> node in your configuration
> > (easybeans.xml),
>
> david,
>
> at the moment I'm testing and evaluating and have used your built in
> default configuration.
>
> from the user guide I also know about the easybeans.xml,
> but I didn't found an information where I have to place this file
> in easybeans OSGI ?
> a fragment bundle to easybeans.core ?
> or are you using something like managed services ?
>
> thx for info
>
> ekke
>
> though I'm not entirely sure the RMI will not start if
> > you do this. If you do this you will still have the carol bundle there
> > but it will not be used, which I think is better than changing the
> > bundle imports for core.
> >
> > Regards
> > David Alves
> >
> >
> > On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
> >> if I'm using Easybeans OSGI without RMI,
> >> is it correct to do the following:
> >>
> >> don't start CAROL bundle
> >> change Manifest of easybeans.core and jotm:
> >> imports from carol changed to optional
> >>
> >> thanks for info
> >>
> >> ekke
> >>
> >
> >
>

[ekke]

David Alves schrieb:
> Hi ekke
>
> You can include the config file wherever you want all you have to do is
> set the directory as a system property. (I pass it as a command line
> argument -Dorg.ow2.easybeans.osgi.conf.dir="./conf/".
>
> David
>
hmmm
I cannot place it into an OSGI bundle ?

ekke

[David Alves-3]

Hi ekke

        I don't know the purpose of your application but I would discourage
including the configuration in a bundle. In my case I must change the
config for the production and dev environments and having to change the
configuration inside a jar does not my specific needs. Configurations
like these (even in the eclipse case with the eclipse.ini) usually
reside outside the runtime bundles.
        That being said I can see two possible solutions to fit your needs.
Since you are repackaging easybeans core you could simply replace the
easybeans.xml that server as the default config inside the bundle OR you
could try and pass a bundle:// type url as the config property (though
I'm not sure the last possibility works).

David

On Fri, 2008-07-11 at 15:56 +0200, ekke wrote:
> hmmm
> I cannot place it into an OSGI bundle ?

[ekke]

hin david,

thanks again...

easybeans.xml works well with Equinox and OSGI Launch configuration on
mac, I added to vm args:

-Dorg.ow2.easybeans.osgi.conf.dir=${workspace_loc}/config/easybeans

(without "" you're using)

ekke

David Alves schrieb:

> Hi ekke
>
> You can include the config file wherever you want all you have to do is
> set the directory as a system property. (I pass it as a command line
> argument -Dorg.ow2.easybeans.osgi.conf.dir="./conf/".
>
> David
>
>
> On Fri, 2008-07-11 at 15:33 +0200, ekke wrote:
>> David Alves schrieb:
>>> Hi ekke
>>>
>>> Actually from a configuration standpoint all you should have to do
>>> would be not to include the <rmi/> node in your configuration
>>> (easybeans.xml),
>> david,
>>
>> at the moment I'm testing and evaluating and have used your built in
>> default configuration.
>>
>> from the user guide I also know about the easybeans.xml,
>> but I didn't found an information where I have to place this file
>> in easybeans OSGI ?
>> a fragment bundle to easybeans.core ?
>> or are you using something like managed services ?
>>
>> thx for info
>>
>> ekke
>>
>> though I'm not entirely sure the RMI will not start if
>>> you do this. If you do this you will still have the carol bundle there
>>> but it will not be used, which I think is better than changing the
>>> bundle imports for core.
>>>
>>> Regards
>>> David Alves
>>>
>>>
>>> On Fri, 2008-07-11 at 09:10 +0200, ekke wrote:
>>>> if I'm using Easybeans OSGI without RMI,
>>>> is it correct to do the following:
>>>>
>>>> don't start CAROL bundle
>>>> change Manifest of easybeans.core and jotm:
>>>> imports from carol changed to optional
>>>>
>>>> thanks for info
>>>>
>>>> ekke
>>>>
>>>
>
>