You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@aries.apache.org by Matt Madhavan <ma...@gmail.com> on 2011/08/03 00:58:09 UTC
Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Hello,
I have seen couple of email threads on this topic. But did not really get a
definitive answer.
Currently we do not use Karaf. We use Felix and other related bundles via
pax runner. I have seen recommendations about using Karaf. Why cannot I just
start the Felix container in debug via mvn pax:provision and do a remote
debug? What do I get out of Karaf that I donot get from Felix and its
webconsole (started using pax web and jetty etc).
Also when using PaxExam (2.x.x), if I'm using the third type "lesson-junit"
my understanding is that:
1. I cannot use Native Container
2. And so I can only do remote debugging.
Please let me know if my understanding is OK!
Thanks in advance!
Matt
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Matt,
well I think, EIK can be found on [1].
Though I don't know the state it's in.
Last time I did take a look at it, and that's very long ago.
I wasn't able to get it running.
One thing about debugging :-)
It's quite easy to debug with Karaf (even remote) or develop with it.
Just to give you a quick impression.
Start your Karaf with karaf -debug it'll start Karaf wich will
be able to be debugged remotely on port 5005.
The next thing in the Karaf shell just do a
osgi:install -s mvn:your.group.id/your.artifact.id/your.version
which returns the bundle id of your newly installed bundle.
now do a dev:watch bundle-id (the id you just got) and
karaf will update your bundle everytime you build it.
Now you just need to do a mvn clean install (on commandline or with
maven eclipse plugin)
and you can do some happy developing.
If you need to do some debugging just attach to the karaf when needed.
There is no need to stop Karaf while doing your "re-deployments" ;)
Regards, Achim
[1] - http://code.google.com/a/eclipselabs.org/p/eik/
Am 26.08.2011 23:16, schrieb Matt Madhavan:
> HI Achim,
> Thank you very much for the reply.
>
> Also I cannot find the eclipse integration for karaf anywhere. Looks like I
> have to build it from the source. Can you send the instructions if you have
> them?
>
> Also even better if you know where I can download EIK or you have a copy you
> can sent it to me I would appreciate it.
>
> Thanks
> Matt
>
>
> On Fri, Aug 26, 2011 at 3:36 PM, Achim Nierbeck<bc...@googlemail.com>wrote:
>
>> Hi Matt,
>>
>> I'm not Andreas, but I might as well answer this (I think Andreas is off to
>> Mailand this weekend :-) )
>>
>> First of all I suggest taking a look at [1] there might be a couple of
>> answers for questions not yet found :)
>> Second in particular you might take a look at [2] where it tells you how to
>> build your own assembly of a karaf based server.
>>
>> regards, Achim
>>
>> [1] - http://karaf.apache.org/**manual/latest-2.2.x/**
>> developers-guide/index.html<http://karaf.apache.org/manual/latest-2.2.x/developers-guide/index.html>
>> [2] - http://karaf.apache.org/**manual/latest-2.2.x/**
>> developers-guide/custom-**distribution.html<http://karaf.apache.org/manual/latest-2.2.x/developers-guide/custom-distribution.html>
>>
>> Am 26.08.2011 21:55, schrieb Matt Madhavan:
>>
>> Hi Andreas,
>>> Just getting to this now after a little while!
>>>
>>> I have few more questions!
>>>
>>> Can you elaborate on the following sentence?
>>> *You can also embed Karaf into your
>>> build cycle creating your very own distribution based on Karaf if this is
>>> what you like
>>> *
>>> Planning on spending the weekend on this. Any help will be appreciated!
>>>
>>> Thanks
>>> Matt
>>>
>>> On Tue, Aug 2, 2011 at 10:12 PM, Andreas Pieber<an...@gmail.com>
>>> wrote:
>>>
>>> Hey Matt,
>>>> On Wed, Aug 3, 2011 at 04:14, Matt Madhavan<ma...@gmail.com>
>>>> wrote:
>>>>
>>>>> Than you very much for the reply!
>>>>>
>>>> Still, I don't like making advertisment on other lists. I always feel
>>>> like
>>>> a
>>>> marketing guy then :-) So maybe we can continue this discussion on one of
>>>> the Karaf lists?
>>>>
>>>>
>>>> I appreciate it. Can you point me to some
>>>>> documentation regarding installing Karaf and Karaf and Eclipse
>>>>>
>>>> Integration
>>>>
>>>>> etc. No hand holding but some pointers/docs etc and I'll be good.
>>>>>
>>>>> OK, this shouldn't be an RTM but there is really a great deal already
>>>> documented there [1] and there [2]. In very short: installing karaf is as
>>>> simple as downloading and starting it :-) You can also embed Karaf into
>>>> your
>>>> build cycle creating your very own distribution based on Karaf if this is
>>>> what you like. For the eclipse integration part: There is a plugin out
>>>> there
>>>> [3] which should help here. Still I'm personally NOT a big fan of direct
>>>> integration with your IDE. I know I'm almost alone with this opinion, but
>>>> everytime there is a bigger upgrade on one side some things stop working.
>>>> And I'm already so pissed off by this that I'm glad that you can work
>>>> with
>>>> Karaf really fine using various dev:commands and maven. Eclipse is only
>>>> what
>>>> it should be: an IDE you use to test and write code. Build and run is
>>>> done
>>>> by maven. This sounds quite slow right now, but in combination with
>>>> building
>>>> your own distribution and dev:watch this allows REALLY fast development!
>>>>
>>>> Feel free to ping us on the Karaf User list if you have any additional
>>>> questions!
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>> [1] http://karaf.apache.org/**manual/2.2.2/users-guide/**index.html<http://karaf.apache.org/manual/2.2.2/users-guide/index.html>
>>>> [2] http://karaf.apache.org/**manual/2.2.2/developers-guide/**index.html<http://karaf.apache.org/manual/2.2.2/developers-guide/index.html>
>>>> [3]
>>>>
>>>> http://fusesource.com/wiki/**display/EIK/Home;jsessionid=**
>>>> 835ECA1235B36A8CE46D14DB2FE4EC**57<http://fusesource.com/wiki/display/EIK/Home;jsessionid=835ECA1235B36A8CE46D14DB2FE4EC57>
>>>>
>>>>
>>>> I'm now intrigued.
>>>>> Thanks a lot and I look forward to hearing from you!
>>>>>
>>>>> Thanks
>>>>> Matt
>>>>> On Aug 2, 2011 8:41 PM, "Andreas Pieber"<an...@gmail.com> wrote:
>>>>>
>>>>>> Hey Matt,
>>>>>>
>>>>>> On Wed, Aug 3, 2011 at 00:58, Matt Madhavan<ma...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hello,
>>>>>>> I have seen couple of email threads on this topic. But did not really
>>>>>>>
>>>>>> get
>>>>> a
>>>>>
>>>>>> definitive answer.
>>>>>>> Currently we do not use Karaf. We use Felix and other related bundles
>>>>>>>
>>>>>> via
>>>>>> pax runner. I have seen recommendations about using Karaf. Why cannot
>>>>>> I
>>>>> just
>>>>>>> start the Felix container in debug via mvn pax:provision and do a
>>>>>>>
>>>>>> remote
>>>>> debug? What do I get out of Karaf that I donot get from Felix and its
>>>>>>> webconsole (started using pax web and jetty etc).
>>>>>>>
>>>>>>> A very good feature information is presented by
>>>>> http://karaf.apache.org/
>>>>> .
>>>>>
>>>>>> While it depends on your needs I personally start any OSGi based
>>>>>>
>>>>> toplevel
>>>>> (!) project without Karaf. The configuration support, features(.xml)
>>>>>> support, the "fancy" command line, easy packaging, hotdeployment,
>>>>>>
>>>>> remote
>>>>> access... All of them are feature you simply do not want to miss in
>>>>> your
>>>>> final server. It's not that you cant configure such a system from
>>>>> ground
>>>>> up
>>>>>
>>>>>> yourself. The question is rather: why would you want to do it? Projects
>>>>>>
>>>>> like
>>>>>
>>>>>> geronimo, smx, talend, openengsb, (and many more) already proof that it
>>>>>>
>>>>> is
>>>>>
>>>>>> pretty easy to develop toplevel projects based on Karaf. My absolute
>>>>>> favorite in the entire development tool-chain here is the "dev:watch *"
>>>>>> command in Karaf which automatically reload snapshot bundles asap they
>>>>>>
>>>>> are
>>>>>
>>>>>> build by maven. Using this together with an on-file-changed mvn install
>>>>>> script you'll get really (!) fast reload cycles. IMHO Karaf is
>>>>>>
>>>>> definitely
>>>>> worth a look for every new OSGi project! If you're looking for more
>>>>> user
>>>>> reports here you may like to write directly to the karaf user list.
>>>>>>
>>>>>> Also when using PaxExam (2.x.x), if I'm using the third type
>>>>>> "lesson-junit"
>>>>>> my understanding is that:
>>>>>>> 1. I cannot use Native Container
>>>>>>> 2. And so I can only do remote debugging.
>>>>>>>
>>>>>>> Please let me know if my understanding is OK!
>>>>>>>
>>>>>>> I can't give any qualified answer on that (still on pax-exam 1.x;
>>>>>> shame
>>>>>>
>>>>> on
>>>>>
>>>>>> me), but for non-native container the "only-remote-debugging" thing is
>>>>>> definitely true. Since the itests does not run in the same "container"
>>>>>>
>>>>> as
>>>>> your unit-tests you'll have to work with the remote debugger.
>>>>>> I hope this helps.
>>>>>>
>>>>>> Kind regards,
>>>>>> Andreas
>>>>>>
>>>>>>
>>>>>> Thanks in advance!
>>>>>>> Matt
>>>>>>>
>>>>>>>
>> --
>> --
>> *Achim Nierbeck*
>>
>>
>> Apache Karaf<http://karaf.apache.org/**> Committer& PMC
>> OPS4J Pax Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>>
>> Committer& Project Lead
>> blog<http://notizblog.**nierbeck.de/<http://notizblog.nierbeck.de/>>
>>
>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
>> For additional commands, e-mail: users-help@felix.apache.org
>>
>>
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer& Project Lead
blog<http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Matt Madhavan <ma...@gmail.com>.
HI Achim,
Thank you very much for the reply.
Also I cannot find the eclipse integration for karaf anywhere. Looks like I
have to build it from the source. Can you send the instructions if you have
them?
Also even better if you know where I can download EIK or you have a copy you
can sent it to me I would appreciate it.
Thanks
Matt
On Fri, Aug 26, 2011 at 3:36 PM, Achim Nierbeck <bc...@googlemail.com>wrote:
> Hi Matt,
>
> I'm not Andreas, but I might as well answer this (I think Andreas is off to
> Mailand this weekend :-) )
>
> First of all I suggest taking a look at [1] there might be a couple of
> answers for questions not yet found :)
> Second in particular you might take a look at [2] where it tells you how to
> build your own assembly of a karaf based server.
>
> regards, Achim
>
> [1] - http://karaf.apache.org/**manual/latest-2.2.x/**
> developers-guide/index.html<http://karaf.apache.org/manual/latest-2.2.x/developers-guide/index.html>
> [2] - http://karaf.apache.org/**manual/latest-2.2.x/**
> developers-guide/custom-**distribution.html<http://karaf.apache.org/manual/latest-2.2.x/developers-guide/custom-distribution.html>
>
> Am 26.08.2011 21:55, schrieb Matt Madhavan:
>
> Hi Andreas,
>> Just getting to this now after a little while!
>>
>> I have few more questions!
>>
>> Can you elaborate on the following sentence?
>> *You can also embed Karaf into your
>> build cycle creating your very own distribution based on Karaf if this is
>> what you like
>> *
>> Planning on spending the weekend on this. Any help will be appreciated!
>>
>> Thanks
>> Matt
>>
>> On Tue, Aug 2, 2011 at 10:12 PM, Andreas Pieber<an...@gmail.com>
>> wrote:
>>
>> Hey Matt,
>>>
>>> On Wed, Aug 3, 2011 at 04:14, Matt Madhavan<ma...@gmail.com>
>>> >
>>> wrote:
>>>
>>>> Than you very much for the reply!
>>>>
>>>
>>> Still, I don't like making advertisment on other lists. I always feel
>>> like
>>> a
>>> marketing guy then :-) So maybe we can continue this discussion on one of
>>> the Karaf lists?
>>>
>>>
>>> I appreciate it. Can you point me to some
>>>> documentation regarding installing Karaf and Karaf and Eclipse
>>>>
>>> Integration
>>>
>>>> etc. No hand holding but some pointers/docs etc and I'll be good.
>>>>
>>>> OK, this shouldn't be an RTM but there is really a great deal already
>>> documented there [1] and there [2]. In very short: installing karaf is as
>>> simple as downloading and starting it :-) You can also embed Karaf into
>>> your
>>> build cycle creating your very own distribution based on Karaf if this is
>>> what you like. For the eclipse integration part: There is a plugin out
>>> there
>>> [3] which should help here. Still I'm personally NOT a big fan of direct
>>> integration with your IDE. I know I'm almost alone with this opinion, but
>>> everytime there is a bigger upgrade on one side some things stop working.
>>> And I'm already so pissed off by this that I'm glad that you can work
>>> with
>>> Karaf really fine using various dev:commands and maven. Eclipse is only
>>> what
>>> it should be: an IDE you use to test and write code. Build and run is
>>> done
>>> by maven. This sounds quite slow right now, but in combination with
>>> building
>>> your own distribution and dev:watch this allows REALLY fast development!
>>>
>>> Feel free to ping us on the Karaf User list if you have any additional
>>> questions!
>>>
>>> Kind regards,
>>> Andreas
>>>
>>> [1] http://karaf.apache.org/**manual/2.2.2/users-guide/**index.html<http://karaf.apache.org/manual/2.2.2/users-guide/index.html>
>>> [2] http://karaf.apache.org/**manual/2.2.2/developers-guide/**index.html<http://karaf.apache.org/manual/2.2.2/developers-guide/index.html>
>>> [3]
>>>
>>> http://fusesource.com/wiki/**display/EIK/Home;jsessionid=**
>>> 835ECA1235B36A8CE46D14DB2FE4EC**57<http://fusesource.com/wiki/display/EIK/Home;jsessionid=835ECA1235B36A8CE46D14DB2FE4EC57>
>>>
>>>
>>> I'm now intrigued.
>>>>
>>>> Thanks a lot and I look forward to hearing from you!
>>>>
>>>> Thanks
>>>> Matt
>>>> On Aug 2, 2011 8:41 PM, "Andreas Pieber"<an...@gmail.com> wrote:
>>>>
>>>>> Hey Matt,
>>>>>
>>>>> On Wed, Aug 3, 2011 at 00:58, Matt Madhavan<ma...@gmail.com>
>>>>> >
>>>>>
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>> I have seen couple of email threads on this topic. But did not really
>>>>>>
>>>>> get
>>>> a
>>>>
>>>>> definitive answer.
>>>>>>
>>>>>> Currently we do not use Karaf. We use Felix and other related bundles
>>>>>>
>>>>> via
>>>>
>>>>> pax runner. I have seen recommendations about using Karaf. Why cannot
>>>>>>
>>>>> I
>>>
>>>> just
>>>>>> start the Felix container in debug via mvn pax:provision and do a
>>>>>>
>>>>> remote
>>>
>>>> debug? What do I get out of Karaf that I donot get from Felix and its
>>>>>> webconsole (started using pax web and jetty etc).
>>>>>>
>>>>>> A very good feature information is presented by
>>>>>
>>>> http://karaf.apache.org/
>>>
>>>> .
>>>>
>>>>> While it depends on your needs I personally start any OSGi based
>>>>>
>>>> toplevel
>>>
>>>> (!) project without Karaf. The configuration support, features(.xml)
>>>>> support, the "fancy" command line, easy packaging, hotdeployment,
>>>>>
>>>> remote
>>>
>>>> access... All of them are feature you simply do not want to miss in
>>>>>
>>>> your
>>>
>>>> final server. It's not that you cant configure such a system from
>>>>>
>>>> ground
>>>
>>>> up
>>>>
>>>>> yourself. The question is rather: why would you want to do it? Projects
>>>>>
>>>> like
>>>>
>>>>> geronimo, smx, talend, openengsb, (and many more) already proof that it
>>>>>
>>>> is
>>>>
>>>>> pretty easy to develop toplevel projects based on Karaf. My absolute
>>>>> favorite in the entire development tool-chain here is the "dev:watch *"
>>>>> command in Karaf which automatically reload snapshot bundles asap they
>>>>>
>>>> are
>>>>
>>>>> build by maven. Using this together with an on-file-changed mvn install
>>>>> script you'll get really (!) fast reload cycles. IMHO Karaf is
>>>>>
>>>> definitely
>>>
>>>> worth a look for every new OSGi project! If you're looking for more
>>>>>
>>>> user
>>>
>>>> reports here you may like to write directly to the karaf user list.
>>>>>
>>>>>
>>>>> Also when using PaxExam (2.x.x), if I'm using the third type
>>>>>>
>>>>> "lesson-junit"
>>>>
>>>>> my understanding is that:
>>>>>>
>>>>>> 1. I cannot use Native Container
>>>>>> 2. And so I can only do remote debugging.
>>>>>>
>>>>>> Please let me know if my understanding is OK!
>>>>>>
>>>>>> I can't give any qualified answer on that (still on pax-exam 1.x;
>>>>> shame
>>>>>
>>>> on
>>>>
>>>>> me), but for non-native container the "only-remote-debugging" thing is
>>>>> definitely true. Since the itests does not run in the same "container"
>>>>>
>>>> as
>>>
>>>> your unit-tests you'll have to work with the remote debugger.
>>>>>
>>>>> I hope this helps.
>>>>>
>>>>> Kind regards,
>>>>> Andreas
>>>>>
>>>>>
>>>>> Thanks in advance!
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>>
>
> --
> --
> *Achim Nierbeck*
>
>
> Apache Karaf<http://karaf.apache.org/**> Committer& PMC
> OPS4J Pax Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>>
> Committer& Project Lead
> blog<http://notizblog.**nierbeck.de/ <http://notizblog.nierbeck.de/>>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@felix.**apache.org<us...@felix.apache.org>
> For additional commands, e-mail: users-help@felix.apache.org
>
>
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi Matt,
I'm not Andreas, but I might as well answer this (I think Andreas is off
to Mailand this weekend :-) )
First of all I suggest taking a look at [1] there might be a couple of
answers for questions not yet found :)
Second in particular you might take a look at [2] where it tells you how
to build your own assembly of a karaf based server.
regards, Achim
[1] -
http://karaf.apache.org/manual/latest-2.2.x/developers-guide/index.html
[2] -
http://karaf.apache.org/manual/latest-2.2.x/developers-guide/custom-distribution.html
Am 26.08.2011 21:55, schrieb Matt Madhavan:
> Hi Andreas,
> Just getting to this now after a little while!
>
> I have few more questions!
>
> Can you elaborate on the following sentence?
> *You can also embed Karaf into your
> build cycle creating your very own distribution based on Karaf if this is
> what you like
> *
> Planning on spending the weekend on this. Any help will be appreciated!
>
> Thanks
> Matt
>
> On Tue, Aug 2, 2011 at 10:12 PM, Andreas Pieber<an...@gmail.com> wrote:
>
>> Hey Matt,
>>
>> On Wed, Aug 3, 2011 at 04:14, Matt Madhavan<ma...@gmail.com>
>> wrote:
>>> Than you very much for the reply!
>>
>> Still, I don't like making advertisment on other lists. I always feel like
>> a
>> marketing guy then :-) So maybe we can continue this discussion on one of
>> the Karaf lists?
>>
>>
>>> I appreciate it. Can you point me to some
>>> documentation regarding installing Karaf and Karaf and Eclipse
>> Integration
>>> etc. No hand holding but some pointers/docs etc and I'll be good.
>>>
>> OK, this shouldn't be an RTM but there is really a great deal already
>> documented there [1] and there [2]. In very short: installing karaf is as
>> simple as downloading and starting it :-) You can also embed Karaf into
>> your
>> build cycle creating your very own distribution based on Karaf if this is
>> what you like. For the eclipse integration part: There is a plugin out
>> there
>> [3] which should help here. Still I'm personally NOT a big fan of direct
>> integration with your IDE. I know I'm almost alone with this opinion, but
>> everytime there is a bigger upgrade on one side some things stop working.
>> And I'm already so pissed off by this that I'm glad that you can work with
>> Karaf really fine using various dev:commands and maven. Eclipse is only
>> what
>> it should be: an IDE you use to test and write code. Build and run is done
>> by maven. This sounds quite slow right now, but in combination with
>> building
>> your own distribution and dev:watch this allows REALLY fast development!
>>
>> Feel free to ping us on the Karaf User list if you have any additional
>> questions!
>>
>> Kind regards,
>> Andreas
>>
>> [1] http://karaf.apache.org/manual/2.2.2/users-guide/index.html
>> [2] http://karaf.apache.org/manual/2.2.2/developers-guide/index.html
>> [3]
>>
>> http://fusesource.com/wiki/display/EIK/Home;jsessionid=835ECA1235B36A8CE46D14DB2FE4EC57
>>
>>
>>> I'm now intrigued.
>>>
>>> Thanks a lot and I look forward to hearing from you!
>>>
>>> Thanks
>>> Matt
>>> On Aug 2, 2011 8:41 PM, "Andreas Pieber"<an...@gmail.com> wrote:
>>>> Hey Matt,
>>>>
>>>> On Wed, Aug 3, 2011 at 00:58, Matt Madhavan<ma...@gmail.com>
>>> wrote:
>>>>> Hello,
>>>>> I have seen couple of email threads on this topic. But did not really
>>> get
>>> a
>>>>> definitive answer.
>>>>>
>>>>> Currently we do not use Karaf. We use Felix and other related bundles
>>> via
>>>>> pax runner. I have seen recommendations about using Karaf. Why cannot
>> I
>>>>> just
>>>>> start the Felix container in debug via mvn pax:provision and do a
>> remote
>>>>> debug? What do I get out of Karaf that I donot get from Felix and its
>>>>> webconsole (started using pax web and jetty etc).
>>>>>
>>>> A very good feature information is presented by
>> http://karaf.apache.org/
>>> .
>>>> While it depends on your needs I personally start any OSGi based
>> toplevel
>>>> (!) project without Karaf. The configuration support, features(.xml)
>>>> support, the "fancy" command line, easy packaging, hotdeployment,
>> remote
>>>> access... All of them are feature you simply do not want to miss in
>> your
>>>> final server. It's not that you cant configure such a system from
>> ground
>>> up
>>>> yourself. The question is rather: why would you want to do it? Projects
>>> like
>>>> geronimo, smx, talend, openengsb, (and many more) already proof that it
>>> is
>>>> pretty easy to develop toplevel projects based on Karaf. My absolute
>>>> favorite in the entire development tool-chain here is the "dev:watch *"
>>>> command in Karaf which automatically reload snapshot bundles asap they
>>> are
>>>> build by maven. Using this together with an on-file-changed mvn install
>>>> script you'll get really (!) fast reload cycles. IMHO Karaf is
>> definitely
>>>> worth a look for every new OSGi project! If you're looking for more
>> user
>>>> reports here you may like to write directly to the karaf user list.
>>>>
>>>>
>>>>> Also when using PaxExam (2.x.x), if I'm using the third type
>>> "lesson-junit"
>>>>> my understanding is that:
>>>>>
>>>>> 1. I cannot use Native Container
>>>>> 2. And so I can only do remote debugging.
>>>>>
>>>>> Please let me know if my understanding is OK!
>>>>>
>>>> I can't give any qualified answer on that (still on pax-exam 1.x; shame
>>> on
>>>> me), but for non-native container the "only-remote-debugging" thing is
>>>> definitely true. Since the itests does not run in the same "container"
>> as
>>>> your unit-tests you'll have to work with the remote debugger.
>>>>
>>>> I hope this helps.
>>>>
>>>> Kind regards,
>>>> Andreas
>>>>
>>>>
>>>>> Thanks in advance!
>>>>>
>>>>> Matt
>>>>>
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer& Project Lead
blog<http://notizblog.nierbeck.de/>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Matt Madhavan <ma...@gmail.com>.
Hi Andreas,
Just getting to this now after a little while!
I have few more questions!
Can you elaborate on the following sentence?
*You can also embed Karaf into your
build cycle creating your very own distribution based on Karaf if this is
what you like
*
Planning on spending the weekend on this. Any help will be appreciated!
Thanks
Matt
On Tue, Aug 2, 2011 at 10:12 PM, Andreas Pieber <an...@gmail.com> wrote:
> Hey Matt,
>
> On Wed, Aug 3, 2011 at 04:14, Matt Madhavan <ma...@gmail.com>
> wrote:
> >
> > Than you very much for the reply!
>
>
> Still, I don't like making advertisment on other lists. I always feel like
> a
> marketing guy then :-) So maybe we can continue this discussion on one of
> the Karaf lists?
>
>
> > I appreciate it. Can you point me to some
> > documentation regarding installing Karaf and Karaf and Eclipse
> Integration
> > etc. No hand holding but some pointers/docs etc and I'll be good.
> >
>
> OK, this shouldn't be an RTM but there is really a great deal already
> documented there [1] and there [2]. In very short: installing karaf is as
> simple as downloading and starting it :-) You can also embed Karaf into
> your
> build cycle creating your very own distribution based on Karaf if this is
> what you like. For the eclipse integration part: There is a plugin out
> there
> [3] which should help here. Still I'm personally NOT a big fan of direct
> integration with your IDE. I know I'm almost alone with this opinion, but
> everytime there is a bigger upgrade on one side some things stop working.
> And I'm already so pissed off by this that I'm glad that you can work with
> Karaf really fine using various dev:commands and maven. Eclipse is only
> what
> it should be: an IDE you use to test and write code. Build and run is done
> by maven. This sounds quite slow right now, but in combination with
> building
> your own distribution and dev:watch this allows REALLY fast development!
>
> Feel free to ping us on the Karaf User list if you have any additional
> questions!
>
> Kind regards,
> Andreas
>
> [1] http://karaf.apache.org/manual/2.2.2/users-guide/index.html
> [2] http://karaf.apache.org/manual/2.2.2/developers-guide/index.html
> [3]
>
> http://fusesource.com/wiki/display/EIK/Home;jsessionid=835ECA1235B36A8CE46D14DB2FE4EC57
>
>
> >
> > I'm now intrigued.
> >
> > Thanks a lot and I look forward to hearing from you!
> >
> > Thanks
> > Matt
> > On Aug 2, 2011 8:41 PM, "Andreas Pieber" <an...@gmail.com> wrote:
> > > Hey Matt,
> > >
> > > On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <ma...@gmail.com>
> > wrote:
> > >
> > >> Hello,
> > >> I have seen couple of email threads on this topic. But did not really
> > get
> > a
> > >> definitive answer.
> > >>
> > >> Currently we do not use Karaf. We use Felix and other related bundles
> > via
> > >> pax runner. I have seen recommendations about using Karaf. Why cannot
> I
> > >> just
> > >> start the Felix container in debug via mvn pax:provision and do a
> remote
> > >> debug? What do I get out of Karaf that I donot get from Felix and its
> > >> webconsole (started using pax web and jetty etc).
> > >>
> > >
> > > A very good feature information is presented by
> http://karaf.apache.org/
> > .
> > > While it depends on your needs I personally start any OSGi based
> toplevel
> > > (!) project without Karaf. The configuration support, features(.xml)
> > > support, the "fancy" command line, easy packaging, hotdeployment,
> remote
> > > access... All of them are feature you simply do not want to miss in
> your
> > > final server. It's not that you cant configure such a system from
> ground
> > up
> > > yourself. The question is rather: why would you want to do it? Projects
> > like
> > > geronimo, smx, talend, openengsb, (and many more) already proof that it
> > is
> > > pretty easy to develop toplevel projects based on Karaf. My absolute
> > > favorite in the entire development tool-chain here is the "dev:watch *"
> > > command in Karaf which automatically reload snapshot bundles asap they
> > are
> > > build by maven. Using this together with an on-file-changed mvn install
> > > script you'll get really (!) fast reload cycles. IMHO Karaf is
> definitely
> > > worth a look for every new OSGi project! If you're looking for more
> user
> > > reports here you may like to write directly to the karaf user list.
> > >
> > >
> > >> Also when using PaxExam (2.x.x), if I'm using the third type
> > "lesson-junit"
> > >> my understanding is that:
> > >>
> > >> 1. I cannot use Native Container
> > >> 2. And so I can only do remote debugging.
> > >>
> > >> Please let me know if my understanding is OK!
> > >>
> > >
> > > I can't give any qualified answer on that (still on pax-exam 1.x; shame
> > on
> > > me), but for non-native container the "only-remote-debugging" thing is
> > > definitely true. Since the itests does not run in the same "container"
> as
> > > your unit-tests you'll have to work with the remote debugger.
> > >
> > > I hope this helps.
> > >
> > > Kind regards,
> > > Andreas
> > >
> > >
> > >>
> > >> Thanks in advance!
> > >>
> > >> Matt
> > >>
> >
>
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Andreas Pieber <an...@gmail.com>.
Hey Matt,
On Wed, Aug 3, 2011 at 04:14, Matt Madhavan <ma...@gmail.com> wrote:
>
> Than you very much for the reply!
Still, I don't like making advertisment on other lists. I always feel like a
marketing guy then :-) So maybe we can continue this discussion on one of
the Karaf lists?
> I appreciate it. Can you point me to some
> documentation regarding installing Karaf and Karaf and Eclipse Integration
> etc. No hand holding but some pointers/docs etc and I'll be good.
>
OK, this shouldn't be an RTM but there is really a great deal already
documented there [1] and there [2]. In very short: installing karaf is as
simple as downloading and starting it :-) You can also embed Karaf into your
build cycle creating your very own distribution based on Karaf if this is
what you like. For the eclipse integration part: There is a plugin out there
[3] which should help here. Still I'm personally NOT a big fan of direct
integration with your IDE. I know I'm almost alone with this opinion, but
everytime there is a bigger upgrade on one side some things stop working.
And I'm already so pissed off by this that I'm glad that you can work with
Karaf really fine using various dev:commands and maven. Eclipse is only what
it should be: an IDE you use to test and write code. Build and run is done
by maven. This sounds quite slow right now, but in combination with building
your own distribution and dev:watch this allows REALLY fast development!
Feel free to ping us on the Karaf User list if you have any additional
questions!
Kind regards,
Andreas
[1] http://karaf.apache.org/manual/2.2.2/users-guide/index.html
[2] http://karaf.apache.org/manual/2.2.2/developers-guide/index.html
[3]
http://fusesource.com/wiki/display/EIK/Home;jsessionid=835ECA1235B36A8CE46D14DB2FE4EC57
>
> I'm now intrigued.
>
> Thanks a lot and I look forward to hearing from you!
>
> Thanks
> Matt
> On Aug 2, 2011 8:41 PM, "Andreas Pieber" <an...@gmail.com> wrote:
> > Hey Matt,
> >
> > On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <ma...@gmail.com>
> wrote:
> >
> >> Hello,
> >> I have seen couple of email threads on this topic. But did not really
> get
> a
> >> definitive answer.
> >>
> >> Currently we do not use Karaf. We use Felix and other related bundles
> via
> >> pax runner. I have seen recommendations about using Karaf. Why cannot I
> >> just
> >> start the Felix container in debug via mvn pax:provision and do a remote
> >> debug? What do I get out of Karaf that I donot get from Felix and its
> >> webconsole (started using pax web and jetty etc).
> >>
> >
> > A very good feature information is presented by http://karaf.apache.org/
> .
> > While it depends on your needs I personally start any OSGi based toplevel
> > (!) project without Karaf. The configuration support, features(.xml)
> > support, the "fancy" command line, easy packaging, hotdeployment, remote
> > access... All of them are feature you simply do not want to miss in your
> > final server. It's not that you cant configure such a system from ground
> up
> > yourself. The question is rather: why would you want to do it? Projects
> like
> > geronimo, smx, talend, openengsb, (and many more) already proof that it
> is
> > pretty easy to develop toplevel projects based on Karaf. My absolute
> > favorite in the entire development tool-chain here is the "dev:watch *"
> > command in Karaf which automatically reload snapshot bundles asap they
> are
> > build by maven. Using this together with an on-file-changed mvn install
> > script you'll get really (!) fast reload cycles. IMHO Karaf is definitely
> > worth a look for every new OSGi project! If you're looking for more user
> > reports here you may like to write directly to the karaf user list.
> >
> >
> >> Also when using PaxExam (2.x.x), if I'm using the third type
> "lesson-junit"
> >> my understanding is that:
> >>
> >> 1. I cannot use Native Container
> >> 2. And so I can only do remote debugging.
> >>
> >> Please let me know if my understanding is OK!
> >>
> >
> > I can't give any qualified answer on that (still on pax-exam 1.x; shame
> on
> > me), but for non-native container the "only-remote-debugging" thing is
> > definitely true. Since the itests does not run in the same "container" as
> > your unit-tests you'll have to work with the remote debugger.
> >
> > I hope this helps.
> >
> > Kind regards,
> > Andreas
> >
> >
> >>
> >> Thanks in advance!
> >>
> >> Matt
> >>
>
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Matt Madhavan <ma...@gmail.com>.
Hi Andreas,
Than you very much for the reply! I appreciate it. Can you point me to some
documentation regarding installing Karaf and Karaf and Eclipse Integration
etc. No hand holding but some pointers/docs etc and I'll be good.
I'm now intrigued.
Thanks a lot and I look forward to hearing from you!
Thanks
Matt
On Aug 2, 2011 8:41 PM, "Andreas Pieber" <an...@gmail.com> wrote:
> Hey Matt,
>
> On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <ma...@gmail.com>
wrote:
>
>> Hello,
>> I have seen couple of email threads on this topic. But did not really get
a
>> definitive answer.
>>
>> Currently we do not use Karaf. We use Felix and other related bundles via
>> pax runner. I have seen recommendations about using Karaf. Why cannot I
>> just
>> start the Felix container in debug via mvn pax:provision and do a remote
>> debug? What do I get out of Karaf that I donot get from Felix and its
>> webconsole (started using pax web and jetty etc).
>>
>
> A very good feature information is presented by http://karaf.apache.org/.
> While it depends on your needs I personally start any OSGi based toplevel
> (!) project without Karaf. The configuration support, features(.xml)
> support, the "fancy" command line, easy packaging, hotdeployment, remote
> access... All of them are feature you simply do not want to miss in your
> final server. It's not that you cant configure such a system from ground
up
> yourself. The question is rather: why would you want to do it? Projects
like
> geronimo, smx, talend, openengsb, (and many more) already proof that it is
> pretty easy to develop toplevel projects based on Karaf. My absolute
> favorite in the entire development tool-chain here is the "dev:watch *"
> command in Karaf which automatically reload snapshot bundles asap they are
> build by maven. Using this together with an on-file-changed mvn install
> script you'll get really (!) fast reload cycles. IMHO Karaf is definitely
> worth a look for every new OSGi project! If you're looking for more user
> reports here you may like to write directly to the karaf user list.
>
>
>> Also when using PaxExam (2.x.x), if I'm using the third type
"lesson-junit"
>> my understanding is that:
>>
>> 1. I cannot use Native Container
>> 2. And so I can only do remote debugging.
>>
>> Please let me know if my understanding is OK!
>>
>
> I can't give any qualified answer on that (still on pax-exam 1.x; shame on
> me), but for non-native container the "only-remote-debugging" thing is
> definitely true. Since the itests does not run in the same "container" as
> your unit-tests you'll have to work with the remote debugger.
>
> I hope this helps.
>
> Kind regards,
> Andreas
>
>
>>
>> Thanks in advance!
>>
>> Matt
>>
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Andreas Pieber <an...@gmail.com>.
Hey Matt,
On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <ma...@gmail.com> wrote:
> Hello,
> I have seen couple of email threads on this topic. But did not really get a
> definitive answer.
>
> Currently we do not use Karaf. We use Felix and other related bundles via
> pax runner. I have seen recommendations about using Karaf. Why cannot I
> just
> start the Felix container in debug via mvn pax:provision and do a remote
> debug? What do I get out of Karaf that I donot get from Felix and its
> webconsole (started using pax web and jetty etc).
>
A very good feature information is presented by http://karaf.apache.org/.
While it depends on your needs I personally start any OSGi based toplevel
(!) project without Karaf. The configuration support, features(.xml)
support, the "fancy" command line, easy packaging, hotdeployment, remote
access... All of them are feature you simply do not want to miss in your
final server. It's not that you cant configure such a system from ground up
yourself. The question is rather: why would you want to do it? Projects like
geronimo, smx, talend, openengsb, (and many more) already proof that it is
pretty easy to develop toplevel projects based on Karaf. My absolute
favorite in the entire development tool-chain here is the "dev:watch *"
command in Karaf which automatically reload snapshot bundles asap they are
build by maven. Using this together with an on-file-changed mvn install
script you'll get really (!) fast reload cycles. IMHO Karaf is definitely
worth a look for every new OSGi project! If you're looking for more user
reports here you may like to write directly to the karaf user list.
> Also when using PaxExam (2.x.x), if I'm using the third type "lesson-junit"
> my understanding is that:
>
> 1. I cannot use Native Container
> 2. And so I can only do remote debugging.
>
> Please let me know if my understanding is OK!
>
I can't give any qualified answer on that (still on pax-exam 1.x; shame on
me), but for non-native container the "only-remote-debugging" thing is
definitely true. Since the itests does not run in the same "container" as
your unit-tests you'll have to work with the remote debugger.
I hope this helps.
Kind regards,
Andreas
>
> Thanks in advance!
>
> Matt
>
Re: Debugging OSGi bundles(Feliix vs Karaf) and PaxExam
Posted by Andreas Pieber <an...@gmail.com>.
Hey Matt,
On Wed, Aug 3, 2011 at 00:58, Matt Madhavan <ma...@gmail.com> wrote:
> Hello,
> I have seen couple of email threads on this topic. But did not really get a
> definitive answer.
>
> Currently we do not use Karaf. We use Felix and other related bundles via
> pax runner. I have seen recommendations about using Karaf. Why cannot I
> just
> start the Felix container in debug via mvn pax:provision and do a remote
> debug? What do I get out of Karaf that I donot get from Felix and its
> webconsole (started using pax web and jetty etc).
>
A very good feature information is presented by http://karaf.apache.org/.
While it depends on your needs I personally start any OSGi based toplevel
(!) project without Karaf. The configuration support, features(.xml)
support, the "fancy" command line, easy packaging, hotdeployment, remote
access... All of them are feature you simply do not want to miss in your
final server. It's not that you cant configure such a system from ground up
yourself. The question is rather: why would you want to do it? Projects like
geronimo, smx, talend, openengsb, (and many more) already proof that it is
pretty easy to develop toplevel projects based on Karaf. My absolute
favorite in the entire development tool-chain here is the "dev:watch *"
command in Karaf which automatically reload snapshot bundles asap they are
build by maven. Using this together with an on-file-changed mvn install
script you'll get really (!) fast reload cycles. IMHO Karaf is definitely
worth a look for every new OSGi project! If you're looking for more user
reports here you may like to write directly to the karaf user list.
> Also when using PaxExam (2.x.x), if I'm using the third type "lesson-junit"
> my understanding is that:
>
> 1. I cannot use Native Container
> 2. And so I can only do remote debugging.
>
> Please let me know if my understanding is OK!
>
I can't give any qualified answer on that (still on pax-exam 1.x; shame on
me), but for non-native container the "only-remote-debugging" thing is
definitely true. Since the itests does not run in the same "container" as
your unit-tests you'll have to work with the remote debugger.
I hope this helps.
Kind regards,
Andreas
>
> Thanks in advance!
>
> Matt
>