J2EE Connection Problem in JWS!!Pls Help!!!!!!
Hi
I'm using Borland AppServer 4.5. I'm trying to run a simple program which connects to EJB.When I'm running from JBuilder it works fine but when running from JWS it gives me Error :
org.omg.CORBA.OBJECT_NOT_EXIST:minor code: 0 completed: No
Code :
javax.naming.Context context = null;
ClassLoader loader = this.getClass().getClassLoader();
Thread.currentThread().setContextClassLoader(loader);
context=new InitialContext();
Object objref = context.lookup("ejb/objectif/keystone/datamodel/general/orgmember");
OrgMemberHome orgHome = (OrgMemberHome)PortableRemoteObject.narrow(objref, OrgMemberHome.class);
My tomcat port 8080
Orb port 15011
Any Idea Pls?
Prat
[771 byte] By [
pratyay] at [2007-9-26 1:14:28]
Remember that your original classpath will be deleted when launching a JAR file - and when launching an application trough Web Start.
Include Borland specific JAR files (like asrt.jar, and others) in your JNLP file. This means that they will be downloaded by Web Start and included in the applications classpath.
/Jan
Thanx
I've included all required jar files in JNLP.Still I'm having the problem.BTW I couldn't sign borland jar files.It gives error.So my jar files are not signed.
Is that a problem?How to sign Borland jar files?They always throws some error while trying to sign them.
prat
The fact that you can't sign Borland JAR files seems to be a deliberate design on the part of Borland; they effectively kill the jar and jarsigner tools by corrupting the checksum of one of the files. You have to use a command-line tool like PKZIP 2.5 as follows:
rem Create a temporary directory.
md temp
cd temp
rem Unzip the JAR file.
pkzip25 -nozip -dir -silent -extract ..\asrt.jar
rem Rejar the file, this time with the correct checksum.
jar cf ..\asrt.jar *
Remove the temporary directory.
cd ..
rd /s/q temp
You will need to do this for vbjorb.jar as well, after which you should be able to sign the JAR files. Signing them is necessary because asrt.jar in particular violates all sorts of security restrictions during initialization.
If your EJB server is on your internal network, that's all you need to do; you should be able to bind to your objects without any further problems. If you're trying to run the EJB's across the Internet, there are probably half a dozen more steps, most of which involve configuring the Gatekeeper. I'll document those steps when I can find some time.
kdean at 2007-6-29 0:31:46 >
