>
>
>> BeanProperties
>
hmm today it is properties but it could be more (i think in another
version we could add some static injections for instance or kind of
interceptors)
> BeanConfig/BeanConfiguration
>
here i wonder is Bean is not linked to ejbs (that's the case in our
code)...open question
> SimpleBean
>
simple sounds for me like a default
> AdministeredObject
>
too prod oriented IMO
> ConfigureBean
>
Playing with configure seems more consistent for me
> SimpleComponent
component is ambiguous IMO
Well i don't really care addind aliases, i think pojo is important for dev
and some aliases should be added for others, just need to make 1 or 2
choices, maybe we need a vote when the format will be fixed
>
>
> -> about resource: if you declare a resource it will work but the resource
>> will be application scoped at least, do you ask to be able to declare a
>> resource for a single bean?
>>
> I would like to use this to have a place for the admin to write all the
> config of the application, so I need only application scoped resources
> <Configuration>
> administratoraddress='**myaddress@mydomain'
> </Configuration>
>
> class NotificationSenderBean {
> @Resource(...) String administratoraddress;
> }
>
>
sounds like you want our env-entries.properties feature, will dig a bit to
see if i can add it now to make a proposal
