Thank you. I was just trying to figure out if we would be able to use
the real EJB3.x container in unit tests in the future. It sounds like
yes, but it will have some dependency on the app client container which
won't be a problem in the future.
I think a focus on being able to unit test EJBs with examples and
tutorials should be on the GlassFish V3 roadmap.
Maybe also tutorials on how to embed the EJB container in Tomcat for
people who want to run their EE5 apps in Tomcat for some reason (such as
running the app with a hosting company). JBoss' EJB container can do that.
Thanks,
Ryan
glassfish_at_javadesktop.org wrote:
> Hi, Ryan.
>
> I'll let Mahesh continue the main thread. I want to respond to your comment about app clients.
>
> Java EE app clients run inside an app client container (ACC). Neither the ACC nor the app clients run inside an app server. Rather, the ACC (and within it the app clients) runs on systems remote from the system where the app server runs.
>
> Having said that, it is certainly true that the GlassFish V2 ACC depends on many (too many) JARs that the app server itself also depends on. So, while the number and size of GlassFish JARs needed by the ACC may suggest that the ACC is an app server or runs inside one, it does not.
>
> We plan significant improvements in the footprint of the ACC for GlassFish V3.
>
> - Tim
> [Message sent by forum member 'tjquinn' (tjquinn)]
>
> http://forums.java.net/jive/thread.jspa?messageID=254031
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>
>