OASIS Stamps Approval on WS-Security 1.1

OASIS has announced the approval of WS-Security v1.1 as an OASIS Standard. The 1.1 specification, crafted by the Web Services Security (WSS) Technical Committee, is highlighted by enhancements to security token support, message attachments and rights management. The 1.0 version became a formal standard in April 2004. The 1.1 specification includes the core WS-Security specification and the Username Token Profile 1.1, X.509 Token Profile 1.1, Kerberos Token Profile 1.1, SAML Token Profile 1.1, Rights Expression (REL) Token Profile 1.1, SOAP With Attachments (SWA) Profile 1.1 and Schema 1.1. With WS-Security, users have a general-purpose method for building integrity, confidentiality and authentication into the message exchanges between or among Web services applications. The protocol fosters integration of technology used to secure messages, including X.509 certificates and Kerberos. Coupled with extensions such as WS-Policy, WS-Trust and WS-Secure Conversation, the specification allows more sophisticated and secure ways for Web services to interact. (Hat tip: Robin Cover’s XML.org Daily Newslink)

Links of interest:

oasis, ws-security, webservices, web+services, saml, swa, x.509, ws-policy, ws-trust, ws-secure, microsoft, oracle, sun

BEA to open-source SolarMetric kodo – EJB 3 Persistence APIs for free

BEA is announcing a plan to open-source SolarMetric Kodo, the JDO/EJB3 based persistence engine that they recently acquired under the project called Open JPA. Open JPA will open source a significant portion of the Kodo code base including the Kodo kernel and the reference implementation of the EJB 3 Persistence specification. Once the EJB 3 specification is approved, Open JPA will be an open source implementation of the EJB 3 Persistence standard under an Apache software license.

Interview Series: Kodo—Towards an Open Source EJB 3.0 Persistence Engine by Jon Mountjoy — Kodo is the popular persistence engine developed by SolarMetric, now BEA. In this interview with Neelan Choksi, we discover some of the details behind Kodo and the announcement to open source a preview of its EJB 3.0 engine.

bea, kodo, solarmetric, ejb3, persistence, open-source, open+jpa, jdo, workshop, eclipse

Daily Del.icio.us for Feb 14, 2006

Google buy MeasureMap

I just got this in my email as I suspect did all of the other beta testers of Measure Map, Adaptive Path’s blog analytics tool.  I really like Measure Map and I blogged about how Google was going to put this space in turmoil by removing the financial upside of these services.  I still use Mint and Measure Map and hope to continue using them to get a better idea on who visits my blog and why.  This looks like a good move for both parties involved.  With Google Analytics, Google took a huge chunk of the market that wanted blog analytics but didn’t want to pay the fee Measure Map would surely have charged.  So what do you do with a decent product that has a fairly active and loyal user-base – dump it for cash and I hope Adaptive Path got some money for it.  Measure Map was pretty innovative with their use of Flash and AJAX together and I hope the Measure Map team continues to flourish at Google.

Here’s the official announcement:

I want to share some important news with our earliest users of Measure Map.

Since its inception, my colleagues and I have seen tremendous potential for Measure Map to influence how people blog, and how they understand participation on the Web. We have always expected it to be big, and as such, our desire was to give Measure Map its start and then send it out into the world to grow and evolve into a strong, meaningful application.

Through the dedication of a fantastic team, along with your tremendous support in the form of feedback, feature requests, and overwhelmingly positive comments, have built a product that is fundamentally different from every other analytics application available today. We’re both grateful and proud.

So I said there was news, and here it is: I’m writing you to announce that Measure Map has been acquired by Google, effective today.  For the near term, you will see no difference in its operations. In the not so distant future, you can expect great things from this acquisition.  We couldn’t be happier to find such an ideal home for Measure Map, and are thrilled at the possibilities.

While this is a milestone for all of us at Adaptive Path, this sale does not affect how we operate, nor will it alter the structure of the Adaptive Path organization. Adaptive Path is still here, stronger than ever, and it will be for a long time to come. Above all, we remain committed to the principle that superior user experience inspires innovation and creates business advantage.

Thank you again for your input, your time, and your support of Measure Map.  Should you have any questions or comments about any of this, please do not hesitate to contact me.

For more information, please see our post on the Google Blog:

[http://googleblog.blogspot.com/2006/02/here-comes-measure-map.html ]

Sincerely,

Jeffrey Veen and the Measure Map and Adaptive Path teams

google, mint, measuremap, measure+map, blog+analytics, ajax, flash

Daily Del.icio.us for Feb 12, 2006

WordPress Upgrade Notes

I finally upgraded my blog to WordPress 2.0 a few weekend ago and am now finally getting around to blog about it. I had blogged previously about issues I had upgrading my blog software but those issues were related to some MySQL upgrade and version compatibilities.  To get around the database issues, I used MySQL Administrator to backup the entire database from the old server and restored it on the new server.  Not sure why that worked, but it did and didn’t create any issues.  In the past, I had backed up the database using MySQL Administrator and then used the MySQL Query Browser to create the new database and insert the data.  I’ve spent a lot of time figuring out the differences between the version of MySQL and the issues I had and will post a lengthy (and boring) blog entry about that in the near future.

After upgrading the database, I upgraded my blog software to WordPress 2.0 and everything worked with the exception of a few minor issues.  One of the biggest issues I ran into was an internal rewrite issue where my blog is deployed under /blog and I had a page whose slug was blogs-i-read.  WordPress was generating a 404 for that page and I fixed this issue by simply renaming the slug to remove the use of the word blog. This issue is fixed in the latest maintenance release of WordPress which currently happens to be 2.0.1.  In addition, I had a problem with the awesome WordPress FeedBurner Plugin that was also related to rewrite rules but Steve Smith had already fixed that problem in the last revision of the plugin.

Since WordPress 2.0 had been working pretty smoothly and 2.0.1 was working in my development area, I applied that today to this site and it worked like a charm.  The biggest improvement (besides the bug fixes) appears to be performance.  It’s too early to tell if the numbers will hold up but here is a performance chart that shows dramatic improvement in performance since the upgrade.

WordPress 2.0.1 Performance
Chart courtesy of GrabPERF

I hope this performance improvement last as WordPress 2.0 was a lot slower than WordPress 1.5 with the WP-Cache plugin. Incidentally, the WP-Cache plugin has not been upgraded to work with WordPress 2.0 but if this performance holds, who needs WP-Cache 🙂

Daily Del.icio.us for Feb 07, 2006

Daily Del.icio.us for Feb 05, 2006