[JBoss JIRA] Created: (CDI-121) TransactionScope
by Richard Hightower (JIRA)
TransactionScope
----------------
Key: CDI-121
URL: https://issues.jboss.org/browse/CDI-121
Project: CDI Specification Issues
Issue Type: Feature Request
Components: Contexts
Affects Versions: 1.1 (Proposed)
Environment: Java EE
Reporter: Richard Hightower
Priority: Minor
Add TransctionalScope as a standard scope to define beans whose lifecycle is the same as a given transaction.
This scope should start automatically when a transaction starts (but lazily when actually needed).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (CDI-189) Event qualifiers - empty set
by Jozef Hartinger (Created) (JIRA)
Event qualifiers - empty set
----------------------------
Key: CDI-189
URL: https://issues.jboss.org/browse/CDI-189
Project: CDI Specification Issues
Issue Type: Bug
Components: Events
Affects Versions: 1.1.EDR1, 1.0
Reporter: Jozef Hartinger
Priority: Minor
Fix For: 1.1.EDR2
The spec says:
{quote}
An event comprises:
* A Java object—the event object
* A (*possibly empty*) set of instances of qualifier types—the event qualifiers
{quote}
while at the same it says that:
{quote}
*Every* event has the qualifier @javax.enterprise.inject.Any, even if it does not explicitly declare this qualifier.
{quote}
which impliest that a set of qualifiers of an event cannot be empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (CDI-192) Unify coding style of the SPI interfaces
by Jozef Hartinger (Created) (JIRA)
Unify coding style of the SPI interfaces
----------------------------------------
Key: CDI-192
URL: https://issues.jboss.org/browse/CDI-192
Project: CDI Specification Issues
Issue Type: Bug
Components: Portable Extensions
Affects Versions: 1.1.EDR1
Reporter: Jozef Hartinger
Priority: Trivial
Fix For: 1.1 (Proposed)
The [JLS|http://java.sun.com/docs/books/jls/third_edition/html/interfaces.html...] says:
{quote}
For compatibility with older versions of the Java platform, it is permitted but discouraged, as a matter of style, to redundantly specify the abstract modifier for methods declared in interfaces.
It is permitted, but strongly discouraged as a matter of style, to redundantly specify the public modifier for interface methods.
{quote}
The vast majority of CDI API interfaces specifies the public modifier while leaving out the abstract modifier, however, there are exceptions:
{code:JAVA}
public interface Context {
...
boolean isActive();
}
{code}
{code:JAVA}
public interface BeanAttributes<T> {
public abstract Set<Type> getTypes();
public abstract Set<Annotation> getQualifiers();
...
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (CDI-209) BeanManager.createProducer missing in the API
by Jozef Hartinger (JIRA)
Jozef Hartinger created CDI-209:
-----------------------------------
Summary: BeanManager.createProducer missing in the API
Key: CDI-209
URL: https://issues.jboss.org/browse/CDI-209
Project: CDI Specification Issues
Issue Type: Bug
Components: Portable Extensions
Affects Versions: 1.1.EDR1
Reporter: Jozef Hartinger
Fix For: 1.1 (Proposed)
The spec says:
{quote}
The method BeanManager.createProducer() returns a container provided implementation of Producer for a given AnnotatedMethod or AnnotatedField or throws an IllegalArgumentException if there is a definition error associated with the producer method or field.
{quote}
However, the createProducer() method is not defined in the API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
CDI-14 retrieving the BM from servlet parameters
by Mark Struberg
Hi!
spi.xml- <para>Web components may obtain an instance of <literal>BeanManager</literal>
spi.xml: by calling <literal>ServletContext.getAttribute("javax.enterprise.inject.spi.BeanManager")</literal>.</para>
got added as part of CDI-14 (according to the commit message for 7f9bc25c)
I'm not sure if we still need this. Actually I'm even -1 for adding this, because we would promote multiple redundant ways to do the same stuff.
I'd rather suggest to remove it again and propagate the use of CDI.current() instead.
LieGrue,
strub
12 years, 11 months
War with no WEB-INF/beans.xml
by Joseph Snyder
I have a test war that does */_not _/*contain WEB-INF/beans.xml.
However, there is a jar in WEB-INF/lib that does contain
META-INF/beans.xml. According to the spec, 12.1, this war contains 1
bean archive, the one in the jar. (If there were a WEB-INF/beans.xml
then there would be 2 bean archives in the war.) So when the war is
deployed only the classes in the jar are managed by the CDI container.
Therefore, if there is an injection point defined in a servlet (in
WEB-INF/classes) then that injection point will never be processed by
the CDI container. Is my interpretation of the spec correct?
12 years, 11 months