L.S.,
I have made some changes to this tutorial:
- added a section on Installing ServiceMix
- added some information about SUs
- tried to clarify why the client.html is being used
- added header/footer {scrollbar}s
- tried to elaborate on the dependency between a SU and a JBI component.
On the exercise page, we already installed a SA without the right
components being available, so people should be aware of the fact that
ServiceMix tells you about this from there. Perhaps I haven't made it
clear enough...?
I also tried to work out the structure you were describing on
http://cwiki.apache.org/confluence/x/ON4, with different levels of
tutorial complexity.
Any additional comment?
Gert
Bruce Snyder wrote:
On 6/7/07, Gert Vanthienen <[EMAIL PROTECTED]> wrote:
Bruce,
I've created a first tutorial, a guided tour of starting, installing,
deploying and testing a first application and, more importantly, a quick
introduction some JBI concepts (service assembly, service unit, ...). It
isn't completely done yet, but it already shows the intention. Is
this what
you had in mind?
For the second tutorial, I would like to focus on the Maven tooling and
archetypes. Any suggestions on that topic?
This is a great start, Gert! Overall this is a wonderful start. I hope
to be able to create a whole series of these guides to help users get
started easier. Below are my comments:
- Provide a headding to the section about installing ServiceMix to
properly identity it. Right now it's under a heading named Content
which isn't very descriptive.
- Make sure to describe both SAs and SUs. Right now SUs are not
described at all. This is easy to do because there are already FAQ
entries about SAs and SUs that can be referenced for this.
- We should break up the whole guide into sections like Beginner,
Intermediate and Advanced. This will allow us to address more complex
topics without confusing beginners. E.g., In the beginner JMX
tutorial, we only address connecting to a local instance of SMX
whereas an intermediate version would describe how to connect to
multiple remote instances of SMX and an advanced version might go into
code level use of JMX, all of which are cross-linked.
- Be very clear about the component dependencies for deploying the
example. It might be a good idea to demonstrate that SMX will tell you
when a component is missing.
- Provide a better description about what the client.html file is
actually doing to invoke the service (i.e., it is sending an XML
message to the URL where the service is exposed). Upon first using
SMX, many people assume that when configuring the locationURI for
servicemix-http that you can simply visit that URL in a browser to use
it and this is not true. We need to explain that an XML message must
be sent to this URL.
- The header and footer with the arrows for navigation are missing
from most of the pages. Please make sure to add them.
Again, very nice work, Gert. My comments are only meant to be constructive.
Bruce
