And since I'm one of the JSR264 Expert Group (EG) Members this is a good day for me. The JSR264 Order Management API already passed the JCP ballot on August 27th, but getting through all the processes from both the OSS/J Community and JCP does take some time....
On the Xebia blog I posted an entry that describes the core features of the Order Management (OM) API. Make sure you read that one for details and of course you can download the specification and read all details of the API. The JSR264 Java.net page is also a good source of information.
My focus area in the EG was the Technology Compatibility Kit (TCK). Each JSR delivered through the JCP process must include this TCK such that implementors of an API can validate if the API is compliant to the specification. As part of the development of the OM API I started the OSS/J TCK Foundation project on Java.net. Why?
A little background... the Order Management API is part of the OSS/J Family of APIs. This group of API has it's origin in the telecommunications world, but several of the APIs (Order Management included) can also be used outside the telecommunications domain. All OSS/J APIs follow a common set of design principles, for example: all functionality exposed by the API must be available in 3 so-called integration profiles:
- EJB
- XML/JMS
- WebServices
Using the OSS/J TCK Foundation you develop one set of tests and are coded against the interface exposed by the EJB profile. The OSS/J TCK Foundation then enables you to execute these same tests against the XML/JMS and Webservices profiles. The advantages are obvious:
- OSS/J TCK developers can focus on developing tests.
- No need to develop plumping code for XML/JMS and Webservices profiles.
- A consistent set of tests is executed on all three profiles (previous OSS/J TCKs had variations in the tests for the various integration profiles).
- The amount of effort to develop a TCK is significantly reduced.
Currently this OSS/J TCK Foundation is used by the Order Management API TCK (yes, of course I eat my own dog food) and the Fault Management API TCK (so even better, others eat it too ;-)). More OSS/J API have shown interest so I expect that it's use will increase over time.
In the Order Management Expert Group we're counting down the week for the final release of the Order Management API (JSR264). We managed to put out an Proposed Final Draft 2 last week and this is your last chance to provide feedback before the 1.0 release. Feel free to drop us a mail at jsr-264-comments@jcp.org. As posted before, I also posted a summary of the Order Management features here. In the next couple of weeks we'll be ironing out the last details in the RI, TCK and documentation and then we'll release it.
JavaOne 2007 is history for almost a week already and finally I found a little time to post a few of the highlights. I arrived on Sunday and Sunday evening Klaas Jan of the NLJUG (like very year) organized a nice diner for all NLJUG member. This year famous blogger MaryMary also joined. Monday was mostly spend together with Andreas to prepare our BoF session. We had worked on the slideset over the phone, but this was the first time we ran through it face to face and that definitely helped us to make it a bit more smooth and cut some slides to meet the time restrictions. When we registered in the speaker room I finally appreciated the fact that JavaOne attendees had to register themselves for session they wanted to attend. Why,... well now the organization could tell us how many people we could expect: 130+! Most likeliky not all 130 would show up, but it was a bit more than we expected and therefore we decided to cut the 'interactive' parts from the slides. With so many attendees that would get out of control (time wise).
Tuesday started of with the key note. As usual a slick and good produced session with JavaFX (Mobile), RealTime Java 2.0 and the milestone of achieving full open source of Java SE as the highlights. The actual mail notifying the world that Java SE was not fully available as open source was typed in during the key note... never try to type serious text in a demo... it was proven again that this is hard to do.
After a nice Mexican diner Andreas and I prepared for our BoF. We had the best timeslot possible, the first BoF on the first day of JavaOne when everybody still fresh and eager to attend evening sessions. We had a good audience (~80) and the session went pretty smooth. On my employers blog I posted an entry regarding the first part of the session: Order Management and SOA. In a few sentences:
Order Management is a process that is used in all industries and the Order Management API (JSR 264) is an API that can be used in all these industries. It is defined such that it fits perfect in an SOA and many of the concepts that apply to SOA are applied or supported by the Order Management API. This API can help you to reduce you integration costs.
Apart from the content of the session JavaOne is always a good place to meet old colleagues and make new friends. When they mention your session in their blog, it gets even better. By the way, Andreas really proved that he practiced, one of his slides had some example XML code and included a date/time: Tue, May 8th, 2007 20:18:00. This was intended to be the moment when the slide should be presented, guess what? Right on time, pretty impressive. Even more impressive was the fact that someone in the audience noticed this, well done Vincent, you were really paying attention ;-)
Unfortunately I missed the JavaPosse BoF session, it was scheduled after our BoF and we decided that we deserved a beer... and after hearing the podcast I regret that even more. Next year I'll definitely attend it.
Wednesday, Thursday I attended sessions on Ruby which convinced me that I should start playing with it. Especially with the good tool support like in NetBeans. Tor Norbye (The 'Demo Stud' as James Gossling announced him on Fridays keynote) showed of the cool features of NetBeans in a technical session and during Fridays keynote. Back home I immediately installed NetBeans 6M9 and it indeed works really smooth. Code completion is smarter, color coding is much smarter (for example variable names of unused of mistyped variables appear light grey or italic. Immediately notificying you that something is wrong.) You should really give it a try.
The session on BluRay, OCAP (Open Cable Application Platform), RealTime Java were interesting to get a feel for what going on in these areas. Not my speciality, but that's the good part of conferences like JavaOne: you can get a taste of all kinds of technology that you do not run into during day-to-day business.
Now I need to get ready for the next conference, Telemanagement World in Nice.
With JavaOne coming up there are lots of announcements, here's another one: JSR 264 Order Management is released for public review (download).
I'm participating in this expert group for a couple of months now and it's fun. You get to work with a lot of interesting people and ... at "interesting times", the standard weekly conference call is at 06:00 AM in my timezone ;-) Feels good that the API is now for public review, we're all interested in your comments, feel free to mail them to jsr-264-comments@jcp.org. For more information regarding JSR-264 refer to https://jsr264-public.dev.java.net/nonav/jsr264/.
Next up are the TCK and RI, I'm currently doing some proof of concept work for the TCK.
Thanks to Wilfred we (Wilfred, Marcel and me) were sitting first row during the first keynote session at JavaOne. One of more funny things was the celebration of the 10th birthday of Java. Most of the original Green team that created the first version of Java was present and was invited to come onto the stage. When James Gossling and Scott Mcneally invited the Green team, all people sitting next to us on the first row stood up and walked onto stage... now that was very tempting... what would have happened if we would have simply did what the rest of the row did?
During this first key note there were a couple of interesting announcements. One cool one was the fact that Solaris DTrace will now also work for Java applications. So if you ever wonder why your Java application is not performing, consider using DTrace. If will give you detailed insight into all the system calls you app is doing and using that you'll be able to identify the bottlenecks.
The interesting announcements on the enterprise level were the open sourcing of Sun's Application Server (Platform Edition) and Sun's JBI (JSR 208) implementation. Both can be found at Java.net. The Studio Enterprise demonstration was interesting, it demo-ed how a service flow could be orchestrated graphically (not sure if the notation was BPMN) and generated a BPEL application of it. The BPEL implementation seemed to be FiveSight PXE since the console said "PXE start" when the application was deployed. Wonder if a BPEL engine will be included in the open sourced JBI implementation.
Labels: jcp
Posts
