Bugs item #513658, was opened at 2002-02-06 00:36
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=513658&group_id=22866

Category: None
Group: v2.4 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Jukka Keto (jketo)
Assigned to: Nobody/Anonymous (nobody)
Summary: EAR deployment problem/Applet revisited

Initial Comment:
When everythin is done as
http://www.jboss.org/online-manual/HTML/ch13s21.html
states there is no problem but...

...when client.war and server.jar are deployed
within application.ear file the very old
Applet problem persist.

When deployed in ear file the old rmi
classloader error seems to reappear:
Applet client gets the file url to the
ear file, rather than true url to the
serverEJB. This obviously throws
AccessDenied error on the Applet.

When client.war and server.jar files
are deployed separately (direcly), the
Applet from client.war is able to access the
serverEJB ok.

My platform is:

bin > ./jboss.sh start
JBOSS_CLASSPATH=:/opt/jdk1.3.1_02//lib/tools.jar:run.jar:../lib/crimson.jar
PARAMETERS catalina
jboss.home 
=/opt/JBoss/JBoss-2.4.4_Tomcat-4.0.1/jboss
Using JAAS LoginConfig: 
file:/opt/JBoss/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/auth.conf
JBoss release: JBoss-2.4.4 CVSTag=JBoss_2_4_4
JBoss version: 2.4.4.2001-12-29 02:04:40 PST
Using configuration "catalina"
[INFO,root] Started Log4jService, 
config=file:/opt/JBoss/JBoss-2.4.4_Tomcat-4.0.1/jboss/conf/catalina/log4j.properties
[INFO,Info] Java version: 1.3.1_02,Sun 
Microsystems Inc.
[INFO,Info] Java VM: Java HotSpot(TM) Server VM 
1.3.1_02-b02,Sun Microsystems Inc.
[INFO,Info] System: Linux 2.4.16,i386
[INFO,Shutdown] Shutdown hook added


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=513658&group_id=22866

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to