Claesson.org

A little bit late but here is it - TechCast Live: NetBeans IDE 6.9 - JavaFX Composer and OSGi. I did the demo of JavaFX Composer - it shows how to use Ai to adjust existing image, JavaFX Production Suite to export the image as fxd (vector graphics format which can be consumed by JavaFX) and NetBeans JavaFX Composer to make an animated application. Skip to about 6:10 for the demo.

TechCast Live

NetBeans 6.10 M1 is available for download.  JavaFX Composer Data Sources have been significantly improved in NetBeans 6.10 M1

• The API has been re-written (old API is still available for compatibility reason)
• Improved Query Language
  
• New Data-sources aware components based on original JavaFX 1.3.1 components. Use of new components makes the whole developer workflow more intuitive and faster
• Write support - it is possible to generate read-write forms and save the data back to the date provider
• Data validation support
• Updated samples

Read the full story here:
http://wiki.netbeans.org/JavaFXComposerNewInM8

8 Milestones of JavaFX Composer so far! Since M3 all public, M5 was the first milestone included in the official NetBeans distribution (6.9 Beta). Thank to all members of the team.

Mårten Mickos, the CEO of Eucalyptus and former CEO of MySQL AB, will be back on stage as the closing keynoter on September 19th at MySQL Sunday, one of the community events at the start of Oracle Open World 2010.

The opening keynote will be delivered by Edward Screven, Chief Corporate Architect at Oracle.

MySQL Sunday has a very rich schedule, and by the registration numbers it looks like it's going to be packed.

8月は北半球(の大半)において一般に活気のない月であるとされますが、今年のGlassFishチームにとってそれは程遠いと言えます。 いくつかのイベント(7月開催でないJavaOne 2010、大合併、GlassFish 3.1の目標スケジュール)が異例であったのですが計画され、一方で予期しないこともいくつかありました。 時折、カリュブディスとスキュラの間を航海しているような心地に襲われ、少し助けが欲しくなることも・・・

これらの気晴らしは余所にして、GlassFish 2ならびにGlassFish 3ファミリーのリリースが続いています。

GlassFish v2ファミリーにおいては、我々は法人向けのパッチリリースを続けています。 最新版はGlassFish 2.1.1 Patch 7であり、旧パッチと同様、GlassFish 2.1 Patch 13かつSJS AS 9.1 U2 (GF v2 U2) Patch 19でもあります。 このパッチは51の不具合に新しく対処し、累積でGlassFish 2.1.1から190のバグが修正されています。

仲間のブログであるGlassFish For Businessは全てのオラクル(および以前のサン)のリリースを記録しています。 特に、GlassFish v2ファミリー概要とGlassFish 2.1.1 patch 7詳細の記事は要チェックです。

パッチの究極の供給源はSunSolveですが、GFBの記事にはそこへのリンクもあります。 なお、パッチはMyOracle Supportからも利用可能です。

GlassFish 3ファミリーにおいては、Milestone 4が完了し、近々公開の予定です。 この次のリリースはMilestone 5ですが、こちらはJavaOne特別版で・・・、JavaOneにお越しいただいた方に詳細をお話しします。 J1開始直前の9月19日、日曜日のコミュニティイベントおよびパーティもお忘れなく。

Tim's Validation API (which is in the "ide" cluster in your NetBeans IDE installation directory), in action in an OutlineView:

And in the Properties window:

To achieve the above, you need to create an InPlaceEditor for your Property. (In the example above, I use a JTextField.) Within the InPlaceEditor's constructor, I simply have this: ValidationPanel panel = new ValidationPanel(); ValidationGroup group = panel.getValidationGroup(); group.add( textField, Validators.REQUIRE_NON_EMPTY_STRING, Validators.NO_WHITESPACE, Validators.URL_MUST_BE_VALID);

...which is copied from here:

http://netbeans.dzone.com/news/how-quickly-add-validation

