Show TOC

Procedure documentationUsing Interactive Conflict Resolution Locate this document in the navigation structure

 

Use this procedure to do interactive conflict resolution when you create outside in Web services or generate Web service proxies.

Procedure

  1. If the WSDL document does not contain a service endpoint, the system prompts you to create a service endpoint and binding. On the Service, Port, Binding names selection screen, proceed as follows:

    1. Specify names for the service, port and binding with which you want the Web service tools to update the WSDL document. You can accept the default values.

      If the WSDL document you are using already contained binding information before you imported it, you cannot edit the name of the binding.

    2. Choose Next.

  2. On the Namespace – Package Mapping screen, proceed as follows:

    1. In the WSDL output package field, enter the name of the package in which you want the framework to generate the Java classes based on the following WSDL artifacts: service endpoint interface (SEI), service, binding, portType, and fault(s). The Java class for the SEI has the name of the WSDL portType and is generated based on the WSDL portType and binding.

      The Bean class, which implements the SEI, is generated in this same package.

      Note Note

      If the WSDL document imports other WSDL documents, only one package is generated with the name you specify.

      End of the note.

    2. In the Package field, specify the name of the package, which will be generated from the namespace of the XSD schema.

      Note Note

      If the WSDL document contains or includes/imports other XSD schemas each in a different namespace, a separate package is generated for each namespace.

      End of the note.

    3. Choose Next.

  3. On the Global Customizations Options screen, you can apply customizations compliant with the JAXB 2.0 specification, Chapter 7.5 <globalBinding> Declaration.

    More information about the meaning of each option: Global Customizations.

    Choose the relevant options.

  4. Depending on the Web service tools wizard, proceed as follows:

    • If you create a Web service outside-in, choose Next.

    • If you create a Web service proxy, choose Finish.

  5. The Found Collisions screen appears when very long Java class names would be generated or when there are still unresolved collisions.

    • In the Mapped to Name column, you can enter a shorter name for a Java class, or resolve any other collisions.

    • To automatically resolve the collisions, choose Resolve Collisions.

    If there are no collisions to resolve, the window does not open.

  6. Depending on the Web service tools wizard, proceed as follows:

    • If you create a Web service outside-in, choose Finish.

    • If you create a Web service proxy, choose OK.

  7. WSDL documents, which use the same schema may use the same types. If you are running the wizard on a WSDL document, for example WSDL_B, which uses the same schema as the WSDL document, for example WSDL_A, on which you have already run the wizard, the framework would have to generate Java classes based on WSDL_B that were already generated based on WSDL_A. When you runt the wizard on WSDL_B, the framework can keep the “duplicate” Java classes from the previous execution of the wizard (based on WSDL_A, in our example) or override the “duplicate” Java classes with the ones from the current execution of the wizard (based on WSDL_B, in our example).

    On the screen that opens, choose the existing files, which you want to the framework to override with the ones from the current generation. The files that you leave deselected are kept from the previous execution of the wizard. Choose OK.