That works with the option that you propose. Kind regards,
Charles Moulliard Senior Enterprise Architect (J2EE, .NET, SOA) Apache Camel - ServiceMix Committer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Blog : http://cmoulliard.blogspot.com | Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard On Thu, Jul 8, 2010 at 7:10 AM, Chris Custine <[email protected]>wrote: > Hi Charles, > I think what you want to do is edit the karaf script, find the KARAF_DEBUG > variable, and change the suspend=n (near the end of the line) to suspend=y. > That will cause the JVM to pause just before running main() until you > attach a debugger then it will resume the execution. This way you can set > your breakpoints anywhere in the code and you should hit them no matter how > early in the startup they are. > > Chris > > -- > Chris Custine > FUSESource :: http://fusesource.com > My Blog :: http://blog.organicelement.com > Apache ServiceMix :: http://servicemix.apache.org > Apache Felix :: http://felix.apache.org > Apache Directory Server :: http://directory.apache.org > > > On Wed, Jul 7, 2010 at 12:09, Charles Moulliard <[email protected] > >wrote: > > > Hi, > > > > When working with camel, cxf projects and using the variable > > KARAF_DEBUG, it is easy to debug an application. But when Karaf > > starts, this option does not allow to have access to the classes of > > the heart of karaf. Is there a trick to allow to debug feature > > mechanism by example in Eclipse ? > > > > Kind regards, > > > > Charles Moulliard > > > > Senior Enterprise Architect (J2EE, .NET, SOA) > > Apache Camel - ServiceMix Committer > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Blog : http://cmoulliard.blogspot.com | Twitter : > > http://twitter.com/cmoulliard > > Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: > cmoulliard > > >
