including logging... On Wed, Sep 19, 2018 at 9:31 AM Raymond Auge <raymond.a...@liferay.com> wrote:
> All I had to do in your project was: > > java -jar my-app/target/my-app.jar > > And it just worked. > - Ray > > On Wed, Sep 19, 2018 at 9:26 AM Raymond Auge <raymond.a...@liferay.com> > wrote: > >> So Philipp, >> >> When I sent you a PR, your app was already resolved. Why do you not have >> the framework packages? >> All you need to do is export the runnable jar, and everything should be >> there,.. then you can run that either locally or in a Docker image that >> provides Java. >> >> You've already done all the work! >> >> :) >> >> - Ray >> >> On Wed, Sep 19, 2018 at 9:16 AM Philipp Höfler < >> philipp.hoef...@pernexas.com> wrote: >> >>> Hallo JB, >>> >>> thanks for your kind reply. >>> >>> I am getting confused :-) >>> I am quite new to the OSGi world, so my questions are probably very >>> basic. >>> >>> I am not sure, if I can use Karaf just like that, as I am using OSGi >>> enRoute R7. >>> As far as I understood, it's not finally released yet? So I guess, that >>> Karaf does it not support yet? >>> >>> Anyhow, I tried to deploy my app on Karaf. And there are a lot of >>> missing dependencies. >>> How is the best way of deploying a OSGi app? I've three bundles and each >>> have different dependencies. >>> The packaged app jar, that is generated from the enRoute example >>> project, packs all these dependencies in a jar folder of the app.jar >>> What I do not understand is, why dependencies like "org.osgi.framework" >>> or "org.osgi.service.log" is missing. I though, that would be provided by >>> Karaf? >>> >>> I recently added logging via the new OSGi Logging standard and logback. >>> I read on the Karaf website, that Karaf can already unify the logging >>> configuration. >>> As I understood, logback is also trying to unify the configuration over >>> all popular logging frameworks. Does it just work or do I have to adapt >>> anything? >>> >>> Thanks for your help, >>> Philipp >>> >>> Am 19.09.18, 14:17 schrieb "Jean-Baptiste Onofré" <j...@nanthrax.net>: >>> >>> Hi Philip, >>> >>> You can use Karaf as a container. It supports different programming >>> model including OSGi of course. >>> >>> Karaf supports Aries JMX and MBean whiteboard pattern to simplify >>> the >>> way of exposing your MBeans (it's just registering a MBean service). >>> >>> Once done, you can use Karaf Decanter to collect the metrics and >>> have >>> monitoring/BAM/alerting. >>> >>> Don't hesitate to ping me if you need more details. >>> >>> Regards >>> JB >>> >>> On 19/09/2018 12:34, Philipp Höfler wrote: >>> > Hi, >>> > >>> > I've setup a small OSGi application. >>> > The application gets some REST requests and forwards these >>> requests to a content repository using CMIS. >>> > So, basically the app consists of three bundles. The first bundle >>> provides and RESTful webservice (HTTP Whiteboard), the second the CMIS >>> connection to the repository and the third is the internal API between the >>> other two bundles. >>> > >>> > Now, I am encountering performances problems. Storing documents to >>> the repository, is quite slower than it should be. >>> > I thought it would be a good idea, to monitor the application to >>> identify the bottle necks. >>> > That's why I would like to connect VisualVM (or JConsole) via JMX. >>> > >>> > Right now the application is not finished yet, so the deployment >>> does not exists. >>> > I am currently using the bundled app from the enRoute R7 example >>> project for testing. >>> > >>> > Is it a realistic to use the bundled app for tests or is an >>> application server like Karaf faster? >>> > Is it possible to connect to the JMX of the bundled app? Would you >>> recommend using Karaf (application server)? >>> > >>> > When you do recommend Karaf, how can I deploy my app to the >>> application server? >>> > Do I have to install every single bundle? >>> > >>> > As always, thanks for your help. >>> > Philipp >>> > >>> > >>> > >>> --------------------------------------------------------------------- >>> > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org >>> > For additional commands, e-mail: users-h...@felix.apache.org >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org >>> For additional commands, e-mail: users-h...@felix.apache.org >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@felix.apache.org >>> For additional commands, e-mail: users-h...@felix.apache.org >>> >> >> >> -- >> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> >> (@rotty3000) >> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> >> (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> >> (@OSGiAlliance) >> > > > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> > (@OSGiAlliance) > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
