Apple: iPhone 5 comparing to iPhone 4s after trial in App Store SF, CA.

I have seen the "iPhone 5" and try it hardly in Apple San Francisco retail store, but i didn't admire with it i did't feel the Wow, In my comparing with iPhone 4s there is no difference between them except few things:

1. Bigger screen 4" instead of 3.5" which is not the big deal.
   
   
2. Processor A6 instead A5.
   
   
3. Lighter than 4s by 40 Gm.
   
   
4. All software features are in iOS 6 are the same for both phones.
   
   
5. New EarPods witch could be bought separately and works with 4s.

lastly front camera is 1.4 m instead of VGA in 4s.

for me those changes is not the big deal that makes me changing my mind to buy iPhone 5.

JDeveloper: Ability to perform ODL log analysis

A possibly lesser known feature of JDeveloper is its ability to perform ODL(Oracle Diagnostic Log) log analysis, known as the Oracle Diagnostic Log Analyzer.

This feature allows you to open a diagnostics log file (or use the log file currently in the Log window in JDeveloper) and do a limited yet useful log analysis. For the Standalone WebLogic Server, diagnostics log files are produced by applications running on the specific WebLogic Server instance.

The log files are produced and saved by WebLogic in a directory configured by the WebLogic administrator. This directory defaults to the logs directory under the servers directory for the specific server instance; that is, for a server instance called ManagedServer1 they can be found in servers/ManagedServer1/logs.

The servers directory is located under the specific domain directory. In this blog, we will see how to analyze a diagnostics log produced when running an ADF Fusion web application on a Standalone WebLogic Server. Alternatively, you can run the application in JDeveloper and analyze the log produced in the Log window.

Getting ready
-----------------
You will need a Standalone WebLogic Server domain configured and started. You will also need your Fusion web application deployed to the Standalone WebLogic Server.

How to do it…
-----------------

1. Run the application deployed on the Standalone WebLogic Server, so that a diagnostics log file is generated. Alternatively, if you already have a diagnostics log file to analyze, you can ignore this step.
   
   
2. In JDeveloper, select Tools | Oracle Diagnostic Log Analyzer from the main menu.
   
   
   
   
   
3. Click on the Browse Log Files button (the search icon) to locate the diagnostics file and open it.
   
   
4. Click on the By Log Message tab and specify the search criteria in the Search section. Press the Search button to commence with the search.
   
   
   
   
   
5. In the Results table, click on a value inside the Related column for a log entry of interest and select Related By Request from the context menu.
   
   
   

How it works…
---------------------
Steps 1 through 5 give the details of the process of analyzing a diagnostics log file using the Oracle Diagnostics Log Analyzer feature in JDeveloper.

The Oracle Diagnostics Analyzer is accessible via the Tools | Oracle Diagnostic Log Analyzer menu selection. Once started, you will need to load the specific diagnostics log file to analyze. We have done this in step 3.

You can search the diagnostics log entries using either the By ADF Request or the By Log Message tab and specifying the search criteria. The By ADF Request tab will display only the log entries related to ADF requests made when a page is submitted.

On the other hand the By Log Message tab will search all log entries in the log file by their log level. Moreover, the search criteria in both tabs allow you to search for diagnostic log entries based on their Log Time and based on the message content (Message Id, User, Application, Module, and so on).

The results of the search are displayed in the Results table. The results data are sortable by clicking on the column headers. To display all related log entries, click inside the Related column for a log entry of interest and select any of the choices available in the context menu.

These choices are:

1. Time:
   Filter diagnostic log entries to view all log entries leading up to the specific entry. You can refine the time before the entry using the dropdown.
   
   
2. Request:
   Filter diagnostic log entries to view all log entries for the same web request.
   
   
3. ADF Request:
   Switches to the By ADF Request tab to display the diagnostic log entries in a hierarchical arrangement to show their execution dependencies.
   

JDK7: When Using the SecureDirectoryStream class

The java.nio.file package's SecureDirectoryStream class is designed to be used with applications that depend on tighter security than that provided by other IO classes.

It supports race-free (sequentially consistent) operations on a directory, where the operations are performed concurrently with other applications.

This class requires support from the operating system. An instance of the class is obtained by casting the return value of the Files class' newDirectoryStream method to a SecureDirectoryStream object. If the cast fails, then the underlying operating system does not support this type of stream.

Getting ready
-----------------
To get and use a SecureDirectoryStream object:

1. Create a Path object representing the directory of interest.
   
   
2. Use the Files class' newDirectoryStream method, and cast the result to a SecureDirectoryStream.
   
   
3. Use this object to affect SecureDirectoryStream operations.

How to do it
-----------------

1. Create a new console application.
   In the main method, add the following code. We will create a Path object for the docs directory and then obtain a SecureDirectoryStream object for it.
   This will be used to view the POSIX permissions for the directory.
   
   
2. Execute the application on a system that supports the SecureDirectoryStream class.
   The following output was obtained by running the application on an Ubuntu/Mac system:
   
   GROUP_EXECUTE OWNER_WRITE OWNER_READ OTHERS_EXECUTE GROUP_READ OWNER_EXECUTE OTHERS_READ
   

How it works
-----------------
A Path object for the docs directory was obtained and then used as the argument of the Files class' newDirectoryStream method.
The result of the method was cast to a SecureDirectoryStream class. The getFileAttributeView method was then executed to obtain a view, which was used to display the POSIX file permissions for the directory.

References
---------------
1- JDK7: Part 1- The power of java 7 NIO.2 (JSR 203) (important concepts)

