This is a Title Slide with Java FY15 Theme slide ideal for including the Java Theme with a brief title, subtitle and presenter information.
To customize this slide with your own picture:
Right-click the slide area and choose Format Background from the pop-up menu. From the Fill menu, click Picture and texture fill. Under Insert from: click File. Locate your new picture and click Insert.
To copy the Customized Background from Another Presentation on PC
Click New Slide from the Home tab's Slides group and select Reuse Slides.
Click Browse in the Reuse Slides panel and select Browse Files. Double-click the PowerPoint presentation that contains the background you wish to copy.
Check Keep Source Formatting and click the slide that contains the background you want.
Click the left-hand slide preview to which you wish to apply the new master layout.
Apply New Layout (Important): Right-click any selected slide, point to Layout, and click the slide containing the desired layout from the layout gallery.
Delete any unwanted slides or duplicates.
To copy the Customized Background from Another Presentation on Mac
Click New Slide from the Home tab's Slides group and select Insert Slides from Other Presentation…
Navigate to the PowerPoint presentation file that contains the background you wish to copy. Double-click or press Insert. This prompts the Slide Finder dialogue box.
Make sure Keep design of original slides is unchecked and click the slide(s) that contains the background you want. Hold Shift key to select multiple slides.
Click the left-hand slide preview to which you wish to apply the new master layout.
Apply New Layout (Important): Click Layout from the Home tab's Slides group, and click the slide containing the desired layout from the layout gallery.
Delete any unwanted slides or duplicates.
This is a Safe Harbor Front slide, one of two Safe Harbor Statement slides included in this template.
One of the Safe Harbor slides must be used if your presentation covers material affected by Oracle’s Revenue Recognition Policy
To learn more about this policy, e-mail: Revrec-americasiebc_us@oracle.com
For internal communication, Safe Harbor Statements are not required. However, there is an applicable disclaimer (Exhibit E) that should be used, found in the Oracle Revenue Recognition Policy for Future Product Communications. Copy and paste this link into a web browser, to find out more information.
http://my.oracle.com/site/fin/gfo/GlobalProcesses/cnt452504.pdf
For all external communications such as press release, roadmaps, PowerPoint presentations, Safe Harbor Statements are required. You can refer to the link mentioned above to find out additional information/disclaimers required depending on your audience.
JEP104
JEP 155
Completion based design. Multiple threads getting stalled by one thread. The way round this is to basically pass on the work from a thread that is waiting to the one doing the work. The waiting thread is then free to be reused.
JEP103
JEP150
Internal storage using just the offset in nanosecods from the Epoch. Things like day and date, etc calculated on demand to improve efficiency.
Partial, e.g. March 20th (no year). Not specific
Duration (nanos), period (minutes, days, etc), interval nanos between two points in time.
JEP 184
Modularisation of the Java platform. Since project Jigsaw was pushed back to Java SE 9 some form of modularisation was needed to make the Java platform more flexible. To do this we now have three compact profiles that subset the standard class libraries to allow applications that only need certain APIs to run in a smaller resource footprint.
Compact 1 is the smallest subset of packages that supports the Java language. Includes logging and SSL. This is the migration path for people currently using the compact device configuration (CDC)
Compact 2 adds support for XML, JDBC and RMI (specifically JSR 280, JSR 169 and JSR 66)
Compact 3 adds management, naming, more securoty and compiler support.
None of the compact profiles include any UI APIs, they are all headless.
See also JEP 161
JEP 174
JEP 173
JEP 122
Fluent API
Monad
Question: how are we going to get there with real collections?
We define a Lambda expression as an anonymous function (like a method, but because it is not associated with a class we call it a function). Like methods there are parameters, a body, a return type and even thrown exceptions.
What Lambda expressions really brings to Java is a simple way to parameterise behaviour. The sequence of methods we have here defines what we want to do, i.e. filter the stream, map its values and so on, but how this happens is defined by the Lambda expressions we pass as parameters.
Erased function types are the worst of both worlds
Current fashion: imagine the libraries you want, then build the language features to suit
But, are we explicit enough that this is what we're doing?
This is hard because lead times on language work are longer than on libraries
So temptation is to front-load language work and let libraries slide
We should always be prepared to answer: why *these* language features?
Can also say “default none” to reabstract the method
Start talking about how this is a VM feature
Stream is an interface, but in Java SE 8 we can now have static methods in interfaces, hence Stream.of()
Files.walk will walk a file tree from a given Path argument
Spliterator interface that represents an object for traversing or partitioning elements of a source