Hi Christian, I had seen this solution as well but here are the reasons I did not used it.

• I was unable on production to request a change on the root path of an already install Websphere

• Working for more than a year with the all the weird stuff Wesbphere introduces I became sort of afraid of it's internal structure and depenencies, they seem to have this thing working under some very specific dependencies. JavaAssist is being used by other libraries WAS uses internally and I would not like to risk any crazy bugs on other layers.

But at the end of the day, the brave take risk, so maybe you would be just fine. When it comes in my case, we have frozen the dependency on 4.2.7, we will be keep monitoring if IBM updates the dependency on a fix pack..and we have already migrated our code base to Wildfly