Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: User Stories: Service Developer"
| Line 1: | Line 1: | ||
| + | == User Stories Service Developer with Runtime focus == | ||
| + | |||
{| border="1" cellpadding="3" cellspacing="0" width="100%" | {| border="1" cellpadding="3" cellspacing="0" width="100%" | ||
| − | |||
|- style="background:#efefef;" | |- style="background:#efefef;" | ||
| Line 93: | Line 94: | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|-} | |-} | ||
| + | |||
| + | == User Stories Service Developer with Tooling focus | ||
{| border="1" cellpadding="3" cellspacing="0" width="100%" | {| border="1" cellpadding="3" cellspacing="0" width="100%" | ||
| − | |||
|- style="background:#efefef;" | |- style="background:#efefef;" | ||
| Line 104: | Line 106: | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
| − | |width="10*" | '''generate''' JAX-WS Service '''Consumers''' | + | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run '''standalone (J2SE)''', |
| − | |width="10*" | I can implement the business logic without | + | |width="10*" | I can implement the business logic without taking care about Service Proxy or any other SOA infrastructure releated code. |
|width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | |width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
| − | |width="10*" | '''generate''' JAX-WS Service '''Providers''' | + | |width="10*" | '''generate''' JAX-WS Service '''Providers from WSDL''' which can run '''standalone (J2SE)'''. |
| − | |width="10*" | I can implement the business logic without | + | |width="10*" | I can implement the business logic without taking care about the Service Skeleton or any other SOA infrastructure releated code. |
|width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | |width="10*" | [[Swordfish_Documentation:_JAX-WS_Code_Generation | JAX-WS Code Generation]] | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
| − | |width="10*" | ''' | + | |width="10*" | '''retrieve''' the WSDL for Code generation out of Eclipse from the '''Service Registry''', |
| − | |width="10*" | I | + | |width="10*" | I do not need to download and generate in two steps. |
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
| − | |width="10*" | ''' | + | |width="10*" | '''deploy''' a J2SE JAX-WS Service Participant from my Eclipse Workspace into the Target Platform outside of Eclipse, |
| − | |width="10*" | I can | + | |width="10*" | I can test my code immediately in a distributed environment. |
| − | |width="10*" | | + | |width="10*" | TBD |
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in a '''Servlet Container (Web)''', | ||
| + | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in a '''Servlet Container (Web)''', | ||
| + | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''test''' my Service Consumer whithout having implemented a Service Provider, | ||
| + | |width="10*" | I can start testing early AND implement consumer and provider independently. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''test''' my Service Provider whithout having implemented a Service Consumer, | ||
| + | |width="10*" | I can start testing early AND implement consumer and provider independently. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''develop simple test scripts''' for my service, | ||
| + | |width="10*" | I can run basic regression tests of all Service Operations with a variety of transports and policies during progressing implementation. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''retreive''' Service artifacts (Service Description, Policy)'''from Service Registry''' for test executions, | ||
| + | |width="10*" | I do not need to download and test in two steps. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Consumers from WSDL''' which can run in an '''JEE Application Server''', | ||
| + | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in an '''JEE Application Server''', | ||
| + | |width="10*" | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | ||
| + | |width="10*" | TBD | ||
|- | |- | ||
------------------- | ------------------- | ||
return to: [[Swordfish_Documentation:_User_Stories | Swordfish User Stories]] | return to: [[Swordfish_Documentation:_User_Stories | Swordfish User Stories]] | ||
Revision as of 09:55, 27 March 2009
User Stories Service Developer with Runtime focus
| 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 | Integrate Apache CXF |
| Eclipse Service Developer | use the http and https transport protocols, | I can communicate over the web. | Integrate Apache CXF |
| 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. | Service Registry Feature |
| 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 |
| As an | I would like to | so that | link to backlog item(s) |
| Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run standalone (J2SE), | I can implement the business logic without taking care about Service Proxy or any other SOA infrastructure releated code. | JAX-WS Code Generation |
| Eclipse Service Developer | generate JAX-WS Service Providers from WSDL which can run standalone (J2SE). | I can implement the business logic without taking care about the Service Skeleton or any other SOA infrastructure releated code. | JAX-WS Code Generation |
| Eclipse Service Developer | retrieve the WSDL for Code generation out of Eclipse from the Service Registry, | I do not need to download and generate in two steps. | TBD |
| Eclipse Service Developer | deploy a J2SE JAX-WS Service Participant from my Eclipse Workspace into the Target Platform outside of Eclipse, | I can test my code immediately in a distributed environment. | TBD |
| Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run in a Servlet Container (Web), | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| Eclipse Service Developer | generate JAX-WS Service Provider from WSDL which can run in a Servlet Container (Web), | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| Eclipse Service Developer | test my Service Consumer whithout having implemented a Service Provider, | I can start testing early AND implement consumer and provider independently. | TBD |
| Eclipse Service Developer | test my Service Provider whithout having implemented a Service Consumer, | I can start testing early AND implement consumer and provider independently. | TBD |
| Eclipse Service Developer | develop simple test scripts for my service, | I can run basic regression tests of all Service Operations with a variety of transports and policies during progressing implementation. | TBD |
| Eclipse Service Developer | retreive Service artifacts (Service Description, Policy)from Service Registry for test executions, | I do not need to download and test in two steps. | TBD |
| Eclipse Service Developer | generate JAX-WS Service Consumers from WSDL which can run in an JEE Application Server, | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |
| Eclipse Service Developer | generate JAX-WS Service Provider from WSDL which can run in an JEE Application Server, | I can implement the business logic without taking care about SOA releated code AND having a free choice of deployment scenarios. | TBD |