This is necessary as deploy skin changes to Skin Managed Bean, updates skin file in File System. And in most cases you will deploy .ear file in your Middleware environment. If it is necessary to apply (mostly in Development environment) skin changes dynamically, deploy your ear file in exploded format.
For example, i have FusionHRDemo.ear file which has HRUI.war module. Before installing this application in WebLogic, i can explode this ear file using commands shown below.
Create folder with same name as your EAR file. And cd in that folder.
mkdir FusionHRDemo.earNow, explode ear file first.
jar -xvf D:\jdevws\jdev121200\blog\mywork\FusionHRDemo\deploy\FusionHRDemo.earNow, we need to explode HRUI.war module as well. First create dummy folder and cd in that folder. Then we will rename this folder to HRUI.war. As we are already in ear folder, this will be created under it.
mkdir warNow extract HRUI.war module, which is in parent folder, so use .. notation.
jar -xvf ../HRUI.warNow go back to parent folder and remove HRUI.war file and rename war folder to HRUI.war.
cd ..If you are using Linux, you can use matching shell commands.
move war HRUI.war
Now, you can install exploded ear folder using WebLogic Console or WLST. And running application will be able to accept dynamic skin changes using Skin Managed Bean.