problem with features-maven-plugin and validate goal

2013-03-12 Thread Christian Müller
We want use the validate goal of the features-maven-plugin (version 2.3.0)
to validate our feature file. But we get the following exception, whereI do
not understand why:

...
[INFO]  - step 2: Checking if all imports for bundles can be resolved
[WARNING] Failed to validate feature xxx
[WARNING] No export found to match
org.apache.commons.logging;version=[1.1.1, 2.0.0) (imported by
mvn:org.springframework/spring-jdbc/3.0.7.RELEASE)
[WARNING] No export found to match javax.jws.soap (imported by
mvn:xxx.yyy.zzz.interfaces/exfts/1.0.0-SNAPSHOT)
[WARNING] No export found to match javax.jws (imported by
mvn:xxx.yyy.zzz.interfaces/exfts/1.0.0-SNAPSHOT)
[WARNING] No export found to match org.slf4j;version=[1.6,2) (imported by
mvn:xxx.yyy.zzz.services/sdol-gateway-dao/1.0.0-SNAPSHOT)
[WARNING] No export found to match javax.xml.ws (imported by
mvn:xxx.yyy.zzz.interfaces/exfts/1.0.0-SNAPSHOT)
[INFO]

[INFO] BUILD FAILURE
[INFO]



Because Karaf use pax-logging, it should be resolved by default, shouldn't
it? Do I have to add additional dependencies to my feature file? I don't
think so because it works for Apache Camel without to define the dependency
to pax logging...

My environment:
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\Program Files (x86)\apache-maven-3.0.4
Java version: 1.7.0_11, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_11\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: windows

My feature file (snippet):
feature name=xxx version=${project.version} resolver=(obr)
start-level=60
feature version=${org.apache.camel.version}camel-core/feature
feature
version=${org.apache.camel.version}camel-spring/feature


bundlemvn:org.apache.geronimo.specs/geronimo-j2ee-connector_1.5_spec/${org.apache.geronimo.specs.geronimo-j2ee-connector_1.5_spec.version}/bundle

bundlemvn:xxx.yyy.zzz.bundles/xxx.yyy.zzz.bundles.ojdbc6/${xxx.yyy.zzz.bundles.ojdbc6.version}/bundle

bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-dbcp/${org.apache.servicemix.bundles.org.apache.servicemix.bundles.commons-dbcp.version}/bundle

bundlemvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.bcprov-jdk16/${org.apache.servicemix.bundles.bcprov-jdk16.version}/bundle

bundlemvn:org.springframework/spring-jdbc/${org.springframework.version}/bundle

bundlemvn:commons-codec/commons-codec/${commons-codec.commons-codec.version}/bundle
bundlemvn:xxx.yyy.zzz.interfaces/exfts/${project.version}/bundle


bundlemvn:xxx.yyy.zzz.services/gateway-dao/${project.version}/bundle
/feature

My plugin config (snippet):
build
plugins
plugin
groupIdorg.apache.karaf.tooling/groupId
artifactIdfeatures-maven-plugin/artifactId
version2.3.0/version
configuration
file${project.build.directory}/classes/features.xml/file

karafConfig${project.build.directory}/classes/config.properties/karafConfig
jreVersionjre-1.7/jreVersion
/configuration
executions
execution
idvalidate/id
phaseprocess-resources/phase
goals
goalvalidate/goal
/goals
/execution
/executions
/plugin
/plugins
/build

My config.properties file:
org.osgi.framework.system.packages= \
 org.osgi.framework.startlevel;uses:=org.osgi.framework;version=1.0, \
 
org.osgi.framework.wiring;uses:=org.osgi.resource,org.osgi.framework;version=1.1,
\
 org.osgi.framework.hooks.bundle;uses:=org.osgi.framework;version=1.1, \
 org.osgi.framework.hooks.service;uses:=org.osgi.framework;version=1.1,
\
 
org.osgi.framework.hooks.resolver;uses:=org.osgi.framework.wiring;version=1.0,
\
 org.osgi.framework.launch;uses:=org.osgi.framework;version=1.1, \
 org.osgi.framework.namespace;uses:=org.osgi.resource;version=1.0, \
 org.osgi.framework;version=1.7,\
 