By the way, thanks Henry Kleynhans in Johannesburg for the above idea!

Oracle Solaris 11 is the future of enterprise IT, that is now clear.

Still, we need to wait a year until it is officially released. What can we do now? Well, quite a lot, it turns out. Even if the preview version (due later this year) hasn't been relased yet, there are a lot of things you can do to prepare for the big OS upgrade.

Here's a list of 11 things you can do now to start enjoying the benefits of Solaris 11, get ahead of your system peers and be a part of the future of Solaris now!

#1: Check out a Preview of the Preview

If you've been following the OpenSolaris project, then you no doubt have noticed, that it already is a preview of the next version of Solaris. Therefore, OpenSolaris 2009.06 is technically a preview to Oracle Solaris 11.

Want something more recent? Download Developer Build 134 of OpenSolaris, which is the most recent publicly available OpenSolaris developer build.

That should give you something nice to play with until the official Preview of Oracle Solaris 11 becomes available.

#2: Find Your Hardware On The Compatibility List

A lot of hardware has been tested with OpenSolaris already, it is documented on the Oracle Solaris Hardware Compatibility List. You'll likely find a lot of popular server equipment there.

Even if at first you don't find your exact hardware component, it's worth searching for your hardware's chipset or a close relative. Most of the time it's close enough to run OpenSolaris on.

And if you find new hardware that works well with OpenSolaris, then feel free to submit it to the HCL so others can benefit from it.

#3: Virtualize Your Hardware For Oracle Solaris 11

If you want to get familiar with new technologies that aren't ready for prime time yet, it's preferable to use a virtualized server. This also allows you to preview Oracle Solaris 11 on your laptop without having to reinstall everything.

Oracle has two great virtualization technologies that you can use for free:

• VirtualBox is hands down the best solution to rapidly try out, evaluate and develop for Oracle Solaris on your workstation or laptop. I use it every day to run a preview of Solaris 11 as my regular work environment, running on my Macbook Pro.
• For more serious server environments, there's also Oracle VM for x86. This is a free, enterprise-class, certified virtualization solution that comes with advanced features such as HA clustering, management software, live migration and much more.

Download one of these now and get started with your Solaris 11 preview installation!

#4: Join a Local OpenSolaris User Group

When trying out new Solaris features, it's good to be in touch with people like you. That's where OpenSolaris User Groups come in. And don't get hung up on the naming details between "OpenSolaris" and "Solaris 11". It's all Solaris, and its all about great OS technology!

There are several dozen Solaris groups world-wide to choose from. They meet regularly and chances are that one is near your town already. Typically, they host interesting presentations on new technologies, install parties or just informal gatherings where you can discuss any Solaris related news over a beer or two.

#5: Join One or More Solaris Related Discussion Lists

Every user group, every major Solaris technology and almost every other Solaris related topic can be found in one of the many OpenSolaris discussion lists.

The majority of discussions on OpenSolaris.org mailing lists are centered around technology topics and the mailing list members are very approachable. Many of them work at Oracle and are eager to help out with understanding Solaris, solve technology problems or take feedback and helpful suggestions.

So check out your favorite topics and join one or more mailing lists now!

#6: Get Ready for the Future of Solaris Networking with Crossbow

Project Crossbow provides the building blocks for network virtualization and resource control. It was introduced with OpenSolaris 2009.06 and it will completely change the way you think about networking.

Crossbow lets you create new virtualized NICs with a single command. You can attach it to a Solaris Container, wire it up to a virtualized switch or route in and out of it. You can create as many virtualized interfaces as you want, measure, control and limit traffic through them and take complete control of all things networking in your datacenter infrastructure.

Check out the Crossbow website for an introduction to the topic, view the documentation, join the crossbow-discuss mailing list and try out some examples.

#7: Get Ready for the Future of Storage Virtualization with COMSTAR

