Conventions for defining Weld resources in Java EE 6?

[ljnelson]

http://docs.jboss.org/weld/reference/latest/en-US/html/resources.html talks about defining resources in Java EE 6 that can then be injected into application code.

Is there a recommended convention on where these resources live?  I've seen in examples the convention of having one class with a laundry list of producer fields in it, each of which obviously is annotated with @Produces.

Has the community settled on a way to do this?  Is it regarded as a Good Thing to place our usage of various @EJB, @PersistenceContext, @Resource etc. annotations in one class?  And if so, do people typically have a common name for this class?

Thanks in advance for your time.

Best,
Laird

[cjalmeida]

Apparently people seems to be preferring wrapping all injectable resources into @Inject.

This allows the use of static annotations instead of strings

@Inject @MyPU EntityManager em; instead of @PersistentContext(myPU)

And the use of more advanced features and lifecycle management - IIRC the @Transaction extension will require the use @Inject in place of @PersistenceContext

[ljnelson]

Right, but where is the @Produces field that defines @MyPU declared?  That's my question.

[nickarls]

That's more of a philosophical question like should brackets be on their own line? ;-)

Personally, I would have them all in some ResourceProducer or so...

[ljnelson]

Yes, knowingly.

Thanks; I've heard answers all over the map which means my question is answered: the community has NOT settled on a way to do this, so at this point any solution is not going to look odd to new developers on my project.

Personally I prefer the single-class solution as well; I've heard plenty of others who say that you should do one XYZProducer class per XYZ.

Thanks again.

Best,
Laird