The IService, IGeoResource or Layer has a status overlay:
- unconfigurede - no factory or plugin knows how to connect
- error - connection was tried, error displayed in status bar when selectedd
- waning - connect was made with some kind of assumption (usualy CRS or username/password)
Layer also uses status to report on the results of the last renderer -
LiteRenderer2 will need a stratagy object in the style of ValidationResults from module/validation. This will let external code (from udig) get back error information to the correct location (the RCP logging facilities.
Lets assume this bug is talking about connection information.
Jody Garnett added a comment - 20/Feb/05 03:23 PM The IService, IGeoResource or Layer has a status overlay:
- unconfigurede - no factory or plugin knows how to connect
- error - connection was tried, error displayed in status bar when selectedd
- waning - connect was made with some kind of assumption (usualy CRS or username/password)
Layer also uses status to report on the results of the last renderer -
LiteRenderer2 will need a stratagy object in the style of ValidationResults from module/validation. This will let external code (from udig) get back error information to the correct location (the RCP logging facilities.
Lets assume this bug is talking about connection information.
Bug
Closed
Major
Not reporting service exceptions
- unconfigurede - no factory or plugin knows how to connect
- error - connection was tried, error displayed in status bar when selectedd
- waning - connect was made with some kind of assumption (usualy CRS or username/password)
Layer also uses status to report on the results of the last renderer -
LiteRenderer2 will need a stratagy object in the style of ValidationResults from module/validation. This will let external code (from udig) get back error information to the correct location (the RCP logging facilities.
Lets assume this bug is talking about connection information.