Activity
From 02/10/2016 to 03/10/2016
02/26/2016
- 05:38 AM Feature #3003: improve performance of BaseDataType.deepCopy()
- Thanks for the detail, Greg.
I've relooked at the call stack - it appears that the deregister() is being called from...
02/25/2016
- 12:55 PM Feature #3003: improve performance of BaseDataType.deepCopy()
- > Since P2J is mimicking Progress, does this not mean that you only need to do a deep copy at block entry when a TRAN...
- 12:19 PM Feature #3003: improve performance of BaseDataType.deepCopy()
- Hi,
We discussed today whether we should investigate making search API calls non-TRANSACTION - which might make a ...
02/24/2016
- 02:14 PM Feature #3003: improve performance of BaseDataType.deepCopy()
- The @BaseDataType.deepCopy@ method stands out in JVM profiling/sampling.
It is invoked for every in-scope, undo-ab... - 02:06 PM Feature #3003 (New): improve performance of BaseDataType.deepCopy()
02/19/2016
- 09:16 AM Support #2998 (New): consider whether we should implement a separate security context for init/te...
02/11/2016
- 09:59 AM Bug #2994 (New): use static code analysis to scan p2j source for security vulnerabilities (Java, ...
- 09:57 AM Support #2993 (New): penetration testing: non-priviledged local user scenario
- 09:55 AM Support #2992 (New): penetration testing: remote access scenario
- 09:50 AM Support #2991: ensure that all XML parsing is done securely
- A useful quote from one of the above articles:
"Java applications using XML libraries are particularly vulnerable ... - 09:48 AM Support #2991: ensure that all XML parsing is done securely
- https://blog.detectify.com/2014/04/11/how-we-got-read-access-on-googles-production-servers/
https://www.owasp.org/in... - 09:47 AM Support #2991 (New): ensure that all XML parsing is done securely
Also available in: Atom