Another landmark project in Solaris is COMSTAR, which is a software framework that enables you to turn any OpenSolaris host into a SCSI target that can be accessed over the network by initiator hosts. Together with ZFS volumes (ZVOLs), this is your ticket to storage virtualization: Create arbitrarily sized, highly available, integrity proofed and self-healing LUNs, then share them on the network via iSCSI, fibre channel or other protocols.

On the internet, nobody knows your dog is the LUN, they say.

Seriously, check out the COMSTAR pages, read the COMSTAR documentation, check out some COMSTAR + ZFS demos and join the OpenSolaris storage discussion mailing list.

#8: Check Out Some Advanced ZFS Features

While we're at it: A lot has been integrated into ZFS since OpenSolaris 2009.06 that you should be prepared for when looking forward to Solaris 11.

The biggest is probably Deduplication but there are numerous other enhancements that are in the works. Some insight into ZFS enhancements are available in the ZFS: The Next Word talk.

And of course, it never hurts to join the ZFS community.

Because the truth is: ZFS has never been better than now, and its future has just started!

#9: Familiarize Yourself With the Image Packaging System

In OpenSolaris, there's a major effort at redesigning the packaging, install and patch system. And it is expected that this will continue throughout the development of Solaris 11, too.

Two projects are important here: The Image Packaging System (IPS) and the Caiman installer. If you want to learn how to write software for Solaris 11, install it, patch it, both manually or automatically over the network, then it's a good idea to study these two projects.

Granted, there's still a lot to do, and there are some interesting discussions around what IPS can and cannot do, but however you put it, now is the time to join these communities, participate in discussions and provide your feedback.

Oh, and while you're at it, check out the Software Porters community as well, because a lot of packages are waiting to be integrated with IPS and Solaris 11, too.

#10: Get Ready for Migrating Solaris 10

The Solaris branded zone technology has recently gotten an interesting feature: Now you can create Solaris 10 branded zones inside OpenSolaris. This provides an elegant, efficient and convenient way for easily migrating your existing Solaris 10 deployments into more recent versions of Solaris.

More information can be found in the Solaris10 Branded Zone Developer Guide and by joining the zone community.

#11: Get Ready for Oracle OpenWorld

Oracle OpenWorld 2010 on September 19-23 is definitely the place to be if you want to learn more about Oracle Solaris 11, Oracle Sun Systems and anything else about Oracle as well.

Don't miss it if you're lucky enough to be in the San Francisco area, otherwise follow the event on the web or visit Oracle's customer events throughout the world that are scheduled to happen right after OpenWorld. Who knows, we might just bump into each other!

How do YOU prepare for Solaris 11?

These are just some suggestions for preparing for Oracle Solaris 11 now. I'm sure you'll find a lot more.

What are you doing to prepare for Solaris 11? What features do you look forward to? Make yourself heard in the comments section!

Oh, and don't forget to add this blog to your favourite reader and stay tuned for more Solaris 11 related posts.

var flattr_uid = '26528'; var flattr_tle = 'Top 11 Things You Can Do Now To Prepare For Oracle Solaris 11'; var flattr_dsc = '<a href="http://constantin.glez.de/blog/2010/08/oracle-solaris-11-future">Oracle Solaris 11 is the future of enterprise IT</a>, that is now clear.Still, we need to wait a year until it is officially released. What can we do now? Well, quite a lot, it turns out. Even if the preview version (due later this year) hasn't been relased yet, there are a lot of things you can do to prepare for the big OS upgrade.Here's a list of 11 things you can do now to start enjoying the benefits of Solaris 11, get ahead of your system peers and be a part of the future of Solaris now!'; var flattr_tag = 'future,Knowhow,Learning,Oracle Solaris,Oracle Solaris 11,solaris,technology,Unix'; var flattr_cat = 'text'; var flattr_url = 'http://constantin.glez.de/blog/2010/08/top-11-things-you-can-do-now-prepare-oracle-solaris-11'; var flattr_lng = 'en_GB'

