You can't have multiple parentIds, but you can have multiple imports (or a parent and an import, or a parent and multiple imports, etc.) which has exactly the same effect:
<web-app xmlns="..." configId="foo"> <import>some/other/configId</import> <import>yet/another/configId</import> ... Aaron On 12/4/05, lubaki nsele <[EMAIL PROTECTED]> wrote: > > > > Aaron, > > Thanks for the reply but can you point out how to use several parentid in > one plan? > > (e.g parentid="one,two..." or parentid="one" parentid="two" .....) > > > > ________________________________ > > From: Aaron Mulder <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: Using Geronimo shared library in Websphere way > Date: Sun, 4 Dec 2005 21:10:30 -0500 > > >There are generally two choices: > > > >1) parentId and/or import, which add another application module or > >configuration as a parent of the current one. Between the two of > >those, you can add any number of "parents". > > > >2) dependency, which adds third-party libraries (outside any > >application module or configuration) to the class path of the current > >module. > > > >There is no way other than parent/import for one application to access > >the WEB-INF/classes of another (though you could presumably put all > >the contents of that in a JAR and access it via a dependency). If I > >understand your situation correctly, I think for you the one child > >could just use many import elements to bring in all the parents it > >needs. > > > >Thanks, > > Aaron > > > >On 12/4/05, lubaki nsele <[EMAIL PROTECTED]> wrote: > > > > > > It is possible that an application running under Websphere to make use > of > > > other application classpaths using Shared Library; Geronimo has a way to > > > accomplishing this? > > > > > > The parentID approach can not really work for I have several web > > > applications that will expose their classpath in this way( > WEB-INF/classes) > > > to only one other application. > > > >
