Um...Thanx, but I don't think you got the gist of what I was asking.
My point is that blogs should not be considered part of "community", and especially not "official", documentation. The blogs information and availability are not tied in any way to the community.
For example, you may find another opportunity and leave Sun. As soon as you do that, your blog, most likely, simply vanishes. And there goes the information.
You may simply tire of Glassfish and app servers, moving on to another project. That's all well and good. That means you'll be even less motivated to maintain your blog entry should any changes happen to this area in the functionality.
If the entry were on the wiki, the community could maintain the information and keep it up to date. That relieves you of the burden of ever having to deal with it again, since anyone here can update or change the wiki. In fact, if it's on the wiki, the developers and documenters of the project can make a sweep through the wiki and use it as an inspiration for unit tests, or even fold it in to official documentation.
See, when the information is posted on the blog, it's YOUR information, not the communities. By posting it on to the wiki, then the community inherits it and can maintain it. It gains higher visibility within the community, and therefore becomes even more valuable to the community than it already is.
So. I'm just asking if you could post the entry to the wiki, because it's good information. I can't just go to your site and copy paste the text in to the wiki, that's not fair use of your copyright. But YOU can gift that information to the community, since it's your text.
But, by all means, leave the blog link.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=259983