org.osgi.framework.hooks.weaving;uses:=org.osgi.framework.wiring;version=1.0,\
 org.osgi.resource;version=1.0,org.osgi.service.url;version=1.0,\
 org.osgi.service.startlevel;uses:=org.osgi.framework;version=1.1,\
 org.osgi.service.packageadmin;uses:=org.osgi.framework;version=1.2,\
 org.osgi.service.url;version=1.0, \
 org.osgi.util.tracker;uses:=org.osgi.framework;version=1.5.1, \
 org.apache.felix.framework.monitor;version=1.0, \
 org.apache.karaf.jaas.boot;version=2.3.0.fuse-71-047, \
 org.apache.karaf.jaas.boot.principal;version=2.3.0.fuse-71-047, \
 org.apache.karaf.version;version=2.3.0.fuse-71-047, \
 org.apache.xalan.extensions; version=2.7.1, \
 org.apache.xalan.xsltc.compiler; version=2.7.1, \
 org.apache.xalan.xsltc.cmdline.getopt; version=2.7.1, \
 org.apache.xalan.xsltc.util; 

Re: karaf features and maven urls

2013-02-03 Thread Christian Müller
The current schema [1] doesn't support it.

[1]
http://karaf.apache.org/manual/2.3.0/users-guide/provisioning-schema.html

Best,
Christian

On Sun, Feb 3, 2013 at 5:29 PM, lbu lburgazz...@gmail.com wrote:

 Hi,
 I would like to know if it possible to set a repository alongside a karaf
 feauture e.g:

 feature name=my-feautre-1 version=1.0.0
 repository=http://maven.mycompany.com;
 feature name=my-feautre-2 version=1.0.0
 repository=file:///opt/maven
 feature name=my-feautre-3 version=1.0.0
 repository=file://${env.HOME}/.m2/repository

 So we can avoid to search in the repository chain configured via config
 admin if we know where a bundle is and where it isn't





 --
 View this message in context:
 http://karaf.922171.n3.nabble.com/karaf-features-and-maven-urls-tp4027592.html
 Sent from the Karaf - User mailing list archive at Nabble.com.




--


Re: Using database locking mechanism for Failover

2012-11-20 Thread Christian Müller
Achim, do you have any pointer for me where this is implemented? I couldn't
figure it out.
Another PCI requirement for us is to use an encrypted connection to our
database. Oracle supports this by setting additional connection properties
[1]. This is (also) not supported yet. You are interested in this patch?

[1] http://docs.oracle.com/cd/B28359_01/network.111/b28530/asojbdc.htm

Best,
Christian

On Mon, Nov 19, 2012 at 3:57 PM, Achim Nierbeck bcanh...@googlemail.comwrote:

 Hi Christian,

 to my knowledge Karaf supports both, though for jasypt you probably need
 to use a 3.0.0-SNAPSHOT right now.
 Need to check if 2.3.x also supports jasypt.

 regards, Achim


 2012/11/19 Christian Müller christian.muel...@gmail.com

 Hello!

 We use the database locking mechanism in Karaf (2.2.2) to support
 Failover. We have to use the database locking machanism because we do not
 have a shared file system in place. We are also forced by PCI [1] to not
 use passwords in plain text. As I can see from the source code [2], Karaf
 doesn't support this right now (e.g. via Jasypt or so).

 I would like to open a JIRA for it, if I didn't overlooked something and
 Karaf already support this requirement. At present, we hve to work around
 this by subclassing the DefaultJDBCLock and extend it for our own needs.

 [1]
 http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard
 [2]
 https://svn.apache.org/repos/asf/karaf/trunk/main/src/main/java/org/apache/karaf/main/lock/DefaultJDBCLock.java

 Thanks in advance,
 Christian




 --

 Apache Karaf http://karaf.apache.org/ Committer  PMC
 OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer 
 Project Lead
 OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home
 Commiter  Project Lead
 blog http://notizblog.nierbeck.de/




