Deployment of Ejb's, Applet calls from a Browser

Question

Hello, and thank you for taking the time to review my post....
PII Celeron 333mHz
256 Megs Ram
Windows NT 4.0 Workstation (SP3)
JDeveloper2.0(Build 343)
Oracle 8.1.5
Netscape 4.06
Everything resides on the same machine.
Problem 1: I had no trouble deploying EJB's initially. As their
size grew, they became increasingly difficult to deploy. Long
delays(10 mins.)were, and are still encountered. Is that
acceptable for a minimal sized EJB? I've also noticed when my
deployment fails, (different errors are presented on different
occassions), it becomes impossible to deploy an EJB without first
closing, and restarting Jdeveloper. Is that normal behavior.?
Other times my deployment hangs when the Oracle 8i deployment is
called. I test my IIOP connection in Jdeveloper, and it fails to
work. I can't access the "sess_sh" from a command prompt either.
Would you know the cause(s)? Which steps should be taken in order
to remedy the situation..? A shutdown, and restart of the
database?
Problem 2: EJB1 is deployed to the database. A simple applet(with
the standalone option) is created. It calls EJB1 from within
Jdeveloper without trouble. Though when i attempt to run the
applet via the provided HTML file, it fails. The HTML file brings
up the appletviewer, which stalls after the applet is started. Is
an invalid "archive" file provided in the applet tag? Which
".jar" file should be present..the *Generated.jar file?
With regards to running the applet in Netscape, it fails. When i
deploy the ejb, should i include the "java40.jar" file as a
dependancy..? Should the "applet.class" file be included in the
deployment as well.? Should the typical Jdeveloper classes be
also stored in the ..Netscape\Program\java\classes directory?
Would someone be able to provide me with a simple applet, ejb
scenario, stating which .jar files are needed, and where they
should be present etc..?
My thanks in advance :)
Robert
null

Answer 1

Hey Mark,
Maybe you can help then, I am getting the below errors (I am
pasting in a message I wrote earlier):
Hello,
I think I got one that could stump a bunch of ya... we'll see.
I wrote an EJB in JDev. 2.0 and deployed it. Worked well, no
problems. Wrote a Client Snippet, worked well (never tested
outside JDev.). Wrote a Client Applet, works very well INSIDE
JDEV. 2.0, once I try to run it outside JDev, I get nothing but
Exceptions.
SO, I tried deploying it to a jar, made sure to add all the
propper .jar and .zip files and everything. I deploy it and run
it inside IE 5.0 (using OBJECT instead of APPLET tags with the
right java plug in etc.), that hangs. SO i use appletviewer to
pick up the error messages and I get the stuff below (exception
and stack trace at end of message).
java.naming.factory.initial (which is in the exception message)
was new to me so I spent the last two days reading about JNDI
etc, and found out that it is just an environment property for
JNDI and that ORACLE does not use it once in any of its examples
or anything.
I have been unable to locate AURORA's version of its
ContextFactory (I tried just about every class with the word
Factory in it -- took forever), and none of those worked. To be
exact I found one class that looked like it could have worked:
oracle.aurora.jndi.sess_iiop.sess_iiopURLContextFactory.class...
I tried that, but that returned a ClassCastException.
So here's my synopsis: Inside JDEV for some reason the command:
Context ic= new InitialContext(environment);
works, as long as I specify a minimal number of environment
properties: javax.naming.Context.URL_PKG_PREFIXES (which I set
to, as Oracle says to do,
oracle.aurora.jndi),Context.SECURITY_PRINCIPAL,
Context.SECURITY_CREDENTIAL, and the NO_SSL one too. That works
fine in JDEV, throws the exception (see below) outside of JDEV.
If then try to specifiy a context factory
(Context.INITIAL_CONTEXT_FACTORY
constant) of the class type above I throw the exception shown
above inside and outside of JDEV (i.e. in appletviewer). Here's
where it gets weird:
If I use the above configuration that works in JDEV (no initial
context factory environment setting) and try to print out via
the list() method the context's bindings, I get the same
exception that is seen below. SO the only time it works, is when
I don't specify the initial context factory and I ONLY run it
inside JDEV WITHOUT performing any actions on the instantiated
context variable other than a lookup. REALLY WEIRD!
So please help ASAP, thanks.
Nadim Homsany
Systems Analyst
Message: Need to specify class name in environment or system
property: java.naming.factory.initial
javax.naming.NoInitialContextException: Need to specify class
name in environment or system property:
java.naming.factory.initial
at
javax.naming.spi.NamingManager.getDefaultInitialContextFactory
(Naming Manager.java:688)
at javax.naming.spi.NamingManager.getInitialContext
(NamingManager.java:7
44)
at javax.naming.InitialContext.getDefaultInitCtx
(InitialContext.java:181
at javax.naming.InitialContext.getURLOrDefaultInitCtx
(InitialContext.jav
a:219)
at javax.naming.InitialContext.lookup
(InitialContext.java:288) at
testejb.FirstEJBClientApplet.startEJB
(FirstEJBClientApplet.java:151)
at testejb.FirstEJBClientApplet.jbInit
(FirstEJBClientApplet.java:72)
at testejb.FirstEJBClientApplet.init
(FirstEJBClientApplet.java:61)
at sun.applet.AppletPanel.run(AppletPanel.java:357)
at java.lang.Thread.run(Thread.java:479)
mark tomlinson (guest) wrote:
: You need to link the applet with the xxxxxx_generated.jar that
: comes back from the deployment tool (and that is really all you
: need to include which is specific to the EJB). Try enabling the
: java console for the browser so you can get more specifc error
: messages.
null