[
https://issues.jboss.org/browse/WFLY-1154?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-1154:
--------------------------------------
The only way we could really do this is to add some kind of file hiding mechanism to VFS,
so that it is handled correctly across subsystems.
I'm not convinced that this is even necessary any more, as any problematic subsystems
can be excluded through the use of jboss-deployment-structure.xml (e.g. if you don't
want persistence.xml read then you can just exclude the JPA subsystem).
Allow the server to ignore files or groups of files at deployment
time
----------------------------------------------------------------------
Key: WFLY-1154
URL:
https://issues.jboss.org/browse/WFLY-1154
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Server
Reporter: Marius Bogoevici
Fix For: Awaiting Volunteers
Legacy and migrated applications may occasionally contain files which are incompatible
with the Java EE specification and can cause the application to fail the deployment. The
difference between those cases and really faulty Java EE applications lies in the intent
of the developer - whether they wish for those files to be picked up by the server and
processed, or not.
In such cases, it may be useful to expand the deployment specification and to be able to
instruct the server to ignore particular files at deployment time.
--
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