You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by lbu <lb...@gmail.com> on 2015/04/20 16:32:46 UTC

Karav 3.0.3 vs 2.4.1 : file install behavior

Hi,

I've noticed that in Karaf 3.0.3 if I add an additional folder to the list
of the folders to watch for configurations, Karaf creates a bundle withe the
name of the folder once a configuration file (even empty) is created in the
new folder.

The File Install configuration (config.properties) is

felix.fileinstall.enableConfigSave = true
felix.fileinstall.dir = ${karaf.etc}, ${karaf.etc}/myfolder
felix.fileinstall.filter = .*\\.cfg
felix.fileinstall.poll = 1000
felix.fileinstall.noInitialDelay = true
felix.fileinstall.log.level = 3



Bundle's header is:
           
myfolder (64)
-------------
Created-By = 1.8.0_45 (Oracle Corporation)
Manifest-Version = 1.0
Bnd-LastModified = 1429539709907
Generated-By-Ops4j-Pax-From =
wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder$Bundle-SymbolicName=myfolder&Bundle-Version=0.0.0
Tool = Bnd-2.3.0.201405100607

Bundle-ManifestVersion = 2
Bundle-SymbolicName = myfolder
Bundle-Version = 0.0.0
Bundle-Name = myfolder

Export-Package = 
	test.cfg



This does not happen in Karaf 2.4.1, is that expected ?


Regards,
Luca

                                         




--
View this message in context: http://karaf.922171.n3.nabble.com/Karav-3-0-3-vs-2-4-1-file-install-behavior-tp4039815.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Karav 3.0.3 vs 2.4.1 : file install behavior

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Oh you meant 3.0.x, I understood 4.0.x. Sorry about that.

Let me take a look.

Regards
JB

On 04/21/2015 08:40 AM, lbu wrote:
> Looking at bundles' headers I see the same version on 3.0.3 and 2.4.1 :
>
> - Karaf 2.4.1:
>
> Bundle-SymbolicName = org.apache.felix.fileinstall
> Bundle-Version = 3.4.2
> Bundle-Name = Apache Felix File Install
>
> Bundle-SymbolicName = org.apache.felix.configadmin
> Bundle-Version = 1.8.0
> Bundle-Name = Apache Felix Configuration Admin Service
>
> - Karaf 3.0.3:
>
> Bundle-SymbolicName = org.apache.felix.fileinstall
> Bundle-Version = 3.4.2
> Bundle-Name = Apache Felix File Install
>
> Bundle-SymbolicName = org.apache.felix.configadmin
> Bundle-Version = 1.8.0
> Bundle-Name = Apache Felix Configuration Admin Service
>
>
> Looks like sub-folders of ${karaf.base}/etc are processed by Blueprint which
> tries to find blueprint applications but see it as a bundle even if it does
> not contains any blueprint data:
>
>   2015-04-21 08:31:11,495 | DEBUG | l for user karaf | BlueprintContainerImpl
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Instantiating component
> shell-516
> 2015-04-21 08:31:35,589 | DEBUG | f-3.0.3-test/etc | BndUtils
> | 2 - org.ops4j.pax.url.wrap - 2.3.0 | Creating bundle for
> [wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder3$Bundle-SymbolicName=myfolder3&Bundle-Version=0.0.0]
> 2015-04-21 08:31:35,590 | DEBUG | f-3.0.3-test/etc | BndUtils
> | 2 - org.ops4j.pax.url.wrap - 2.3.0 | Overwrite mode: KEEP
> 2015-04-21 08:31:35,630 | INFO  | f-3.0.3-test/etc | fileinstall
> | 7 - org.apache.felix.fileinstall - 3.4.2 | Installing bundle myfolder3 /
> 0.0.0
> 2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
> destruction process for bundle myfolder3
> 2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for myfolder3.
> 2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | myfolder3
> | 66 - myfolder3 - 0.0.0 | BundleEvent INSTALLED - myfolder3
> 2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
> destruction process for bundle myfolder3
> 2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for myfolder3.
> 2015-04-21 08:31:35,640 | DEBUG | lixDispatchQueue | framework
> | 0 - org.apache.felix.framework - 4.2.1 | FrameworkEvent PACKAGES REFRESHED
> - org.apache.felix.framework
> 2015-04-21 08:31:35,643 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
> destruction process for bundle myfolder3
> 2015-04-21 08:31:35,644 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for myfolder3.
> 2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | myfolder3
> | 66 - myfolder3 - 0.0.0 | BundleEvent RESOLVED - myfolder3
> 2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
> destruction process for bundle myfolder3
> 2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
> destruction of BlueprintContainer already finished for myfolder3.
> 2015-04-21 08:31:35,646 | DEBUG | f-3.0.3-test/etc | myfolder3
> | 66 - myfolder3 - 0.0.0 | BundleEvent STARTING - myfolder3
> 2015-04-21 08:31:35,646 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | Scanning bundle myfolder3
> for blueprint application
> 2015-04-21 08:31:35,647 | DEBUG | f-3.0.3-test/etc | BlueprintExtender
> | 15 - org.apache.aries.blueprint.core - 1.4.2 | No blueprint application
> found in bundle myfolder3
> 2015-04-21 08:31:35,647 | DEBUG | f-3.0.3-test/etc | myfolder3
> | 66 - myfolder3 - 0.0.0 | BundleEvent STARTED - myfolder3
> 2015-04-21 08:31:35,647 | INFO  | f-3.0.3-test/etc | fileinstall
> | 7 - org.apache.felix.fileinstall - 3.4.2 | Started bundle:
> wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder3$Bundle-SymbolicName=myfolder3&Bundle-Version=0.0.0
>
>
>
>
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Karav-3-0-3-vs-2-4-1-file-install-behavior-tp4039815p4039821.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

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

