Adrian, I am deeply impressed - you actually seem to read the installer
scripts.
Many thanks (f)
On 02/26/2010 11:53 AM, Adrian Brock wrote:
On Thu, 2010-02-25 at 17:41 -0600, Jason T. Greene wrote:
> Hi Thomas,
>
> It would be great to offer JBoss OSGi functionality in the next
> milestone. Would you mind giving an overview of what the changes, both
> structural and components, involved in JBAS-7661 are?
>
>
The main change is the addition of an osgi.deployer
which contains some new OSGi deployers and their support classes.
https://svn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/distributio...
For other changes (e.g. default bundles)
see JBossAS integration here:
https://svn.jboss.org/repos/jbossas/projects/jboss-osgi/trunk/distributio...
The goals (and probably outdated summary of status?) are here:
http://community.jboss.org/thread/4917
> Thomas Diesler wrote:
>
>> Jason,
>>
>> in JIRA this is currently on the M3 roadmap
>>
>>
https://jira.jboss.org/jira/browse/JBAS-7661
>>
>> As you probably know, in our quest towards OSGi Core Framework TCK
>> compliance we rely on changes made to the MC. AFAICS, some of them are
>> quite fundamental and semantically don't map as cleanly onto MC as we
>> would like it to be.
>>
>> In short, adding OSGi to AS might trigger frequent MC updates which can
>> be disruptive to others. However, it should be quite obvious that "JBoss
>> OSGi Support" actually means that OSGi is supported in AS, which can
>> only be verified in AS.
>>
>> Currently, I do the OSGi QA such that my installer replaces MC
>> components in AS. Such I can verify that the OSGi stuff is working, but
>> I cannot know if at the same time the MC replacement breaks other stuff.
>>
>> I recommend that we do include JBAS-7661 in M3, which would raise the
>> level of urgency for issues related MC changes that are triggered by
>> OSGi. i.e. MC updates need to work for OSGi *and* existing services.
>>
>> Whether we actually ship OSGi in the M3 distribution is a different
>> story IMHO.
>>
>> cheers
>> -thomas
>>
>> On 02/18/2010 05:03 PM, Jason T. Greene wrote:
>>
>>> Hello everyone,
>>>
>>> Thanks again for all the hard work on M2. Now that it's out the door,
>>> it's time to look at our plan/goals for M3.
>>>
>>> The tentative code/component freeze date for M3 is March 22. Please let
>>> me know what updates you feel comfortable including in this release.
>>>
>>> Ideally we would be able to deliver:
>>> - Completed HornetQ Integration
>>> - Remoting 3 Integration
>>> - Various major EJB 3.1 features
>>>
>>> Let me know your thoughts on this.
>>>
>>> Thanks!
>>>
>>>
>>
>
>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx