On Wed, Nov 10, 2010 at 2:40 PM, Timothy Ward <[email protected]> wrote: > > I'm afraid I simply don't agree that the proposed syntax is better. The 99% > use case for JPA is to inject a persistence unit or context via a setter > method, and this is the case that needs to be optimised. Forcing users to add > property elements around the JPA elements unnecessarily complicates this > scenario.
If a blueprint developer wants to inject a list or a bean, etc. as a property or argument, he/she puts the value within the <property> or <argument/> elements. Any blueprint developer knows that. So this is nothing new or complex about it. And in fact when you go outside of this convention things become unfamiliar and unexpected. So this "optimization" has quite the opposite effect to me. Jarek
