Hum... that's a bit of a shame. The entire message with Java EE 6 is
modularity, extensibility... I like the idea of just having to depend on
what I need. If the only choice is javaee-api, the modularity message is
lost. I think javaee-api is very useful, but also having separate artifacts
would help.
My 2 ents
Antonio
2009/11/7 Sahoo <Sahoo_at_sun.com>
> You should not be depending on javax.ejb and nor should you use
> javax.interceptor even if it were available. To compile your code, you
> should be using a different dependency for Java EE APIs.
> <dependency>
> <groupId>javax</groupId>
> <artifactId>javaee-api</artifactId>
> <version>6.0-SNAPSHOT</version>
> <scope>provided</scope>
> </dependency>
>
> Ludo,
>
> Which repo has this artifact? Is there a non-SNAPSHOT version?
>
> Sahoo
>
> Antonio Goncalves wrote:
>
>> Hi,
>>
>> Now that the interceptor is a seperate spec (still bundled with EJBs, but
>> a seperate spec) which also workd with ManagedBeans, I was excepting to see
>> a javax.interceptor repository under
>> http://download.java.net/maven/glassfish/org/glassfish/ (a bit like
>> javax.annotation). But it's not the case.
>>
>>
>> I'm developing a javax.annotation.ManagedBean and I use an interceptor.
>> It's a bit frustrating to have a dependency to javax.ejb when I just want to
>> use an interceptor for a ManagedBean.
>>
>>
>> Will this separate javax.interceptor be created or it will stay with
>> javax.ejb ?
>>
>>
>> Thanks,
>> Antonio
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
--
--
Antonio Goncalves (antonio.goncalves_at_gmail.com)
Software architect
Web site : www.antoniogoncalves.org
Blog: agoncal.wordpress.com
Feed: feeds2.feedburner.com/AntonioGoncalves
Paris JUG leader : www.parisjug.org
LinkedIn: www.linkedin.com/in/agoncal