--


Re: Thank you Karaf from marioteguh.tumblr.com :-)

2012-11-20 Thread Christian Müller
Thanks for sharing and enjoy your further Camel ride.

Best,
Christian

On Tue, Nov 20, 2012 at 11:25 AM, Hendy Irawan he...@soluvas.com wrote:

 Hi Karaf,

 I'd like to say thank you that Karaf (and Camel) :) has been rock solid on
 one of my project, syncing between Mario Teguh Facebook page and Tumblr at
 http://marioteguh.tumblr.com/ :

 It's been running Karaf 2.2.8 and Camel 2.10 for 3+ months without a hitch
 (yeah, no time to upgrade to 2.3.0. If it ain't broke, don't fix it
 hehe...). Very low RAM consumption too :-)

 Actually it's been running longer than that, but we had occasional server
 restarts due to package upgrades.

 karaf@root info
 Karaf
   Karaf version   2.2.8
   Karaf home  /home/ceefour/karaf
   Karaf base  /home/ceefour/karaf
   OSGi Framework  org.apache.felix.framework - 3.0.9

 JVM
   Java Virtual MachineJava HotSpot(TM) Server VM version 23.1-b03
   Version 1.7.0_05
   Vendor  Oracle Corporation
   Uptime  106 days 16 hours
   Total compile time  34.192 seconds
 Threads
   Live threads37
   Daemon threads  32
   Peak40
   Total started   34841
 Memory
   Current heap size   19,576 kbytes
   Maximum heap size   27,776 kbytes
   Committed heap size 27,776 kbytes
   Pending objects 0
   Garbage collector   Name = 'Copy', Collections = 2307917, Time =
 1
 hour 13 minutes
   Garbage collector   Name = 'MarkSweepCompact', Collections =
 2564,
 Time = 4 minutes
 Classes
   Current classes loaded  5,977
   Total classes loaded182,904
   Total classes unloaded  176,927
 Operating system
   NameLinux version 3.4.2-linode44
   Architecturei386
   Processors  4
 karaf@root

 The server uptime itself :

 $ uptime
  09:56:27 up 106 days, 18:02,  2 users,  load average: 1.06, 0.96, 0.80

 So Karaf itself has been running continuously from the last server restart
 to this day. :-)

 karaf@root list -s
 START LEVEL 100 , List Threshold: 50
ID   State Blueprint  Level  Symbolic name
 [  64] [Active ] [] [   50] org.apache.camel.camel-core
 (2.10.0)
 [  65] [Active ] [Created ] [   50]
 org.apache.camel.karaf.camel-karaf-commands (2.10.0)
 [  66] [Active ] [] [   50] javax.mail (1.4.5)
 [  67] [Active ] [] [   50]
 org.apache.ws.commons.axiom.axiom-impl (1.2.10)
 [  68] [Active ] [] [   50]
 org.apache.ws.commons.axiom.axiom-api (1.2.10)
 [  69] [Active ] [] [   50] org.apache.abdera.core (1.1.2)
 [  70] [Active ] [] [   50]
 org.apache.abdera.extensions-main (1.1.2)
 [  71] [Active ] [] [   50] org.apache.abdera.i18n (1.1.2)
 [  72] [Active ] [] [   50] org.apache.abdera.parser
 (1.1.2)
 [  73] [Active ] [] [   50] org.apache.commons.codec
 (1.6.0)
 [  74] [Active ] [] [   50] org.apache.camel.camel-atom
 (2.10.0)
 [  75] [Active ] [] [   50]
 org.apache.servicemix.bundles.jdom (1.1.0.4)
 [  76] [Active ] [] [   50]
 org.apache.servicemix.bundles.rome (1.0.0.3)
 [  77] [Active ] [] [   50] org.apache.camel.camel-rss
 (2.10.0)
 [  78] [Active ] [] [   50] org.apache.camel.camel-mail
 (2.10.0)
 [  79] [Active ] [] [   50]
 org.apache.servicemix.bundles.mvel (2.0.18.3)
 [  80] [Active ] [] [   50] org.apache.camel.camel-mvel
 (2.10.0)
 [  81] [Active ] [] [   80] org.codehaus.jettison.jettison
 (1.3.1)
 [  87] [Active ] [] [   80] org.apache.commons.io (2.4.0)
 [  88] [Active ] [Created ] [   80]
 marioteguh-to-tumblr_v3.blueprint.xml (0.0.0)
 [  89] [Active ] [Created ] [   50]
 org.apache.camel.camel-blueprint
 (2.10.0)
 [  90] [Active ] [] [   80] com.daneshzaki.tumblej
 (2.0.0.SNAPSHOT)
 [  91] [Active ] [] [   80]
 org.soluvas.social.tumblej-camel
 (1.0.0.SNAPSHOT)
 [  93] [Active ] [] [   80] jackson-core-asl (1.9.8)
 [  94] [Active ] [] [   80] jackson-jaxrs (1.9.8)
 [  95] [Active ] [] [   80] jackson-mapper-asl (1.9.8)
 [ 127] [Active ] [] [   80]
 com.sun.jersey.contribs.jersey-oauth.oauth-client (1.13.0)
 [ 128] [Active ] [] [   80] com.sun.jersey.core (1.13.0)
 [ 129] [Active ] [] [   80] com.sun.jersey.json (1.13.0)
 [ 130] [Active ] [] [   80] com.sun.jersey.client (1.13.0)
 [ 131] [Active ] [] [   80]
 com.sun.jersey.contribs.jersey-oauth.oauth-signature (1.13.0)

 Unfortunately, it's time to do yet another server restart due to package
 and
 kernel upgrades. So before I reset the counter 

