Anyone who had an automated SourceForge. release process is soon about to discover that it is broken.
Yesterday, their site status feed announced uploads was offline( 2008-05-15 08:13:49 - SourceForge.net Web Site ) As of 8:00AM Pacific on 2008-05-15, file release uploads have been disabled for a systems upgrade.Today we get the follow up news
( 2008-05-16 04:17:52 - Download Servers ) As of 2008-05-15 at 08:00 Pacific the new File Release System upload interfaces were put into place, replacing the old FTP-based one. Web form, WebDAV, rsync over SSH and SFTP are the new supported methods
If you follow the documentation links you can see that they are right -with no notice other than a 24 hour outage, they've pulled the single existing way to upload artifacts, FTP.
The doc discusses how to mount WebDAV filesystems and use drag/drop or a command line to make releases, and what GUIs there are for SFTP, but there seems to be little thought to how to automate this. Why, for windows users they recommend cygwin, which is the worst of both worlds.
I'm clearly unhappy about this. Ant doesn't have an sftp task, and while I could add it, it would force us to release on 1.8.0 alpha releases. And my coverage in Ant in Action on how to automate the release to SourceForge in Ant is henceforth obsolete. Maybe we should move off SourceForge. If our tools can't talk to it, what choice do we have?
I've upgraded my real+virtual XP boxes to SP3. What's it like? Faster, that's what. The GUI feels more responsive, and the laptop just seems happier. I should be able to get some more months out of the box before corporate IT gets hold of me and downgrades to vista on a widescreen notebook whose area is actually less than my current 1500x1050 laptop monitor.
Despite all the horror stories, it went fairly smoothly. The only troublespot was my own fault. Before SP3 installs, it copies files it is about to stamp on, and it couldn't copy outlook express. At some point in the past I must have got fed up with outlook express and MS messager, being uninstallable parts of the system, and sometimes starting up without my explicit consent (especially messenger). You can't even delete the file without System Protection Manager noticing, and correcting your mistake by putting it back. So I must have turned off the System Protection Manager service and fiddled with the protection of the exes so they werent readable by anyone. This certainly stopped outlook express from running, from msimn.exe from starting and telling me off for not logging in, but SP3 wouldn't back up the existing files, let alone install. I had to stop system protection manager, reset the permissions and then do an upgrade. And afterwards, make the files unreadable again.
No applications have broken, all seems well. What a service pack should be.

