8 Replies Latest reply on Jun 8, 2010 7:22 PM by aslak

    Known locations inside spec archives

    germanescobar

      If the idea is that a "container" maps a path inside the archive, I think we should agree on the following table which shows how each container is mapped inside each spec archive:

       


      JARWAREARRAR
      ClassContainer//WEB-INF/classesN/AN/A
      EnterpriseContainerN/AN/A?N/A
      LibraryContainerN/A/WEB-INF/libN/AN/A
      ManifestContainer/META-INF/META-INF/META-INF/META-INF
      ResourceAdapterContainerN/AN/AN/A/META-INF
      ResourceContainer//WEB-INF/classes???
      WebContainerN/A?N/AN/A

       

      WebContainer and EnterpriseContainer maps to more than path inside the archive. I don't think we should allow this. Each container should only map to only one path. Also, I notice that there are missing paths. For example, what about if I want to add something to WEB-INF or META-INF (that is not a manifest). I know you can always relay on add(Asset, ArchivePath) but we should have methods to add things into every "known location" in my opinion.

       

      Do we need more "containers"? less?

       

       

      What do you think?

        • 1. Re: Known locations inside spec archives
          aslak

          About time we got up a mapping table, nice!

           

          germanescobar wrote:


          WebContainer and EnterpriseContainer maps to more than path inside the archive. I don't think we should allow this. Each container should only map to only one path. Also, I notice that there are missing paths. For example, what about if I want to add something to WEB-INF or META-INF (that is not a manifest).

          WebContainer.addWebResource -> /WEB-INF/

          ManifestContainer.addManifestResource -> /META-INF/

          • 2. Re: Known locations inside spec archives
            aslak

             

            JARWAREARRAR
            ClassContainer//WEB-INF/classesN/AN/A
            EnterpriseContainerN/AN/AN/A
            - ApplicationResources
            /META-INF
            - Modules/
            LibraryContainerN/A/WEB-INF/lib/lib/
            ManifestContainer/META-INF/META-INF/META-INF/META-INF
            ResourceAdapterContainerN/AN/AN/A/META-INF
            ResourceContainer//WEB-INF/classes/META-INF//
            WebContainerN/A/WEB-INF/N/AN/A

             

             

            ResourceContainer for EnterpriseArchive should maybe be /, not /META-INF. .not 100% sure..

             

            EnterpriseContainer is the only container that maps to more then one location as far as I can see.

            • 3. Re: Known locations inside spec archives
              alrubinger

              Awesome.

               

              This looks prime for inclusion in a ShrinkWrap User's Guide, which I think bears further discussion (and creation!)  I'll open a Thread for that.

               

              My only question: what does the color coding represent?

               

              S,

              ALR

              • 4. Re: Known locations inside spec archives
                aslak
                My use of RED means changed to the orginal
                • 5. Re: Known locations inside spec archives
                  aslak
                  ORANGE is N/A i guess.
                  • 6. Re: Known locations inside spec archives
                    aslak
                    Container TypeJARWAREARRAR
                    ClassContainer//WEB-INF/classesN/AN/A
                    ResourceContainer//WEB-INF/classes/META-INF//
                    ManifestInformationContainer/META-INF/WEB-INF/classes/META-INF/META-INF/META-INF
                    LibraryContainerN/A/WEB-INF/lib/lib/
                    WebInformationContainerN/A/WEB-INF/N/A

                    N/A

                    WebContainerN/A/N/AN/A
                    ResourceAdapterContainerN/AN/AN/A/META-INF
                    EnterpriseContainerN/AN/A
                    N/A
                    - ApplicationResources

                    /META-INF
                    - Modules

                    /

                     

                     

                    Changes:

                    - Rename ManifestContainer to ManifestInformationContainer

                    - Create WebInformationContainer

                    • 7. Re: Known locations inside spec archives
                      dan.j.allen

                      Is this a document? If not, you should consider making it one.

                      • 8. Re: Known locations inside spec archives
                        aslak

                        it's a proposal to make WebArchive and all it's locations make sense..