wingkwok wrote : I got similar problem but my exception is
java.security.AccessControlException: access denied
(java.util.PropertyPermission SERIALIZATION read).
| I don't use Java Security Manager.
|
| What does this SERIALIZATION read mean? Why do I get the
AccessControlException even
hello,
yes definitively what you mentionedi sthe solution..
had same problems (wrong way of packaging, ejb files in WEB-INF\lib)
my callByVaue probably wasnt the solution but it is ejb files outside .war
thanks and regards
marco
View the original post :
Thanks. I found another solution - ensure your ejb jar file only occurs once in
your ear. I had my maven 2 pom entries improperly set to include the ejb jar in
both the war and enclosing ear files.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3975213#3975213
In reference to the initial question, I have the same problem with the object
returned in Jboss 4.0.x being a org.jboss.ejb.plugins.local.LocalHomeProxy, not
the expected javax.ejb.EJBLocalHome. I cannot upgrade to 4.0.x if I am required
to use org.jboss classes in my code. Has there been a
hiya..
i found and solved problem... didnt post cos i had no time
somehow, it has to do with naming system in jboss ..
check followign files
conf\jboss-service.xml
deploy\ejb-deployer.xml
deploy\ear-deployer.xml
deploy\naming**something**.xml
you'll see an entry CallByValue.
you have to set it
I got similar problem but my exception is
java.security.AccessControlException: access denied
(java.util.PropertyPermission SERIALIZATION read).
I don't use Java Security Manager.
What does this SERIALIZATION read mean? Why do I get the
AccessControlException even I don't use
Is your bean's interfaces (remote/local or localhome/remotehome) packaged in
more than one places(may be in the war and then in some jar). If yes, then
remove it from the war and maintain it in only one single jar file.
Also, have a look at: