Right Java tools for J2EE, Web Service, Grid and more

FAQ For EasyEJB

• Can I spy on a specific copy of EJB from a remote client?
• Do I have the privilege to Peek/Poke an EJB?
• Do I need to modify my EJBs for using EasyEJB?
• What are peek-able and poke-able methods?
• I have a long list of client jar files. What is the best way to include them on CLASSPATH?
• My EJB is not on the JNDI name list. Why?
• I tried the stateless session bean example from Weblogic. But the result shows a Java memory address instead of meaningful values. Why?
• My EJB is on JNDI tree, but not on JNDI name list. Why?
• Anything I should know about monitoring Stateful Session Bean?

Can I spy on a specific copy of EJB from a remote client?
Yes, for entity beans. No, for session beans. See PeekPoke Overview for details.

Do I have the privilege to Peek/Poke an EJB?
The privilege of accessing EJBs is specified by the EJB's Deployment Descriptor and your J2EE server. This is required by your J2EE server.

Do I need to modify my EJBs for using EasyEJBDo I need to modify my EJBs for using EasyEJB?
No.

What are peek-able and poke-able methods?
Peek-able and poke-able are peek-operation-able and poke-operation-able methods. Some peek-able methods may have side effects of changing EJB's attributes. Some poke-able methods may just return a value of an attributes. PeekPoke is a tool, you must know the consequence of your method call.

I have a long list of client jar files. What is the best way to include them on CLASSPATH?
1. Un-jar all jar files under myClasses directory, then include myClasses on the CLASSPATH.
2. Combine all client jar files into one big jar file and include it on the CLASSPATH.

My EJB is not on the JNDI name list. Why?

Common problems are:

• You do not have sufficient privileges to access the EJB.
• The stub of the EJB (client jar) was not on the CLASSPATH of Super when Super started.
• The EJB was deployed, installed or started after Super was started.

See EJB stubs are needed for more information.

I tried the stateless session bean example from Weblogic. But the result shows a Java memory address instead of meaningful values. Why?

EasyEJB uses the toString( ) method to show the return value. The return data type of Weblogic's stateless session bean example is TradeResult, which does not implement toString( ) method. So the toString( ) is from java.lang.Object which is a memory address. It is a good practice to implement toString( ) for every class you define.

My EJB is on JNDI tree, but not on JNDI name list. Why?

Most likely, the stub of the EJB (client jar) was not on the CLASSPATH of Super when Super started.

Anything I should know about monitoring Stateful Session Bean?

For Stateful Session Beans, one bean instance on the server corresponds to one instance of interaction with a particular client, for example, EasyEJB.

The instance of the Stateful Session Bean may disappear by many reasons in a peek period, for example, it may be timeouted. When that happens, EasyEJB will create a new instance of the Stateful Session Bean. But the state of the new created bean may or may not be the same as the deceased one.