Problem Solving
Here are a list of some current problems you may encounter during the
different phases of development of an EJB application.
Bean Development:
-
Deployment descriptor generation:
-
How to generate a deployement descriptor?
-
If you've got com.bull.ejb.tools.TokenMgrError: Lexical error ...
when you want to generate a deploment descriptor
-
Check the syntax of your deploment descriptor description
-
Where to find the syntax of the description language ?
-
GenDD -grammarprints the syntax of
the deployment descriptor description language
-
GenDD -exampleprints sample EJB
deployment descriptor templates. See the GenDD commandescription in the Tools
Reference Guide
-
Bean development:
-
How to be sure that the bean provider is conform to the EJB Specification?
-
use CheckEJB to check the compliance of your
Bean
Bean Deployement
-
Container classes generation:
-
If you've got compilation error during the Container classes generation via
GenIC tool
Running the EJB Server:
-
Error in the server at launching time :
-
If you've got JOnAS configuration error!
-
Verify that Naming Service runs properly by checking the coherence of the port
number for rmiregistry and the java.naming.provider.url in
BullEJB.properties file
-
Verify that the bullejb.datasources property is well set or if set
check the contentsof the corresponding file(See Configuring JDBC DataSources)
-
If you've got: new InitialContext() : [Root exception
isjava.lang.ClassNotFoundException:
-
Verify that CLASSPATH for JNDI classes.
Running the Client:
-
Error in the client at launching time:
-
If you've got Exception connection refused
-
Verify that the server is running
-
Verify that Naming Service runs properly by checking the coherence of the port
number for rmiregistry and the -D java.naming.provider.url
parameter you are using.
Execution errors: