Laird,
I switched embeddable EJB container to use the new API. Can you check if
there are still differences in behavior, and if there are, let me know
the details?
thanks,
-marina
Laird Nelson wrote:
> On Sun, May 15, 2011 at 7:54 PM, emiddio-frontier
> <emiddio_at_frontier.com <mailto:emiddio_at_frontier.com>> wrote:
>
> i have test EJB with no-interface, local interface, and remote
> interface views.
>
> when deployed to embedded EJBContainer i can only get the local,
> and no interface views to work;
>
> when deployed to a glassfish v301 non-embedded instance -- i can
> via application client
> invoke the remote EJB interface successfully.
>
> I get a classcast/naming exception in some portable to remote
> narrow method layer.
>
> I thought @Remote was allowed for EJB Embedded Container usage ???
>
>
> It is not. I ran into this problem too.
>
> You want to use the glassfish-embedded APIs, although those have a
> whole host of bugs open against them as well.
> (http://embedded-glassfish.java.net/nonav/apidocs/)
>
> Good luck,
> Best,
> Laird