Thanks, however where should I keep this feature.xml file? In featuresBoot 
property I can give only name i.e. my-ldap-feature


feature.xml
=========
<feature name="my-ldap-feature" version="1.0.0" resolver="(obr)" 
start-level='50'>
              <bundle>blueprint:file:etc/my-ldap.xml</bundle>
   </feature>


Thanks,
Omkar

From: Freeman Fang [mailto:[email protected]]
Sent: Wednesday, October 16, 2013 3:28 PM
To: [email protected]
Subject: Re: Installing and Starting up bundle at startup

Hi,

You can define a customer feature which refer your LDAP blueprint configuration 
file and then add this feature in etc/org.apache.karaf.features.cfg  
featuresBoot property,
your customer feature would be like

  <feature name="my-ldap-feature" version="1.0.0" resolver="(obr)" 
start-level='50'>
              <bundle>blueprint:file:etc/my-ldap.xml</bundle>
    </feature>

-------------
Freeman(Yue) Fang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋



On 2013-10-16, at 下午5:49, 
<[email protected]<mailto:[email protected]>> 
<[email protected]<mailto:[email protected]>> wrote:


Hi,

I want to add my own bundle into karaf and make it up the moment karaf starts. 
It just contains xml to specify LDAP as realm to be used. Actually I want to 
configure karaf to use LDAP realm without putting blueprint xml into deploy 
folder. Is there any other way to do this?

Could someone please let me know how can I achieve this?

Thanks and Regards,
Omkar Chogale
This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking
action on the basis of information in this e-mail and must delete all
copies. Nomura will not accept responsibility or liability for the
accuracy or completeness of, or the presence of any virus or disabling
code in, this e-mail. If verification is sought please request a hard
copy. Any reference to the terms of executed transactions should be
treated as preliminary only and subject to formal written confirmation
by Nomura. Nomura reserves the right to monitor e-mail communications
through its networks (in accordance with applicable laws). No
confidentiality or privilege is waived or lost by Nomura by any
mistransmission of this e-mail. Any reference to "Nomura" is a
reference to any entity in the Nomura Holdings, Inc. group.
Please read our Electronic Communications Legal Notice which forms
part of this e-mail: http://www.Nomura.com/email_disclaimer.htm


This e-mail (including any attachments) is confidential, may contain
proprietary or privileged information and is intended for the named
recipient(s) only. Unintended recipients are prohibited from taking
action on the basis of information in this e-mail and must delete all
copies. Nomura will not accept responsibility or liability for the
accuracy or completeness of, or the presence of any virus or disabling
code in, this e-mail. If verification is sought please request a hard
copy. Any reference to the terms of executed transactions should be
treated as preliminary only and subject to formal written confirmation
by Nomura. Nomura reserves the right to monitor e-mail communications
through its networks (in accordance with applicable laws). No
confidentiality or privilege is waived or lost by Nomura by any
mistransmission of this e-mail. Any reference to "Nomura" is a
reference to any entity in the Nomura Holdings, Inc. group.
Please read our Electronic Communications Legal Notice which forms
part of this e-mail: http://www.Nomura.com/email_disclaimer.htm

Reply via email to