Hi Robert, the initial exception on startup is gone now, however the generated WSDL initially contained no method definitions.
I had to manually add a "operation" tag in the service XML. This is my new Service.xml definition (I only test with the UserService modified only): http://code.google.com/p/openmeetings/source/browse/branches/dev/injection/src/META-INF/services.xml It SHOULD look like from my point of view: http://demo.openmeetings.de/openmeetings/services/UserService?wsdl But the resulting WSDL looks like that: http://pastebin.com/mzMznPhC You got an idea what might went wrong with it? Why are those *<operation>* Tags needed by using the Spring integration? Previously I did not configure anything like that in the service.xml, Axis2 just made all Methods available that are public in the Service-Class. Do we now need to manually add all method calls by using the "<operation name=xyz><operation>"-Definition in the service.xml now? What about params, do we need to specify params in the service.xml too? What about returned JavaBeans, do we need to write mappings for those Beans manually in the service.xml? For example this Return Object "Sessiondata" ... I cannot find it in the newly generated WSDL. I see an error in the namespace of the generated WSDL? Or is there any special trick? For example by using an Interface as placeholder in the service.xml-definition?! I cannot find any docs on that, I would be great if you could shed some light on this. BTW: Is there a DTD or something about possible TAGs in the service.xml ? I was searching for that for a long time but I cannot find any Docs about what TAGs are allowed in the service.xml Thanks a lot Sebastian 2011/8/22 seba.wag...@gmail.com <seba.wag...@gmail.com> > Hi Robert, > > I will test and give feedback. > > Thanks a lot! > Sebastian > > 2011/8/21 robert lazarski <robertlazar...@gmail.com> > >> On Sun, Aug 21, 2011 at 3:58 PM, seba.wag...@gmail.com >> <seba.wag...@gmail.com> wrote: >> > service.xml including that service: >> > >> http://code.google.com/p/openmeetings/source/browse/branches/dev/injection/src/META-INF/services.xml >> >> The docs indicate that for servlet context loading you should use >> SpringServletContextObjectSupplier, not >> SpringAppContextAwareObjectSupplier. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org >> For additional commands, e-mail: java-user-h...@axis.apache.org >> >> > > > -- > Sebastian Wagner > http://www.webbase-design.de > http://openmeetings.googlecode.com > http://www.wagner-sebastian.com > seba.wag...@gmail.com > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com seba.wag...@gmail.com
