Asankha,
I have a suggestion,
In the existing sample services, user has to go the relevant src folder of
the service and type ant to create the archive and copy that. User has to do
this for all the services. Instead we can let the user just type ant on the
axis2Server level without going to the src of services and deploy all the
services so that he can just start the server and try all the samples
without restarting the axis2server.
Thanks,
Ruwan.
On 4/3/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Hi All
I am thinking of improving and streamlining the Synapse samples before our
1.0 release.. as such I am hoping to structure the current samples as
stated below and add the missing pieces.
*Sample Clients
*I feel that a single command line client could replace the current
stockquote, customquote and dumbstockquote and placeorder as follows:
ant stockquote
[-Dsymbol=<sym>] [-Drepository=<repo>]
[-Dpolicy=<policy>]
[-Dmode=quote | customquote | fullquote | placeorder
| marketactivity]
[-Daddressingurl=<url>] [-Dtransporturl=<url> |
-Dproxyurl=<url>]
Specifying a transporturl alone would implement the 'gateway' model, and
specifying a proxyurl alone would implement the 'http proxy' model.
Specifying a WS-A url different from the transport url would be the 'smart
client' mode. I hope to document the differences of these for proper
understanding by those who are new to Synapse. The mode would select if the
outgoing payload would be a getQuote, placeOrder, customQuote (to be
transformed through Synapse) or two new operations for getFullQuote (to test
a small request and a large response) and getMarketActivity (to test a large
request and a large response) for performance and large message testing
*Sample Services)*
Similarly I think the SimpleStockQuoteService, SecureStockQuoteService and
the FastStockQuoteService would be adequate to cover all cases. (Note: the
FastStockQuoteService is a pure static response service used only for
performance testing aspects)
*Sample Configurations
*Message Mediation
Deployment models
Sequences
Endpoints
Local Registry
Mediators
Content based routing
soap/transport headers
message body
Switch case & property
Validation
Transformation
Header manipulation
Class mediator
Script mediation
Error handling
Remote Registry resources
Dynamic Sequences
Dynamic Endpoints
Full registry based configurations
Endpoints
Address endpoints
SOAP/POX conversion
WS-Addressing
WS-Security
WS-RM
WSDL Endpoints
Loadbalancing
Failover
Proxy services
Transport switching
Custom/inline sequences
Publishing a WSDL
REST proxies
WS-Security
WS-RM
Transports
HTTPS
- Keystores (identity/trust), 2-way auth, hostname
verification, debugging
Binary and Text JMS to SOAP
Miscellaneous
One way messaging
MTOM
I am planning to make these changes over this week, so some of the samples
may get broken during the changes.. please bear with me. Also I am going to
document each sample in a separate HTML of its own - I hope this would
provide us with enough 'space' for each sample - if we want to introduce
images or embed the configuration etc. and allow us to present each sample
more clearly with sample output etc.
Let me know if you have any suggestions for improvement or inclusion -
especially from the point of view of end users who are new to Synapse
asankha
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
