In this week just before JavaOne and Oracle OpenWorld the topic “the future of Java” keeps coming up again and again. Today the tweets coming out of the Oracle ACE Director briefing, that some how aren’t affected by a non-disclosure agreement, seem strong and positive: Ranging fromExtremely passionate and very impressive, andincredibly passionate addresstoamazingly open words. Resulting in the statementOracle is on the good side of the force… as far as Java is concerned. As close as we mere mortals can get at this point in time…
After my keynote, there is no longer any confusion about the Java feature roadmap.
To see for yourself what the future of Java looks like, watch Thomas Kurian’s keynote live via the stream on JavaOne and Java Develop. To be continued…
Note that the Java Champions have joined the Oracle ACE Directors. As was stated here this significantly raised the number of Eclipse users
In the 10g release of Oracle SOA Suite you could set properties to instruct web service calls to go via SOAP or not. If you were calling services on the same server or domain you could gain some performance with a native call and avoiding the SOAP overhead. To do this you would set the optSoapShortcut property.
With SOA Suite 11g on WLS SOAP optimization is automatically configured. In the scenario where you upgraded to 11g R1 and are using this optimization shortcut approach, you should specify the Server URL in the SOA Infrastructure Common Settings. Optimized calls are only active when the host name value (referred to as WSDL URL in the composite.xml) matches the Server URL.
To configure the SOA Infrastructure Common Settings choose from the SOA Infrastructure Menu > SOA Administration > Common Properties. As shown in the screenshot. Other access ways to this configuration screen are described here.
Enter the server URL in the Server URLs section. This URL is published as part of the SOAP address of a service in the concrete WSDL file. Either set both values to the host name (for example, myhost) or to the full domain name (for example, myhost.domain.com). If these values do not match, a regular SOAP call is performed instead of an optimized local call.
One of the scenarios that you have to set the Server URL in order to use the optimized local call is after a migration of AIA to AIA 11g R1.
Many of the arguments that have traditionally been brought forward in favor of Spring are invalid or outdated, because they target disadvantages of J2EE 1.4 and prior versions, rather than Java EE 5/6. … the original argument that this is not supported by Java EE is simply gone, and the remaining argument, if present, is much weaker.
If you’re in a position where evaluating these alternatives read the entire blogpost. Generally speaking there is no best way to go. Both are viable frameworks for writing Java applications.
The choice should be made by taking into account the particular requirements and technology strategy of the organizations building and using the application.
If there’s an opportunity we’ll see if we can come up with some rules of thumb for the selection.
Recently I was going through an SOA Implementation Survey when I saw the question as shown in the screen-shot. Well I’ve always been under the impression that Microsoft does have an Application Platform (although I must admit even after Google-ing I’m not sure what it is exactly), even for SOA. Did I miss something or is it occasionally just hard to come up with a good survey? Please leave your thoughts in the comments.
Few days ago a colleague published an interesting blogpost on jBPM, JPA, and Hibernate. The post was noticed by Tom Baeyens, who until late March 2010 was the project lead for jBPM at JBoss.
Of course JBoss restates their commitment to advancing the jBPM project, but it will be very interesting to see what will come from Tom Baeyens’s new initiative…
For a lot of us the migration to Windows7 will be the first time we get easy access to a 64-bit desktop OS. One of the first things after an upgrade like that is to get your tools, like in my case JDeveloper, working again. First step is to download the jdevinstall jar, and the Sun JDK. The installation worked fine:
1
java -jar jdevstudio11112install.jar
Running JDeveloper on 64-bit JVM
Running JDeveloper with the 64-bit JVM resulted in an error:
1
2
3
Unable TO launch the Java Virtual Machine
located at path:
C:\Java\jdk1.6.0_18\jre\bin\server\jvm.dll
A solution is to use the 32-bit JVM. To do this change the SetJavaHome in thejdev.conf that is located in the {JDEV_HOME}\jdev\bin\jdev.conf.
1
SetJavaHome C:\Java\jdk1.6.0_18_x86
Where the jdk1.6.0_18_x86 is a 32-bits JVM version.
After installing JDeveloper 11G successfully, we encountered the following error while starting JDeveloper:
Unable to create an instance on the Java Virtual Machine located on c:\jdeveloper11g\Middleware\jdk160_05\jre\bin\client\jvm.dll
Using Google and Oracle Support showed us that the virtual memory for the PC was not set to level that allowed the JVM to initialise. The solution is to increase the virtual memory or swap area. To do this on Vista:
The webcast of the SOA and Integration strategy was a few days later available as the overall strategy. You can find the entire webcast here.
SOA Platform
The combined Oracle Sun solution focus boils down to the following bullets:
Oracle SOA Suite continues as the strategic product.
Sun JCAPS continues to be supported and maintained
GlassFish ESB continues as an open source project
A bridging technology is planned to support collaboration between JCAPS and Oracle SOA Suite.
Key functions from the Sun SOA products will be incorporated in the Oracle SOA products.
Portal technologies
Oracle WebCenter stays the strategic portal offering. Support for both GlassFish Web Space Server and Sun Portal Server will be continued. An upgrade path to WebCenter is planned for both. The IP (Intellectual Property) for Sun’s Web Space Server will be released into the Liferay open source community.
