Hi,
Does anyone know how to solve this error? I have practically every jar from
c:\jboss\client in my classpath and still it doesn't work.
[Auto deploy] Pop org.apache.struts.action.ActionMapping
[Container factory] Deploying:file:/C:/jboss/tmp/deploy/Default/Power20.ear
[Verifier] Verifying
file:/C:/jboss/tmp/deploy/Default/Power20.ear/ejb1001.jar
[Container factory] Deploying JDBCSource
[Container factory] Deployed application:
file:/C:/jboss/tmp/deploy/Default/Powe
r20.ear
[J2EE Deployer Default] J2EE application: file:/C:/jboss/deploy/Power20.ear
is d
eployed.
[Auto deploy] Started
[Service Control] Started 27 services
[Default] JBoss 2.1-BETA Started in 0m:13s
[EmbeddedTomcat] Username is test
[EmbeddedTomcat] JDBCSessionMgr:getInstance()
[EmbeddedTomcat] Createing Session Mgr
[EmbeddedTomcat] JDBCSessionMgr.getTheSessionBean()
[EmbeddedTomcat] JDBCSessionMgrCREATING SESSION BEAN
[EmbeddedTomcat] ----> Initial Context=javax.naming.InitialContext@22c9df
[EmbeddedTomcat] JDBCSessionMgr.getTheSessionBean() failed. Exception:
javax.na
ming.CommunicationException [Root exception is
java.lang.ClassNotFoundException:
com.power20.ejb.sessionbeans.JDBCSourceHome]
[EmbeddedTomcat] javax.naming.CommunicationException [Root exception is
java.lan
g.ClassNotFoundException: com.power20.ejb.sessionbeans.JDBCSourceHome]
[EmbeddedTomcat] java.lang.NullPointerException
Which is basically the same as mentioned below (at
http://www.jboss.org/documentation/HTML/ch01s12.html )
Compiling and running test client
We're now ready to run the test client, but first a word of explanation.
In reality the client and the server are likely to be on different
computers. When you compile the client, the compiler needs to know about the
organization and methods of classes in the Bean so it can do type checking.
When you run the client, the run-time engine needs to know about the Bean
classes, because type-casting is done at run-time. So when the client
attempts to cast the remote reference to a reference to an object of class
InterestHome for example, it needs to know about this class. This means that
you will need the Bean class files on both the client and the server even
though they execute on the server. This is fairly obvious if you think about
the logic, but it causes all sorts of problems for people who are new to RMI
programming. If the client can't find the Bean classes, you will get error
messages like this:
javax.naming.CommunicationException [Root exception is
java.lang.ClassNotFoundException: com.web_tomorrow.interest.InterestHome]
A 'communication exception' is the exception that represents any error that
can't readily be ascribed to a definite cause. If you get this message you
need to pay attention to the CLASSPATH on the client. NOTE that the server
doesn't need to have the classpath set, you just need to put it in the
deploy directory and the server will generate a ClassLoader for it.
Thanks,
Southin
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
