That code is active for application client container. Your code is *not*
running inside application client container, hence you can't use that
code path.
Why would you not like to use EJB? You can expose the EJB as a Web
Service end point and a remote interface and you have both of your
access paths covered? Are you not trying to reinvent the same using RMI?
Sahoo
glassfish_at_javadesktop.org wrote:
> Yes, I may be forced to use EJB even though I really have no need for it. I access these interfaces either through SOAP/Servlet or RMI. Seems like I should be able to get the line of glassfish code to work:
> case ComponentInvocation.APP_CLIENT_INVOCATION:
> 161
> 162 module = (ApplicationClientDescriptor) descriptor;
> 163 app = module.getApplication();
> 164
> 165 break;
>
> It's there so there must be a way for me to set up the application client invocation type I would think.
> [Message sent by forum member 'melodyk' (melodyk)]
>
> http://forums.java.net/jive/thread.jspa?messageID=332730
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>