• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WebSphere app server, shared libs and class files

 
Greenhorn
Posts: 12
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I've got (hopefully!) a quick question around WAS 7 and shared libraries. I've not made use of shared libs before, so forgive me if my questions seem a little stupid!

I've got everything working from my development workspace and using an application with shared libraries pointing to JAR files. This is great, but it means I have to keep JAR-ing up my workspace to test out changes I make to the Java code.

Is it possible to use shared libraries but *not* use JARs? Previous to using shared libs I was using the ws.ext.dirs attribute on the server JVM to point to the root folder of various class paths, e.g.

c:\myApplication\myJavaProject\;c:\myApplication\anotherJavaProject\;

This has become something like this in my libraries XML file:



Ideally I'd like to change this so that it worked as before, pointing to the root of the package folder structure:



Unfortunately this doesn't seem to work. Is there something I've missed out, or is this just not possible using shared libs?

Many thanks,

Dan
 
reply
    Bookmark Topic Watch Topic
  • New Topic