• Airbus startet A350-Produktion in Deutschland
• Boeing Shakes Up 747-8 Program Management
• IBM Names Itself Worst Company For Fixing Critical Software Security Bugs
• In Defense of Links, Part One: Nick Carr, hypertext and delinkification - Scott Rosenberg's Wordyard (tags: links linking hypertext writing internet)
• Warum haben Buegeleisen keinen Ein-/ Aus-Schalter? in der tat eine gute frage ....
• Manual FriendlyARM m2440 (tags: sbc linux arm)
• Mini2440 | S3C2440 ARM9 Board - FriendlyARM (tags: arm embedded hardware mini2440 sbc linux)
• Augenschmalz das iPad ist wirklich praktisch als datengrab
• DevOps - Wikipedia, the free encyclopedia (tags: management development it devops)

From the announcement on the mailing list:

The Grizzly Team would like to announce the release of Grizzly 2.0 RC1 (release candidate).   This goal of this release was a stable core and solid API.  While this is a significant step to getting Grizzly 2.0 finalized, we still have work to do in the area of documentation, performance, and resolving any feedback solicited by this release.

The bits are available on our maven repository under the group ID com.sun.grizzly, versioned 2.0.0-RC1.

Here's some info on the artifacts that are currently available:

• framework (artifact ID: grizzly-framework) : The core Grizzly runtime.
• http (artifact ID: grizzly-http) : HTTP protocol implementation, which contains HTTP Filters and utility classes to work with HTTP artifacts.
• webcontainer (artifact ID: grizzly-webcontainer) :  Lightweight Grizzly web server implementation, which provides high level abstractions based on the entities provided by the HTTP module. While the concept is similar to the Grizzly 1.x web server, it does expand this abstraction idea by providing an API for non-blocking streams to read/write application content.
• websockets (artifact ID: grizzly-websockets) : Web Sockets implementation based on http module.

There are several samples available that demonstrate all of these modules in action.

• Core framework samples [1], [2], [3], [4].
• HTTP protocol framework sample [5]
• Webcontainer samples using non-blocking streams [6], [7]
• Web Socket samples [8]

We're looking forward to hearing back from the community about their experiences using this release (either good or bad).  Feel free to start a discussion on the grizzly mailing lists or send us an issue report.

[1] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/framework-samples/src/main/java/com/sun/grizzly/samples/echo/ [2] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/framework-samples/src/main/java/com/sun/grizzly/samples/udpecho/ [3] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/framework-samples/src/main/java/com/sun/grizzly/samples/ssl/ [4] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/framework-samples/src/main/java/com/sun/grizzly/samples/tunnel/ [5] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/http-samples/src/main/java/com/sun/grizzly/samples/http/download/ [6] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/webcontainer-samples/src/main/java/com/sun/grizzly/samples/webcontainer/blockingadapter/ [7] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/webcontainer-samples/src/main/java/com/sun/grizzly/samples/webcontainer/nonblockingadapter/ [8] https://grizzly.dev.java.net/source/browse/grizzly/branches/2dot0/code/samples/websockets/chat/

This year we are going to show how to use Java ME Location API to build application to track and share current users position. During our HOL participants create a mobile application which uses the Java ME Location API to track a user's friends and display them on a map. Additionally, this mobile application allows the user to exchange status with friends and shows them on a map along with their photos and names. This HOL is aimed at developers who would like to learn how to bind application content with the current position of an application user.

Participants will learn:

How to use Java ME Location API

How to use maps web services in a Java ME application

How to use Java ME Generic Connection Framework

How to use visual tools to design the flow and UI of the application

This application can be used with Yahoo Maps (which we are going to use during HOL) or Google Maps (license restrictions).

Details about HOL:

Thursday: 3:30PM Where My Friends Are: Java ME Location API in Practice
Stream(s): JAVAONE
Track(s): Java ME and Mobile

