User: kimptoc 
  Date: 01/04/19 04:38:11

  Modified:    src/docs howtoj2eedeployer.xml
  Log:
  added some notes about where manifest.mf goes and a jdk bug
  
  Revision  Changes    Path
  1.3       +15 -4     manual/src/docs/howtoj2eedeployer.xml
  
  Index: howtoj2eedeployer.xml
  ===================================================================
  RCS file: /cvsroot/jboss/manual/src/docs/howtoj2eedeployer.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- howtoj2eedeployer.xml     2001/03/21 08:30:20     1.2
  +++ howtoj2eedeployer.xml     2001/04/19 11:38:11     1.3
  @@ -146,7 +146,7 @@
                <para>In JBoss we achieve this issue with the following classloader 
architecture: </para>
                <para>On deployment one - common - classloader is created. This 
classloader will get 
   all archives in its classpath
  -that are referenced (MANIFEST.MF/Class-Path)by any module contained in this 
  +that are referenced (MANIFEST.MF/Class-Path <co id = "classpath.gotcha"/>)by any 
module contained in this 
   application. </para>
                <para>When afterwards all modules become deployed in their containers, 
the 
   classloaders created by these containers 
  @@ -165,8 +165,8 @@
   directory /lib of our application.</para>
                <para>To make sure that this package is now loaded by the common 
classloader, we 
   reference it from within the web 
  -package by adding a Class-Path: entry to the web packages MANIFEST.MF file 
  -that it looks something like that: </para>   
  +package by adding a Class-Path: entry to the web packages MANIFEST.MF file <co id = 
"classpath.gotcha"/> 
  +that looks something like this: </para>   
                <literallayout>   
                        <computeroutput>   Manifest-Version: 1.0
      Class-Path: ./lib/ejb-client.jar
  @@ -186,5 +186,16 @@
      lib/ejb-client.jar
    </computeroutput>  
                </literallayout>
  +           <calloutlist>
  +               <callout arearefs = "classpath.gotcha">
  +                  <para>
  +                    <orderedlist>
  +                       <listitem>The MANIFEST.MF referred to is the one inside the 
ejb or war archive and NOT the one directly in the ear archive.</listitem>
  +                       <listitem>There is a "feature" of the jdk jarfile reader 
that means that you need to have a carriage return after the Class-Path entry in the 
manifest file - otherwise it is not found.</listitem>
  +                    </orderedlist>
  +                  </para>
  +               </callout>
  +           </calloutlist>
  +
        </section>
  -</section>
  \ No newline at end of file
  +</section>
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to