Better check from time to time what Maven does in a complex project .
We'll have to check how to get rid of all the jars needed for testing. In
the meantime, I have removed at least the toxic items from the lib folder
(osgi jars, javax.servlet, and, to be sure, also the jetty jars). Already
after
If you work with larger maven projects make sure you do use test, compile
and provided scopes on your dependencies.
Usually this will help filter out lot's of your issues already as only
compile dependencies are included if you use the maven-bundle-plugin.
Right now I wouldn't know of any
Wanted to ask if this is a feature or a bug:
karaf@root() feature:install 007
Error executing command: No feature named '7' with version '0.0.0' available
I have other, custom commands using string arguments and these now require
quoted values in case of leading zeros.
I guess that it works if you do feature:install 007 ?
Regards
JB
On 11/12/2014 03:06 PM, Martin Lichtin wrote:
Wanted to ask if this is a feature or a bug:
karaf@root() feature:install 007
Error executing command: No feature named '7' with version '0.0.0' available
I have other, custom
Richard,
Logging is working in my environment. The environment contains Karaf 3.0.2
JAXWX in CXF 3.0.2 and services are defined using Blueprint.
blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
Karaf 3.0.2, CXF 3.0.2
How to define an CXF Web Service endpoint with an argument in the constructor?
Below is my configuration and the stack trace.
***
* OSGI-INF/blueprint/services.xml
***
blueprint...
jaxws:endpoint id=“MyService” wsdlLocation=“MY_SERVICE.wsdl”
Karaf 3.0.2, CXF 3.0.2
How to define an CXF Web Service endpoint with an argument in the constructor?
Below is my configuration and the stack trace.
***
* OSGI-INF/blueprint/services.xml
***
blueprint...
jaxws:endpoint id=“MyService” wsdlLocation=“MY_SERVICE.wsdl”
Yes, quoting leaves the argument value unmodified.
jbonofre wrote
I guess that it works if you do feature:install 007 ?
Regards
JB
On 11/12/2014 03:06 PM, Martin Lichtin wrote:
Wanted to ask if this is a feature or a bug:
karaf@root() feature:install 007
Error executing command: No
One more question
I have a bunch of logger defines in logback.xml
e.g.
logger name=io.netty level=WARN/
I want them to appear when I do log:get ALL in karaf console. But the only
thing I see in Karaf console is
---
Logger | Level
--
ROOT | DEBUG
---
Where should I
You could have look the link below, i have done it in karaf and its working
fine for me.
I used logback.xml file and added all my logback configurations in file.
http://www.gharki.com/2014/07/how-to-configure-pax-logging-to-use.html
Srikanth Hugar
www.gharki.com
On Thu, Nov 13, 2014 at 7:20
Hi
Likely you just checked the title and replied. I have
pax-logback-service working -- in my latest post -- I was asking about
how the loggers we define in logback.xml appear in karaf console
as for me just the root logger shows up i.e. using
log:get ALL
command --- I don't see other
This should work, just to verity, can you create different appender and see
whether it works. May be you can write in different file.
Just to me sure, all configurations is proper and its picking up the
logback.xml file configurations.
Srikanth Hugar
www.gharki.com
On Thu, Nov 13, 2014 at
Seems the following is happenning:
Though I have specified the logback.xml usage in
etc/org.ops4j.pax.logging.cfg
by setting
org.ops4j.pax.logging.logback.config.file=path/logback.xml
what I see is that when I set a log level using karaf console
---
log:set DEBUG
--
an entry gets added to
The log:set command unfortunately assumes that the backend is
pax-logging-service.
This need to be enhanced to work with pax-logging-logback and
pax-logging-log4jv2.
Could you please raise a JIRA ?
2014-11-13 8:16 GMT+01:00 syedbahm syedb...@cisco.com:
Seems the following is happenning:
I have openned https://issues.apache.org/jira/browse/KARAF-3358 for the
same..
Please update it as appropriate -- as Im not sure which component this
should be put in -- I have assigned it to Karaf-core for now.
The reason I marked it as major is that without it working it would be
difficult
Hi
I changed it from Bug to new Feature. This is because the log4j backend is
still the prefered backend for Pax Logging and Karaf. Also due to the way
it's possible to use the properties to directly manipulate the config admin
properties.
So you have a new requirement. The Workaround would be go
16 matches
Mail list logo
