Hi szczyp
Yes, the BeanManager must be available if the java:/comp context is
available. Could you please file a bug and attach a sample application
to reproduce the issue?
I was also curious to understand your usecase. Usually BeanManager is
used for portable extensions. Are you trying to deploy a portable
extension in embedded glassfish?
Thanks
--Siva.
On Wednesday 30 June 2010 05:34 PM, glassfish_at_javadesktop.org wrote:
> Hi. I am starting glassfish embedded like so:
>
> [code]
> EmbeddedFileSystem.Builder efsb = new EmbeddedFileSystem.Builder();
> //efsb.configurationFile(new File("domain.xml"), true);
> efsb.autoDelete(true);
> EmbeddedFileSystem efs = efsb.build();
>
> Server.Builder builder = new Server.Builder("test");
> builder.embeddedFileSystem(efs);
> Server server = builder.build();
> server.addContainer(Type.web);
> server.addContainer(Type.ejb);
>
> InitialContext ic = new InitialContext();
> UserTransaction ut = (UserTransaction) ic.lookup("java:comp/UserTransaction");
> BeanManager bm = (BeanManager) ic.lookup("java:comp/BeanManager");
> [/code]
> I can look up UserTransaction, but not BeanManager. Is it supposed to be available there? When I deploy a webapp on standalone GF, the JNDI lookup for BeanManager works as promised by the CDI specs.
>
> szczyp
> [Message sent by forum member 'szczyp']
>
> http://forums.java.net/jive/thread.jspa?messageID=476391
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>