Hi:
I have similar concerns. I wanted to protect a particular endpoint. Here's
what I have done, so far:
// pom file
org.apache.felix
maven-bundle-plugin
3.3.0
true
true
/
Hello,
I've noticed that the container built with maven-karaf-plugin (4.2.4) "doesn't
work" without any error message.
After the inspection I've noticed that one of my features is not installed.
The name of the feature was misspelled.
The problem is, that maven build has not failed.
It looks l
Hi,
Do you use karaf:verify on your features ?
Regards
JB
On 04/06/2019 16:37, Lukasz Lech wrote:
> Hello,
>
>
>
> I’ve noticed that the container built with maven-karaf-plugin (4.2.4)
> “doesn’t work” without any error message.
>
> After the inspection I’ve noticed that one of my features
Is it possible to change the session variable "PROMPT" by a executed custom
command in a bundle?
For example:
karaf@root()> item:add Something
Created item with id 12345 and content "Hello World!"
karaf@root():item:12345>item:change content "42 rules"
Changed content of item with id 12345 to "42
Hello, we are currently developing an application based on karaf 4.1.6, but
we do not manage the operating system in which it is installed. Recently, to
our regret, two actions have come together:
1.- The operating system was changed to SUSE.
2.- We have updated the version of our application.
With
Hi,
you can change PROMPT property in the command Session.
The command has an access to Session, so you can do:
...
public class MyCommand implements Action {
@Reference
Session session;
public Object execute() {
session.put(Session.PROMPT, "fooo");
return null;
}
Regards
JB
On 04/06/201
Hi,
As you are using directly bin/karaf (via bin/start & bin/stop), without
wrapper or watchdog, karaf doesn't stop automatically. Especially, if
you see a Karaf dump zip file created, it's certainly a manual or
programmatic action.
Maybe you can take a look on the audit.log to see what is perfor
