diff options
Diffstat (limited to 'docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml')
-rw-r--r-- | docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml | 137 |
1 files changed, 0 insertions, 137 deletions
diff --git a/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml b/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml deleted file mode 100644 index bed6711b8..000000000 --- a/docs/org.eclipse.wst.ws.infopop/webserviceui-f1Contexts.xml +++ /dev/null @@ -1,137 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?NLS TYPE="org.eclipse.help.contexts"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2005 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> - -<contexts> - -<!--WSIPage.java--> -<context id="PWSI0001"> -<!--desc--> -<description>The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant. - -You can set the level of compliance for either the Basic Profile and the Simple SOAP Binding Profile, or for the Attachments Profile. You can select from three levels of compliance with WS-I specifications: -- Require WS-I compliance - this level prevents you from creating a non-compliant Web service. -- Suggest WS-I compliance - this level allows you to create a non-compliant Web service, but provides a visible warning stating how the service is non-compliant. -- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance. - -You can also select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. - -If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file. -</description> -</context> - -<context id="PWSI0004"> -<description>The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant. -You can set the level of compliance for either the Basic Profile and the Simple SOAP Binding Profile, or for the Attachments Profile. You can select from three levels of compliance with WS-I specifications: -- Require WS-I compliance - this level prevents you from creating a non-compliant Web service. -- Suggest WS-I compliance - this level allows you to create a non-compliant Web service, but provides a visible warning stating how the service is non-compliant. -- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance. -</description> -</context> - -<context id="PWSI0008"> -<description>The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant. -You can set the level of compliance for either the Basic Profile and the Simple SOAP Binding Profile, or for the Attachments Profile. You can select from three levels of compliance with WS-I specifications: -- Require WS-I compliance - this level prevents you from creating a non-compliant Web service. -- Suggest WS-I compliance - this level allows you to create a non-compliant Web service, but provides a visible warning stating how the service is non-compliant. -- Ignore WS-I compliance - this level allows you to create a non-compliant Web service and does not notify you of non-compliance. -</description> -</context> - -<context id="PWSI0009"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWSI0010"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWSI00011"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWSI0012"> -<!--desc--> -<description> -If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file. -</description> -</context> - -<context id="PWRS00009"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWRS00010"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWRS00011"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWRS00012"> -<!--desc--> -<description> -You can select which types of WSDL files to run validation on: -- By selecting "No wizard WSDL validation" the wizards will not run validation on the WSDL file. -- By selecting to run validation on remote files, the wizards will only validate WSDL files that exist outside of your workspace. -- By selecting to run validation on all WSDL files the wizard will validate all WSDL files, regardless of where they reside. -</description> -</context> - -<context id="PWRS0013"> -<!--desc--> -<description> -If you select to wait for WSDL validation to complete, the Web services wizards will prevent you from going forward and completing additional wizard pages once you have selected your WSDL file until that WSDL file has been validated. If the WSDL file is not valid, you will be given the option of exiting the wizard or continuing with the invalid WSDL file. -</description> -</context> - -</contexts>
\ No newline at end of file |