Hi Robert, no the "useOriginalwsdl" doesn't work for me. What should it do actually? I mean I don't want to specify a WSDL on my own manually I want Axis2 to create one based on the Methods that are declared public the the Service Class. In Version 1.3 of Axis2 there was no need to write any additional method information for that in the service.xml.
The only config explenation I can find is here: http://axis.apache.org/axis2/java/core/docs/axis2config.html#Service_Configuration But there is not mentioned anywhere if there is now need to define any method as <operation> or not .. or if there is a <parameter> tag. Even in the sample config there is a tag called *actionMapping* ...any idea what that Tag means? It is not mentioned anywhere else. However thanks a lot Sebastian 2011/8/22 robert lazarski <robertlazar...@gmail.com> > On Mon, Aug 22, 2011 at 3:23 PM, seba.wag...@gmail.com > <seba.wag...@gmail.com> wrote: > > 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? > > > IIRC, set the "useOriginalwsdl" parameter "true" in your services.xml > so that Axis2 will use the one you supplied originally. You may want > to double check the docs, but I believe that is still: > > <parameter name="useOriginalwsdl">true</parameter> > > > Why are those *<operation>* Tags needed by using the Spring integration? > > That's axis2 stuff and not specific to Spring. They define what > methods can be invoked. See the <excludeOperations> tag to prevent > access to, for example, your setters. > > > 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? > > That is all explained in the docs. > > > 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. > > > > See "useOriginalwsdl" above. > > > 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 > > > > There was talk of an xml schema at one point for service.xml, search > the source distro or google for it. The docs could be the best you can > do on that ... not sure. > > > Thanks a lot > > Sebastian > > --------------------------------------------------------------------- > 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
