File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes WebSphere app server, shared libs and class files Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of OCM Java EE 6 Enterprise Architect Exam Guide this week in the OCMJEA forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere app server, shared libs and class files" Watch "WebSphere app server, shared libs and class files" New topic
Author

WebSphere app server, shared libs and class files

Dan Lingard
Greenhorn

Joined: Aug 12, 2009
Posts: 12
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
 
jQuery in Action, 2nd edition
 
subject: WebSphere app server, shared libs and class files