MicroDoc's Oracle Java(TM) SE Embedded 8 for ARM Linux (32Bit and 64Bit)
MicroDoc's Oracle Java SE Embedded 8 for ARM (32Bit and 64Bit)
MicroDoc is offering "Oracle Java SE Embedded 8 for ARM" - a full implementation of the Java SE Embedded 8 specification for ARM platforms (32Bit and 64Bit). The VM is developed in close cooperation with Oracle's product development and engineering services teams and is based on the current Java SE Embedded 8 platform code. See the Oracle Website for product details. The codebase is targeted for embedded use and has a rich set optimizations over the OpenJDK implementation. The VM can be configured for various profiles and includes a JIT compiler.
The first implementation that will be made available to the open market will be designed for single and multicore ARM / LINUX (32Bit and 64Bit).
Choose from the following profiles:
|
compact1 |
additional packages in compact2 |
additional packages in |
|
java.io |
java.rmi |
java.lang.instrument |
|
java.lang |
java.rmi.activation |
java.lang.management |
|
java.lang.annotation |
java.rmi.dgc |
java.security.acl |
|
java.lang.invoke |
java.rmi.registry |
java.util.prefs |
|
java.lang.ref |
java.rmi.server |
javax.annotation.processing |
|
java.lang.reflect |
java.sql |
javax.lang.model |
|
java.math |
javax.rmi.ssl |
javax.lang.model.element |
|
java.net |
javax.sql |
javax.lang.model.type |
|
java.nio |
javax.transaction |
javax.lang.model.util |
|
java.nio.channels |
javax.transaction.xa |
javax.management |
|
java.nio.channels.spi |
javax.xml |
javax.management.loading |
|
java.nio.charset |
javax.xml.datatype |
javax.management.modelmbean |
|
java.nio.charset.spi |
javax.xml.namespace |
javax.management.monitor |
|
java.nio.file |
javax.xml.parsers |
javax.management.openmbean |
|
java.nio.file.attribute |
javax.xml.stream |
javax.management.relation |
|
java.nio.file.spi |
javax.xml.stream.events |
javax.management.remote |
|
java.security |
javax.xml.stream.util |
javax.management.remote.rmi |
|
java.security.cert |
javax.xml.transform |
javax.management.timer |
|
java.security.interfaces |
javax.xml.transform.dom |
javax.naming |
|
java.security.spec |
javax.xml.transform.sax |
javax.naming.directory |
|
java.text |
javax.xml.transform.stax |
javax.naming.event |
|
java.text.spi |
javax.xml.transform.stream |
javax.naming.ldap |
|
java.time |
javax.xml.validation |
javax.naming.spi |
|
java.time.chrono |
javax.xml.xpath |
javax.security.auth.kerberos |
|
java.time.format |
org.w3c.dom |
javax.security.sasl |
|
java.time.temporal |
org.w3c.dom.bootstrap |
javax.sql.rowset |
|
java.time.zone |
org.w3c.dom.events |
javax.sql.rowset.serial |
|
java.util |
org.w3c.dom.ls |
javax.sql.rowset.spi |
|
java.util.concurrent |
org.xml.sax |
javax.tools |
|
java.util.concurrent.atomic |
org.xml.sax.ext |
javax.xml.crypto |
|
java.util.concurrent.locks |
org.xml.sax.helpers |
javax.xml.crypto.dom |
|
java.util.function |
|
javax.xml.crypto.dsig |
|
java.util.jar |
|
javax.xml.crypto.dsig.dom |
|
java.util.logging |
|
javax.xml.crypto.dsig.keyinfo |
|
java.util.regex |
|
javax.xml.crypto.dsig.spec |
|
java.util.spi |
|
org.ietf.jgss |
|
java.util.stream |
|
|
|
java.util.zip |
|
|
|
javax.crypto |
|
|
|
javax.crypto.interfaces |
|
|
|
javax.crypto.spec |
|
|
|
javax.net |
|
|
|
javax.net.ssl |
|
|
|
javax.script |
|
|
|
javax.security.auth |
|
|
|
javax.security.auth.callback |
|
|
|
javax.security.auth.login |
|
|
|
javax.security.auth.spi |
|
|
|
javax.security.auth.x500 |
|
|
|
javax.security.cert |
|
|
Engagement Model
How can you get a Java SE Embedded 8 VM customized for your target device ?
We have a straight forward engagement model which is implemented in the following steps:
(a) Provide a short non confidential description of your target device and field of use to MicroDoc
(b) Optional: Request an NDA
(c) Provide a detailed description of your HW and OS as well as your constraints and requirements with respect to Java (which Java Profile do you need, do you need graphical I/O etc..)
(d) We will evaluate your information and come back with a suggestion how to proceed
The typical next steps may include:
(e) You send us a copy of your HW and OS including a toolchain to build the VM
(f) We build an evaluation VM for you, perform some preliminary testing and provide it to you for a time-limited evaluation under our standard evaluation agreement.
The potential next steps may include:
(g) Commercial negotiations (NRE, Runtime Licenses)
(h) Product level testing and JCK certification of the VM
(i) Product release for your target device
Contact us via eMail to Christian Kuka (cku @ microdoc.com) or contact us by phone at +49-89-551 969 60 during CET business hours.
This service is rendered to you by MicroDoc Software GmbH, a subsidiary of MicroDoc Computersysteme GmbH
Java is a registered trademark of Oracle and/or its affiliates.
All other trademarks are trademarks of the respective owner.