• S314126
• [HOL]
• Hilton San Francisco/Plaza A

With the engineers cranking new milestones releases of GlassFish 3.1, the screencasts try to follow.
The latest one is discussed on TheAquarium. Here's a direct link to the video.

Last week i've reported about the point that the X-Force numbers regarding unpatched disclosures could be sorted in a different way to yield a completely different view on the data. More interesting is a recent development: After reassessing the data, many of the vulnerabilities had to be sorted into different categories. So the numbers were fundamentally incorrect as well.

The list changed a lot due to this changes: Sun went from 9% high+critical to 0%. IBM leads the pack with 29% unpatched high+critical vulnerabilities without patches. However 22% for Oracle doesn't look that good as well. You will find the updated list in the blog entry " Mid-Year 2010 X-Force Trend and Risk Report - Update to Unpatched Vulnerabilities Chart".

当七年前进入SUN时还不是很清楚Sun Club为何物，但是因为原本喜欢打网球的缘 故（大学毕业后间断数年）开始积极参加每周的网球活动，遇到了雨天偶尔也参加 羽毛球的活动,在这个过程中我结识了很多同事，迅速完成了从新员工的转化。 后来在03年11月份第一次参加了Outing Club的活动去了海南，居然在那里还 看到了世界小姐选美比赛的实况，美！在随后的数年间，尽管工作起起伏伏，在 Club中我从一个活动的积极参与者变成了组织者，从Tennis Club主席到ERI Sun Club主席，这是我在加盟SUN之前没有想到的，颇有一点无心插柳的意思。更加让我意外的是在这样的一天，太阳就要落山了，ERI Sun Club也将随之消失。尽管我有足够的时间准备着抵达终点，可真的到了，心中还是不免有些怅然。。。

人生不如意十之八九，今天算是一天吧！在我的sunrise的Blog中，让我们一起见证sunset吧！

Currently SGESv2.x supports RMI-IIOP loadbalancing. But this loadbalancing is based on the InitialContext:when a new InitialContext() is created, a load balancing decision is made, binding that InitialContext to a replica, until the replica fails, at which point all requests using that InitialContext fail over to a new replica.
Refer : http://docs.sun.com/app/docs/doc/820-4341/fxxqs?a=view

The PRLB feature aims at addressing the requirement, where for the same EJB object of a stateless session bean, the method calls to the bean needs to be loadbalanced. An EJB instance is represented (in GlassFish) by a dynamic stub, which contains a reference to the endpoints. The loadbalancing of the calls happens in a round robin fashion. The list has the lifetime of the stub and anything
that clears or resets the list starts the PRLB process all over again. Hence, ideally an ejb lookup() would reset the list and restarts the
PRLB process.

Configuration:
In sun-ejb-jar.xml, a new optional boolean child element for the ejb element "per-request-load-balancing" is introduced.If per-request-load-balancing is set to true for a stateless session bean, per request load balancing will be enabled for invocations made through Remote EJB 2.x and 3.x client invocations on that bean. If set to false or not set, per request load balancing will not be enabled for the bean. The per-request-load-balancing element only applies to stateless session beans. Use of the element on other bean types will result in
a deployment error.

For example :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.1.1 EJB 3.0//EN" "http://www.sun.com/software/appserver/dtds/sun-ejb-jar_3_0-1.dtd">
<sun-ejb-jar>
<enterprise-beans>
<unique-id>1</unique-id>
<ejb>
.
.
<per-request-load-balancing>true</per-request-load-balancing>
.
.
</ejb>

The sun-ejb-jar.xml needs to be updated as above and EJB jar needs to be redeployed.

As a verification check, you can verify that this is configured properly by looking for the following (FINE, in the CORBA logger) log message when the EJB is loaded:

"Setting per-request-load-balancing policyfor EJB <EJBNAME>"

Important requisites for PRLB feature to work :

