For a starting point, have you tried creating a JSR181/JAX-WS POJO that then calls a Spring assembly? That would seem like a good starting point. I think the idea of adding JAXWS support to WSF/Spring is also interesting.
Paul On Tue, Jun 10, 2008 at 10:50 AM, Wang, Dapeng <[EMAIL PROTECTED]> wrote: > Hi, > > I have been asking myself what is the best WS-implementation strategy = when > using Axis2. I prefer to follow the code-first paradigm. But I am = not > always happy with the default WSDL generation conventions and want = to > control the =B4the WSDL and schema-generation. Therefore the = > JAX-WS-support in Axis2 is very sexy for me. But the JAX-WS receiver = > doesn't support Spring directly. For most of the service implementations = I > have are spring configured beans, so WSF/Spring oder even the Spring = > object supplier is more attractive, so that I can use the Spring bean = > directly without any adapter. But how can I combine JAX-WS and Spring = > support. Is there any extension in this direction planned? If I want to = do > it myself, what is the best strategy to choose? > > > > > > Mit freundlichen Grüßen / Best regards > > SUZUKI INTERNATIONAL EUROPE GMBH > > Dapeng Wang > Extern > > SUZUKI INTERNATIONAL EUROPE GMBH > > > > Phone > > Suzuki-Allee 7 D-64625 Bensheim > > > > Fax > > Homepage www.suzuki.de > > > > E-Mail > > > > > > > > > > > > > > Amtsgericht (Local Court) Darmstadt > > HRB 21266 > > Geschäftsführer (Managing Directors) > > Ken Iijima, Minoru Amano, Kunihiko Uetsuki > > > > > > > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
