This is a very loose schema: event.xsd

But the application is rather simple.

The simplest definition of a web service:

• XML in

• XML out

• via a standard web protocol (e.g. http, https, etc.)

SOAP, WSDL, etc. are not required.

Each message:

• Asks the web service to do something as an XML document.

• Has a single document as a response.

• But that response document could have different content depending on the results.

This application has:

• get event list - asks for the list of events.

• create event - creates event(s).

• delete event - deletes event(s).

• alive - the response to a "ping" message.

• error - notification of an error during the operation.

• ok - notification of success

Just for kicks, I made the web service respond to a HTTP GET with no XML message.

It returns the alive message if successful:

<alive xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403"/>

The request is simple:

<get-all-events xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403"/>

The response is a list of events:

<events xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403">
<event xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:schemas:event:200403" timestamp="1079122269643" start-date="sdfsdf" id="e1079122269651">
...
</event>
</events>

The request is simple:

<add xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403">
<event xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:schemas:event:200403" timestamp="1079122269643" start-date="sdfsdf" id="e1079122269651">
...
</event>
<event xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:schemas:event:200403" timestamp="1079122269643" start-date="sdfsdf" id="e1079122269651">
...
</event>
</add>

The response the events repeated with the id value returned:

<ok xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403">
<event xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:schemas:event:200403" id="e1234" timestamp="1079122269643" start-date="sdfsdf" id="e1079122269651">
...
</event>
<event xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:schemas:event:200403" id="e5678" timestamp="1079122269643" start-date="sdfsdf" id="e1079122269651">
...
</event>
</ok>

The request is simple:

<delete xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403">
<event ref="e1234"/>
<event ref="e5678"/>
</delete>

The response is a list of events:

<ok xmlns="urn:publicid:IDN+cde.berkeley.edu:examples:webservice:event:200403"/>

The web server uses Cocoon.

It uses a custom component that I wrote to post & receive the results from the web service.

The web service is a simple JSP page (242 lines) that runs in tomcat

The front-end (web service) XSLT is only 388 lines total.

The UI (web front end) is really, really basic (read: bad).

From the Apache website:

Simple description: Its a web server that runs servlets and JSP pages.

Available at Apache's Jakarta Project

From the Cocoon website:

Basically, you map URL requests to pipelines.

Pipelines can do simple or complex "inline" processes.

Available at Apache's Cocoon Website

This application uses three pipelines:

1. Handle post data & talk to the web service.

2. Handle get queries & talk to the web service.

3. Style XML content with XSLT.

A web service can be written in any language.

This demo uses JSP for simplicity.

The JSP page consumes XML and produces an XML page.

It looks like any other JSP page except my XML elements are used instead of XHTML.

It would be much nicer to have it call a real "library of Java code".