Dear Wiki user, You have subscribed to a wiki page or wiki category on "Axis Wiki" for change notification.
The "Axis2Spring" page has been changed by AndreasVeithen. http://wiki.apache.org/axis/Axis2Spring -------------------------------------------------- New page: = Goals and high level requirements = The goal is to provide Spring integration for Axis2 in scenarios where Axis2 is embedded inside Spring (i.e. where the Axis2 runtime is controlled by the Spring container). This is different from the scenario supported by the existing axis2-spring module, which addresses the scenario of implementing a service using Spring, while all other aspects (configuration of the Axis2 runtime, service and module deployment, etc.) are still managed by Axis2. The framework should be easy to use for developers familiar with Spring, but who have no prior experience with Axis2. At the same time, developers who have used Axis2 before should be able to quickly become familiar with the Spring integration, i.e. the framework should use concepts, paradigms and syntax familiar to Axis2 developers wherever this makes sense (i.e. wherever this is compatible with the Spring programming model). Scenarios that are supported by other Web service stacks (e.g. CXF) should be supported with at least the same ease of use. A particular example is the popular scenario of deploying JAX-WS services in combination with Spring in a WAR. The framework should minimize the amount of configuration required in common scenarios. = Requirements = * Support for deployment in a servlet container (i.e. with AxisServlet as transport) as well as in standalone scenarios. * It should be possible to configure the Axis2 runtime using only Spring configuration files (i.e. without relying on an axis2.xml file). In this case, the configuration items (transports, message builders and formatters, phase configuration, etc.) should be top level beans, so that the configuration can be assembled from different files (some of which would be configuration files bundled with the framework and that provide defaults). Spring namespace handlers should be used so that the syntax of the configuration items is similar to the existing axis2.xml file. * For users familiar with Axis2 or migrating an existing Axis2 project to Spring should still be able to use their existing axis2.xml file. * Support for JAX-WS. * Support for the client side: * Injection of ConfigurationContext into stubs; injection of stubs into beans (thread safety??). * Injection of JAX-WS dynamic proxies into beans. * Support for multiple configuration contexts [to be confirmed; using a different configuration context for services and client stubs seems to be a common pattern]. * ... --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@axis.apache.org For additional commands, e-mail: general-h...@axis.apache.org
