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"
(reprioritized JAX-WS plugin Fragment) |
m |
||
Line 14: | Line 14: | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''install''' Swordfish Tools into my existing Eclipse IDE, | |width="10*" | '''install''' Swordfish Tools into my existing Eclipse IDE, | ||
− | |width="10*" | I can continue to use plugins I have already. | + | |width="10*" | I can start developing services quickly AND continue to use plugins I have already. |
|width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] | |width="10*" | [[Swordfish_Documentation:_SwordfishPlatform | Set Swordfish as target patform]] | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''run''' a JAX-WS Service Participant | + | |width="10*" | '''run''' a JAX-WS Service Participant within Eclipse Equinox, |
|width="10*" | I can test my code immediately | |width="10*" | I can test my code immediately | ||
|width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | |width="10*" | [[Swordfish_Documentation:_Product_Backlog#Done | Integrate Apache CXF]] | ||
Line 58: | Line 58: | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | + | |width="10*" | '''deploy''' a JAX-WS Service Participant into the running Target Platform outside of Eclipse, | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | |width="10*" | '''deploy''' a | + | |
|width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment). | |width="10*" | I can test my code immediately without needing to restart the target platform (hot deployment). | ||
|width="10*" | See also user story for deployment in tooling list below. For dynamic configuration: [[Swordfish_Documentation:_OSGi_Configuration_Agent | OSGi configuration Agent]] | |width="10*" | See also user story for deployment in tooling list below. For dynamic configuration: [[Swordfish_Documentation:_OSGi_Configuration_Agent | OSGi configuration Agent]] | ||
Line 73: | Line 68: | ||
|- | |- | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
− | |width="10*" | '''start''' a | + | |width="10*" | '''start''' a JAX-WS Service Provider in the Target Platform outside of Eclipse, |
|width="10*" | 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 | ||
Line 101: | Line 96: | ||
|width="10*" | I can provide high performance applications with low roundtrip times even for larger amounts of data transferred. | |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 | ||
Line 129: | Line 119: | ||
|width="10*" | Eclipse Service Developer | |width="10*" | Eclipse Service Developer | ||
|width="10*" | '''generate WSDL''' for a JAX-WS Service '''from code'''(code first generation). | |width="10*" | '''generate WSDL''' for a JAX-WS Service '''from code'''(code first generation). | ||
− | |width="10*" | I can | + | |width="10*" | I can publish my WSDL easily into Service Registry from implemented code. |
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- | ||
Line 140: | Line 130: | ||
|width="10*" | '''generate''' JAX-WS Service '''Provider from WSDL''' which can run in a '''Servlet Container (Web)''', | |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*" | 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*" | '''use jms as transport protocol''', | ||
+ | |width="10*" | I can provide a reliable transport. | ||
|width="10*" | TBD | |width="10*" | TBD | ||
|- | |- |
Revision as of 02:22, 3 April 2009
As an | I would like to | so that | link to backlog item(s) |
Eclipse Service Developer | use the target platformprovisioning P2 repository to download a released version of Swordfish, | I can install swordfish and set it as target platform.. | Swordfish Eclipse Features from download site |
Eclipse Service Developer | install Swordfish Tools into my existing Eclipse IDE, | I can start developing services quickly AND continue to use plugins I have already. | Set Swordfish as target patform |
Eclipse Service Developer | run a JAX-WS Service Participant within Eclipse Equinox, | 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 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 | write a JAX-WS Service using Eclipse and compile it, | I can get started with Swordfish Service development. | Develop JAX-WS Swordfish Bundle |
Eclipse Service Developer | run a JAX-WS Service Bundle in Eclipse, | I can check my Service Bundle within the development environment. | Run JAX-WS Swordfish Bundle |
Eclipse Service Developer | bundle Business Participant with necessary Swordfish Artefacts, | I can work with one single bundle during deployment. | TBD |
Eclipse Service Developer | run a JAX-WS Service Consumer in a Servlet Engine, | I can test my code immediately | TBD |
Eclipse Service Developer | want to be guided through examples/tutorials for implemtation and running JAX-WS services with Swordfish, | I can get started easily | Not a Backlog Item but part of Feature completeness criteria |
Eclipse Service Developer | deploy a 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). | See also user story for deployment in tooling list below. For dynamic configuration: OSGi configuration Agent |
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 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 | use JAX-WS plugin fragment for new Plugin project wizard, | I can start with my ready-made example. | Use JAX-WS Plugin Fragment |
Eclipse Service Developer | Get thw WSDL from a URL of a deployed service | I can save it into my local workspace. | TBD |
Eclipse Service Developer | debug my JAX-WS services related to the SOA infrastructure based on clearly understandable, well structured error messages, | I do not get lost in lengthy meaningless logs. | 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 | generate JAX-WS Service Consumers from WSDL which can run in Equinox (J2SE) (WSDL first), | 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 in Equinox (J2SE)(WSDL first). | 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 WSDL for a JAX-WS Service from code(code first generation). | I can publish my WSDL easily into Service Registry from implemented code. | 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 | use jms as transport protocol, | I can provide a reliable transport. | 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 | 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 | 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 | 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 | edit Service related spring configuration based on Swordfish semantics, | I can ensure my service will run in Swordfish. | 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 |
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 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 | upgrade an existing development environment with Swordfis and SOA Tools | I can use the latest version. | TBD |
See also: Swordfish Product Backlog
Return to Swordfish User Stories
Return to Swordfish Wiki Home