|
|
|
|
The following issue has been reopened. |
|
Author: Olivier Grisel
Date: 16/05/07 11:41
Comment:
I do think this is a huge productivity problem when working with the Nuxeo platform and it really deserves a fix. There should be an easy way to spot dependency typos at least at info level by the "end of a jboss boot". For instance it, is it possible to log a report of the queued registration just before the "JBoss started in xx hours^W minutes" info line?
Granted that the "end of a jboss boot" does not exists in the OSGi framework since one can still register new components till the end of a nxruntime cycle. But to the programmer / integrator this is a real PITA to test her application manually and then encounter unexpected behaviors that are sometimes a non trivial consequence of an unitialiased component and then have to grep 5MB of logs at level debug to find out what happened.
We also definitely need a OSGi dashboard page that displays the current list of registered components, the list of dependencies that are not met and a refresh button to reload some of them live when possible (for instance those that are -bundle.xml files deployed in the deploy/nuxeo.ear/config/ folder and that are meant to be edited after a build/deploy).
A graphviz map of the loaded components would be even greater.
|
|
There is no error log when trying to register an extension to an inexistent component, or requiring an inexistent component.
This is really difficult to detect and can happen very easily doing typos or when renaming components.
|
|
|
|
![]() |
|
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
