New SAR-INF/lib impl

[Paul Hammant <Pa...@yahoo.com>]

Peter,

We've gone back to the the jar files not being unpacked. I had problems 
with that and Jesktop in the past.  I'll try to do some work to see if 
that is still an issue.  It is fine for EOB which is similar to Jesktop 
in that it is an application hosting environment, but different in that 
it does not support hot installation.

How about an xml file in the lib dir which denotes what is what in terms 
of interface and impl

SAR-INF/lib/
    jo-interface.jar
    jo-impl.jar
    cornerstone-api.jar
    cornerstone-impl.jar
    myblock-api.jar
    myblock-impl.jar
    separation.xml

Where separation.xml is like :

<?xml version="1.0"?>
<separation>
   <classloader id="1">
     <interface jar="jo-interface.jar"/>
     <impl jar="jo-impl.jar"/>
   </classloader>
   <classloader id="2">
     <interface jar="cornerstone-api.jar"/>
     <impl jar="cornerstone-impl.jar"/>
   </classloader>
   <classloader id="3">
     <interface jar="myblock-api.jar"/>
     <impl jar="myblock-impl.jar"/>
   </classloader>
</separation>

Thoughts?

- Paul

   
   


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: New SAR-INF/lib impl

[Paul Hammant <Pa...@yahoo.com>]

Actually scratch that, the xdocs/classloader.txt file details a far more 
evolved solution,

-PH


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: New SAR-INF/lib impl

[Peter Donald <pe...@apache.org>]

On Sun, 12 May 2002 19:27, Paul Hammant wrote:
> We've gone back to the the jar files not being unpacked.

There still unpacked. They are just unpacked under a temporary hierarchy - 
namely  

$PHOENIX_HOME/work/myapp-1234/SAR-INF/classes/
$PHOENIX_HOME/work/myapp-1234/SAR-INF/lib/*.jar

> Where separation.xml is like :
>
> <?xml version="1.0"?>
> <separation>
>    <classloader id="1">
>      <interface jar="jo-interface.jar"/>
>      <impl jar="jo-impl.jar"/>
>    </classloader>
>    <classloader id="2">
>      <interface jar="cornerstone-api.jar"/>
>      <impl jar="cornerstone-impl.jar"/>
>    </classloader>
>    <classloader id="3">
>      <interface jar="myblock-api.jar"/>
>      <impl jar="myblock-impl.jar"/>
>    </classloader>
> </separation>

I am not sure what the above is trying to do exactly (You mean to put the 
interface and implementations in same ClassLoaders?). However you may want to 
have a look at 

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8653

which describes one strategy of fixing things.

-- 
Cheers,

Peter Donald


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>