Re: Karav 3.0.3 vs 2.4.1 : file install behavior

Posted by lbu <lb...@gmail.com>.
Looking at bundles' headers I see the same version on 3.0.3 and 2.4.1 :

- Karaf 2.4.1:

Bundle-SymbolicName = org.apache.felix.fileinstall
Bundle-Version = 3.4.2
Bundle-Name = Apache Felix File Install

Bundle-SymbolicName = org.apache.felix.configadmin
Bundle-Version = 1.8.0
Bundle-Name = Apache Felix Configuration Admin Service

- Karaf 3.0.3:

Bundle-SymbolicName = org.apache.felix.fileinstall
Bundle-Version = 3.4.2
Bundle-Name = Apache Felix File Install

Bundle-SymbolicName = org.apache.felix.configadmin
Bundle-Version = 1.8.0
Bundle-Name = Apache Felix Configuration Admin Service


Looks like sub-folders of ${karaf.base}/etc are processed by Blueprint which
tries to find blueprint applications but see it as a bundle even if it does
not contains any blueprint data:

 2015-04-21 08:31:11,495 | DEBUG | l for user karaf | BlueprintContainerImpl          
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Instantiating component
shell-516
2015-04-21 08:31:35,589 | DEBUG | f-3.0.3-test/etc | BndUtils                        
| 2 - org.ops4j.pax.url.wrap - 2.3.0 | Creating bundle for
[wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder3$Bundle-SymbolicName=myfolder3&Bundle-Version=0.0.0]
2015-04-21 08:31:35,590 | DEBUG | f-3.0.3-test/etc | BndUtils                        
| 2 - org.ops4j.pax.url.wrap - 2.3.0 | Overwrite mode: KEEP
2015-04-21 08:31:35,630 | INFO  | f-3.0.3-test/etc | fileinstall                     
| 7 - org.apache.felix.fileinstall - 3.4.2 | Installing bundle myfolder3 /
0.0.0
2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
destruction process for bundle myfolder3
2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for myfolder3.
2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | myfolder3                       
| 66 - myfolder3 - 0.0.0 | BundleEvent INSTALLED - myfolder3
2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
destruction process for bundle myfolder3
2015-04-21 08:31:35,631 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for myfolder3.
2015-04-21 08:31:35,640 | DEBUG | lixDispatchQueue | framework                       
| 0 - org.apache.felix.framework - 4.2.1 | FrameworkEvent PACKAGES REFRESHED
- org.apache.felix.framework
2015-04-21 08:31:35,643 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
destruction process for bundle myfolder3
2015-04-21 08:31:35,644 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for myfolder3.
2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | myfolder3                       
| 66 - myfolder3 - 0.0.0 | BundleEvent RESOLVED - myfolder3
2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Starting BlueprintContainer
destruction process for bundle myfolder3
2015-04-21 08:31:35,645 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Not a blueprint bundle or
destruction of BlueprintContainer already finished for myfolder3.
2015-04-21 08:31:35,646 | DEBUG | f-3.0.3-test/etc | myfolder3                       
| 66 - myfolder3 - 0.0.0 | BundleEvent STARTING - myfolder3
2015-04-21 08:31:35,646 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | Scanning bundle myfolder3
for blueprint application
2015-04-21 08:31:35,647 | DEBUG | f-3.0.3-test/etc | BlueprintExtender               
| 15 - org.apache.aries.blueprint.core - 1.4.2 | No blueprint application
found in bundle myfolder3
2015-04-21 08:31:35,647 | DEBUG | f-3.0.3-test/etc | myfolder3                       
| 66 - myfolder3 - 0.0.0 | BundleEvent STARTED - myfolder3
2015-04-21 08:31:35,647 | INFO  | f-3.0.3-test/etc | fileinstall                     
| 7 - org.apache.felix.fileinstall - 3.4.2 | Started bundle:
wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder3$Bundle-SymbolicName=myfolder3&Bundle-Version=0.0.0







