Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
(New page: {| border="1" cellpadding="3" cellspacing="0" width="100%" |+'''User Stories Service Developer with Runtime focus''' |- style="background:#efefef;" |width="10*" |'''As an''' |width="10*" ...) |
|||
| Line 92: | Line 92: | ||
|width="10*" | | |width="10*" | | ||
|width="10*" | TBD | |width="10*" | TBD | ||
| − | |- | + | |-} |
| + | {| border="1" cellpadding="3" cellspacing="0" width="100%" | ||
| + | |+'''User Stories Service Developer with Tooling focus''' | ||
| + | |||
| + | |- style="background:#efefef;" | ||
| + | |width="10*" |'''As an''' | ||
| + | |width="10*" |'''I would like to''' | ||
| + | |width="10*" |'''so that''' | ||
| + | |width="10*" |link to backlog item(s) | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Consumers''' from WSDL which can run '''standalone (J2SE)''', | ||
| + | |width="10*" | I can implement the business logic without needing to take 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*" | Eclipse Service Developer | ||
| + | |width="10*" | '''generate''' JAX-WS Service '''Providers''' from WSDL which can run '''standalone (J2SE)'''. | ||
| + | |width="10*" | I can implement the business logic without needing to take 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*" | Eclipse Service Developer | ||
| + | |width="10*" | '''deploy''' a J2SE JAX-WS Service Participant from my Eclipse Workspace into the running Target Platform outside of Eclipse, | ||
| + | |width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment). | ||
| + | |width="10*" | TBD | ||
| + | |- | ||
| + | |width="10*" | Eclipse Service Developer | ||
| + | |width="10*" | '''use dynamic policy based Service lookup''' | ||
| + | |width="10*" | I can utilize QOS with different service levels for the Same service i.e. different security levels. | ||
| + | |width="10*" | [[Swordfish_Documentation:_Registry_Feature | Service Registry Feature]] | ||
| + | |- | ||
------------------- | ------------------- | ||
return to: [[Swordfish_Documentation:_User_Stories | Swordfish User Stories]] | return to: [[Swordfish_Documentation:_User_Stories | Swordfish User Stories]] | ||
Revision as of 09:17, 27 March 2009
| 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 needing to take 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 needing to take care about the Service Skeleton or any other SOA infrastructure releated code. | JAX-WS Code Generation |
| Eclipse Service Developer | deploy a J2SE JAX-WS Service Participant from my Eclipse Workspace 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 | 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 |