#Logtail aries how to

Overall, Gemini Blueprint on Virgo works great, just as advertised, and I have yet to hit any edge cases. If Gemini Blueprint can support those in the future, or better yet: standardize them, it'd be great. On other project I use Blueprint 'Compendium', it seems like Aries' 'proprietary' extension on OSGi Blueprint, specifically these namespaces: I just happen to have those (SpringSource EBR version) lying around so I'm a bit lucky. Then Aries needed 3 more JARs: asm, asm.tree, asm.commons. I hope Virgo will also integrate these features, to which Borislav has confirmed that Virgo 3.0 will release with Felix GoGo + SSH integration! (oh yeah!)Īctually, installing Gemini is much less troublesome than Aries because I only had to put 3 bundles (io, core, extender, pretty intuitive) without no missing external dependency.įor Aries Blueprint, I needed 3 Aries bundles (aries.blueprint, aries.proxy, and aries.util), the latter two are not so intuitive to infer that they're blueprint's dependencies but perhaps it's because Aries modules (as a whole) are more cohesive than Gemini subprojects. Though particularly for my sample case, Apache Karaf won big (not to brag the competition, but hoping it would be a constructive feedback to Virgo team) due to well-integrated Felix GoGo, SSH server, Apache Aries as OSGi Blueprint implementation, and also good logging that can be inspected right inside console/SSH (Karaf shell commands like log:tail). So do you want Blueprint support in Virgo ? If so, please comment/vote on and maybe you can help too by testing/developing/etc. In my sample case Gemini Blueprint 1.0.0.M1 ran without problems in Virgo 3.0.0.M5! Yay! I also created a sample PDE plug-in project openly accessible in GitHub:

#Logtail aries how to

I blogged a tutorial on how to integrate Felix GoGo, SSH, and OSGi Blueprint (Gemini Blueprint, but working instructions for Apache Aries also available) with Eclipse Virgo Web Server here: > at (Thread.Glyn Normington suggested me to create this thread so other Virgo users would benefit this information. > .console - 2.3.7 | Exception caught while executing > 11:49:10,839 | ERROR | l Console Thread | Console > .mbeans.scr - 2.3.7 | Activating the Apache Karaf > 11:49:01,757 | INFO | l Console Thread | ScrServiceMBeanImpl > - .scr - 2.3.7 | Activating the Apache Karaf SCR > DeactivateCommandComponent | l.scr.DeactivateCommandComponent 66 | 57 > .scr - 2.3.7 | Activating the Apache Karaf SCR Activate > 11:49:01,741 | INFO | l Console Thread | ActivateCommandComponent > .scr - 2.3.7 | Activating the Apache Karaf SCR List > 11:49:01,738 | INFO | l Console Thread | ListCommandComponent > .scr - 2.3.7 | Activating the Apache Karaf SCR Details > 11:49:01,730 | INFO | l Console Thread | DetailsCommandComponent > .cm.ConfigurationAdminMBean to MBeanServer > .wiring.BundleWiringStateMBean to MBeanServer > Error executing command: Cannot coerce info() to any of

> To reproduce using a vanilla karaf 2.3.7 > Karaf shell - scr:info - Cannot coerce info() to any of I will 'improve' the error message (something like 'Component expected'). Jean-Baptiste Onofré commented on KARAF-3217: