做ejb3.0的Demo的時候出現的一個反常錯誤,錯誤提示如下:
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: ejb.facade.IFacade (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:786)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
at javax.naming.InitialContext.lookup(Unknown Source)
at make.Test.main(Test.java:29)
Caused by: java.lang.ClassNotFoundException: ejb.facade.IFacade (no security manager: RMI class loader disabled)
at sun.rmi.server.LoaderHandler.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader$2.loadProxyClass(Unknown Source)
at java.rmi.server.RMIClassLoader.loadProxyClass(Unknown Source)
at sun.rmi.server.MarshalInputStream.resolveProxyClass(Unknown Source)
at java.io.ObjectInputStream.readProxyDesc(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.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:710)
... 3 more
這個錯誤郁悶了我很久原來是 我從服務器拷貝出來的接口和實體類到客戶端的時候他們在客戶端的包名與服務端所在的包名不一致是造成的, 服務端與客戶端jar必須完全一致。否則造成客戶端訪問時，客戶端須先從服務端下載，報安全許可異常。記下這個錯誤防止以后在做錯了