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

add library


I'm trying to use the mysql connector librarie in a web-dynpro project. The problem is that I always get "no suitable driver found" exception. I used the deploy tool to deploy the lib on the server. The deploy was succesful. Do I need to add some references in my project properties? What fields are important when I deploy a lib ( I kept the default values)? I followed the instructions in the help files with no sucess.

best regards


Add comment
10|10000 characters needed characters exceeded

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on May 04, 2004 at 11:42 AM


    Hope you had solved your problem by now, but if not this might help u.

    *When you deploy the library, do restart the server.

    *Secondly you are right to include the library reference you have to add the following (reference tag) in application-j2ee-engine.xml(of the generated EAR file when u archive ur web dynpro project)





    provider-name=" name as when u deployed ur library, it is by default)"

    target-type="library">(Name of the deployed library) </reference-target>


    <other-tags>.... </other-tags>


    • I think you are following the hard way to include a library, try adding the jar manually in the archive (EAR file) generated when u build archive WebDynPro project before deploying it on the SAP Web AS.

    Hope any of the above points helps, if you already found the remedy, do share it by replying on this thread.

    With Regards,

    Rohit Jaiswal

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Werner and Rohit,

      there's tool support in the DevStudio for adding library (and other) references to a WD project. You don't have to edit the portalapp.xml manually!

      This can be done using the contextmenu at the WD Project->Properties. In the following dialog, select Web Dynpro References->Library References. Add the library there. The name to use is exactly the same as you will see in the Visual Admin for example. This should solve the problem.

      Hope that helps.