Mailing-List: contact users-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Discussion" <users@myfaces.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.de;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
  b=biUHD2/tt/xqFOS2nnqOTyHvC5dj82dFrChGgUqe49JUFDo+DYpMYoEwf0pmqlxOn8g2xBFmWO9DtAjymbs7scFETUKqZ3RewapR2Hbw/CHdSUnKwv+4fKG/ut6rs26pi2TH2fs2aqFuradZ98NO+lYNg0/RI0jnrzX9v74ppvo=;
Message-ID: <1350565422.27130.YahooMailNeo@web28902.mail.ir2.yahoo.com>
Date: Thu, 18 Oct 2012 14:03:42 +0100 (BST)
From: Mark Struberg <struberg@yahoo.de>
Reply-To: Mark Struberg <struberg@yahoo.de>
Subject: a small CDI related survey
To: My Faces Discussion <users@myfaces.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hi folks!

I have a slightly offtopic survey for you.

The question is how the current @ApplicationScoped in CDI should behave.
Should it be 1 instance per WAR or 1 instance per EAR?

To make this more clear: in CDI-1.1 we will have both scopes at the end.
Please also note that any scope broader than 1 per WAR file will break @Specializes and @Alternatives in WAR files.
So if you have an EAR project and like to use @Specializes or @Alternatives you need to do that in a jar on the shared classpath. 


Here is the survey:

http://www.surveymonkey.com/s/9VNXZDB


LieGrue,
strub


PS: having 1 per ear will mean 1 BeanManager for the whole EAR as well, so 
CODI, DeltaSpike and even Seam3 are known to be broken with that 
approach I fear ...