SOA and Web services are becoming the most popular key words in nowadays software industry. As a results of that there are so many other technologies and components build around SOA. Among them ESB and Registry can be considered as top of the list. Different people have different definitions for them and there are a number of different implementations out there as well. It is a very hard questions to answer whether the ESB is more important or the Registry when it comes to SOA.
When we considering about SOA registry , which is of course not a new concepts. UDDI is one of the good example for a traditional way of dealing with SOA registry. I can not tell the exact reason but UDDI does not become that popular , that is why people try to find new alternatives for UDDI (based on SOAP , REST etc.. ). So if someone going to implement a new SOA registry then I think he has to address following items,
Service publishing
The implementations should be provide a way to publish services as well as service related metadata such as WSDL , XML Schema and etc..
Service discovery
The implementations should provide a way to discover the service. Say for a example I need to find GPS service , then from the registry I should be able to find out one or more end point addresses for that service. And invoke the service.
Federation
Different implementations should be able to communicate with each other and share , validate data and so on. This is also a key feature in SOA governors.
So no matter how and who is going to implement a SOA registry , they need to address above. IMO without having support for at least first two items of above we can not claim what we have is a SOA Registry.
In addition to those SOA governors is also key factor we need to consider when we implement SOA registry. Governors is more about management side of the services. Service lifecycle , different kind of policy , ensuring various standard like WS-I , and then validating artifact like WSDL , Schema and Policy is also part of SOA governors.
In any given registry we can find two stages deployment time as well as runtime. At the deployment we will be using the registry to store various artifacts , however at the run time we will use the registry to authenticate , authorize , ensuring policy etc...
Geir Magnusson Jr: Given that fact that the statements contained in [link] are given by a Sun employee identifying himself in his job role, can I assume that Sun is interested in taking this discussion public? I think that is a really healthy approach. I think there is confusion about the basic facts and I think clarification will be useful for the community as a whole.
Simon Phipps: The lesson to be learned is that the best way to get Java everywhere was to work with the community rather than expect the community to work with Sun. Let’s hope that lesson sticks and spreads.
There is a discussion going on. At the moment, it appears to be between Sun and the press.
It is the right discussion to be having. Let’s just make sure that the right people have every opportunity to participate.
<parameter name="tcpListenHost">host0</parameter>
<parameter name="tcpListenPort">4000</parameter>
<members>
<member>
<hostname>host1</hostname>
<port>4000</port>
</member>
<member>
<hostname>host2</hostname>
<port>4001</port>
</member>
</members>
B1.1 of Agile Web Development with Rails, 3rd Edition is out. Unless you have an deep interest in the migration function, there isn’t much new content here — the primary focus on this update is addressing the errata and forum comments received to date.
This effort has turned out to be both harder and more rewarding than I would have ever anticipated. Harder in that Rails has changed so much, there has been so much to learn (in terms of Rails 2.0, SQLite3, and also in terms of working with a different publisher, operating system, and toolset). But I can’t begin to express how much I like the beta books program — the readers that this book has attracted so far have been great and their comments, questions, and feedback have been most appreciated.
Also, while this book has always had ample source code provided, I’m continuing to look for ways to both expand and automate. Rerunning the code on rails edge, for example is now something I can repeatedly do in a matter of minutes.
So the reason for having rich client applications is for a better off-line experience, right? Why then, does outlook suck? Why is it actually less responsive than gmail on firefox?
Why, when you have set 'empty deleted items on shutdown' does it try and delete the deleted items folder contents (a directory on the server), one by one, with some animation? Not only does this take so long on OS reboot (it's reboot tuesday) that the OS gets fed up and kills it, making the database corrupt, given that the mailbox is server hosted, surely a quick request to the server (rm, "inbox/deleted/*") could do the work. The client -that is meant to be a cache of the server- could do its cleanup in the background, some other time.
DNS is still hosed. Either the the network stack is dropping most of the DNS packets or Virgin Media are screwing up. Either hypothesis is currently valid. What is clear is that DNS takes 30s to respond. What is more interesting is what fails. Ivy, deserves special mention here. On a machine where DNS is playing up, sorting dependencies takes forever. The only way to get the build to work is to disable the network adapter. I've filed a bug.
OpenOffice is complaining a lot on start up. I'm not the only one. It looks like a recurrence of an old problem -bad migration of settings.
Power management? The SCSI driver wont go into ACPI D3 state, so no Hibernate for me. Same as before.
I have managed to roll back to FireFox 2, by removing my .mozilla directory. Before upgrading to Ubuntu 8.04, take a copy of the .mozilla directory if you ever want to roll back to firefox 2.
I can't say its been a seamless upgrade. The network is unusable; everything else on the LAN seems happy, DNS is just not working properly. I've turned off ipv6, disabled mDNS, edited resolv.conf, edited /etc/host.conf, edited /etc/nsswitch.conf. No use whatsoever. Next: ethernet packet sniffing time.
Paul Fremantle: For me the core difference between Open Standards and Open Source is this: Open Standards enable companies to compete in a structured way, Open Source projects enable people or companies to collaborate in a structured way
I think Paul may be onto something. It is rapidly becoming the case that this more than this is becoming the exemplar for open standards. While it is popular to malign the JCP, it is worth noting that many (most?) JSRs have TCKs which actively promote the idea of multiple, independent, interoperable implementations.
this looks interesting -the Yahoo! Internet Location Platform
There's an Artima Article on Java TCKs that seems to have been got at by the JCP management
Why?
Because it argues in favour of a strong Test suite (the TCK) and that it needs to be kept a secret for the return on investment of the companies behind it. And it criticises lots of OSS projects -hibernate, Apache HTTPD- for not having a 'specification' or an independent TCK.
I disagree
danah boyd: I decided to go with a Scion xD because it was the right combination of small, cheap, quirky, practical, and dependable. I feel a little guilty because it’s painfully clear that Scion is targeted directly at people like me and I hate ending up fitting into a stereotype, but, well... it is nice to have an iPod jack built in standard and have a design aesthetic meant for hipster 20-30somethings.
danah deserves a commission. No, I’m clearly not a hipster 20-30something, but there seems to be a transitive property in effect as teenage girls tend to be 20-30something wannabies. In addition to the aspects that danah mentioned, gas mileage is not too bad. I also feel that — for this demographic at least — the ability to control an iPod from the steering wheel is an vital safety feature. We also went for the electronic stability control.
Anybody who happens to be by Fred Anderson Toyota should ask for Phil.
If you use a computer, and worry about its security, you should subscribe to the SANS diary, which keeps you up to date with the networks big security issues.
Today the news is Mozilla Firefox bug ID 432406: Virus found in Vietnamese language pack
It looks like
As it takes Mozilla more than a 1 week to scan the repository, they aren't in a position to detect malware that creeps in ahead of the signatures being updated.
This is pretty scary. It shows that you cant trust .xpi files, even from mozilla.org but I doubt most PC virus scanners look in them. It also shows that the security of OSS products is limited to its weakest link: the security of the computers of the people who make the contributions. Which means that you are pretty vulnerable, as a lot of machines are a mess out there, especially windows ones, where the default low-energy state is 0wned.
When you think that the whole OSS platform is based on an explicit trust of the repositories and the source, that's very scary.
The virus scanning process needs to be improved. A month? Someone needs to copy all the files up to HDFS and then run the scanner as a Hadoop Map/Reduce algorithm...make each signature scan a single map and stream the tasks past the files.
Apache Axis2/C Team is pleased to announce the release of Apache Axis2/C version 1.4.0
You can download this release from
http://ws.apache.org/axis2/c/download.cgi
Key Features
------------
1. Support for one-way messaging (In-Only) and request response messaging (In-Out)
2. Client APIs: Easy to use service client API and more advanced operation client API
3. Transports supported: HTTP
* Inbuilt HTTP server called simple axis server
* Apache2 httpd module called mod_axis2 for server side
* IIS module for server side
* Client transport with ability to enable SSL support
* Basic HTTP Authentication
* Digest HTTP Authentication
* libcurl based client transport
4. Transports supported: HTTPS
* HTTPS Transport implementation using OpenSSL
5. Transports supported: TCP
* for both client and server side
6. Transport proxy support (HTTP)
* Proxy Authentication (Basic/Digest)
7. Module architecture, mechanism to extend the SOAP processing model.
8. WS-Addressing support, both the submission (2004/08) and final (2005/08) versions,
implemented as a module.
9. MTOM/XOP support.
10. AXIOM, an XML object model optimized for SOAP 1.1/1.2 messages;
This has complete XML infoset support.
11. XML parser abstraction
* Libxml2 wrapper
* Guththila pull parser support
12. Both directory based and archive based deployment models for deploying
services and modules
13. Description hierarchy providing access to static data of
Axis2/C runtime (configuration, service groups, services, operations and messages)
14. Context hierarchy providing access to dynamic
Axis2/C runtime information (corresponding contexts to map to each level of
description hierarchy)
15. Message receiver abstraction
* Inbuilt raw XML message receiver
16. Code generation tool for stub and skeleton generation for a given
WSDL (based on Java tool)
* Axis Data Binding (ADB) support
17. REST support (more POX like) using HTTP POST, GET, HEAD, PUT and DELETE
* Support for RESTful Services
18. Comprehensive documentation
* Axis2/C Manual
19. WS-Policy implementation called Neethi/C, with WS-SecurityPolicy extension
Major Changes Since Last Release.
--------------------------------
1. Fixed library version numbering
2. Made Guththila as default XML parser
3. Many bug fixes.
4. Memory leak fixes
We welcome your early feedback on this implementation.
Thanks for your interest in Axis2/C
-- Apache Axis2/C Team --
Norman Walsh: In case you haven’t found it yet, here’s a pointer to the instructions for building VMWare Tools under Ubuntu 8.04, “Hardy Heron”.
It turns out that IBM Ubuntu software layer (e.g. VPN software) does not yet work with Hardy Heron. A few years ago, I would compiling and comparing notes with collegues, but now I’ve gotten complacent. I mean, really, Hardy has been out for 11 days now, what’s the problem?
So, I decided to try VMWare Workstation (i.e., for Windows). The above instructions (originally for VMWare Fusion) also work for VMWare Workstation. Suspend/Resume work, but unless Ubuntu is separately suspended, it won’t re-synchronize with the hardware clock on resume, but the following in crontab for root addresses this:
0,10,20,30,40,50 * * * * /etc/init.d/hwclock.sh start > /dev/null
The VM runs above the Wifi layer (i.e., appears to the VM as eth0), but below the VPN layer (drats!).
On a T61p, the display runs about as well as the native open source video driver (i.e., no compiz). One idiosyncrasy I’ve found so far is that releasing the right mouse button often has the effect of selecting the first menu item.
Switching back and forth between operating systems is fast, and one can even share directories (e.g. C:\cygwin\home\rubys as /mnt/hgfs/rubys) and copy/paste between host and VM windows.
This is an emergency warning to people engaged in outdoor activites. There is a fundamental force, "Gravity", which can cause pain and injury if applied incorrectly.
"Gravity" is a very weak force which attracts subatomic particles, those with "mass". While very weak, it does scale up and in large quantities, "planets" can exert quite a force on smaller objects. Normally it provides a valuable service, holding down an atmosphere, keeping property on the planets surface, and such like. It amplifies the effect of "friction", which for mountain biking can be used to transform pedalling into forward motion. "Gravity" is invaluable.
However, it has a downside. Because of the force it exerts on mass, any object with weight (such as a cylist and their bicycle) are unable to travel in straight object through space once friction fails, which it may do in wet and muddy conditions. Instead of continuing through 3-space in a vector consistent with their existing direction of travel, "gravity" alters the vector of the massed object, pulling it towards other objects with mass, such as rocks. While the direction of travel is altered, the overall momentum of the object is not affected, resulting in large amounts of kinetic energy being dispersed when the massing objects encounter each other. Some objects may disperse such energy by transforming it to heat and noise. Unfortunately, people appear to transform the energy into pain and damage to bodily parts.
To avoid such problems, consider avoiding cycling on low friction surfaces, such as on wet roots after a rain shower. If such activites are planned, consider body protection (knee pads) and practising safely ejecting from cleated pedals.
There will be infinite number of points like this, which will be on a circle with radius = 1 + (1/(2*pi)) miles and making north pole the center. So do we have more?? Yes !!Folks,
Just over 8 months since the 1.3 release, we are very proud to announce the release of Apache Axis2 version 1.4.
Downloads are available at:
~ http://ws.apache.org/axis2/download.cgi
The Maven2 main repository has the latest jars as well.
Apache Axis2 is a complete re-design and re-write of the widely used Apache Axis engine and is a more efficient, more
scalable, more modular and more XML-oriented Web services framework. It is carefully designed to support the easy
addition of plug-in "modules" that extend its functionality for features such as security and reliability.
Modules supporting WS-Security/Secure-Conversation (Apache Rampart), WS-Trust (Apache Rahas), WS-Reliable Messaging
(Apache Sandesha) and WS-Eventing (Apache Savan) will be available soon after the Apache Axis2 1.4 release. Please see
these projects' own sites for further information.
Major Changes Since 1.3:
- Support for JAXWS and JSR 181 Annotations (See 7 samples in the binary distribution)
- Experimental CORBA Support
- Fixed tons of small and not-so-small bugs (See list in release-notes.html in the binary distribution)
Known Issues and Limitations in 1.4 Release:
- Need to use wsimport/wsgen tools in JDK1.6 for JAXWS code generation.
- Please see JIRA for the current status of bugs
We welcome any and all feedback at:
~ axis-user@ws.apache.org (please include "[axis2]" in the subject, please subscribe first)
~ axis-dev@ws.apache.org (please include "[axis2]" in the subject, please subscribe first)
~ http://issues.apache.org/jira/browse/AXIS2
Thank you for your interest in Apache Axis2!
Apache Synapse is not just for large scale enterprise integration work. The simplicity of the configuration, out-of-the-box feature set, extensible architecture, and the minimal footprint makes it a versatile and powerful tool that you can use for a variety of tasks.
This IBM developerWorks tutorial will explain how you can use Apache Synapse to create mock Web services. Apache Synapse is a multi use tool that every developer should have in his or her tool set whether be it for solving enterprise systems integration problems or personal tasks.


Mike Melanson: the previous restriction that anyone who looks at the spec technically isn’t allowed to create an independent SWF decoder (if documentation EULAs are to be believed) was a point of contention among many open source types.
I would agree that the ability to create a license-free, independent open source implementation is an important aspect of an open standard.
"What is cool is the open-source aspect, the support for JavaScript-based mashups that can migrate from server to client, and support for lightweight but enterprise-oriented Web services."