Remember the issues that occur during the process of generating the WebService server with axis in eclipse

Question One,

Unable to find config file. Creating new servlet engine config file:/WEB-INF/SERVER-CONFIG.WSDD

Can't find this. WSDD configuration file, not automatically generated!

The reason is that the last step is not performed when using eclipse to automatically generate an axis server!

When you do this, you need to click on the button to start the service, then the Next button will be available, and the Next button will automatically generate this. wsdd file!

Question Two,

Axisfault
FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}server.generalexception
Faultsubcode:
Faultstring:maketypeelement () was told to create a type ...

This is the error that occurs when you click the WSDL link to view the HTTP://127....?WSDL document after publishing the service, but not when you access it? WSDL is all right!

This error occurs because the parameter in the interface method is a complex type and there are complex types in the constructor of the parameter! eq

<xs:elementname= "OrderList"minOccurs= "0">                <Xs:complextype>                    <xs:sequence>                        <xs:elementname= "Order"type= "Tns:ordertype"minOccurs= "0"maxOccurs= "unbounded"/>                    </xs:sequence>                </Xs:complextype>            </xs:element>

In the above code, OrderList is a parameter in an interface method and is a complex type, and order is a complex type.

This issue does not affect the call of the server and client of axis, which is said to be a bug in axis, and does not seem to appear every time! Do not know when to appear, may also be related to the browser! ......

For normal display, you can also modify this, extract the complex type, and add the type parameter to OrderList. eg

<xs:elementname= "OrderList"minOccurs= "0"type= "Tns:orderlisttype"></xs:element><Xs:complextypename= "Orderlisttype">        <xs:sequence>            <xs:elementname= "Order"type= "Tns:ordertype"maxOccurs= "unbounded"/>        </xs:sequence>    </Xs:complextype>

2:) WSDL does not display normally the general call that affects CXF, because CXF's client is generated on a WSDL basis! The general invocation method is as follows:

  New Service (Wsdlurl, service_name);   = Ss.getport ();  Port.getinfo ();  

Where WSDL is the focus, the display of the WSDL affects the invocation.

To avoid this effect, the CXF client can adapt to another method when invoking the server: EQ:

New Jaxwsproxyfactorybean (); Factory.setserviceclass (PortType. class  = (PortType) factory.create ();

RPI

Question three,

Forget, think again.

Remember the issues that occur during the process of generating the WebService server with axis in eclipse