Google App Engine (GAE) versus Amazon Web Services (AWS) The most fun part of developing usually comes in the first 33% of the project life cycle. Creating that rapid prototype that demonstrates your idea is where most of the fun is. From that point on, the excitement of the project nose dives as you start looking at where you are going to run the darn thing, and making sure your system is scalable enough to handle its own success. jetty - Jetty WebServer Jetty provides a Web server and javax.servlet container, plus support for HTTP/2, WebSocket, OSGi, JMX, JNDI, JAAS and many other integrations. These components are open source and available for commercial use and distribution. Jetty is used in a wide variety of projects and products, both in development and production. Jetty can be easily embedded in devices, tools, frameworks, application servers, and clusters. See the Jetty Powered page for more uses of Jetty.
From JavaCC Grammar to NetBeans Code Editor You can get pretty far without much coding, if you start off with a JavaCC grammar file and want to end up with an editor for your language, as these two new tutorials show: These tutorials are based on some notes in the Wiki, created by various NetBeans Platform developers. That document should now be considered obsolete and the above two documents replace them. More features will be described and the features described so far will be expanded. AWS CloudFormation AWS CloudFormation gives developers and systems administrators an easy way to create and manage a collection of related AWS resources, provisioning and updating them in an orderly and predictable fashion. You can use AWS CloudFormation’s sample templates or create your own templates to describe the AWS resources, and any associated dependencies or runtime parameters, required to run your application. You don’t need to figure out the order for provisioning AWS services or the subtleties of making those dependencies work. CloudFormation takes care of this for you. After the AWS resources are deployed, you can modify and update them in a controlled and predictable way, in effect applying version control to your AWS infrastructure the same way you do with your software.
PHP Cloud Zend cloud solutions offer affordable pricing (hourly or monthly) Cloud computing solutions level the playing field for developers and small teams. For a low monthly investment, you have access to infrastructure that was previously only available to the shops with deep pockets. A full Zend Server environment is available starting as low as $29 a month with Amazon Web Services. Plus, as your application takes off, you can grow your Zend cloud image and only pay for what you need. Blazing performance for your PHP apps El Libro para Principiantes en Node.js» Un tutorial completo de node.js Sobre el Tutorial El objetivo de este documento es ayudarte a empezar con el desarrollo de aplicaciones para Node.js, enseñándote todo lo que necesites saber acerca de JavaScript "avanzado" sobre la marcha. Este tutorial va mucho más allá del típico manual "Hola Mundo". Status Estás leyendo la versión final de este libro, es decir, las actualizaciones solo serán hechas para corregir errores o para reflejar cambiar en nuevas versiones de Node.js. Las muestras de código de este libro están probadas para funcionar con la versión 0.6.11 de Node.js.
WebSphere Application Server - France - Français - Produits Accélérez la distribution des applications de manière plus productive, plus fiable, plus sûre et plus maîtrisée IBM Impact 2014The Venetian, Las Vegas, NV | Avril 27 - Mai 1 IBM WebSphere Application Server propose des solutions pour mettre en place un environnement d'exécution de serveur d’applications Java plus rapide et plus flexible, avec une fiabilité et une résilience accrues. Ce logiciel prend en charge des environnements monoserveur et des configurations de taille moyenne, ainsi que des applications Web dynamiques exigeant un groupement de niveaux Web sur plusieurs instances de serveur d'application. WebSphere Application Server vous aide à :
It is what it is » Blog Archive » JSON to Java with JDK6 There are multiple frameworks for transforming a JSON expression to a Java object tree, but the Java Platform does not come out of the box with some javax.json package (I heard there are plans for that). Today I will show that you can easily transform a JSON expression to a simple Java object tree (map, arrays, primitive wrappers and string) with Java 6 and no additional framework. Obviously, it may not be the best way to proceed, specially when it comes to speed, security or java mapping.
JOnAS OpenSource Java EE Application Server - Main - WebHome The OW2 development community includes many academic institutes (Grenoble University, INRIA, LIFL, Peking University, UPM, ...) working with JOnAS; this fastens technology transfers and make JOnAS a top level product in term of technology innovation. JOnAS 5 is designed with an OSGiTM based services architecture to provide a dynamically adaptable application serverJOnAS implements the full Java EE 6 Web Profile execution stack and provides, with EasyBeans, an efficient, pluggable and easy to use EJB3 containerThe OW2 JASMINe project contains tools for creating, deploying and monitoring JOnAS clusters; it will include self-management features Read the White Paper for details about these aspects. JOnAS is a mature project (started in 1998), providing a production ready application server, already used within many critical operational applications. Meet the users' needs
353 Status: Active JCP version in use: 2.8 Java Specification Participation Agreement version in use: 2.0 Description: The Java API for JSON Processing (JSON-P) JSR will develop a Java API to process (for e.g. parse, generate, transform and query) JSON. Expert Group Transparency: Public Communications Issue Tracking Updates to the Original JSR Top 7 Features in Tomcat 7: The New and the Improved — Developer.com Tomcat 7 introduced a number of new features as well as enhancements to existing features. Several articles list the new Tomcat 7 features, but most don't explain them in detail, critique them, or provide working code examples. Rather than just list the new features, this article will identify the seven most notable Tomcat 7 features and enhancements, critique them, and present examples of working code that you can use to get a better understanding of each feature/enhancements. The features are categorized as either "New Tomcat 7 Features: Revolutionary Changes" or "Tomcat 7 Enhancements: Evolutionary Changes" as follows:
Wicket Tabbed Application with Guest Book I took the "Tabbed Application" sample provided by the NetBeans Wicket plugin and integrated Jeff Schwartz's GuestBook (see yesterday's blog entry for details on that) into it (click to enlarge the images below): The application now looks like this, i.e., note the new panels package and the TabbedPanelPage class (from the abovementioned sample), which hooks everything together: Without a doubt the most difficult thing was figuring out how to display static resources, i.e., the image in the first tab. In the end, I set up a specific location for all static resources, i.e., within the 'web' folder: When you build the project, the 'static' folder is now right at the top (though it could be anywhere, depending on how the 'ignorePaths' parameter is set below): And then in the web.xml file, take note of the "ignorePaths" parameter:
Selecting Your Java EE 6 Application Server The number one question I get asked is: ‘Which Java EE Application server should we use?’. With the growing adoption of Java EE 6 new compatible application server get certified. The current official compatibility and certification matrix lists 12 different products certified for the Full Profile, the Web Profile or both. If you are going to start a new project on a green field which decision would you make? Here is what I do trying to narrow the solution space down.
Loosely Coupled Wicket The next step in the Wicket example I've been looking at, which currently looks as follows... ...is to make the panels "Welcome Page", "About Page", and "Guest Book" loosely coupled from the web application. I.e., each tab in the web application now comes from a different JAR: There are great benefits to this structure. First of all, the application is now more cleanly organized since each archive (whether it be JAR or WAR) is dedicated to a specific task. You could have a different group of developers working on each JAR, which would be especially useful when the web application becomes very large, where you'll find that each tab (or page) in the application becomes more specialized and distinct from the rest of the application.