Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of chubrilo@gmail.com designates
 209.85.214.43 as permitted sender)
MIME-Version: 1.0
Sender: chubrilo@gmail.com
In-Reply-To: 
 <CA++FMTxqd4bfV04N3Uv_7rB6+i-8XV13SPOaXqt0dw5mif8xiQ@mail.gmail.com>
References: 
 <CA++FMTyUKyS2bqKHwzeLo6KLPrqLMi2CAM-SYST7GnbGUxzD3Q@mail.gmail.com>
	<CAGeh-pHqY0ZvD==enhx-sm0xfHE9=My-FSZM0piQq7UTvBkuyQ@mail.gmail.com>
	<CA++FMTxqd4bfV04N3Uv_7rB6+i-8XV13SPOaXqt0dw5mif8xiQ@mail.gmail.com>
Date: Tue, 12 Feb 2013 15:19:57 +0100
Message-ID: 
 <CAGeh-pHatGVnF9TNKapv00eCY7Lh_dxFKr5JQz6QicSg_2E7ag@mail.gmail.com>
Subject: Re: osgi manifest headers are missed in 5.8.0 release
From: Dejan Bosanac <dejan@nighttale.net>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi Dmytro,

with previous version you'd use activemq-core, which also contained
all broker classes, so there's no much of a difference now. You only
need to use activemq-osgi bundle instead of activemq-core one. There's
an activemq-client feature among karat features that's supposed to be
used if you're only interesting using a client-side stuff. Also, for
the http transport you should use activemq-http feature (note that
activemq-optional module doesn't exist anymore, so you should use
activemq-http instead).


Regards
--
Dejan Bosanac
----------------------
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosanac@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Tue, Feb 12, 2013 at 3:12 PM, Dmytro Pishchukhin
<dmytro.pishchukhin@gmail.com> wrote:
> Hi Dejan,
>
> thank you for details.
>
> As I see, activemq-osgi contains all functionality (client, broker,
> all transports, dependencies etc.). I'd like to use only small
> functionality sub-scope (e.g. client + http transport). With previous
> versions, I can use bundles/modules I need. With the latest version, I
> have to include all functionality into my osgi framework and I don't
> have any way to configure it. Of course, I can wrap the other activemq
> jars and add osgi manifest headers on the fly, but it's not "off the
> shelf" solution. Or did I miss something?
>
>
> --
> Best regards,
> Dmytro Pishchukhin
>
>
> On Tue, Feb 12, 2013 at 2:46 PM, Dejan Bosanac <dejan@nighttale.net> wrote:
>> Hi Dmytro,
>>
>> we changed the modules of the activemq for 5.8.0 and how it integrates
>> with osgi containers. You can find more details on it here
>>
>> http://activemq.apache.org/osgi-integration.html
>>
>> but in a nutshell, there's now activemq-osgi bundle that incorporates
>> all classes and is ready to be used in osgi land. You can also take a
>> look at karat features for 5.8.0 and see how it's deployed.
>>
>>
>> Regards
>> --
>> Dejan Bosanac
>> ----------------------
>> Red Hat, Inc.
>> FuseSource is now part of Red Hat
>> dbosanac@redhat.com
>> Twitter: @dejanb
>> Blog: http://sensatic.net
>> ActiveMQ in Action: http://www.manning.com/snyder/
>>
>>
>> On Tue, Feb 12, 2013 at 2:41 PM, Dmytro Pishchukhin
>> <dmytro.pishchukhin@gmail.com> wrote:
>>> Hi,
>>>
>>> I've just found that ActiveMQ 5.8.0 artifacts do no contain OSGi
>>> headers in manifest files. What was the reason to remove them?
>>>
>>> Thanks in advance.
>>>
>>> --
>>> Best regards,
>>> Dmytro Pishchukhin