8 Replies Latest reply: Jun 8, 2010 7:22 PM by Aslak Knutsen RSS

Known locations inside spec archives

German Escobar Newbie

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?