geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil Arora" <>
Subject RE: GBean classloader and dependencies
Date Fri, 02 Nov 2007 07:23:08 GMT

Here's what I think you're saying...although I've not been able to get
this to work right.


<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns=""






















    <sys:gbean name="SharedLib1"



        <sys:reference name="ServerInfo">



        <!-- DO I NEED THIS?















From: David Jencks [] 
Sent: Friday, November 02, 2007 1:14 AM
Subject: Re: GBean classloader and dependencies



On Nov 1, 2007, at 5:06 PM, Anil Arora wrote:

I have an issue now.  I added some libraries using the sharedlib gbean. 

However, one of my classes that is in one of these libraries has a
dependency of the jasper-jdt compiler in tomcat.  I know that this is a
module which I can reference, but I'm not sure how. 

Do I put a dependency tag in the gbean definition?   I tried this and
this didn't seem to work.


>From you previous post it looks like you added a dependency to the
shared lib configuration rather than adding a shared lib gbean to your
plan.  There's no way to affect the parent classloaders of the shared
lib configuration, so you won't be able to get the jasper compiler into
that classloader.


However if you add a shared llib gbean to your plan then you can get the
jasper stuff into your classloader by also adding a dependency on the
jasper config.  If you are really sure you will never need a jsp in your
app you can try using a dependency on the jasper jar but you are more
likely to avoid problems if you add a dependency on the jasper



david jencks







Anil Arora

Interlace Systems

1900 S. Norfolk St.  Suite 325

San Mateo, CA 94403-1511

W: (650) 574-1422 x110

F: (650) 574-1423



View raw message