JDK7: NIO.2 - Getting Filesystem information

A filesystem is composed of a hierarchy of directories and files. There is a limited amount of information regarding a filesystem that is normally useful. For example, we may want to know whether the filesystem is read-only or who the provider is. In this recipe we will examine the methods available to retrieve filesystem attributes.

Getting ready
--------------------
To access the method of a filesystem we need to:

1. Obtain a reference to a java.nio.file.FileSystem object.
   
   
2. Use the methods of this object to access filesystem information.

How to do it...
---------------------
1- Create a new console application. Add the following code to the main method of the application.
This sequence displays several fileSystem attributes, including the filesystem provider, file open status, whether the file is available to be read-only, the root directories, and the names of the file stores:

2. Execute the application. Your output will depend upon the configuration of your system. However, it should mimic the output that follows:

How it works...
---------------------
The getDefault method returned the default filesystem used by the JVM. Next, several methods were invoked against this object:

• The provider method returned the provider, that is, implementer of the filesystem.
  In this case, it was a Windows filesystem provider that came bundled with the JVM.
  
  
• The isOpen method indicated that the filesystem is open and ready for use.
  
  
• The isReadOnly method returned false, meaning that we can read and write to the system.
  
  
• We used the getRootDirectories method to create an Iterable object that permitted us to list each root directory.
  
  
• The getFileStores method returned another Iterable object, which was used to display the names of the file stores.
  

There's more...
-----------------------
While we do not normally need to close a filesystem, the close method can be used to close the filesystem. Any subsequent methods executed against the filesystem will result in a ClosedFileSystemException being thrown. Any open channels, directory streams, and watch services associated with the filesystem will also be closed. Note that the default filesystem cannot be closed.

The FileSystems class' getFileSystem method can be used to access a specific filesystem. In addition, the overloaded newFileSystem method will create new filesystems. The close method can be used with these instances.

Filesystems are thread-safe. However, if one thread attempts to close the filesystem while another thread is accessing the filesystem object, the close operation may be blocked until the access is complete.

Refrences
-----------------

1. java.nio.file.FileSystem
2. Java 7 New Features ebook
3. The power of java 7 NIO.2 (JSR 203) (important concepts

Software: Why is virtualization useful?

• Running multiple operating systems simultaneously.
  

  virtualization software allows you to run more than one operating system at a time.
  
  This way, you can run software written for one operating system on another (for example, Windows software on Linux or a Mac) without having to reboot to use it.
  
  Since you can configure what kinds of “virtual” hardware should be presented to each such operating system, you can install an old operating system such as DOS or OS/2 even if your real computer’s hardware is no longer supported by that operating system.

• Easier software installations.
  

  Software vendors can use virtual machines to ship entire software configurations.
  For example, installing a complete mail server solution on a real machine can be a tedious task.
  
  With virtualization software, such a complex setup (then often called an “appliance”) can be packed into a virtual machine. Installing and running a mail server becomes as easy as importing such an appliance into virtualization software.

• Testing and disaster recovery.
  

  Once installed, a virtual machine and its virtual hard disks can be considered a “container” that can be arbitrarily frozen, woken up, copied, backed up, and transported between hosts.
  
  On top of that, with the use of another virtualization software feature called “snapshots”, one can save a particular state of a virtual machine and revert back to that state, if necessary.
  
  This way, one can freely experiment with a computing environment. If something goes wrong (e.g.after installing misbehaving software or infecting the guest with a virus), one can easily switch back to a previous snapshot and avoid the need of frequent backups and restores.
  
  Any number of snapshots can be created, allowing you to travel back and forward in virtual machine time. You can delete snapshots while a VM is running to reclaim disk space.

• Infrastructure consolidation.
  

  Virtualization can significantly reduce hardware and electricity costs. Most of the time, computers today only use a fraction of their potential power and run with low average system loads. A lot of hardware resources as well as electricity is thereby wasted. So, instead of running many such physical computers that are only partially used, one can pack many virtual machines onto a few powerful hosts and balance the loads between them.

Some terminology:
---------------------

• When dealing with virtualization, it helps to acquaint oneself with a bit of crucial terminology, especially the following terms:
  
  1. 
     Host operating system (host OS).
     This is the operating system of the physical computer on which virtualization software was installed.
     
     
  2. Guest operating system (guest OS).
     This is the operating system that is running inside the virtual machine. Theoretically, virtualization software can run any x86 operating system (DOS, Windows, OS/2, FreeBSD, OpenBSD), but to achieve near-native performance of the guest code on your machine, we had to go through a lot of optimizations that are specific to certain operating systems.
     
     So while your favorite operating system may run as a guest, the support and optimize can be applied.
     
     
  3. Virtual machine (VM).
     This is the special environment that virtualization software creates for your guest operating system while it is running. In other words, you run your guest operating system “in” a VM.
     
     Normally, a VM will be shown as a window on your computer’s desktop, but depending on which of the various frontends of virtualization software you use, it can be displayed in full screen mode or remotely on another computer.
     
     In a more abstract way, internally, virtualization software thinks of a VM as a set of parameters that determine its behavior. They include hardware settings (how much memory the VM should have, what hard disks virtualization software should virtualize through which container files, what CDs are mounted etc.) as well as state information (whether the VM is currently running, saved, its snapshots etc.).
     
     
  4. Guest Additions.
     This refers to special software packages which are shipped with virtualization software but designed to be installed inside a VM to improve performance of the guest OS and to add extra features.