Hi Jordan,
I don't quite understand what you are doing, but I do wonder why you are making the
topic definition a qualifier at all. IMO it is simpler to just treat the topic annotation
a normal annotation, meta annotated with @JmsDestination. You can then use the injection
point metadata to query the annotation and find out the destination name.
WDYT?
Pete
On 7 Apr 2010, at 13:30, Jordan Ganoff wrote:
All,
I'd like some feedback on how I've implemented JMS destination injection. For
reference see the design notes at
http://sfwk.org/Seam3/JMSModule.
Generic destination injection is realized by decorating the AnnotatedTypes which define
any transitive annotations of @JmsDestination. The annotations are replaced with the
defined @JmsDestination and a simple pair of producer methods handle their production
(
http://github.com/jganoff/seam3-jms/blob/master/src/main/java/org/jboss/s...).
Although this works it removes the annotations. I'd much prefer another solution
which leaves all annotations intact and somehow provides producers for each (if not
already defined).
Any thoughts on the matter would be greatly appreciated. Am I correct in assuming the
original annotations should be preserved?
Code base is currently on github until the svn repo is set up:
http://github.com/jganoff/seam3-jms
Relevant test cases are here:
http://github.com/jganoff/seam3-jms/tree/master/src/test/java/org/jboss/s...
Thanks!
--
Jordan Ganoff
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev