|
|
|
|
|
One of the benefits of using JSR-199 in GlassFish is Very Fast JSP compilation: the generated Servlets can be passed directly, in-memory, to javac. But if you really want to see what's going on you have a problem, as shown by this long mail thread: there is no Servlet code to see because writing it to disk would defeat most of the benefits of JSR-199! The solution is easy: ask GlassFish to write the Servlet code go to disk using the keepgenerated parameter. Check out Byron's note for the details. |
|
News from Rajiv, the JSP project at GlassFish:
• Announcement: JSP Project Live We hope to give you news on additional adoption in the near future. |
|
The GlassFish community is composed of many projects; some already existed when we started GlassFish, like JSF, JAXB and JAX-WS (nee JAX-RPC). Others came later but were separate from the beginning, like Jersey, and others spawned from GlassFish like Grizzly. Separate projects encourate reuse and contributions but are more work and can create confusion so we wait before creating them. We have received several requests for a JSP project so we are going to create one. Please let me know (or just post here) if you are interested in this project. |
BTW, I found the JSP Duke in the April, 2000 JSP 1.1_a errata. Two other early serving dukes are here and here
|
There is a good thread on memory use on GlassFish at the USERS alias. In the use-case described, the main issue was JSP compilation. Memory consumption is much lower (and compilation is also much faster) in GlassFish v2 using JDK 6 because JSP compilation is done in-memory, using JSR-199 and without forking. Forking can also be avoided in GF v1 and in earlier JDKs with some caveats. Check the mail thread for details. |
Picture is a close up on Core Memory. Ah... the good? old days of core and Punched Cards! Have you ever dropped your deck of cards and had to reorder them? That is what those extra columns in the punched card were for :-)...
|
Sun Java System Web Server 7.0 update 1 is now available for download (the preview version had been available for a few months). New in this release is: • Performance and stability improvements
|
You'll notice that the main features are Java-related. Specifically, the product is now at the Java EE 5 specification level which means that any web application that runs on GlassFish now also runs on Sun's Web Server 7.0 Update 1 (the implementation is actually taken straight from GlassFish). On the more technical side of things, you can use dependency injection in the web tier.
When released in early 2007, Web Server 7.0 enjoyed an excellent review and has been powering a whole new set of demanding web sites (including the one serving you this content). Any question, see the dedicated forum.
|
Last week several of us participated in the very first jMaki Day. We wanted to provide training material including presentations, labs and demos to get folks started. The talks included a session on Web 2.0 technologies, Introduction to jMaki, Introductiion to Phobos, Tools, and State of the Union for jMaki. This set of talks were presented to Sun internal folks mostly because we wanted to keep the number of attendees small and also have the ability to get specific feedack. All material has been made available on the jMaki website here. See my blog and Arun's blog for more details on jMaki day. |
|
Ludo spent the last couple of weeks working on the much asked for Eclipse plugin for jMaki. The plugin is now available and also supports the latest release (v.8.3.1) of jMaki. Ludo also provided some documentation on how to get started using the new Eclipse plugin. Enjoy. |
|
|
If learning how to write Ajax enabled web apps is one of your New Year's resolutions then check out the following blogs. My blog, Building web 2.0 apps with jMaki uses one of the layout templates, glue code to tie widgets together and the injector code to load pages within a div tag to create a web application. The glue code ties the Yahoo Geocoder and Google Maps widgets. The injector is used to load the page containing those widgets in the div tag genereated by layout template and navigation is done using the Dojo fisheye widget. |
Jennifer published two blogs at roughly the same time. Fun with jMaki: Using the Yahoo Geocoder service with the Dojo Combobox also uses the Yahoo Geocoder but she used the Yahoo Map and a combobox to select the city to map. More Fun with jMaki: Getting Data From a Bean shows how to get data from a bean using an EL experssion to a widget (in this case ComboBox). The data is converted to JSON format using the org.json libary.
Finally, checkout the new project jmaki-charting. This friend of jMaki project provides a charting widget which can be added to the jMaki framework. It's open source, freely available and it supports Java, PHP and Phobos.
|
|
jMaki beta 2 release is now available for download. Highlights of this release include a new widget model, improvements to the dynamic container which loads pages on demand and of course, bug fixes. Check out my blog for more details. jMaki is a framework that provides a lightweight model for building Ajax enabled web applications using standards-based technologies. It allows you to use widgets from popular toolkits and includes support for PHP, JSP, JSF and Phobos. |
|
|
jMaki is a framework that provides a lightweight model for reusable Ajax-enabled widgets. The lastest (.5.1) release of jMaki includes:
At the same time, the jMaki NetBeans plugin was updated to include a new stylized JSP wizard. See a previous Aquarium entry for more info. |
|
One of the benefits of using an OpenSource license is to simplify adoption by other F/OSS groups, and, slowly we are getting more customers. |
In the case of Geronimo their Report Card shows a plan to use JAXB 2.0 (or 2.1?). Other modules are listed as multiple options, including JSF 1.2, TopLink Essentials, and JSP 2.1 (used by Jetty). The table is probably not up-to-date; for example, check this Thread on JSTL 1.2.
|
There are two new tutorials that explain how to use jMaki. The first one shows how to use jMaki widgets in JSP pages, the second how to use jMaki widgets as a JSF component. Also see the earlier tutorial that introduces jMaki Components. Thanks to Jennifer for the tip. |
|
Jan reports that Jetty Has Integrated the GlassFish JSP compiler and it has nice things to say about us. The GlassFish Team is actively supporting this reuse, typical of open source projects (see DTrace in Leopard) and it factored out the JSP compiler to make it possible to Use the JDT Compiler in JSP compilations. I expect more cross-project sharing / recombinations in the future. |
Added: Also check out Jan (Bartel)'s blog.
|
Most JSP implementations translate a JSP file into a Java source file and then compile it, which means that Java compilation speed is a key factor in the JSP development experience. Recently Jan reported on how to use the JDT Compiler to get a substantial improvement but Kin-Man now reports even Better Results. Kin-Man updated the JSP GlassFish compiler to dynamically use the JSR-199 APIs when running on Mustang so it can bypass both ant and the file system. The results are very good: JSP compilation is around 10x faster and the JSP test-suite is now running 3.5x times faster! |
This is already checked into GlassFish V2 and will be in the next promotion b11, and in the first milestone. And Kin-Man also has further improvements to try out...
|
Tomcat 5.5 by default uses the Eclipse JDT Compiler instead of the javac from Sun's SDK and one of the requests on Project GlassFish has been to be able to use JDT for JSP compilation. Jan just modified Jasper to accomplish this; read the instructions from Jan's Blog Entry. |
BTW, Kin-Man is, separatedly, working on allowing Jasper to use the Mustang standard javac API, which should give substantial performance improvements; stay tuned.
