From 946150eb4a832e5d61acfa12632109f2215a4c86 Mon Sep 17 00:00:00 2001 From: kprice Date: Wed, 31 Jan 2007 13:40:00 +0000 Subject: [167443] removing nested tags breaking F1 help, updating version numbers --- .../META-INF/MANIFEST.MF | 2 +- .../plugin.xml | 2 +- .../wsconsumptionui-f1Contexts.xml | 40 ++++----- .../wscreationui-f1Contexts.xml | 47 +++++------ .../META-INF/MANIFEST.MF | 2 +- docs/org.eclipse.wst.ws.infopop/plugin.xml | 2 +- .../webserviceui-f1Contexts.xml | 96 ++++++++-------------- 7 files changed, 79 insertions(+), 112 deletions(-) diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF index a450cd021..8da9cf190 100644 --- a/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF +++ b/docs/org.eclipse.jst.ws.consumption.infopop/META-INF/MANIFEST.MF @@ -2,6 +2,6 @@ Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: %pluginName Bundle-SymbolicName: org.eclipse.jst.ws.consumption.infopop; singleton:=true -Bundle-Version: 1.0.201.qualifier +Bundle-Version: 1.0.202.qualifier Bundle-Vendor: %pluginProvider Bundle-Localization: plugin diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml index 8d28fdb73..cc9d1f891 100644 --- a/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml +++ b/docs/org.eclipse.jst.ws.consumption.infopop/plugin.xml @@ -2,7 +2,7 @@ On this page select the artifact from which your Web client will be created, and the stages of Web services development that you want to complete: - +- Develop: this will create the client code +- Assemble: this ensures that the project that will host the client gets associated to an EAR when required by the target application server +- Deploy: this will create the deployment code for the client +- Install: this will install the client on the chosen server +- Start: this will start the server once the client has been installed on it +- Test: this will provide various options for testing the client Select the server and runtime for your Web client, and whether or not you want to publish or monitor the service. @@ -93,14 +90,13 @@ service will be overwritten by the client's generated artifacts. Select the stages of Web services client development that you want to complete using the slider: - +- Develop: this will create the client code +- Assemble: this ensures that the project that will host the client gets associated to an EAR when required by the target application server +- Deploy: this will create the deployment code for the client +- Install: this will install the client on the chosen server +- Start: this will start the server once the client has been installed on it +- Test: this will provide various options for testing the client + @@ -434,14 +430,14 @@ to complete using the slider: -

These tables respresents the the types of projects available into which you can generate +These tables respresents the the types of projects available into which you can generate a Web service or client. You cannot add or remove project types, however you can change the order in which they appear in the Web services wizard. This is useful if you are creating several Web services that use the same type of service or client project because you can set that service or client project type as the default. To change the order, select a project type and use the up and down arrows to move it within the list. Changing the -order of the list does not restrict your ability to select any of the options.

-

If you select the check box, by default the Web services wizard will generate the Web services -server and client code into different EARs. It is recommended that you enable this feature.

+order of the list does not restrict your ability to select any of the options. +If you select the check box, by default the Web services wizard will generate the Web services +server and client code into different EARs. It is recommended that you enable this feature. diff --git a/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml b/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml index a82cbaf01..d2ccfe8ef 100644 --- a/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml +++ b/docs/org.eclipse.jst.ws.consumption.infopop/wscreationui-f1Contexts.xml @@ -1,7 +1,7 @@ On this page select the artifact from which your Web service or client will be created, and the stages of Web services development that you want to complete: - +- Develop: this will create the service code +- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server +- Deploy: this will create the deployment code for the service +- Install: this will install the service on the chosen server +- Start: this will start the server once the service has been installed on it +- Test: this will provide various options for testing the service Select the server and runtime for your Web service or client, and whether or not you want to publish or monitor the service. @@ -117,14 +114,13 @@ will be used to generate the service Select the stages of Web services development that you want to complete using the slider: - +- Develop: this will create the service code +- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server +- Deploy: this will create the deployment code for the service +- Install: this will install the service on the chosen server +- Start: this will start the server once the service has been installed on it +- Test: this will provide various options for testing the service + @@ -159,14 +155,13 @@ service will be overwritten by the client's generated artifacts. Select the stages of Web services client development that you want to complete using the slider: - +- Develop: this will create the client code +- Assemble: this ensures that the project that will host the Web service or client gets associated to an EAR when required by the target application server +- Deploy: this will create the deployment code for the client +- Install: this will install the client on the chosen server +- Start: this will start the server once the client has been installed on it +- Test: this will provide various options for testing the client + diff --git a/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF index 77d6061f8..34c8d83f6 100644 --- a/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF +++ b/docs/org.eclipse.wst.ws.infopop/META-INF/MANIFEST.MF @@ -2,7 +2,7 @@ Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: %pluginName Bundle-SymbolicName: org.eclipse.wst.ws.infopop; singleton:=true -Bundle-Version: 1.0.201.qualifier +Bundle-Version: 1.0.202.qualifier Bundle-Localization: plugin Eclipse-LazyStart: true Bundle-Vendor: %providerName diff --git a/docs/org.eclipse.wst.ws.infopop/plugin.xml b/docs/org.eclipse.wst.ws.infopop/plugin.xml index 8b54fb02f..3fe3bfd65 100644 --- a/docs/org.eclipse.wst.ws.infopop/plugin.xml +++ b/docs/org.eclipse.wst.ws.infopop/plugin.xml @@ -2,7 +2,7 @@ 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. 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. 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. @@ -64,11 +54,9 @@ You can set the level of compliance for either the Basic Profile and the Simple 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. @@ -76,11 +64,9 @@ You can select which types of WSDL files to run validation on: 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. @@ -88,11 +74,9 @@ You can select which types of WSDL files to run validation on: 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. @@ -107,11 +91,9 @@ If you select to wait for WSDL validation to complete, the Web services wizards 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. @@ -119,11 +101,9 @@ You can select which types of WSDL files to run validation on: 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. @@ -131,11 +111,9 @@ You can select which types of WSDL files to run validation on: 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. @@ -143,11 +121,9 @@ You can select which types of WSDL files to run validation on: 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. -- cgit v1.2.3