Well, I think there is impl specific code in the ee api classes
themselves, so it is possible the real classes would be different for
another ee 6 vendor.
This is why it is stirpped. Otherwise you could have the impression it
works most of the time until it does not work for some scenarios with
other vendors.
I wish the specs were cleaner with perfect interfaces versus impls.
Ludo
On Jan 7, 2010, at 12:26 AM, Richard Kolb <rjdkolb_at_gmail.com> wrote:
>
>
> 2010/1/7 Wouter van Reeven <wouter_at_van.reeven.nl>
> On Thu, Jan 07, 2010 at 08:15:05AM +0200, Richard Kolb wrote:
> > This dependency is added to Java-EE project in Netbeans.
> >
> > <dependency>
> > <groupId>javax</groupId>
> > <artifactId>javaee-api</artifactId>
> > <version>6.0</version>
> > <scope>provided</scope>
> > </dependency>
> >
> > So to tell the NetBeans guys that this should be removed to add
> in GlassFish
> > embedded, that's confusing.
>
> Well, as far as I can tell that dependency is only added when a Maven
> Web Application is created. If, and only if, you then deploy the app
> on
> GlassFish this will work. So you have a point that the javaee-api
> dependency should be removed in some cases.
>
> But also what could happen is the EJB or WAR could be deployed to
> Apache Tomcat, JBoss or any other Java-EE 6 container.
>
> Having GlassFish embedded as a test, or provided dependency will
> work, but do you really want to do that ?
>
>
>
> I guess this should be discussed on either the
> user_at_mevenide.codehaus.org mailinglist or some NetBeans mailinglist.
>
> I would like to start a similar discussion here, that would involve
> this.
> Doing Test driven development with Java-EE6 and NetBeans.
>
> regards
> Richard