1. The "per-request-load-balancing" property needs to be enabled in sun-ejb-jar.xml
2. If the client you are using is a Web Client, both EJB and Web Client needs to reside in the same JVM.

Client Example:

public class EJBClient {
    public static void main(String args[]) {
    :
    :
    :
    try {
    // only one lookup

    Object objref = initContext.lookup("test.cluster.loadbalancing.ejb.TestSessionBeanRemote");
        myGreeterRemote = (TestSessionBeanRemote)PortableRemoteObject.narrow(objref,
                                            TestSessionBeanRemote.class);

    } catch (Exception e) {
    :
    }

    for (int i=0; i < 10; i++ ) {
    // method calls in a loop.
        String theMessage = myGreeterRemote.sayHello(Integer.toString(i));
        System.out.println("got"+": " + theMessage);
        }
    }
}

It just came to my mind that my virtual UX blog contains 100 articles. Hurray!

PS_ In fact I have 134. But the list displays just 100 max. Who knows how to return more than 100 items by $model.weblog.getRecentWeblogEntries?

I'm seeing as I hear more and more from customers that few of them are aware that DBXtool has come back as an independent, standalone tool in Studio. I would hate for this lovely tool to be Studio's best kept secret , so this blog is a note to get the word out, but while I'm at it, let us look at it in somewhat greater depth.

History of Dbxtool: OK, its inevitable that the re-emergence of DBXtool is tied to past history. So, lets peek a bit at the last 20 years. I remember back from the mid to late 80s when Sun's introduction of a desktop Windowing system called SunView featured a graphical debugger called dbxtool. dbxtool was a simple, easy to use interface to the source-level debugger, dbx. [I am amazed that you can still find references to it on the web!]. Personally, I found dbxtool to be a huge productivity enhancer and used it more than any other graphical productivity application (other than perhaps email!). In particular, I remember cool commands like "button expand" that let you create your own buttons in the panel. In the early 90s, Sunview evolved into a short-lived but very interesting project called NeWS. But more significantly, as Sun upgraded to the Open Look feel, dbxtool was rewritten for the new look-and-feel, so that events like Breakpoint-controls and Execution, Stack and Data display properties all had their own menus. From here on, dbxtool (now called simply: Debugger) was increasingly integrated into a programming environment which included editors-of-choice (vi, xemacs, nedit), a source browser, a build system and a source code management system (called Teamware). The debugger could still be invoked individually, if so desired, but it was all in the context of a larger toolset called Workshop. Workshop was an immensely popular product in the mid 90s for Sun's developer tools offering and to this day, many of Sun's enterprise customers fondly remember it.
But Sun was also undergoing a lot of change (particularly: Java, in this context) and in a quest to get a state-of-the-art IDE and to allow programmers to use the same tools for Java and C/C++, Sun bought a Czech company called NetBeans. This IDE had its own strong notion of workflow, learning much from the Microsoft and Borland models of tightly-integrated edit-compile-debug cycle support. The tools were all tightly integrated and Workshop went through three more name changes before finally settling in on the Sun Studio name(Workshop -> Forte Developer -> Sun ONE Studio -> Sun Studio). The Workshop group integrated C/C++ language support into NetBeans and thus made this offering equally complete and competitive for C/C++ users as well.
Since the late 90s and throughout this decade, the debugger has lived inside the (NetBeans-based) Studio IDE. Which is great. However, not everyone in Unix likes an IDE. In particular, many of them want simple, standalone tools. Make, SCCS/TeamWare, Source Browser etc. all evolved in Unix/Solaris from this strong need. So, despite a fairly strong undercurrent of demand for a lightweight, standalone tool for debugging, this has been available only through the IDE. Finally, in 2009, Studio released a standalone debugger, dbxtool to satisfy this constant demand.

