Hey all,
It seems that scr:info report is not clearly indicating when a required
configuration is not available. It is showing good info when the component
has a configuration:
Here is the report WITH required configuration:
----------------------------------
g! scr:info com.liferay.portal.http.tunnel.extender.HttpTunnelExtender
*** Bundle: com.liferay.portal.http.tunnel.extender (60)
Component Description:
Name: com.liferay.portal.http.tunnel.extender.HttpTunnelExtender
Default State: enabled
Activation: immediate
Configuration Policy: require
Activate Method: activate
Deactivate Method: deactivate
Modified Method: modified
Configuration Pid:
[com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfiguration]
Services: Service Scope: null
Properties:
Component Configuration:
ComponentId: 1936
State: active
Properties:
component.id = 1936
component.name =
com.liferay.portal.http.tunnel.extender.HttpTunnelExtender
hostsAllowed = [127.0.0.1]
service.pid =
com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfiguration
g!
----------------------------------
And here is the report when NO required configuration is available:
----------------------------------
g! scr:info com.liferay.portal.http.tunnel.extender.HttpTunnelExtender
*** Bundle: com.liferay.portal.http.tunnel.extender (60)
Component Description:
Name: com.liferay.portal.http.tunnel.extender.HttpTunnelExtender
Default State: enabled
Activation: immediate
Configuration Policy: require
Activate Method: activate
Deactivate Method: deactivate
Modified Method: modified
Configuration Pid:
[com.liferay.portal.http.tunnel.configuration.HttpTunnelExtenderConfiguration]
Services: Service Scope: null
Properties:
g!
----------------------------------
As you can see it's not clear at all that the component is missing the
configuration it requires.
Can we fix this?
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
