Skip to main content

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.

Jump to: navigation, search

Swordfish Documentation: User Stories: Service Developer

Revision as of 07:49, 31 March 2009 by Joerg.drescher.sopera.de (Talk | contribs) (add generic User stories)

return to Swordfish User Stories
se also: Swordfish Product Backlog


User Stories for Service Developers (generic - affecting runtime and Tooling

As an I would like to so that link to backlog item(s)
Eclipse Service Developer download a released version of Swordfish form the Eclipse Download site, I can use the usual eclipse mechanism for getting new versions and installling them. Swordfish Eclipse Features from download site
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

User Stories for Service Developers 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 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 run a JAX-WS Service Consumer in a Servlet Engine within Eclipse, I can test my code immediately TBD
Eclipse Service Developer use jms as transport protocol, I can provide a reliable transport. 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 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 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 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 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 TBD

User Stories for Service Developers with Tooling Focus

As an I would like to so that link to backlog item(s)
Eclipse Service Developer install swordfish in my eclipse and 'set it as a target platform, I can deploy my develped service participants out of the workspace. Set Swordfish as target patform
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 export my CXF Swordfish bundle as JAR file, I can deploy it into different environments. Export JAX-WS Swordfish Bundle as JAR
Eclipse Service Developer generate JAX-WS Service Consumers from WSDL which can run standalone (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 standalone (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 implement the Service without needing to create the WSDL manually. 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 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

Back to the top