Feature #1895
improve/automate PLJava registration
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
24.00 h
billable:
No
vendor_id:
GCD
version_reported:
version_resolved:
History
#1 Updated by Greg Shah over 11 years ago
The idea is to eliminate the need for a separate step to register the pljava.jar and the p2jpl.jar by detecting if it is needed and in that case dynamically running that SQL at server startup. One issue is that we have to know the path to those jar files and the registration requires that path to be absolute. Yuck.
#2 Updated by Greg Shah over 7 years ago
- Target version deleted (
Deployment and Management Improvements)