-
Feature Request
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
This is a typical area of weakness in Seam etc. due to misuse of singletons etc.
Write some tests to check that multiple wars in an ear work as expected. For example that beans are not resolvable between the two unless there is classloader visibility, and that the servlet context from one is not mixed to another, and that bean instances do not leak.
- is related to
-
WELD-1065 Ambiguous name validation should not cross visibility boundaries
- Resolved
-
WELD-1584 Ambiguous name validation should not cross visibility boundaries
- Resolved
- relates to
-
WELD-1042 @Initialized(ApplicationScoped.class) ServletContext events fired accross web application boundaries
- Resolved