This week's book giveaway is in the Java in General forum.
We're giving away four copies of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 and have ishori Sharan & Adam L Davis on-line!
See this thread for details.
Win a copy of Beginning Java 17 Fundamentals: Object-Oriented Programming in Java 17 this week in the Java in General 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Junilu Lacar
  • Rob Spoor
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Tim Moores
  • Jesse Silverman
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Piet Souris
  • Frits Walraven

Defining shared jars in application.xml doesn't seem to work in 8.1

 
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm coming from a JBoss background and in some apps I've worked with we'd define common jars that are ejb and war needed in our application.xml file and everything worked fine. I'm now stuck at a place using old Bea Weblogic 8.1 and it seems like I can only define the shared jars in the manifest file definitions. When I try and use application.xml to declare the shared jars that I want my ejb and webapp to use, weblogic complains with class not found errors.

The docs seem to be confusing on the issue. On one hand they have these docs on application.xml
http://e-docs.bea.com/wls/docs81/programming/app_xml.html#1007302

but in another area it mentions having to use the manifest files for declaring external jar dependencies.
 
Rick Reumann
Ranch Hand
Posts: 281
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
After doing even more research, I think what I was doing in JBoss wasn't really standard. Not positive though.
 
Sheriff
Posts: 10445
227
IntelliJ IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Rick Reumann:
After doing even more research, I think what I was doing in JBoss wasn't really standard. Not positive though.



You are right, JBoss allows you to declared those shared libraries in the application.xml file as a < java> module. But ideally, the < java> module is meant to represent an "application-client" in J2EE.

You might want to have a look at this article, which speaks of packaging utility classes in a portable J2EE application.
 
WHAT is your favorite color? Blue, no yellow, ahhhhhhh! Tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic