From: Gavin King <gavin@hibernate.org>
To: Scott Ferguson <ferg@caucho.com>
Cc: Java Community Process JSR #299 Expert List <JSR-299-EG@jcp.org>; Jim Knutson <knutson@us.ibm.com>; WebBeans <webbeans-dev@lists.jboss.org>; Michael Keith <michael.keith@oracle.com>
Sent: Sunday, December 21, 2008 9:59:07 PM
Subject: Re: [webbeans-dev] Re: XML configuration format

SF>1) The inline bean vs property needs to be simplified.  (9.5 injection
SF> point declarations), specifically the existence of a child element should
SF >not affect the parsing.  Instead, it should follow the method model (9.2.6)
SF> where "has a direct child <Initializer>, ..., or binding type."  9.5 should
SF> be rewritten as:
>
SF    a) If the Java type is a parameterized type .... is a type declaration
SF  b) Otherwise if ... binding type ... is a type declaration
SF    c) Otherwise, the injection point declaration is an inline Web Bean
SF declaration, and the declared type ...
>
SF i.e. removing the old 3rd rule because it was making things more confusing.
SF  The slight extra verbosity by requiring <Current/> for an injected type is
SF outweighed by the simplification, and consistency with 9.2.6.

GK> This change would amount to *always* having to specify <Current/> in
GK>the common case where an injection point is not an inline Web Bean
GK>definition. I'm really not keen on that.

As an implementor of the XML configuration, I think it is good idea to add  for example,<Inline/>
element for specifying inline webbeans decleration. It also provides better view in the
developer perspective,(easily finds inline webbeans declerations in the XML.)