Writing content at runtime to locations within the web application is always risky for various reasons. Consider a case where the images (for examples) have been uploaded/written to the deployed web app and now the development team comes up with a new version of the .war that you need to deploy. How do you manage the older war without losing contents that have been added to it?
One way to deal with this is to write them out to some static location outside of the web context and then use something like this Re: wildfly hot deploy of static content. That way your runtime uploaded content isn't affected when you have to deploy new versions of the application. Furthermore, you won't even have to worry about where the .war deployment resides or how it is deployed (filesystem vs management API).
Thanks so much for the reply/answer. This is exactly what I was looking for!!