You can wire the injection so that it needs additional marker
annotations; when you declare you service you annotate the service to
identify which marker annotation(s) are used to select it.
On Fri, Dec 4, 2009 at 3:30 PM, Pierce T. Wetter III wrote:
>
> On Dec 3, 2009, at 11:20 AM, Piero Sartini
On Dec 3, 2009, at 11:20 AM, Piero Sartini wrote:
>> @CommitAfter("unit1")
>>
>> JPA already defines something like this does anyone have an opinion on
>> using @Inject vs. @PersistenceContext("unit1")?
>
> Hard to say, but I would prefer @Inject. I like to know that I am
> working with the
> �...@commitafter("unit1")
>
> JPA already defines something like this does anyone have an opinion on using
> @Inject vs. @PersistenceContext("unit1")?
Hard to say, but I would prefer @Inject. I like to know that I am
working with the tapestry stuff, not in the JavaEE context. Could be
confusin
> This has come up recently; the simple idea is that the when injecting
> a Hibernate Session and additional annotation may be present to
> identify *which* session to inject.
i.e.
@CommitAfter("unit1")
JPA already defines something like this does anyone have an opinion on using
@Injec
This has come up recently; the simple idea is that the when injecting
a Hibernate Session and additional annotation may be present to
identify *which* session to inject. However, this raises another
problem ... ValueEncoders and determining which session to use to
convert from a string id back to
