ejb - Unknown JNDI Lookup String -

-

i new ejb concept. have seen following in different website :

sample 1:

@stateless @ejb(name="audit", beaninterface=anotherejblocal.class) public class employeebean implements employeeservicelocal, employeeserviceremote {   @persistencecontext(unitname = "employeeservice")   private entitymanager manager;    public void doaction(){     try {       context ctx = new initialcontext();       anotherejblocal audit = (anotherejblocal) ctx.lookup("java:comp/env/audit");       audit.doanother();   } catch (namingexception e) {       throw new ejbexception(e);   }    } }

sample 2:

public static void main(string[] a) throws exception {      employeeserviceremote service = null;     service = (employeeserviceremote) new initialcontext().lookup("employeebean/remote");       service.doaction();      }

sample 3:

obj = ctx.lookup(ejb/cbdwebappear/cbdwebapp.jar/<ejb name>/<remote interface class name>);

cbdwebapp project name in bean resides.

my question is:

  1. what need & meaning of java:comp/env/audit

  2. why same type of string not used in case of sample 2. guess remote ejb not local.

  3. why meaning of ejb string in sample 3.

  1. the java:comp/env/audit string looking ejb reference declared earlier @ejb(name="audit", beaninterface=anotherejblocal.class). names declared @ejb (and @resource , other ee references) implicitly declared in java:comp/env context. reference, deployer can retarget "audit" reference ejb in application implements anotherejblocal interface, or if deployer doesn't specify anything, javadoc @ejb annotation requires target single ejb within same application implements interface.

  2. this main method (probably) declared standalone java program. in case, (probably) configured via system properties connect jndi server of application server, return remote reference client. name looked vendor-specific, , configured ejb during deployment.

  3. this similar #2, difference being specific string being used. in case, relying on application server's "default" binding name if none configured ejb during deployment using pattern ejb/<app>/<module>/<bean>/<interface>.


Comments

Post a Comment

Popular posts from this blog

Java 3D LWJGL collision -

-
i making 3d java game lwjgl library, , wondering how add collision detection, player not go through models. i using obj models. here objloader class, loads models: package renderengine; import java.io.bufferedreader; import java.io.file; import java.io.filenotfoundexception; import java.io.filereader; import java.util.arraylist; import java.util.list; import models.rawmodel; import org.lwjgl.util.vector.vector2f; import org.lwjgl.util.vector.vector3f; public class objloader { public static rawmodel loadobjmodel(string filename, loader loader){ filereader fr = null; try { fr = new filereader(new file("res/"+filename+".obj")); } catch (filenotfoundexception e) { system.err.println("couldn't load file!"); e.printstacktrace(); } bufferedreader reader = new bufferedreader(fr); string line; list<vector3f> vertices = new arraylist<vector3f...
Read more

spring - SubProtocolWebSocketHandler - No handlers -

-
i have ugly error during deploying spring app on jboss. 18:11:16,025 error [org.apache.catalina.core.containerbase.[jboss.web].[default-host].[/consumer]] (msc service thread 1-7) exception sending context initialized event listener instance of class org.springframework.web.context.contextloaderlistener: org.springframework.context.applicationcontextexception: failed start bean 'subprotocolwebsockethandler'; nested exception java.lang.illegalargumentexception: no handlers @ org.springframework.context.support.defaultlifecycleprocessor.dostart(defaultlifecycleprocessor.java:176) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.springframework.context.support.defaultlifecycleprocessor.access$200(defaultlifecycleprocessor.java:51) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.springframework.context.support.defaultlifecycleprocessor$lifecyclegroup.start(defaultlifecycleprocessor.java:346) [spring-context-4.1.3.release.jar:4.1.3.release] @ org.s...
Read more

methods - python can't use function in submodule -

-
my folder structure this: pythonstuff/ program.py modulea/ __init__.py foo.py bar.py here's code bar.py : def hello(): print("hello, world!") here's code program.py : #!/usr/bin/env python3 modulea import bar bar.hello() i run $ python3 program.py somehow error: file "program.py", line 3, in <module> bar.hello() attributeerror: 'module' object has no attribute 'hello' edit: __init__.py file empty. edit2: after trying realized had bar.py in root directory contained hello() method. bar.py in modulea/ directory empty. add it import os __all__ = [] module in os.listdir(os.path.dirname(__file__)): if module != '__init__.py' , module[-3:] == '.py': __all__.append(module[:-3]) the init .py files required make python treat directories containing packages; done prevent directories common name, such string, unintentionally hiding v...
Read more