bundle issueshttps://gitlab.ow2.org/weblab/bundle/-/issues2018-12-09T14:49:10Zhttps://gitlab.ow2.org/weblab/bundle/-/issues/9Issue with named host access2018-12-09T14:49:10ZYann MombrunIssue with named host accessWhen a server is started to only listen to its named host, it was not possible to connect to it to know if it is started since current method relies on hardcoded "localhost".When a server is started to only listen to its named host, it was not possible to connect to it to know if it is started since current method relies on hardcoded "localhost".2.1.2Yann MombrunYann Mombrunhttps://gitlab.ow2.org/weblab/bundle/-/issues/1Exclude useless dependencies from zookeeper2018-12-09T14:49:10ZYann MombrunExclude useless dependencies from zookeeperThe zookeeper import in the bundle does not exclude the dependencies.
But since we are importing a tar.gz package to be untar, it is useless to have the list of dependencies in the project model.The zookeeper import in the bundle does not exclude the dependencies.
But since we are importing a tar.gz package to be untar, it is useless to have the list of dependencies in the project model.2.1.2Yann MombrunYann Mombrunhttps://gitlab.ow2.org/weblab/bundle/-/issues/7WebLab reset should clear activemq2018-12-09T14:49:10ZYann MombrunWebLab reset should clear activemqWhen calling weblab.sh reset we currently clear all the data from the system.
However, since the queues are not emptied already processed data may arrive in the meantimeWhen calling weblab.sh reset we currently clear all the data from the system.
However, since the queues are not emptied already processed data may arrive in the meantime2.1.2https://gitlab.ow2.org/weblab/bundle/-/issues/8Add a Launcher for Jetty simple webserver2018-09-27T16:07:23ZYann MombrunAdd a Launcher for Jetty simple webserverIt would be good to be able to manage a Jetty from the launcher directly.
Could be used like for OpenAXES to manage a dedicated component (like LIMAS or Geoserver for instance)It would be good to be able to manage a Jetty from the launcher directly.
Could be used like for OpenAXES to manage a dedicated component (like LIMAS or Geoserver for instance)2.1.2Vincent CorjonVincent Corjonhttps://gitlab.ow2.org/weblab/bundle/-/issues/3Launcher is not able to access activemq when not started using localhost as h...2018-09-18T09:06:44ZYann MombrunLauncher is not able to access activemq when not started using localhost as hostnameThe JMX identifier used to connect to activemq (in order to get status of the queues) contains the brokerName.
However this is hardcoded inside the launcher to be localhost.
This prevent from using the launcher to handle an activemq with...The JMX identifier used to connect to activemq (in order to get status of the queues) contains the brokerName.
However this is hardcoded inside the launcher to be localhost.
This prevent from using the launcher to handle an activemq with a custom broker name.2.1.2Yann MombrunYann Mombrunhttps://gitlab.ow2.org/weblab/bundle/-/issues/6Add a few more camel components by default inside karaf2018-09-07T10:16:43ZYann MombrunAdd a few more camel components by default inside karafAt least camel-facebook but I'm sure that a few other camel components could be added in the meantimeAt least camel-facebook but I'm sure that a few other camel components could be added in the meantime2.1.2https://gitlab.ow2.org/weblab/bundle/-/issues/4Use a logger abstraction + log4J implementation in launcher2018-09-07T10:16:13ZYann MombrunUse a logger abstraction + log4J implementation in launcherCurrent code of the launcher relies on java.util.logging classes.
As a result, the logger cannot be easily configured.Current code of the launcher relies on java.util.logging classes.
As a result, the logger cannot be easily configured.2.1.2