> 4) when trying to generate a client using an Axis 1.2 WSDL2Java from the > automatically generated WSDL > > http://localhost:8080/axis2/services/wublast2?wsdl > > which has renamed some of the elements from the original WSDL > I got an java.io.Exception, Erro: missing type of ref attribute for node > 'unknown'. WSDL2Java works fine if I use the original WSDL
May be this is a bug .. if nobody answers back file a bug report at jira (https://issues.apache.org/jira/browse/AXIS2). I think our wsdl generation need to be fixed > > 5) but trying to access it through an aplication using the generated stub > with Axis 1.2 WSDL2Java > > I got this error > > [java] Operation Not found > EPR is http://localhost:8080/axis2/services/wublast2 and WSA Action = > > it should be trying to access the blast operation > > but I suppose is becouse of the modifications in the namespaces between > both wsdl files > > trying to use this in the browser > http://localhost:8080/axis2/services/wublast2 I got an Oh! this > place seems to be empty!!! message, maybe it is a related problem > > so, after this, some questions, > > a) can I call Axis2 services using previous Axis version clients or > WSDL2Java? Yes .. that is idea of using Web Services .. I think problem is Axis2 do not have information to find the operation. You should do ONE of the follwoing to make sure Axis2 server can find the operation 1) change the EPR to http://localhost:8080/axis2/services/wublast2/<operation-name> 2) put SOAP action as <operation-name> 3) Use WS-Addressing with wsa:action > b) where should I place jars needed by my service, in a lib directory in > the aar file? Yes AFAIK it works > c) is there any chance of this service to work, or should I be using > Axis2 clients instead? You can test with Axis2 client .. but as I say in #a .. this should work .. if we can not it is a bug in Axis2 .. we should fix it. Thanks Srinath
