We are pleased to announce the first developer snapshot release of the CASheW-s editor.

The CASheW-s editor project is an attempt to create an editor, which allows for the visual composition of web services. It also includes significant low-level Java code to interact with semantic web and web service technologies, and provides a binding to the CASheW-s engine (http://savannah.nongnu.org/projects/cashew-s-engine).

The highlights of this initial release are as follows:

Basic RDF parsing

Basic WSDL parsing

Basic client-side SOAP engine

Basic XML serializer

Models of the OWL-S and CASheW-s languages.

An Eclipse-based editor, in which performances can be created and linked via connection elements.

3 people actively contributed code to this release and made 155 CVS commits during the last seven months of development.

This project is of primary interest to those interested in semantic web services, and particularly in their composition. At present, you should install the CASheW-s editor if you are interested in its development or in reporting bugs.
We appreciate both.

2). What is required to build/install/run?

The CASheW-s editor requires a working GNU build environment and a Java byte code compiler capable of handling the language extensions present in the 1.5 specification. Our reference compiler is the Eclipse compiler, ecj, although we intend to support more compilers once Free Software 1.5 compilers become more widely available.

You will also need a runtime environment. The project
hackers use JamVM 1.3 (http://jamvm.sourceforge.net/) for this purpose. Other environments may also be usable, but these have not yet been tested.

For using the editor, the latest version of Eclipse is required. The editor has primarily been tested on the current beta, 3.1, as this supports 1.5 language constructs.

Our code makes full use of parameteric typing and JAXP 3, and these features need to be available within the deployed environment.

2). Which platforms are supported?

The GNU/Linux platform is regularly tested by the developers.
We aim to make our code as portable as possible, and this,
combined with the platform independence already inherent
in the Java language, should make this project usable in
alternate environments.