The only thing I'm trying to figure out though, is how to make the main Running Application change or point to the new Library version without having the need to stop it.
To start with, I created a simple application which already utilizes shared taskflow libraries.
|MainApplication - Default|
Next I'll create a separate application which contains the CSS file as well as the Trinidad definition (trinidad-skins.xml). We need to create a separate project mainly so that we can deploy it as a shared library which requires it to be a WAR.
|sharedDefault.css - Let's keep it simple and obvious, for testing anyway hehe.|
|Default Shared Skin Project|
|Shared Skin Library - Deployment Profiles|
|WAR Context Root to Empty|
|Filter the skin library as part of deployment files|
|Deployment in Weblogic Console|
Here's our FAILED attempt #1.
So as you can see, worst thing that could happen is that your application will use simple skin because it can't find the skin you want.
So for this, what we're missing is the weblogic.xml entry for the library-ref. Let's add it now and re-run our page.