Jump to: navigation, search

Difference between revisions of "Swordfish Documentation: User Stories"

(New page: Under construction! == Eclipse SOA Runtime == {| border="1" cellpadding="3" cellspacing="0" width="100%" |+'''User Stories''' |- style="background:#efefef;" |width="10*" |'''As an''' |...)
 
Line 1: Line 1:
 
 
Under construction!
 
Under construction!
  
Line 14: Line 13:
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''run''' a JAX-WS Service Consumer standalone within Eclipse,
+
|width="10*" | '''run''' a JAX-WS Service Participant standalone within Eclipse,
 
|width="10*" | I can test my code immediately
 
|width="10*" | I can test my code immediately
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine within Eclipse,
+
|width="10*" | '''use the http and https transport protocols''',
|width="10*" | I can test my code immediately
+
|width="10*" | I can communicate over the web.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''deploy''' a standalone JAX-WS Service Participant into the running Target Platform outside of Eclipse,
+
|width="10*" | '''use jms as transport protocol''',
|width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment).
+
|width="10*" | I can provide a reliable transport.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''use dynamic policy based Service lookup'''
|width="10*" |  
+
|width="10*" | I can utilize QOS with different service levels for the Same service i.e. different security levels.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" | '''use http and https as transport protocol''',
|width="10*" |  
+
|width="10*" | I can communicate over the Web.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''run''' a JAX-WS Service Consumer in a Servlet Engine within Eclipse,
|width="10*" |  
+
|width="10*" | I can test my code immediately
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse,
+
|width="10*" | '''deploy''' a standalone JAX-WS Service Participant into the running Target Platform outside of Eclipse,
|width="10*" | I can test my code in a distributed environment.
+
|width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment).
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | '''start''' a standalone JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" | '''select the consumer policy''' dynamically,
|width="10*" | so that I can test my code in a distributed environment.
+
|width="10*" | I can invoke service calls with different policies from the same consumer
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" | I would like to  start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
+
|width="10*" | '''start''' a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
|width="10*" | so that I can test my code in a distributed environment.
+
|width="10*" | I can test my code in a distributed environment.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''run''' a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse,
|width="10*" |  
+
|width="10*" | I can test my code in a distributed environment.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''start''' a standalone JAX-WS Service Provider in the Target Platform outside of Eclipse,
|width="10*" |  
+
|width="10*" | I can test my code in a distributed environment.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
|width="10*" |  
+
|width="10*" | I can test my code in a distributed environment.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''reference message schemas from the WSDL''',
|width="10*" |  
+
|width="10*" | I do not need to modify the WSDL when something in the message schemas changes AND I can reuse the same schemas for multiple WSDLs.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''utilize message streaming''',
|width="10*" |  
+
|width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''start''' a JAX-WS Service Provider in a JEE Application Server
|width="10*" |  
+
|width="10*" | I can test my code in a distributed JEE environment.
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" | Eclipse Service Developer
|width="10*" |  
+
|width="10*" | '''use any other transport protocol offered by ServiceMix''',
|width="10*" |  
+
|width="10*" | I can integrate easier with legacy Systems. (I am aware that restrictions apply regarding policies influencing the wire format.)
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
Line 98: Line 97:
 
|width="10*" | TBD
 
|width="10*" | TBD
 
|-
 
|-
|width="10*" | Eclipse Service Developer
 
|width="10*" |
 
|width="10*" |
 
|width="10*" | TBD
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" |
 
|width="10*" |
 
|width="10*" | TBD
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" |
 
|width="10*" |
 
|width="10*" | TBD
 
|-
 
|width="10*" | Eclipse Service Developer
 
|width="10*" |
 
|width="10*" |
 
|width="10*" | TBD
 
|-
 
 
 
As an Eclipse Service Developer
 
I would like to  start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse,
 
so that I can test my code in a distributed environment.
 
 
As an Eclipse Service Developer
 
I would like to start a JAX-WS Service Provider in a JEE Application Server
 
so that I can test my code immediately.
 
 
As an Eclipse Service Developer
 
I would like to select the consumer policy dynamically,
 
so that I can invoke service calls with different policies from the same consumer
 
 
As an Eclipse Service Developer
 
I would like to reference message schemas from the WSDL,
 
so that I do not need to modify the WSDL when something in the message schemas changes AND I can reuse the same schemas for multiple WSDLs.
 
 
As an Eclipse Service Developer
 
I would like to use dynamic policy based Service lookup
 
so that I do not need to implement QOS within the Business participant BUT still can offer different Service Levels for the Same service i.e. different security levels.
 
 
As an Eclipse Service Developer
 
I would like to use http and https as transport protocol.
 
so that I can utilize the web infrastructure.
 
 
As an Eclipse Service Developer
 
I would like to use jms as transport protocol,
 
so that I can provide a reliable transport.
 
 
As an Eclipse Service Developer
 
I would like to be able to use any other transport protocol offered by ServiceMix
 
so that I can integrate easier with legacy Systems.
 
I am aware that restrictions apply regarding policies influencing the wire format.
 
 
As an Eclipse Service Developer
 
I would like to utilize message streaming
 
so that I am able to provide high performance applications with low roundtrip times even for larger amounts of data transferred.
 

Revision as of 06:40, 27 March 2009

Under construction!

Eclipse SOA Runtime

User Stories
As an I would like to so that link to backlog item(s)
Eclipse Service Developer run a JAX-WS Service Participant standalone within Eclipse, I can test my code immediately TBD
Eclipse Service Developer use the http and https transport protocols, I can communicate over the web. TBD
Eclipse Service Developer use jms as transport protocol, I can provide a reliable transport. TBD
Eclipse Service Developer use dynamic policy based Service lookup I can utilize QOS with different service levels for the Same service i.e. different security levels. TBD
Eclipse Service Developer use http and https as transport protocol, I can communicate over the Web. TBD
Eclipse Service Developer run a JAX-WS Service Consumer in a Servlet Engine within Eclipse, I can test my code immediately TBD
Eclipse Service Developer deploy a standalone JAX-WS Service Participant into the running Target Platform outside of Eclipse, I can test my code immediately without needing to restart the target platform (hot deployment). TBD
Eclipse Service Developer select the consumer policy dynamically, I can invoke service calls with different policies from the same consumer TBD
Eclipse Service Developer start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer run a JAX-WS Service Consumer in a JEE Application Server outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer start a standalone JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer start a Servlet JAX-WS Service Provider in the Target Platform outside of Eclipse, I can test my code in a distributed environment. TBD
Eclipse Service Developer reference message schemas from the WSDL, I do not need to modify the WSDL when something in the message schemas changes AND I can reuse the same schemas for multiple WSDLs. TBD
Eclipse Service Developer utilize message streaming, I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. TBD
Eclipse Service Developer start a JAX-WS Service Provider in a JEE Application Server I can test my code in a distributed JEE environment. TBD
Eclipse Service Developer use any other transport protocol offered by ServiceMix, I can integrate easier with legacy Systems. (I am aware that restrictions apply regarding policies influencing the wire format.) TBD
Eclipse Service Developer TBD