Using database locking mechanism for Failover

2012-11-19 Thread Christian Müller
Hello!

We use the database locking mechanism in Karaf (2.2.2) to support Failover.
We have to use the database locking machanism because we do not have a
shared file system in place. We are also forced by PCI [1] to not use
passwords in plain text. As I can see from the source code [2], Karaf
doesn't support this right now (e.g. via Jasypt or so).

I would like to open a JIRA for it, if I didn't overlooked something and
Karaf already support this requirement. At present, we hve to work around
this by subclassing the DefaultJDBCLock and extend it for our own needs.

[1]
http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard
[2]
https://svn.apache.org/repos/asf/karaf/trunk/main/src/main/java/org/apache/karaf/main/lock/DefaultJDBCLock.java

Thanks in advance,
Christian


Re: deploying a database source as service in Karaf 2.2.5

2012-03-11 Thread Christian Müller
Run: osgi:install
mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-dbcp/1.4_1

Best,
Christian

On Sun, Mar 11, 2012 at 4:15 AM, James Gartner james.gart...@moodys.comwrote:

 Thanks David, according to what I found on SyBooks Online:
 Connection libraries and XA resource libraries for Windows (CR #399593)
 The
 XA resource library for JDBC database driver should be
 com.sybase.jdbc3.jdbc.SybXADataSource.
 and
 The value for the Driver property (DLL or Class Name) to configure the
 connection cache should be com.sybase.jdbc3.jdbc.SybXADataSource.
 
 so I was presuming that it would implement this.
 Also, I tried the non-XA class com.sybase.jdbc3.jdbc.SybDriver which
 gives
 the same results.

 Looks like I may have found part of the fix:

 bean id=xaDataSource destroy-method=close
 class=org.apache.commons.dbcp.BasicDataSource
property name=driverClassName
 value=com.sybase.jdbc3.jdbc.SybXADataSource/
property name=url  value=jdbc:sybase:Tds:machine:port/dbname/
 property name=user value=/
property name=password value=/
property name=defaultTransactionIsolation value=2/
/bean

 Now I'm getting that:
 ERROR: Bundle datasource-sybase.xml [84] Error starting

 blueprint:file:/C:/JavaApps/apache-karaf-2.2.5/apache-karaf-2.2.5/deploy/dat
 asource-sybase.xml (org.osgi.framework.BundleException: Unresolved
 constraint in bundle datasource-sybase.xml [84]: Unable to resolv
 e 84.3: missing requirement [84.3] package;
 (package=org.apache.commons.dbcp))
 org.osgi.framework.BundleException: Unresolved constraint in bundle
 datasource-sybase.xml [84]: Unable to resolve 84.3: missing requ
 irement [84.3] package; (package=org.apache.commons.dbcp)

 I tried to do the:
 karaf@root osgi:install
 mvn:org.apache.servicemix.bundles.commons-dbcp/1.4_1
 ^C
 java.lang.RuntimeException: URL
 [mvn:org.apache.servicemix.bundles.commons-dbcp/1.4_1] could not be
 resolved.
 so it looks like something is up with my maven settings, but at least I got
 past the original error.
 If anyone has any ideas as to why I can't resolve the url here, I'd
 appreciate it (I haven't worked much with maven, so still trying to get
 everything setup correctly -- I may just install the jar/pom manually in my
 m2 repository).

 --
 View this message in context:
 http://karaf.922171.n3.nabble.com/deploying-a-database-source-as-service-in-Karaf-2-2-5-tp3814097p3816086.html
 Sent from the Karaf - User mailing list archive at Nabble.com.



feature:uninstall console command

2012-03-04 Thread Christian Müller
The documentation of feature:uninstall console command says: Uninstalls a
feature with the specified name and version.

I tried the following:
On a fresh Apache Karaf 2.2.5 instance I added the Apache Camel features
file and checked, that no bundle unless the system bundles are installed

christian-muellers-macbook-pro:bin cmueller$ ./karaf
__ __  
   / //_/ __ _/ __/
  / ,  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/

  Apache Karaf (2.2.5)

Hit 'tab' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.

karaf@root feature:add-url
mvn:org.apache.camel.karaf/apache-camel/2.9.0/xml/features
karaf@root list
START LEVEL 100 , List Threshold: 50
   ID   State Blueprint  Level  Name


Than I installed the camel-cxf feature and checked that each bundle could
be installed successfully:

karaf@root feature:install camel-cxf
karaf@root list
START LEVEL 100 , List Threshold: 50
   ID   State Blueprint  SpringLevel  Name
[  69] [Active ] [] [   ] [   50] camel-core (2.9.0)
[  70] [Active ] [Created ] [   ] [   50] camel-karaf-commands
(2.9.0)
[  71] [Active ] [] [   ] [   50] geronimo-jta_1.1_spec
(1.1.1)
[  72] [Active ] [] [   ] [   50] camel-spring (2.9.0)
[ 100] [Active ] [] [   ] [   60] OPS4J Pax Web -
Extender - WAR (1.0.7)
[ 101] [Active ] [] [   ] [   60] OPS4J Pax Web -
Extender - Whiteboard (1.0.7)
[ 102] [Active ] [] [   ] [   60] OPS4J Pax Web -
FileInstall Deployer (1.0.7)
[ 103] [Active ] [] [   ] [   60] OPS4J Pax Url - war
(1.2.8)
[ 108] [Active ] [] [   ] [   60] Joda-Time (1.6.2)
[ 109] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: opensaml (2.5.1.1)
[ 110] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: xmlsec (1.4.5.1)
[ 111] [Active ] [] [   ] [   60] WSS4J (1.6.4)
[ 112] [Active ] [] [   ] [   60] Commons Codec (1.4)
[ 113] [Active ] [] [   ] [   60] Axiom Impl (1.2.10)
[ 114] [Active ] [] [   ] [   60] Axiom API (1.2.10)
[ 115] [Active ] [] [   ] [   60] Abdera Core (1.1.2)
[ 116] [Active ] [] [   ] [   60] Abdera Extensions -
Main (1.1.2)
[ 117] [Active ] [] [   ] [   60] I18N Libraries (1.1.2)
[ 118] [Active ] [] [   ] [   60] Abdera Parser (1.1.2)
[ 120] [Active ] [] [   ] [   60] Commons Lang (2.6)
[ 121] [Active ] [] [   ] [   60] Commons Collections
(3.2.1)
[ 123] [Active ] [] [   ] [   60] Apache Neethi (3.0.1)
[ 124] [Active ] [] [   ] [   60] XmlSchema Core (2.0.1)
[ 125] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: wsdl4j (1.6.2.3)
[ 126] [Active ] [] [   ] [   60] jettison (1.3)
[ 127] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: xmlbeans (2.5.0.2)
[ 128] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: js (1.0.0.7R2_1)
[ 129] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: xmlresolver (1.2.0.3)
[ 130] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: xercesImpl (2.9.1.4)
[ 131] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: bcel (5.2.0.3)
[ 132] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: xalan (2.7.1.3)
[ 133] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: oro (2.0.8.4)
[ 134] [Active ] [] [   ] [   60] Apache Velocity (1.7)
[ 135] [Active ] [] [   ] [   60] Apache ServiceMix ::
Bundles :: jdom (1.1.0.3)
[ 136] [Active ] [Created ] [   ] [   60] Apache CXF Bundle Jar
(2.5.1)
[ 137] [Active ] [Created ] [   ] [   60] Apache CXF Karaf
Commands (2.5.1)
[ 138] [Active ] [] [   ] [   50] camel-cxf-transport
(2.9.0)
[ 139] [Active ] [Created ] [   ] [   50] camel-cxf (2.9.0)


Afterwards I uninstalled this feature and checked that all bundles are also
uninstalled:

karaf@root feature:uninstall camel-cxf
karaf@root list
START LEVEL 100 , List Threshold: 50
   ID   State Blueprint  SpringLevel  Name
[  69] [Active ] [] [   ] [   50] camel-core (2.9.0)
[  70] [Active ] [Created ] [   ] [   50] camel-karaf-commands
(2.9.0)
[  71] [Active ] [] [   ] [   50] geronimo-jta_1.1_spec
(1.1.1)
[  72] [Active ] [] [   ] [   50] camel-spring (2.9.0)
[ 100] [Active ] [

Re: feature:uninstall console command

2012-03-04 Thread Christian Müller
Thanks JB for the clarification.

Best,
Christian

Sent from a mobile device
Am 04.03.2012 17:55 schrieb Jean-Baptiste Onofré j...@nanthrax.net:

 Hi Christian,

 feature:uninstall uninstalls only the feature itself, not the feature
 dependencies.

 It means that your camel-cxf feature is really uninstall, but not the CXF
 feature (in dependency of camel-cxf), as this feature could be installed by
 others features or bundles.

 We plan to add a -r (recursive) to uninstall the feature and all depency
 features.

 Regards
 JB

 On 03/04/2012 12:12 PM, Christian Müller wrote:

 The documentation of feature:uninstall console command says: Uninstalls
 a feature with the specified name and version.

 I tried the following:
 On a fresh Apache Karaf 2.2.5 instance I added the Apache Camel features
 file and checked, that no bundle unless the system bundles are installed

 christian-muellers-macbook-**pro:bin cmueller$ ./karaf
 __ __  
/ //_/ __ _/ __/
   / ,  / __ `/ ___/ __ `/ /_
  / /| |/ /_/ / /  / /_/ / __/
 /_/ |_|\__,_/_/   \__,_/_/

   Apache Karaf (2.2.5)

 Hit 'tab' for a list of available commands
 and '[cmd] --help' for help on a specific command.
 Hit 'ctrl-d' or 'osgi:shutdown' to shutdown Karaf.

 karaf@root feature:add-url
 mvn:org.apache.camel.karaf/**apache-camel/2.9.0/xml/**features
 karaf@root list
 START LEVEL 100 , List Threshold: 50
ID   State Blueprint  Level  Name


 Than I installed the camel-cxf feature and checked that each bundle
 could be installed successfully:

 karaf@root feature:install camel-cxf
 karaf@root list
 START LEVEL 100 , List Threshold: 50
ID   State Blueprint  SpringLevel  Name
 [  69] [Active ] [] [   ] [   50] camel-core (2.9.0)
 [  70] [Active ] [Created ] [   ] [   50]
 camel-karaf-commands (2.9.0)
 [  71] [Active ] [] [   ] [   50]
 geronimo-jta_1.1_spec (1.1.1)
 [  72] [Active ] [] [   ] [   50] camel-spring (2.9.0)
 [ 100] [Active ] [] [   ] [   60] OPS4J Pax Web -
 Extender - WAR (1.0.7)
 [ 101] [Active ] [] [   ] [   60] OPS4J Pax Web -
 Extender - Whiteboard (1.0.7)
 [ 102] [Active ] [] [   ] [   60] OPS4J Pax Web -
 FileInstall Deployer (1.0.7)
 [ 103] [Active ] [] [   ] [   60] OPS4J Pax Url -
 war (1.2.8)
 [ 108] [Active ] [] [   ] [   60] Joda-Time (1.6.2)
 [ 109] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: opensaml (2.5.1.1)
 [ 110] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: xmlsec (1.4.5.1)
 [ 111] [Active ] [] [   ] [   60] WSS4J (1.6.4)
 [ 112] [Active ] [] [   ] [   60] Commons Codec (1.4)
 [ 113] [Active ] [] [   ] [   60] Axiom Impl (1.2.10)
 [ 114] [Active ] [] [   ] [   60] Axiom API (1.2.10)
 [ 115] [Active ] [] [   ] [   60] Abdera Core (1.1.2)
 [ 116] [Active ] [] [   ] [   60] Abdera Extensions
 - Main (1.1.2)
 [ 117] [Active ] [] [   ] [   60] I18N Libraries
 (1.1.2)
 [ 118] [Active ] [] [   ] [   60] Abdera Parser
 (1.1.2)
 [ 120] [Active ] [] [   ] [   60] Commons Lang (2.6)
 [ 121] [Active ] [] [   ] [   60] Commons
 Collections (3.2.1)
 [ 123] [Active ] [] [   ] [   60] Apache Neethi
 (3.0.1)
 [ 124] [Active ] [] [   ] [   60] XmlSchema Core
 (2.0.1)
 [ 125] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: wsdl4j (1.6.2.3)
 [ 126] [Active ] [] [   ] [   60] jettison (1.3)
 [ 127] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: xmlbeans (2.5.0.2)
 [ 128] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: js (1.0.0.7R2_1)
 [ 129] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: xmlresolver (1.2.0.3)
 [ 130] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: xercesImpl (2.9.1.4)
 [ 131] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: bcel (5.2.0.3)
 [ 132] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: xalan (2.7.1.3)
 [ 133] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: oro (2.0.8.4)
 [ 134] [Active ] [] [   ] [   60] Apache Velocity
 (1.7)
 [ 135] [Active ] [] [   ] [   60] Apache ServiceMix
 :: Bundles :: jdom (1.1.0.3)
 [ 136] [Active ] [Created ] [   ] [   60] Apache CXF Bundle
 Jar (2.5.1)
 [ 137] [Active ] [Created ] [   ] [   60] Apache CXF Karaf
 Commands (2.5.1)
 [ 138] [Active ] [] [   ] [   50]
 camel-cxf

Re: Changing the location of the /etc/users.properties file

2012-01-08 Thread Christian Müller
Thanks for your reply JB and sorry for responding so late. Busy weeks - all
my colleges enjoy the holidays...

I looked into the Karaf documentation but I didn't found the solution I was
looking for. My wish is to edit org.apache.karaf.jaas.cfg and set the
property users to e.g. /Users/admin/karaf/users.properties. But this is
not possible as long this property is hard coded to
$[karaf.base]/etc/users.properties. May there is a good reason for this
hard coded value you can share with me?

However, I understood I have to deploy a blueprint configuration like as
the one below:
blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;
  xmlns:jaas=http://karaf.apache.org/xmlns/jaas/v1.1.0;
  xmlns:ext=http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0;

  ext:property-placeholder placeholder-prefix=$[ placeholder-suffix=]/

  jaas:config name=karaf rank=100
jaas:module
className=org.apache.karaf.jaas.modules.properties.PropertiesLoginModule
flags=required
  users = $[karaf.base]/etc/users.properties
  ...
/jaas:module
  /jaas:config
/blueprint

In SMX 4.2.0 (Felix Karaf 1.4.0) I found a similar solution (only a
different namespace).

Thanks for your help,
Christian

On Thu, Dec 1, 2011 at 6:21 PM, Jean-Baptiste Onofré j...@nanthrax.netwrote:

 Hi Christian,

 yes, you can change the users.properties location.

 It's in the JAAS PropertiesLoginModule configuration.

 We package one by default:

 http://svn.apache.org/repos/**asf/karaf/branches/karaf-2.2.**
 x/jaas/modules/src/main/**resources/OSGI-INF/blueprint/**
 karaf-jaas-module.xmlhttp://svn.apache.org/repos/asf/karaf/branches/karaf-2.2.x/jaas/modules/src/main/resources/OSGI-INF/blueprint/karaf-jaas-module.xml

 You have documentation about the Security Framework:

 http://karaf.apache.org/**manual/latest-2.2.x/**developers-guide/security-
 **framework.htmlhttp://karaf.apache.org/manual/latest-2.2.x/developers-guide/security-framework.html

 explaining how to override the property.

 Regards
 JB


 On 12/01/2011 06:13 PM, Christian Müller wrote:

 Hello list!

 We are using the FuseSource versions of SMX 4.2.0 (Felix Karaf 1.4.0)
 and 4.3.1 (Karaf 2.1.4).
 Is it possible to change the location/name of the
 ${KARAF_ROOT}/etc/users.**properties file? Where I have to configure
 this?

 I found the thread [1] which looks for me this feature was introduced in
 Karaf 2.2.0. Is this right?

 [1]
 http://karaf.922171.n3.nabble.**com/Keep-clean-repo-and-JAAS-**
 configuration-for-the-end-**users-td2382766.htmlhttp://karaf.922171.n3.nabble.com/Keep-clean-repo-and-JAAS-configuration-for-the-end-users-td2382766.html

 Best,
 Christian


 --
 Jean-Baptiste Onofré
 jbono...@apache.org
 http://blog.nanthrax.net
 Talend - http://www.talend.com



Re: Camel Active MQ Queue Stopping polling - Make it eent driven

2011-10-13 Thread Christian Müller
The reason is, because you use the bean component in a from definition.
You can put your two routes together into one.

Christian

Sent from a mobile device
Am 13.10.2011 21:37 schrieb Matt Madhavan mattmadha...@gmail.com:

 Hello,
 Please bear with me as I'm new to Camel.

 I have a my camel snippet as follows:
camelContext xmlns=http://camel.apache.org/schema/blueprint;
route id=in-bound autoStartup=true
descriptionCamel In-Bound Route/description
from uri=activemq:example.A/
to uri=bean:processMsgService?method=processmsg/
/route
route id=out-bound autoStartup=true
descriptionCamel Out-Bound Route/description
from
 uri=bean:processMsgService?method=processmsg/
to uri=activemq:example.B/
/route
/camelContext


 Event when I do not send any message the bean/method
 *uri=bean:processMsgService?method=processmsg* gets invoked periodically.

 how do I stop this? Looks like activemq:example.A keeps producing null msgs
 or the method above always called.

 Any help will be appreciated

 Thanks in advance!

 Matt

 --
 View this message in context:
 http://karaf.922171.n3.nabble.com/Camel-Active-MQ-Queue-Stopping-polling-Make-it-eent-driven-tp3419564p3419564.html
 Sent from the Karaf - User mailing list archive at Nabble.com.



Re: Open Ports in Karaf

2010-11-09 Thread Christian Müller
Hello Roshan,

looks like an issue we figured out some weeks ago. I discussed this in [1]
and opened an issue for it [2]. It's fixed in 2.2.0 and it's easy to fix it
in previous versions...
Hope this helps.

[1]
http://servicemix.396122.n5.nabble.com/DISCUSS-changing-the-default-JMX-service-uri-td3229446.html#a3229446
[2] https://issues.apache.org/jira/browse/KARAF-253

Cheers,
Christian