Raistlin SOA Container / News: Recent posts

RaistlinSOA is now in beta release and available for download. This beta release passes all tests and is actually being used for production work. Since we are still working on some of the documentation, it was decided that making it a beta release would be best until such time as the documentation reflects the quality of the release.

Due to some server probs, I was unable to get everything deployed. Going to try again on January 3rd. Happy freakin' new year...

The RaistlinSOA team would like to announce that our first release will be January 1st, 2006. We will launch with a large number of reference materials, examples and tutorials on how to use the container. Most of this information will be hosted on our Wiki site which is currently being contributed to.

We will be looking for volunteers to help move the project from Maven 1.0.2 to the newest version of Maven (2.0) in January or February. This will involve refactoring some of the plugins and perhaps developing new ones to facilitate faster bootstrapping for projects and ease migration for existing Avalon components to RaistlinSOA.... read more

Thanks to Chris for getting the TWiki up! The Raistlin team is currently populating the TWiki with installation instructions as well as reference materials and tutorials. This is going to be an ongoing process and as soon as the first few docs have been vetted (like any good writer/developer, I desperately need editors/testers), we'll open up the TWiki to all.

In addition, Woody is currently testing the binary to ensure it is live and ready to rock and roll without any tampering (by those of us who have been for more than 2 years now) of property files and environment variables.... read more

Sorry for the long delay. Between changing jobs, being ill, and desperately attempting to field test the container, it's been a little difficult to get the rest done.

However, the first small tutorial for the system is now being edited and should be up this week. Also, the RaistlinSOA binary release is pretty much ready. We experienced a server crash and therefore have desperately trying to get the raistlinsoa site back up as well as get our own maven/raistlin repository ready for users.... read more

The Raistlin team would like to announce that the alpha version of Raistlin is now in cvs. Although regression builds still have to be run, the system appears to be working as expected and hopefully will be in beta by the end of the weekend. We will be releasing beta distributions as soon as we able to. Again, thank you for your patience.

At long last, we have migrated enough of the source code that we were able to put the project into cvs this weekend. As soon as I have a chance, I will put documentation up as to how to build raistlin.

For those of you who grab the source, please read the maven description in the maven.xml file (in the raistin root) in order to figure out how to build the system. Currently, only the raistlin-container/cli project has a failing test case. I hope to address this tonight and get it fixed asap.... read more

I have entered two bugs for the raistlin team to begin dealing with. Both have to do with the same issue in two sections of the code base. The plan is to essentially begin putting what the team considers bugs and then move forward on them once the migration is completed. Cheers.

I have successfully ported the build system and the raistlin team has begun writing documentation and getting the project site together.

Migration continues on the package front as we move the org.apache package structure to org.dwg.

Once this is done, we will submit the files into cvs. I expect class diagrams, sequences, and the submittal of new features will follow.

Cheers.

I am currently in the process of cleaning up the existing Maven/Gump build files as well as re-factoring the package names for the existing avalon codebase.

I am making progress, but this will take some time. I will not place any files in cvs until I have the source tree under control.

In the meantime, I ask for patience and I will attempt to get documentation up as soon as possible.

Since I am currently contracting on a project using the existing Merlin codebase, I expect to be able to provide a list of new features/requests that my own team has had as well as an architectural description for virtual services/components as well as a call for comments on the plan.... read more