Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 367742

Summary:	[nano] org.eclipse.virgo.kernel.userregion configuration included in nano
Product:	[RT] Virgo	Reporter:	Glyn Normington <glyn.normington>
Component:	runtime	Assignee:	Borislav Kapukaranov <b.kapukaranov>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	b.kapukaranov
Version:	unspecified
Target Milestone:	3.5.0.M02
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Glyn Normington

2012-01-03 06:23:53 EST

This seems inappropriate since nano does not include a user region.

Comment 1 Glyn Normington

2012-01-03 06:24:30 EST

This can be observed by using jconsole and looking under MBeans->org.eclipse.virgo.kernel->Configuration

Comment 2 Borislav Kapukaranov

2012-01-03 07:44:20 EST

Note that the properties file itself is NOT included in /config so there must be someone that creates this configuration programatically.

Comment 3 Glyn Normington

2012-01-03 08:58:43 EST

(In reply to comment #2)
> Note that the properties file itself is NOT included in /config so there must
> be someone that creates this configuration programatically.

Agreed. CommandLinePropertiesSource seems to be the source as the single property appears in jconsole: commandLineArtifacts which appears to have an empty string value.

Comment 4 Borislav Kapukaranov

2012-01-06 04:55:57 EST

(In reply to comment #3)
> Agreed. CommandLinePropertiesSource seems to be the source as the single
> property appears in jconsole: commandLineArtifacts which appears to have an
> empty string value.

Do you have any idea why CommandLinePropertiesSource binds this configuration with one empty-valued property? Can this behavior be removed?

Comment 5 Glyn Normington

2012-01-06 05:05:23 EST

(In reply to comment #4)
> (In reply to comment #3)
> > Agreed. CommandLinePropertiesSource seems to be the source as the single
> > property appears in jconsole: commandLineArtifacts which appears to have an
> > empty string value.
> 
> Do you have any idea why CommandLinePropertiesSource binds this configuration
> with one empty-valued property? Can this behavior be removed?

No, sorry. I hope this behaviour can be removed without much impact.

Comment 6 Borislav Kapukaranov

2012-01-06 11:26:53 EST

It seems this default value can be safely removed, I tested that on a VK instance. 
I guess it was put there precautionary to avoid any chance of NPEs in case the StringUtils that are handling this value won't cope with null string values. Apparently this is not the case.

Fixed in commit 3515ad8 of the Nano repository.