[
https://issues.jboss.org/browse/SHRINKWRAP-402?page=com.atlassian.jira.pl...
]
Andrew Rubinger commented on SHRINKWRAP-402:
--------------------------------------------
What I mean is that the spec defines WAR and EAR not by adding in specific extensions to
the flat file; it's just a ZIP with specification-defined naming conventions and
contents. So why is is that ShrinkWrap should provide some mechanism to define what
"type" it is? If all other deployment mechanisms in AS7, GlassFish, etc, handle
flat-file deployments by appropriately inspecting name and contents, why does Arquillian
need this support from ShrinkWrap?
Support method for checking what type of Archive this is
--------------------------------------------------------
Key: SHRINKWRAP-402
URL:
https://issues.jboss.org/browse/SHRINKWRAP-402
Project: ShrinkWrap
Issue Type: Feature Request
Components: api, impl-base
Affects Versions: 1.0.0
Reporter: Aslak Knutsen
Assignee: Aslak Knutsen
ShrinkWrap has the notion of views to wrap a Archive. While a view can be anything, some
of the views describes types of Archives, e.g. WebArchive. A Archive should be able to
tell which type it is. Even tho the content structure to some extent define the type,
external sources like a Container will determine the type of the Archive soley on the
archive name extension.
{code}
ShrinkWrap.create(JavaArchive.class).isOfType(WebArchive.class) == false
ShrinkWrap.create(JavaArchive.class, "my.war").isOfType(WebArchive.class) ==
true
ShrinkWrap.create(MySpecialWebArchive.class,
"my.war").isOfType(WebArchive.class) == true
{code}
A simple check if the current archive name ends with the Types defined extension mapping
should work in most cases.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira