java.rmi.AccessException: CORBA NO_PERMISSION 0 No; nested exception is: org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No org.omg.CORBA.NO_PERMISSION: minor code: 0 completed: No at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Unknown Source) at com.sun.corba.ee.internal.iiop.messages.ReplyMessage_1_2.getSystemExc eption(ReplyMessage_1_2.java:93) at com.sun.corba.ee.internal.iiop.ClientResponseImpl.getSystemException( ClientResponseImpl.java:108) at com.sun.corba.ee.internal.POA.GenericPOAClientSC.invoke(GenericPOACli entSC.java:136) at org.omg.CORBA.portable.ObjectImpl._invoke(Unknown Source) at headfirst._AdviceHome_Stub.create(Unknown Source) at AdviceClient.go(AdviceClient.java:31) at AdviceClient.main(AdviceClient.java:12)
it looks like that i don't have the permission. i just can't figure out why? (everything seems ok to me)
-- quote ------------------------ When running the AdviceClient, if you get a CORBA NO_PERMISSION 0 error:
You are probably using the older version (1.3.01) of the J2EE RI, rather than 1.3.1. The 1.3.01 version has a bug which makes the default security permission too strict; switching to 1.3.1 should fix it. However, if you cannot fix it or for some reason you are unable to switch to 1.3.1, you can do the following:
Use the deploytool to build a deployment descriptor that does not require a strict security policy:
1) Under the Security screen of the EJB wizard or the Security tab of the EJB inspector in deploytool, click "Deployment Settings..". Under the box "Client Authentication", make sure "Support Client Choice" is checked instead of "Certificate" or "Password".
2. Now from Deplotool click on "Update & redeploy"