Thanks for that response, Stuart. One comment inline...
On 5/31/16 5:34 PM, Stuart Marks wrote:
On 5/30/16 11:48 AM, Richard Hillegas wrote:
Dalibor Topic recommended that I post this feedback on core-libs-dev.
This is my
feedback after ameliorating the deprecation warnings which surfaced
Dalibor Topic recommended that I post this feedback on core-libs-dev.
This is my feedback after ameliorating the deprecation warnings which
surfaced when I compiled and tested Apache Derby with early access
builds 116 and 118 of JDK 9. Derby is a pure Java relational database
whose original
I am looking for advice about how to tighten up module encapsulation
while generating byte code on the fly. I ask this question on behalf of
Apache Derby, a pure-Java relational database whose original code dates
back to Java 1.2. I want to reduce Derby's attack-surface when running
with a
On 10/4/18 9:45 AM, Alan Bateman wrote:
On 04/10/2018 17:10, Richard Hillegas wrote:
I am looking for advice about how to tighten up module encapsulation
while generating byte code on the fly. I ask this question on behalf
of Apache Derby, a pure-Java relational database whose original code
On 10/4/18 9:26 AM, Remi Forax wrote:
- Mail original -
De: "Richard Hillegas"
À: "core-libs-dev"
Envoyé: Jeudi 4 Octobre 2018 18:10:13
Objet: generated code and jigsaw modules
I am looking for advice about how to tighten up module encapsulation
while generating
to get over these speed
bumps.
Thanks,
-Rick
On 10/4/18 9:10 AM, Richard Hillegas wrote:
I am looking for advice about how to tighten up module encapsulation
while generating byte code on the fly. I ask this question on behalf
of Apache Derby, a pure-Java relational database whose original code
Thanks, Alan. This is very helpful.
On 10/10/18 9:53 AM, Alan Bateman wrote:
On 10/10/2018 16:37, Richard Hillegas wrote:
:
java.lang.invoke.MethodHandles.lookup().defineClass(generatedClassBytes)
This approach does indeed put the generated class where I want it:
inside the Derby engine
I am updating Apache Derby documentation to reflect the recent
modularization of the codeline. While doing this, I have stumbled across
an old piece of advice from the Derby Tuning Guide:
"The structure of your classpath can affect Derby startup time and the
time required to load a particular
Thanks, Alan.
On 11/23/18 12:06 AM, Alan Bateman wrote:
On 22/11/2018 19:27, Richard Hillegas wrote:
Can I scribble something in a jar file manifest which will cause
"java -jar" to boot with a modulepath rather than a classpath? I do
not see any support for a modulepath attribute i
Can I scribble something in a jar file manifest which will cause "java
-jar" to boot with a modulepath rather than a classpath? I do not see
any support for a modulepath attribute in the Java 9 jar file
documentation at
https://docs.oracle.com/javase/9/docs/specs/jar/jar.html. My sense is
Thanks, Rémi and Alan.
On 11/19/18 12:53 AM, Alan Bateman wrote:
On 18/11/2018 20:00, Richard Hillegas wrote:
I am updating Apache Derby documentation to reflect the recent
modularization of the codeline. While doing this, I have stumbled
across an old piece of advice from the Derby Tuning
11 matches
Mail list logo
