applet作为UI页面,数据处理层使用EJB3,这个方案是否可行?

SW13968086129 2009-05-25 10:16:13
applet的init函数如下:
public void init() {
super.init()
try {
String jndiPath = "ManageIndexDAOBean/remote";
Properties props = new Properties();

/* JBOSS 服务器 */
props.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
props.setProperty("java.naming.provider.url", "localhost:1099");
props.setProperty("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
InitialContext ctx = new InitialContext(props);
ManageIndexDAO dao = (ManageIndexDAO)ctx.lookup(jndiPath);
if (dao != null) {
}
} catch (NamingException e) {
e.printStackTrace();
}
}

调用Applet的html内容如下:
<applet codebase="."
code="cn.hz.epower.applet.ManageIndexApplet.class"
name="ManageIndexApplet"
archive="Client/jbossall-client.jar,
Client/jboss-ejb3-client.jar,
Client/jboss-aop-jdk50-client.jar,
Client/jboss-aspect-jdk50-client.jar,
Client/PlanStatManageLocal.jar"
width="520"
height="240">
</applet>
</body>

...全文
281 8 打赏 收藏 转发到动态 举报
写回复
用AI写文章
8 条回复
切换为时间正序
请发表友善的回复…
发表回复
jeff2033333 2009-05-25
  • 打赏
  • 举报
回复
applet是在用户的jre上跑的,访问EJB组件只能用远程方式,性能上恐怕会比jsp/servlet差很多。
kokobox 2009-05-25
  • 打赏
  • 举报
回复



network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/jndi.properties
network: 正在使用代理 DIRECT 连接 http://localhost:1099/
network: 未找到高速缓存项 [url: http://IBM-PC/crossdomain.xml,版本: null]
network: 正在使用代理 DIRECT 连接 http://IBM-PC/crossdomain.xml
network: 正在使用代理 DIRECT 连接 http://IBM-PC:80/
java.security.PrivilegedActionException: java.net.ConnectException: Connection refused: connect



不用applet不行吗? 直接用jsp或者html
SW13968086129 2009-05-25
  • 打赏
  • 举报
回复
怎么没人回答啊,郁闷中
SW13968086129 2009-05-25
  • 打赏
  • 举报
回复
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/jndi.properties
network: 正在使用代理 DIRECT 连接 http://localhost:1099/
network: 未找到高速缓存项 [url: http://IBM-PC/crossdomain.xml,版本: null]
network: 正在使用代理 DIRECT 连接 http://IBM-PC/crossdomain.xml
network: 正在使用代理 DIRECT 连接 http://IBM-PC:80/
java.security.PrivilegedActionException: java.net.ConnectException: Connection refused: connect
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.net.CrossDomainXML.check(Unknown Source)
at com.sun.deploy.net.CrossDomainXML.check(Unknown Source)
at sun.plugin2.applet.Applet2SecurityManager.checkConnect(Unknown Source)
at java.net.InetAddress.getLocalHost(Unknown Source)
at sun.rmi.transport.tcp.TCPEndpoint.<clinit>(Unknown Source)
at sun.rmi.transport.LiveRef.read(Unknown Source)
at sun.rmi.server.UnicastRef2.readExternal(Unknown Source)
at java.rmi.server.RemoteObject.readObject(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at java.rmi.MarshalledObject.get(Unknown Source)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:252)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(Unknown Source)
at cn.hz.epower.applet.ManageIndexApplet.init(ManageIndexApplet.java:249)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.<init>(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at com.sun.deploy.net.CrossDomainXML$2.run(Unknown Source)
... 27 more
network: 正在使用代理 DIRECT 连接 http://127.0.0.1:1098/
basic: 已删除进度监听程序:sun.plugin.util.GrayBoxPainter$GrayBoxProgressListener@19616c7
Exception in thread "thread applet-cn.hz.epower.applet.ManageIndexApplet.class-1" java.lang.ExceptionInInitializerError
at org.jboss.remoting.InvokerLocator.<clinit>(InvokerLocator.java:78)
at sun.misc.Unsafe.ensureClassInitialized(Native Method)
at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(Unknown Source)
at sun.reflect.ReflectionFactory.newFieldAccessor(Unknown Source)
at java.lang.reflect.Field.acquireFieldAccessor(Unknown Source)
at java.lang.reflect.Field.getFieldAccessor(Unknown Source)
at java.lang.reflect.Field.getLong(Unknown Source)
at java.io.ObjectStreamClass.getDeclaredSUID(Unknown Source)
at java.io.ObjectStreamClass.access$700(Unknown Source)
at java.io.ObjectStreamClass$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.io.ObjectStreamClass.<init>(Unknown Source)
at java.io.ObjectStreamClass.lookup(Unknown Source)
at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
at java.io.ObjectInputStream.readClassDesc(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
at java.io.ObjectInputStream.readSerialData(Unknown Source)
at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
at java.io.ObjectInputStream.readObject0(Unknown Source)
at java.io.ObjectInputStream.readObject(Unknown Source)
at java.rmi.MarshalledObject.get(Unknown Source)
at org.jnp.interfaces.MarshalledValuePair.get(MarshalledValuePair.java:72)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:654)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(Unknown Source)
at cn.hz.epower.applet.ManageIndexApplet.init(ManageIndexApplet.java:249)
at sun.plugin2.applet.Plugin2Manager$AppletExecutionRunnable.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.security.AccessControlException: access denied (java.util.PropertyPermission jboss.remoting.pre_2_0_compatible read)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPropertyAccess(Unknown Source)
at java.lang.System.getProperty(Unknown Source)
at org.jboss.remoting.Version.<clinit>(Version.java:51)
... 35 more
network: 正在使用代理 DIRECT 连接 http://127.0.0.1:1098/



最后说明:
1、EJB3类没有问题,在客户机器上测试通过。
2、部署EJB3的服务器采用jboss-4.2.1.GA

苦恼了我好多天了,不知道有没有高手能帮我解决一下,或者提供给我一个思路,对回贴的人不胜感激
SW13968086129 2009-05-25
  • 打赏
  • 举报
回复
最后的APPLET的JDK控制面板提示出错信息如下:

security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.deploy
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.deploy
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.definition value null
security: property package.definition new value com.sun.javaws
security: property package.definition value com.sun.javaws
security: property package.definition new value com.sun.javaws,com.sun.deploy
security: property package.definition value com.sun.javaws,com.sun.deploy
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.access value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.access new value sun.,com.sun.xml.internal.ws.,com.sun.xml.internal.bind.,com.sun.javaws,com.sun.deploy,com.sun.jnlp,org.mozilla.jss
security: property package.definition value com.sun.javaws,com.sun.deploy,com.sun.jnlp
security: property package.definition new value com.sun.javaws,com.sun.deploy,com.sun.jnlp,org.mozilla.jss
basic: 已添加进度监听程序:sun.plugin.util.GrayBoxPainter$GrayBoxProgressListener@19616c7
network: 没有与未签名的 JAR 文件有关的证书信息: http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar,版本: null]
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar
network: CleanupThread used 68317 us
network: 正在使用代理 DIRECT 连接 http://localhost:9090/
network: http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/Client/jbossall-client.jar 的连接
network: 没有与未签名的 JAR 文件有关的证书信息: http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar,版本: null]
network: CleanupThread used 4 us
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/Client/jboss-ejb3-client.jar 的连接
network: 没有与未签名的 JAR 文件有关的证书信息: http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar,版本: null]
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/Client/jboss-aop-jdk50-client.jar 的连接
network: CleanupThread used 3 us
network: CleanupThread used 3 us
network: CleanupThread used 3 us
network: CleanupThread used 4 us
network: 没有与未签名的 JAR 文件有关的证书信息: http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar,版本: null]
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/Client/jboss-aspect-jdk50-client.jar 的连接
network: 没有与未签名的 JAR 文件有关的证书信息: http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar,版本: null]
network: CleanupThread used 3 us
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar
network: http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/Client/PlanStatManageLocal.jar 的连接
network: 找到了高速缓存项 [url: http://localhost:9090/PlanStatManageWeb/cn/hz/epower/applet/ManageIndexApplet.class,版本: null]
network: CleanupThread used 3 us
network: 正在使用代理 DIRECT 连接 http://localhost:9090/PlanStatManageWeb/cn/hz/epower/applet/ManageIndexApplet.class
network: http://localhost:9090/PlanStatManageWeb/cn/hz/epower/applet/ManageIndexApplet.class 的响应代码: 304
network: http://localhost:9090/PlanStatManageWeb/cn/hz/epower/applet/ManageIndexApplet.class 的编码: null
network: 断开与 http://localhost:9090/PlanStatManageWeb/cn/hz/epower/applet/ManageIndexApplet.class 的连接
basic: 小程序已载入。
basic: Applet resized and added to parent container
basic: PERF: AppletExecutionRunnable - applet.init() BEGIN ; jvmLaunch dt 364241 us, pluginInit dt 563531 us, TotalTime: 927772 us

iamklaus 2009-05-25
  • 打赏
  • 举报
回复
UP RMI
SW13968086129 2009-05-25
  • 打赏
  • 举报
回复
RMI似乎可以实现的

67,538

社区成员

发帖
与我相关
我的任务
社区描述
J2EE只是Java企业应用。我们需要一个跨J2SE/WEB/EJB的微容器,保护我们的业务核心组件(中间件),以延续它的生命力,而不是依赖J2SE/J2EE版本。
社区管理员
  • Java EE
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