• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

WSAD v5.01 + Cloudscape v5.1

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
I trying to replace the default Cloudscape 5.0 install that comes with WSAD with the newer Cloudscape v5.1. For this I need WSAD to pick up the Cloudscape license.jar file. I do not want to add this .jar at project level, I want to add it to the WSAD default classpath, ie. the one used by WSAD when it fires up. I have tried placing it in C:\Program Files\IBM\WebSphere Studio\eclipse\jre\lib\ext directory but it ain't a working. Anybody know how to modify the WSAD runtime classpath to force it to pickup thirdpary .jars?
Thanks,
Stephen
 
Stephen Bennett
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
OK, got over my problem.
Added the contents of the cloudscape v5.1 license.jar to the cloudscape V5.1 db2j.jar. WSAD v5.0.1 now picks up the license.properties from db2j.jar, a file WSAD is sure to load.
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic