One of the problems that you would come across at runtime would be due to ServiceComponents being in the "Unsatisfied" state. The server startup could be successful but the server is not in a correct running state because of these unsatisfied SCs. I came across such a scenario in AS, where webapp & tenant lazy loading did not work because of this issue.
If we could startup the server with the OSGi console enabled, do an ls, and grep for "Unsatified" during integration testing, we can catch these situation easily. Otherwise, critical issues may show up after we release or during production. Azeez -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
