This week's book giveaways are in the Jython/Python and Object-Oriented programming forums.
We're giving away four copies each of Machine Learning for Business: Using Amazon SageMaker and Jupyter and Object Design Style Guide and have the authors on-line!
See this thread and this one for details.
Win a copy of Machine Learning for Business: Using Amazon SageMaker and JupyterE this week in the Jython/Python forum
or Object Design Style Guide in the Object-Oriented programming forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Joe Ess
  • salvin francis
  • fred rosenberger

JBoss JSP compilation

Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi there.
I am using the "Class-Path" entry in the manifest file (MANIFEST.MF) of my war files to point to JAR libraries I need to reuse. This way I can guarantee that these classes are loaded by the application classloader. If I put these JARs in [JBoss]/lib/ext they will indeed be shared, but will also be loaded by the extensions classloader. You see, I need shared libraries that are loaded by *each* application, but I don't want to copy the JARs into every WEB-INF/lib.
Using absolute file paths at the MANIFEST.MF "Class-Path" entry in each WAR file works well with WebSphere, and also works with JBoss. For an example:
Manifest-Version: 1.0
Class-Path: file:/W:/lib/persistencia/atual/persistencia.jar

When I deploy such a web-app to JBoss I can read at the server log that the "persistencia" library has been loaded. Indeed, the following code in a JSP page compiles and runs ok:
The class "" exists in a JAR referenced in the manifest file classpath. That means that the class exists and has been found by the application classloader. But the code below doesn't compile:
<% c;
I get an "org.apache.jasper.JasperException: Unable to compile ... Class not found.". *VERY* weird. I can only conclude that the JSP compiler is not the same classpath of the application classloader. Is that possible?
There are 29 Knuts in one Sickle, and 17 Sickles make up a Galleon. 42 tiny ads in a knut:
Java file APIs (DOC, XLS, PDF, and many more)
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!