|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
1) I gave up after this test because it was a show-stopper.
2) About thirty different modules (https://truevfs.java.net ).
Why does this matter? Well, modern day software should be composed of different modules/components/bean archives. In most cases, an application is a mix of components from different ISVs. Each of these ISVs may want to use a private CDI container to wire their components without any configuration required by the client which integrates all these components into the application. For example, I considered to use Weld in TrueVFS to make my life a bit simpler (I am currently doing DI manually). However, if Weld cannot peacefully coexist with other containers or even other instances of itself, e.g. when used by the client, then this scenario is prohibitive.
As an implication, for now I will continue to do DI manually.