The following describes a work-around for 2 situations for which instance patching and migration is not supported, being changing the level of an activity, and removal of an embedded sub-process. In short this work-around consists of re-implementation of the activities to move, and emptying the reusable sub-process.
This article describes how to standardize your JDeveloper Patching as requested in Planning & Getting Started – Team, Skills and Development Environments.
This article describes how to standardize your JDeveloper Installation as requested in Planning & Getting Started – Team, Skills and Development Environments.
It is kinda nutty to treat a code injection attack on a base utility on the utility rather than on the poorly-programmed vectors.
I just published a maintenance release of PL-jrxml2pdf with some bugfixes.
Dynamic SQL by itself is not sufficient for a SQL Injection Attack