Hi all.
These are just ideas (and constraints) we should discuss for the
turorial.
The first elements about this tutorial were defined here :
http://wiki.eclipse.org/Integrated_STP_Tutorial_Proposal_-_EclipseCON%2709
And the proposal is here :
https://www.eclipsecon.org/submissions/2009/view_talk.php?id=368
And as a reminder, it seems we have to send the slides before February
9th.
Since we target a simple SOA application ("helloWorld" SOA), I think we
should consider the following elements:
- From the SCA point of view, the component implementations should
be limited to Java. And the bindings limited to Web-Service bindings.
Other protocols would be IMO an advanced case for a beginner.
- People interested in more complex examples will be able to see
SCA samples and runtime platforms.
- Since we use SCA, a nice demonstration would be to use existing
services, call them in the "application process" and add additional
processing.
- Show that thanks to SCA / SOA, we create an application from
existing elements with a higher-value for the business (and if I had to
define business here, I would say for the application developer - who
himself is the technical for another business).
- This would not be a simple orchestration of services.
- Eventually, the tutorial will also be available online after the
conference, and reusing existing services would probably require an
internet connection.
- So maybe we should focus on using existing web services, e.g.
from Google or other service providers, and build some "mash-up"
applications with the Eclipse tools.
- This would ensure people can use and try the tutorial even
after the conference. It would not be something that worked only
because we deployed all the things we needed for the tutorial.
All of this would avoid us to spend too much time on preparing the
environement for the conference.
And we would be sure it works with the tooling (using WSDL interfaces
in SCA applications having a Java implementation) and with all the
platforms (implementations, bindings).
The tutorial should allow us to make a simple application, try to
explain SOA's concepts, make the application run, and demonstrate most
of the features offered by our tools.
This is just my opinion... :)
Regards,
Vincent Zurczak.
--
Vincent Zurczak
EBM WebSourcing
+33 (0) 4 38 12 16 77
|
