Skip to Content
author's profile photo Former Member
Former Member

Cannot parse persistent.xml storage.xml... null pointer exception


i have an EAR with a WAR and an EJB jar. i only have session beans. no entity beans. my EJB jar does not have a persistent.xml or storage.xml. i build my EAR using ant and deploy using visual administrator (thanks to Vladimir Pavlov). i get this huge stack that says

" Cannot parse persistent.xml or storage.xml for JAR F:\usr\sap\J2E\JC00\j2ee\admin\.\temp\deploying\deploy_temp\reader1115328611113\tap-ejb.jar.

Reason: java.lang.NullPointerException."

i get this only when i have <security-permission> in the ejb-j2ee-engine.xml. does this tag need one of these files. the application deploys just fine if i dont have the <security-permission>. i need to map the users to the roles in the application for EJBs.

can someone please tell me what is happening here.


- RD

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on May 06, 2005 at 11:16 AM

    Hi RD,

    I guess this is kind of a strange behavior with the Deploy Tool and Visual Admin tool, you could report an OSS message for that. But you definitely don't need persistent.xml or storage.xml in this case. These descriptors are only for the O/R mapping of CMP entity beans in Web AS Java 6.40 and 6.20, respectively.

    Hope this clarifies your issues!


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.