Well, I am rather curious, how this TCK will look like ;)

But besides that I really would like to know, whether jsr299 is gonna become
jsr330 compliant. The point with annotations is, they have not any
behaviour, so it is just up to the environment to interpret them. If the
same annotation types are used in different environments, they should share
a common sense about there meaning and not just "reuse a class which name
approximately matches the desired intention". If jsr299 can not comply with
330, I rather would like to see 330's annotations in jsr299 being dropped
than being re(mis)used.

On the other side... if jsr299 complies, I have not found any argument why
jsr299 implementations should not also comply with jsr330's TCK.

br, Sven




2009/9/14 Mark Struberg <[email protected]>

> Hi!
>
> Bob today announced that they will release a TCK for JSR-330.
>
> My Question: I'm still not sure if JSR-299 is 100% 330 compliant or if we
> only use the same annotations to have some 'basic' similarity.
>
> So, should OWB (and other 299 containers) also comply with this TCK or only
> with the 299er suite?
>
> LieGrue,
> strub
>
>
>
>

Reply via email to