New features for 6.7 include integration with Project Kenai (Like JavaForge/SourceForge but with many more services), a collaborative environment for developers to host their open-source projects; with native Maven support; and with integrations with GlassFish Java EE Server and Hudson Build management server.
This release also offers enhancements for Java, PHP, Ruby, JavaScript, Groovy and C/C++, and more.
Downloads can be found at http://download.netbeans.org/netbeans/6.7
Monday, June 29, 2009
Thursday, June 18, 2009
How to capture wild electricity to provide to mobile instruments
Check this article on how/when to capture electricity provided by Radio/TV/... networks and use it for your phone/laptop/sensor networks...
Intel aims to capture wild electricity
Intel aims to capture wild electricity
Monday, June 1, 2009
Sun has released Netbeans 6.7 RC 3
New features for 6.7 include integration with Project Kenai (Like JavaForge/SourceForge but with many more services), a collaborative environment for developers to host their open-source projects; with native Maven support; and with integrations with GlassFish Java EE Server and Hudson Build management server.
This release also offers enhancements for Java, PHP, Ruby, JavaScript, Groovy and C/C++, and more.
Downloads can be found at http://download.netbeans.org/netbeans/6.7
This release also offers enhancements for Java, PHP, Ruby, JavaScript, Groovy and C/C++, and more.
Downloads can be found at http://download.netbeans.org/netbeans/6.7
Java Dev Kit 6 Update 14 is available
Java SE 6 Update 14 (1.6.0_14)
This release is Windows 7 support-ready and includes support for Internet Explorer 8, Windows Server 2008 SP2, and Windows Vista SP2. New features include the G1 garbage collector, plus performance and security enhancements.
This release is Windows 7 support-ready and includes support for Internet Explorer 8, Windows Server 2008 SP2, and Windows Vista SP2. New features include the G1 garbage collector, plus performance and security enhancements.
Friday, May 22, 2009
Why an Application Grid?
Application servers, those dependable workhorses that run most enterprise Java applications, are rarely a hot topic of conversation these days. As a technology category, the application server appears to be fairly “established” and that the focus has moved elsewhere in the stack, but appearances can be deceiving.
Wednesday, April 22, 2009
Thursday, April 9, 2009
Free Web Application Container (Java, Servlet JSP, ...) on Google Cloud available...
Google has released today a beta of AppEngine for Java, that is a Hosted Web Application Container (Java, Servlet JSP, ...) on the Google Cloud.
Google described it as "With App Engine, you can build web applications using standard Java technologies and run them on Google's scalable infrastructure. The Java environment provides a Java 6 JVM, a Java Servlets interface, and support for standard interfaces to the App Engine scalable datastore and services, such as JDO, JPA, JavaMail, and JCache.":
The Google App Engine uses the Java Servlet standard for web applications. You provide your app's servlet classes, JavaServer Pages (JSPs), static files and data files, along with the deployment descriptor (the web.xml file) and other configuration files, in a standard WAR directory structure.
The Java Virtual Machine runs in a secured "sandbox" environment to isolate your application for service and security. The sandbox ensures that apps can only perform actions that do not interfere with the performance and scalability of other apps. For instance, an app cannot spawn threads, write data to the local file system or make arbitrary network connections. An app also cannot use JNI or other native code. The JVM can execute any Java bytecode that operates within the sandbox restrictions.
The Google AppEngine is limited in the Free version for CPU (50 CPU Hours/Day), Network Bandwith/Usage (10 GB each day), Email (2000 emails a day) but is available through billing additional quota (CPU, bandwidth in/out, storage, and e-mail) if necessary.
Google described it as "With App Engine, you can build web applications using standard Java technologies and run them on Google's scalable infrastructure. The Java environment provides a Java 6 JVM, a Java Servlets interface, and support for standard interfaces to the App Engine scalable datastore and services, such as JDO, JPA, JavaMail, and JCache.":
The Google App Engine uses the Java Servlet standard for web applications. You provide your app's servlet classes, JavaServer Pages (JSPs), static files and data files, along with the deployment descriptor (the web.xml file) and other configuration files, in a standard WAR directory structure.
The Java Virtual Machine runs in a secured "sandbox" environment to isolate your application for service and security. The sandbox ensures that apps can only perform actions that do not interfere with the performance and scalability of other apps. For instance, an app cannot spawn threads, write data to the local file system or make arbitrary network connections. An app also cannot use JNI or other native code. The JVM can execute any Java bytecode that operates within the sandbox restrictions.
The Google AppEngine is limited in the Free version for CPU (50 CPU Hours/Day), Network Bandwith/Usage (10 GB each day), Email (2000 emails a day) but is available through billing additional quota (CPU, bandwidth in/out, storage, and e-mail) if necessary.
Subscribe to:
Posts (Atom)