want to look for
Mikes-Awesome-Karaf-Build dev:show-tree
I'd like to say that you can also look for imports and exports in the Eclipse
debugger, but that would be a lie. So, the above stuff is what I normally use.
v/r,
Mike Van
- Original Message -
From: Andreas Gies [via
There are no such things as stupid questions. Just my opinion.
v/r,
Mike Van
- Original Message -
From: Kit Plummer [via Karaf] ml-node+1865644-84520632-228...@n3.nabble.com
To: Mike Van mvangeert...@comcast.net
Sent: Monday, November 8, 2010 5:07:36 PM
Subject: Re
Rosh,
Could you please let us know how you identified that as an issue? I'd like to
see if I can replicate this with Karaf 2.0 and 1.6.
v/r,
Mike Van
- Original Message -
From: Roshan A. Punnoose [via Karaf]
ml-node+1870475-1529360336-228...@n3.nabble.com
To: Mike Van
in Strings or
Ints. Kind of unnerving.
v/r,
Mike Van
--
View this message in context:
http://karaf.922171.n3.nabble.com/Accessing-database-connections-using-SpringDM-in-Karaf-tp1932916p1956889.html
Sent from the Karaf - User mailing list archive at Nabble.com.
class implement the InitializingBean,
changing the doPopulate() method to afterPropertiesSet(), and then
removing all static declarations.
Thanks to Joed from the IRC group for helping me figure this out.
v/r,
Mike Van
--
View this message in context:
http://karaf.922171.n3.nabble.com/Accessing
-
From: Łukasz Dywicki [via Karaf]
ml-node+2060078-1778899901-228...@n3.nabble.com
To: Mike Van mvangeert...@comcast.net
Sent: Thursday, December 9, 2010 3:58:32 PM
Subject: RE: Placing properties files in the classpath
It depends on the configuration admin. Karaf uses etc directory
-309240584-228...@n3.nabble.com
To: Mike Van mvangeert...@comcast.net
Sent: Thursday, December 9, 2010 4:06:15 PM
Subject: RE: Placing properties files in the classpath
No,
These bundles may reffer same persistent id (configuration file) without
problems.
In fact - you may introduce new bundle which
to allow the user to set the resultant package versions, or to override the
default behavior to use the ${pom.version} for each package instead of
0.0.0.
v/r,
Mike Van (karafman)
--
View this message in context:
http://karaf.922171.n3.nabble.com/maven-bundle-plugin-shading-version-issue
I have a database bean and I'm using ConfigAdmin to allow me to make changes
to an .cfg file, and have those properties set in karaf. This is working.
Woot!!!
I've noticed that individual bundles need to be restarted in order to use
these new properties. While karaf only takes six thousandths
