Hi Sahoo,
Thanks your reply very much!
> This is a dead module. We should remove it.
I see.
>> 2) mean of GF OBR Integration
>> From https://wikis.oracle.com/display/GlassFish/3.1OSGi, having the
>> following goal,
>>
>> "
>> OBR integration: We plan to have OBR integration in place so that
>> GlassFish deployment process can resolve dependencies of bundles via
>> OBR. OBR integration will also help us having a better provisioning
>> story for embedded glassfish use case, for we can then provide a la
>> carte access to GF modules via OBR.
>> "
>>
>> About the above goal, I considered the following use cases:
>>
>> $B-!(B GlassFish-Self modules's provisioning
>> For a user, he/she maybe only use a few function of glassfish/modules,
>> by using obr, glassfish's installation may be more "thiner", that is to
>> say, user needs not to install some modules which he/she is not ready to
>> use firstly in order to save the resouces.
> This is a work in progress. I have implemented this to some extent in
> trunk. I call this "on demand" mode. You can try it out by setting
> glassfish.osgi.ondemand=true in glassfish/config/osgi.properties.
OK, I will try it and because the field(provisioning) also my interested
field, if possible, in the future, please give some things to do.
>> $B-"(B Glassfish-Outside modles's provisioning
>> Liking apache ace and karaf, by using obr, will give user more strenth
>> to deploy a big app, and I will spend some time to investigate it.
>>
> Yes, this is where we have to bring in OBR. This is the use case the
> Wiki page refers to as well.
>> So, what I said is right?
> Very much.
>
> Thanks,
> Sahoo
>> --Best Regard!
>> --Tang
>>
>>
>>
>
>
>