[DELTASPIKE-335] re-visit support of EARs

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.4
• Assignee: Mark Struberg
• Reporter: Gerhard Petracek
• Created: 26/Mar/13 12:36
• Updated: 16/Aug/14 21:48
• Resolved: 16/Aug/14 21:48

Description

#1
our current approach to get rid of basic classloader issues (esp. with EARs) is to collect information during bootstrapping and inject the extension instance to consume the result later on. that can expose the collected information of one web-app to other web-apps (of the same EAR). in codi we used the classloader as key, however, this approach also has disadvantages.
(something like @WebApplicationName would only work in some cases.)

#2
there was no real agreement about https://issues.jboss.org/browse/CDI-129.
currently we expect that @ApplicationScoped is separated per web-app.
however, that's at least not the case with current versions of weld.
-> (at least for current versions of weld) we have to think about an own @WebApplicationScoped

Issue Links

• blocks: DELTASPIKE-386 PropertyFileUtils.getResourceBundle() fails in EAR
• blocks: DELTASPIKE-362 BeanManagerProvider floods log file with warnings on AS7
• incorporates: DELTASPIKE-359 Websphere 8.0.x javaassist proxy does not reflect instance value