What is in Dbxtool? Three things are different from the debugger in IDE. First, dbxtool is standalone and only loads the modules needed for debugging (and thus has faster startup and is lighter in memory usage). Second, dbxtool can be used to directly act upon a binary without having to create a project. Finally, you can embed dbxtool invocation into shell scripts and driver programs (via ss_attach) and do "dbx-specific" things like debug corefiles, debug process-ids without an executable, etc. Thus dbxtool more closely mimics the functionality in dbx, while preserving the advantages and convenience of graphical look-and-feel.
In dbxtool, you can look at stack traces, register dumps, [dis]assembly of corresponding source, watchpoints, multiple thread execution states, examining variables, and perform extensive expression evaluation.
Among other things that you might not know about, Dbxtool does runtime memory checking, allows for multiple sessions and does remote debugging (Solaris/Linux Client to Solaris/Linux server).

Read more about it from the manpage here . Or from the dbxtool video screencast here.

Finally, here is a screenshot of dbxtool:

In this article I discuss and illustrate a “SOA-less” solution in which the Oracle SOA Suite 11g R2 B2B receives a stream of different HL7 v2 delimited messages types (A01 and A03) using a single inbound adapter. The messages are converted into their “equivalent” HL7 v2 XML messages. I say “SOA-less” because all the work is done entirely within the B2B part of the SOA Suite – no OSB or SOA Composites are involved.

The complete text of the article is availabloe at http://blogs.czapski.id.au/wp-content/uploads/2010/08/07_Oracle_SOA_Suite_B2B_Receiving_Stream_of_

Verifying your Java ME app just got cheaper with a price cut from UTI.

See:

UTI's price cut

Here's a quote: The change is intended to increase the number of Java ME apps in play. Currently, all apps must be certified at one of three testing houses, with developers paying a starting price of 75 euros ($92.91) to test and verify a "simple" application - a sharp reduction on the earlier price. The price cut announce in June was the first change in the UTI's Java ME verification process in the face of the growing popularity of [blah- blah-blah], which runs a subset of Java Standard Edition (Java SE). So, according to the article, UTI's price cut to verify your Java ME app will increase the "number of Java ME apps in play". That's cool. It's nice to be using nice and clean, free and clear of uncertainty, Java ME technology for mobile app development.

Hinkmond

One of my favorite bike builders is Russell Mitchell, owner of Exile Cycles. He designed and his crew builds bikes like the Fat Bloke pictured above. You can buy the bike already built like the movie stars do, or initiate yourself into the world of old-school motorcycling by building it yourself from parts in Russell's shop.

Here's another Fat Bloke that's got something interesting to offer. Migrating from VMWare to VirtualBox with Oracle Enterprise Linux describes how to move a virtual machine from one virtualization platform to another. Kinda like moving your hard drive from one machine to another, as the Fat Bloke puts it. Or swapping out the engine on Exile's Brown Pearl and dropping it into the Hot Rod. Or, God-forbid, a Honda Gold Wing.

The writeup by Fat Bloke the blogger includes these topics:

Preparing to Migrate

Exporting the Virtual Machine

Importing into VirtualBox

Installing the VirtualBox Guest Additions

An Alternative Approach for Advanced Users

My favorite of Russell's bikes is the Silver Bullet, though the Brown Pearl is a close second.

- Rick

This short screencast demonstrates the new application-scoped resources feature available starting with Milestone 4 of GlassFish 3.1 (the demo used promoted build #17). Such resources are bound to a module (war, ear, ejb) and as such they are created on deploy and destroyed when the module is undeployed. They are defined in a file called glassfish-resources.xml (schema-constrained) and shipped with the archive.

These resources are available only from the application they "belong" to which offers some level of security, more configuration flexibility (no resource name collision and different settings for different applications) as well as some level of performance isolation. They overall provide a single click/single deploy experience.

More details such as full demo description, application-scoped vs. module-scoped, location of glassfish-resources.xml and more are available from Feature one-pager (GlassFish Wiki) and Application Scoped Resources (Demo instructions).