--
View this message in context: http://karaf.922171.n3.nabble.com/Karav-3-0-3-vs-2-4-1-file-install-behavior-tp4039815p4039821.html
Sent from the Karaf - User mailing list archive at Nabble.com.

Re: Karav 3.0.3 vs 2.4.1 : file install behavior

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,

we used different Felix FileInstall/ConfigAdmin version between 3.0.x 
and 2.4.x.
I will update 2.4.2 with aligned versions.

Regards
JB

On 04/20/2015 04:32 PM, lbu wrote:
> Hi,
>
> I've noticed that in Karaf 3.0.3 if I add an additional folder to the list
> of the folders to watch for configurations, Karaf creates a bundle withe the
> name of the folder once a configuration file (even empty) is created in the
> new folder.
>
> The File Install configuration (config.properties) is
>
> felix.fileinstall.enableConfigSave = true
> felix.fileinstall.dir = ${karaf.etc}, ${karaf.etc}/myfolder
> felix.fileinstall.filter = .*\\.cfg
> felix.fileinstall.poll = 1000
> felix.fileinstall.noInitialDelay = true
> felix.fileinstall.log.level = 3
>
>
>
> Bundle's header is:
>
> myfolder (64)
> -------------
> Created-By = 1.8.0_45 (Oracle Corporation)
> Manifest-Version = 1.0
> Bnd-LastModified = 1429539709907
> Generated-By-Ops4j-Pax-From =
> wrap:jardir:/opt/sfw/containers/apache-karaf-3.0.3-test/etc/myfolder$Bundle-SymbolicName=myfolder&Bundle-Version=0.0.0
> Tool = Bnd-2.3.0.201405100607
>
> Bundle-ManifestVersion = 2
> Bundle-SymbolicName = myfolder
> Bundle-Version = 0.0.0
> Bundle-Name = myfolder
>
> Export-Package =
> 	test.cfg
>
>
>
> This does not happen in Karaf 2.4.1, is that expected ?
>
>
> Regards,
> Luca
>
>
>
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/Karav-3-0-3-vs-2-4-1-file-install-behavior-tp4039815.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

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