On Fri, 2009-04-03 at 23:39 +0530, Sahoo wrote:
> Yes and No. Yes, if it can't run without ejb-api in the system, no if
> the dependency is an optional (optional refers to OSGi import-package
> optional attribute) one.
With the currently planned distributions (web profile and Java EE
profile), I would assume that it is needed for both and hence won't be
optional.
> Why does it depend on ejb-api? Can this be broken?
There are cases where we need to check the component invocation type and
do actions. If container-common will be able to provide those
abstractions, then it may be possible.
Thanks,
-Jagadish
>
> Thanks,
> Sahoo
> Jagadish Prasath Ramu wrote:
> > Sahoo : If we need to avoid dependency on ejb, it has to avoid accessing
> > ejb api also ?
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>