[
https://issues.jboss.org/browse/SHRINKWRAP-402?page=com.atlassian.jira.pl...
]
Andrew Rubinger commented on SHRINKWRAP-402:
--------------------------------------------
So what we're asking here really is to further couple ShrinkWrap archives (generic
VFS) with Java EE spec-defined naming conventions.
I'm not a fan of coupling in general, but as it stands, Java EE support is already
built into ShrinkWrap core. This seems like a natural extension of that, and if it makes
things easier for users without introducing some opinionated behaviors, then OK.
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira