jst/components/ws/1.5.2/news/jst-ws-1.5.2news.html - gerrit/www.eclipse.org/webtools - Git at Google

 <!doctype html public "-//w3c//dtd html 4.0 transitional//en">
 <html>
 <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
    <meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
    <title>Web Tools Platform 1.0 News and Noteworthy for Web Services
 Tools</title>
 <link rel="stylesheet"
 	href="../../../../../development/news/default_style.css" />
 </head>
 <body>

 <h1>
 Web Tools Platform 1.5.2 Release - New and Noteworthy for Web Services Tools</h1>

 <table BORDER=0 CELLSPACING=0 CELLPADDING=10 WIDTH="85%" >
 <caption><tbody>
 <br></tbody></caption>

 <tr>
 <td COLSPAN="2">
 <hr /></td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <h3>
 Highlights</h3>
 </td>
 </tr>


 <tr>
 <td COLSPAN="2">
 <p>
 Here are the highlights of the changes to the Web services tools since the WTP 1.0 release:


 		<ul>
 			<li>In WTP 1.5, the first 3 pages of the Web Service wizards had been combined. By using
 			the scale setting slider on the left-hand side of the Web Service wizards,
 			you can independently control how much of the J2EE life cycle you want to do with the
 			Web service and Web service client.  Valid scale settings for the service and client
 			side are:
 			<ul>
 			<li>Develop</li>
 			<li>Assemble</li>
 			<li>Deploy</li>
 			<li>Install</li>
 			<li>Start</li>
 			<li>Test</li>
 			</ul>
 			<p>For example, to start the Web service and to test the Web service client, you
 			would move the scales to the following:</p>
 			<br>
 			<img border="0" src="WSWizard.png">

 			<p>You could also use the hyperlinks under the <b>Configuration</b> group on
 			the right-hand side to change the server, Web service runtime, project and EAR.</p>
 			</li>
 			<li>In WTP 1.5, the Apache Axis runtime JARs has been updated from Axis 1.2.1 to Axis 1.3 </li>
 			<li>Aside from the items listed above, the focus in WTP 1.5.2 has been on fixing defects to
 			improve on quality of the Web Services tools.

 </li>
 		</ul></td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <hr /></td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <h3>
 Tutorials</h3>
 </td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <hr /></td>
 </tr>

 <tr>
 <td COLSPAN="2">The following tutorials demonstrate functionality of the Web Services tools in the 1.0M9 release:
 <ul>
 <li>
 <a href="../../1.5/tutorials/BottomUpWebService/BottomUpWebService.html">Creating bottom-up Web Service</a></li>

 <li>
 <a href="../../1.5/tutorials/TopDownWebService/TopDownWebService.html">Creating top-down Web Service</a></li>

 <li>
 <a href="../../1.5/tutorials/WebServiceClient/WebServiceClient.html">Creating Web Service Client</a></li>

 <li>
 <a href="../../1.0/tutorials/WebServiceAntTask/WebServiceAntTask.html">Web Service Ant Tasks</a></li>

 <li>
 <a href="../../1.0/tutorials/WebServiceExplorer/WebServiceExplorer.html">Using Web Service Explorer
 to test a Web service</a></li>
 </ul>
 </td>
 </tr>
 <tr>
 <td COLSPAN="2">
 <hr /></td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <a name="known-problems" />
 <h3>
 Known Problems</h3>
 </td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <hr /></td>
 </tr>

 <tr>
 <td COLSPAN="2">
 <p>
 Please be aware of the following known problems when using the Web Services
 tools.&nbsp; See the associated Bugzilla defect for further details.</p>

 <!-- https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&component=jst.ws&component=wst.command&component=wst.ws&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=114852%2C+85823%2C+92429%2C+103999%2C+105089%2C+105087%2C+106239%2C+104993%2C+116025%2C+121605%2C+121199%2C+121082%2C+120140%2C+119954%2C+119508%2C+119296%2C+119167%2C+118623%2C+118315%2C+119165&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= -->

 <ul>
 <li>Creating Web service or Web service client</li>
 <ul>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119508">119508</a></b>:
 When creating top-down Web service or Web service client, if you are entering an URI
 to a WSDL or WSIL document not in the workspace, make sure that the document is loaded and the
 table below the URI titled <b>Select a WSDL</b> is populated before proceeding with the wizard.
 Otherwise, you may get an error message <tt>Selection must be WSDL</tt> and the fields
 in the next page may be empty.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=108623">118623</a></b>:
 When creating Web service client, do not choose to generate Web service client proxy in the same
 Web project as the one containing the Web service since if you selected <b>Overwrite file without warning</b>,
 the generated Web service client proxy will overwrite the Web service implementation files contained in the Web
 service project.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=145857">145857</a></b>:
 The Web services wizard
 may produce an error during creation of a Web service if the name of the target
 Web project includes non-latin-1 characters. The problem occurs because the
 Web services code generators calculate HTTP URLs based on the project name,
 and non-Latin-1 characters are not permitted in HTTP URLs. To resolve this,
 use project names that contain only latin-1 characters.</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159458">159458</a></b>:
 You might get the
 following error when running through the Web service wizard if you delete
 the server runtime after you've created a server on that runtime or delete
 the sever adapter plugins:
 <pre>IWAB0014E Unexpected exception occured.
       java.lang.NullPointerException
       at
 org.eclipse.jst.ws.internal.consumption.ui.wsrt.WebServiceRuntimeExtensionUtils2.getAllServerFactoryIdsWithRuntimes(Unknown Source)</pre>
 Do
 not delete the server runtime after you have created a server.  Delete the
 server first if you need to delete a server runtime.  Also, do not use the
 same workspace if you have added or removed server adapters (such as by clicking
 on the "Don't see your server listed?  Click here" link in the Server ->Installed
 runtimes preference page).</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159618">159618</a></b>:
 If you select a
 Web service or Web service client from the JSR-109 branch of the J2EE perspective
 and then launch the Web services wizard, several fields in the wizard may
 not be filled in correctly. You can select the correct server, runtime
 environment, project and EAR values by clicking the appropriate hyperlinks in the Web Services wizards.</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=138502">138502</a></b>:
 The default server,
 runtime environment, project and EAR on the first page of the Web services
 wizards may change depending on what you select for the Web service type,
 Web service implementation, server and runtime.  Ensure that all fields and
 configurations are what your Web service or client requires before clicking <span class="uicontrol">Next</span> or <span class="uicontrol">Finish</span> on
 the wizard.</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117924">117924</a></b>:
 When generating an Axis
 Web service client in a Java project with the option to test using
 the sample JSP enabled, you will receive an HTTP 500 internal server error
 in the result pane of the JSP.  To eliminate this error,  generate into a Web project instead of a Java project. Another
 alternative is to manually copy the Axis JARs into the WebContent/WEB-INF/lib
 directory of the Web project containing the sample JSP.</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159356">159356</a></b>:
 If you create an Axis Web service on a Tomcat server running on port
 	other than 8080, you might run into problem deploying to Axis if the
 	server has not been started or the module has not been associated with
 	the server. You can avoid the problem by using the default port of
 	8080, starting the server, or associating the Web module with the
 	server before running the Web service wizard.</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161426">161426</a></b>:
 When using the context menu in the JSR Web Services branch of the J2EE Project Explorer to create Web service, if
 you have select to <b>Hide create Web service dialog</b> in the Web Services Popup Dialog preference,
 you might run into an
 <pre>IWAB0014E Unexpected exception occured.
 org.eclipse.jst.j2ee.webservice.wsdd.internal.impl.ServiceImplBeanImpl
 incompatible with java.lang.String
       java.lang.ClassCastException:
 </pre>
 To avoid the problem, do
 not hide the popup dialog or use the Web Service wizard instead of the context menu.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=162288">162288</a></b>:
 When creating top-down Web service in a workspace with space in the path, the wizard would not
 launch the Java Editor on the skeleton implementation file.  You will need to manually open
 the editor on the skeleton implementation file which has the naming convention of <WSDL port name>Impl.java.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161589">161589</a></b>:
 When creating a top-down Web service, if the service definition is blank, you click
 Browse and then Cancel, you might get the following error:
 <pre>IWAB0014E Unexpected exception occured.
       java.lang.NullPointerException
       at
 org.eclipse.jst.ws.internal.creation.ui.extension.PreServiceDevelopCommand.execute(PreServiceDevelopCommand.java:113)
 </pre>
 To avoid the problem, select a valid WSDL in the Browse dialog rather than clicking Cancel.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=160497">160497</a></b>:
 When accessing a HTTP basic authentication enabled WSDL using the Web Services wizard,
 the wizard prompts the user to enter the userid and password.  This userid and password
 is being remembered for the duration of the workbench.  To be able to enter
 a different userid or password, the workaround is to restart Eclipse.
 </li>
 </ul>

 <li>Preference</li>
 <ul>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116025">116025</a>
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=130965">130965</a>
 </b>:
 The Web services Server Runtime preference page currently displays all server types in
 the "Server" combo box and all Web service runtimes in the "Web service
 runtime" combo box, instead of filtering them so that only compatible
 combinations appear. Also, the Web service runtime might change when a different
 server is picked.  This means the user should check that the server and runtimes are
 what the user intented to choose and are valid combinations before applying the preference
 change.
 </li>
 </ul>

 <li>Supported servers</li>
 <ul>
 <li>
 <b>
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119964">119964</a>
 </b>:
 When creating Axis Web services on certain servers (such as Geronimo,
 JBoss or Tomcat running outside of the workspace), the <kbd
 		class="userinput">server-config.wsdd</kbd> file needed by the Axis
 	runtime to determine what has been deployed is not persisted in the
 	workspace. You will be able to invoke a Web service right after it is
 	created but will get the error "Could not find the target service"
 	after another Web service is deployed or in general after the project
 	republishes. To resolve this problem, deploy the generated <kbd
 		class="userinput">deploy.wsdd </kbd>(this can be found in
 	subdirectories under the WebContent/WEB-INF directory of the Web
 	project) to Axis manually using the Axis AdminClient tool . Refer to
 	"Using the AdminClient " section of the Axis 1.3 User's Guide for more
 	detail.</li>
 </ul>

 <li>Web Services Explorer</li>
 <ul>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92429">92429</a></b>:
 The Web Services Explorer does not work with the Netscape browser. Change
 the default Web Browser by using <b>Window -> Preferences -> General ->
 Web Browser</b>.&nbsp;</li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=282413">282413</a></b>:
 When the Web Services
 Explorer loads WSDL files that use multiple inline schemas, warning messages
 will be generated for types that are referenced across these schemas. The
 warning message will be similar to: <samp class="codeph">Reference of type &lt;<em>qualified_type_name</em>&gt;
 isn't resolved.</samp> These are warnings and not errors and will not interfere
 with the Web Services Explorer's ability to invoke operations, and therefore
 can be safely ignored.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=214876">214876</a></b>:
 When using the Web Services
 Explorer with the Private UDDI Registry, the Manage Publisher Assertion Form
 of a business node will not load in the following situations: <ul><li>You are not logged in to the registry node containing the business node.</li>
 <li>You are logged in to the registry node containing the business node, but
 the business node is not owned by the User ID/Password that is used to log
 in to the containing registry.</ul>
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=257398">257398</a></b>:
 When attempting to publish
 a business, service or service interface to the XMethods UDDI Registry, you
 may get an error message regarding an "SSL Handshake Failure". XMethods UDDI
 registry should be used for discovery purposed only.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=132850">132850</a></b>:
 The Web Services Explorer
 does not support invocation of Web services via authenticating proxy servers
 that use a protocol other then HTTP Basic Authentication, such as NTLM. If
 the Web Services Explorer fails to connect to the chosen Web service for this
 or any other reason, it will display in its results pane the error <kbd class="userinput">IWAB0135E
 An unexpected error has occurred</kbd> followed by information about
 the failure as retrieved from the HTTP response. To resolve this issue, switch
 to an HTTP Basic Authenticating proxy server.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=145615">145615</a></b>:
 Web Services Explorer
 has problems when switching from the source view to the form view when the
 schema uses choices containing sequences. If you are using a choice element
 in a complexType, the choice contains two or more elements including a sequence,
 and you switch from the form view to the source view, the Web Services Explorer
 may be unable to correctly convert the corresponding XML fragment in the source
 view back into the form view without losing data. To resolve this, invoke
 the sequence from the form view when the data is initially entered. When this
 configuration occurs, it is not recommended the source view be used. If the
 source view is used, do not switch back to the form view.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=150666">150666</a></b>:
 The Web Services Explorer
 imports WSDL without resolving relative import URLs.  When using the Web Services
 Explorer, there is an issue when importing a WSDL from the WSDL Page to the
 workspace. If the option <span class="uicontrol">Import as a service reference to a WSIL
 document</span> is chosen, this will refer to the original URL of the
 WSDL and therefore all relative imports will be reachable. If <span class="uicontrol">Import
 WSDL Document</span> is chosen and the WSDL file contains relative imports
 these will no longer be reachable, leaving the copy of the WSDL difficult
 or impossible to process elsewhere in the tools. It is recommended that if
 there are relative imports in the WSDL you are importing the WSIL method should
 be used. If the there is a need for a copy of the WSDL a check for relative
 imports should be made manually after the import to resolve any broken links.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161112">161112</a></b>:
 The Web Services Explorer cannot find business thru a proxy server that needs
 basic authentication.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=151174">151174</a></b>:
 Unpublished service interfaces
 show up after re-login in the Web Services Explorer. When a service interface
 (tModel) is unpublished, it is removed from the Publish Service Interface
 node, but after re-logging in to the UDDI registry the removed service interface
 is still listed.  To resolve this, delete the interface again or ignore it.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105089">105089</a></b>:
 The Web Service Explorer may run into error opening WSIL files containing Japanese
 characters. You might get an error indicating that the document "is not a valid WSIL URL
 or HTML URL" or corrupted characters in the Web Service Explorer WSIL page summary table.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105087">105087</a></b>:
 The Web Service Explorer is unable to publish objects with non-English name.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=106239">106239</a></b>:
 When using the Web Services Explorer with the IBM UDDI Test Registry to add business assertions,
 you might get an error message stating that the business in not owned by you.</li>

 </ul>
 <li>Web Services Ant Command line</li>
 <ul>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119964">119964</a></b>:
 The Web Services
 Ant tasks targetting the Axis runtime handle the generation of Web services,
 but not the deployment of them. As a result, Axis Web services created using
 the Ant tasks will not be reachable on the running server until you manually
 deploy your services using the Apache Axis native "AdminClient" utility.
 Deploy the generated deploy.wsdd (this can be found in subdirectories under
 the WebContent/WEB-INF directory of the Web project) to Axis manually using
 the Axis AdminClient tool . Refer to "Using the AdminClient " section of
 the Axis 1.3 User's Guide for more detail.
 </li>
 <li><b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159283">159283</a></b>:
 When generating
 a Web service or Web service client using Ant on the command line, and the
 target runtime supports EAR association, the created project will not be associated
 with the EAR project. This occurs if the EAR is initially empty, or when the
 EAR does not exist in the workspace at all. This results in validation errors
 against the EAR because it must have at least one associated module. The errors,
 which are seen in the wsgen.txt output file, looks like the following:
 <pre>
 *** ERROR ***: Thu Sep 28 15:11:14 EDT 2006    org.eclipse.emf.common.util.WrappedException:
 org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element
 'application' is not complete. One of '{"http://java.sun.com/xml/ns/j2ee":display-name,
 "http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":module}'
 is expected.
 </pre>
 <p>To workaround the problem, associate the project to the EAR manually before running
 the Web Serive Ant command line.</p>
 </li>

 </ul>

 </ul>
 </td>
 </tr>
 </table>


 </body>
 </html>
	<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
	<html>
	<head>
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
	<meta name="GENERATOR" content="Mozilla/4.75 [en] (Windows NT 5.0; U) [Netscape]">
	<title>Web Tools Platform 1.0 News and Noteworthy for Web Services
	Tools</title>
	<link rel="stylesheet"
	href="../../../../../development/news/default_style.css" />
	</head>
	<body>

	<h1>
	Web Tools Platform 1.5.2 Release - New and Noteworthy for Web Services Tools</h1>

	<table BORDER=0 CELLSPACING=0 CELLPADDING=10 WIDTH="85%" >
	<caption><tbody>
	<br></tbody></caption>

	<tr>
	<td COLSPAN="2">
	<hr /></td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<h3>
	Highlights</h3>
	</td>
	</tr>


	<tr>
	<td COLSPAN="2">
	<p>
	Here are the highlights of the changes to the Web services tools since the WTP 1.0 release:


	<ul>
	<li>In WTP 1.5, the first 3 pages of the Web Service wizards had been combined. By using
	the scale setting slider on the left-hand side of the Web Service wizards,
	you can independently control how much of the J2EE life cycle you want to do with the
	Web service and Web service client. Valid scale settings for the service and client
	side are:
	<ul>
	<li>Develop</li>
	<li>Assemble</li>
	<li>Deploy</li>
	<li>Install</li>
	<li>Start</li>
	<li>Test</li>
	</ul>
	<p>For example, to start the Web service and to test the Web service client, you
	would move the scales to the following:</p>
	<br>
	<img border="0" src="WSWizard.png">

	<p>You could also use the hyperlinks under the <b>Configuration</b> group on
	the right-hand side to change the server, Web service runtime, project and EAR.</p>
	</li>
	<li>In WTP 1.5, the Apache Axis runtime JARs has been updated from Axis 1.2.1 to Axis 1.3 </li>
	<li>Aside from the items listed above, the focus in WTP 1.5.2 has been on fixing defects to
	improve on quality of the Web Services tools.

	</li>
	</ul></td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<hr /></td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<h3>
	Tutorials</h3>
	</td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<hr /></td>
	</tr>

	<tr>
	<td COLSPAN="2">The following tutorials demonstrate functionality of the Web Services tools in the 1.0M9 release:
	<ul>
	<li>
	<a href="../../1.5/tutorials/BottomUpWebService/BottomUpWebService.html">Creating bottom-up Web Service</a></li>

	<li>
	<a href="../../1.5/tutorials/TopDownWebService/TopDownWebService.html">Creating top-down Web Service</a></li>

	<li>
	<a href="../../1.5/tutorials/WebServiceClient/WebServiceClient.html">Creating Web Service Client</a></li>

	<li>
	<a href="../../1.0/tutorials/WebServiceAntTask/WebServiceAntTask.html">Web Service Ant Tasks</a></li>

	<li>
	<a href="../../1.0/tutorials/WebServiceExplorer/WebServiceExplorer.html">Using Web Service Explorer
	to test a Web service</a></li>
	</ul>
	</td>
	</tr>
	<tr>
	<td COLSPAN="2">
	<hr /></td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<a name="known-problems" />
	<h3>
	Known Problems</h3>
	</td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<hr /></td>
	</tr>

	<tr>
	<td COLSPAN="2">
	<p>
	Please be aware of the following known problems when using the Web Services
	tools.  See the associated Bugzilla defect for further details.</p>

	<!-- https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Web+Tools&component=jst.ws&component=wst.command&component=wst.ws&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=114852%2C+85823%2C+92429%2C+103999%2C+105089%2C+105087%2C+106239%2C+104993%2C+116025%2C+121605%2C+121199%2C+121082%2C+120140%2C+119954%2C+119508%2C+119296%2C+119167%2C+118623%2C+118315%2C+119165&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= -->

	<ul>
	<li>Creating Web service or Web service client</li>
	<ul>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119508">119508</a></b>:
	When creating top-down Web service or Web service client, if you are entering an URI
	to a WSDL or WSIL document not in the workspace, make sure that the document is loaded and the
	table below the URI titled <b>Select a WSDL</b> is populated before proceeding with the wizard.
	Otherwise, you may get an error message <tt>Selection must be WSDL</tt> and the fields
	in the next page may be empty.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=108623">118623</a></b>:
	When creating Web service client, do not choose to generate Web service client proxy in the same
	Web project as the one containing the Web service since if you selected <b>Overwrite file without warning</b>,
	the generated Web service client proxy will overwrite the Web service implementation files contained in the Web
	service project.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=145857">145857</a></b>:
	The Web services wizard
	may produce an error during creation of a Web service if the name of the target
	Web project includes non-latin-1 characters. The problem occurs because the
	Web services code generators calculate HTTP URLs based on the project name,
	and non-Latin-1 characters are not permitted in HTTP URLs. To resolve this,
	use project names that contain only latin-1 characters.</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159458">159458</a></b>:
	You might get the
	following error when running through the Web service wizard if you delete
	the server runtime after you've created a server on that runtime or delete
	the sever adapter plugins:
	<pre>IWAB0014E Unexpected exception occured.
	java.lang.NullPointerException
	at
	org.eclipse.jst.ws.internal.consumption.ui.wsrt.WebServiceRuntimeExtensionUtils2.getAllServerFactoryIdsWithRuntimes(Unknown Source)</pre>
	Do
	not delete the server runtime after you have created a server. Delete the
	server first if you need to delete a server runtime. Also, do not use the
	same workspace if you have added or removed server adapters (such as by clicking
	on the "Don't see your server listed? Click here" link in the Server ->Installed
	runtimes preference page).</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159618">159618</a></b>:
	If you select a
	Web service or Web service client from the JSR-109 branch of the J2EE perspective
	and then launch the Web services wizard, several fields in the wizard may
	not be filled in correctly. You can select the correct server, runtime
	environment, project and EAR values by clicking the appropriate hyperlinks in the Web Services wizards.</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=138502">138502</a></b>:
	The default server,
	runtime environment, project and EAR on the first page of the Web services
	wizards may change depending on what you select for the Web service type,
	Web service implementation, server and runtime. Ensure that all fields and
	configurations are what your Web service or client requires before clicking <span class="uicontrol">Next</span> or <span class="uicontrol">Finish</span> on
	the wizard.</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117924">117924</a></b>:
	When generating an Axis
	Web service client in a Java project with the option to test using
	the sample JSP enabled, you will receive an HTTP 500 internal server error
	in the result pane of the JSP. To eliminate this error, generate into a Web project instead of a Java project. Another
	alternative is to manually copy the Axis JARs into the WebContent/WEB-INF/lib
	directory of the Web project containing the sample JSP.</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159356">159356</a></b>:
	If you create an Axis Web service on a Tomcat server running on port
	other than 8080, you might run into problem deploying to Axis if the
	server has not been started or the module has not been associated with
	the server. You can avoid the problem by using the default port of
	8080, starting the server, or associating the Web module with the
	server before running the Web service wizard.</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161426">161426</a></b>:
	When using the context menu in the JSR Web Services branch of the J2EE Project Explorer to create Web service, if
	you have select to <b>Hide create Web service dialog</b> in the Web Services Popup Dialog preference,
	you might run into an
	<pre>IWAB0014E Unexpected exception occured.
	org.eclipse.jst.j2ee.webservice.wsdd.internal.impl.ServiceImplBeanImpl
	incompatible with java.lang.String
	java.lang.ClassCastException:
	</pre>
	To avoid the problem, do
	not hide the popup dialog or use the Web Service wizard instead of the context menu.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=162288">162288</a></b>:
	When creating top-down Web service in a workspace with space in the path, the wizard would not
	launch the Java Editor on the skeleton implementation file. You will need to manually open
	the editor on the skeleton implementation file which has the naming convention of <WSDL port name>Impl.java.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161589">161589</a></b>:
	When creating a top-down Web service, if the service definition is blank, you click
	Browse and then Cancel, you might get the following error:
	<pre>IWAB0014E Unexpected exception occured.
	java.lang.NullPointerException
	at
	org.eclipse.jst.ws.internal.creation.ui.extension.PreServiceDevelopCommand.execute(PreServiceDevelopCommand.java:113)
	</pre>
	To avoid the problem, select a valid WSDL in the Browse dialog rather than clicking Cancel.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=160497">160497</a></b>:
	When accessing a HTTP basic authentication enabled WSDL using the Web Services wizard,
	the wizard prompts the user to enter the userid and password. This userid and password
	is being remembered for the duration of the workbench. To be able to enter
	a different userid or password, the workaround is to restart Eclipse.
	</li>
	</ul>

	<li>Preference</li>
	<ul>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116025">116025</a>
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=130965">130965</a>
	</b>:
	The Web services Server Runtime preference page currently displays all server types in
	the "Server" combo box and all Web service runtimes in the "Web service
	runtime" combo box, instead of filtering them so that only compatible
	combinations appear. Also, the Web service runtime might change when a different
	server is picked. This means the user should check that the server and runtimes are
	what the user intented to choose and are valid combinations before applying the preference
	change.
	</li>
	</ul>

	<li>Supported servers</li>
	<ul>
	<li>
	<b>
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119964">119964</a>
	</b>:
	When creating Axis Web services on certain servers (such as Geronimo,
	JBoss or Tomcat running outside of the workspace), the <kbd
	class="userinput">server-config.wsdd</kbd> file needed by the Axis
	runtime to determine what has been deployed is not persisted in the
	workspace. You will be able to invoke a Web service right after it is
	created but will get the error "Could not find the target service"
	after another Web service is deployed or in general after the project
	republishes. To resolve this problem, deploy the generated <kbd
	class="userinput">deploy.wsdd </kbd>(this can be found in
	subdirectories under the WebContent/WEB-INF directory of the Web
	project) to Axis manually using the Axis AdminClient tool . Refer to
	"Using the AdminClient " section of the Axis 1.3 User's Guide for more
	detail.</li>
	</ul>

	<li>Web Services Explorer</li>
	<ul>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=92429">92429</a></b>:
	The Web Services Explorer does not work with the Netscape browser. Change
	the default Web Browser by using <b>Window -> Preferences -> General ->
	Web Browser</b>. </li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=282413">282413</a></b>:
	When the Web Services
	Explorer loads WSDL files that use multiple inline schemas, warning messages
	will be generated for types that are referenced across these schemas. The
	warning message will be similar to: <samp class="codeph">Reference of type <<em>qualified_type_name</em>>
	isn't resolved.</samp> These are warnings and not errors and will not interfere
	with the Web Services Explorer's ability to invoke operations, and therefore
	can be safely ignored.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=214876">214876</a></b>:
	When using the Web Services
	Explorer with the Private UDDI Registry, the Manage Publisher Assertion Form
	of a business node will not load in the following situations: <ul><li>You are not logged in to the registry node containing the business node.</li>
	<li>You are logged in to the registry node containing the business node, but
	the business node is not owned by the User ID/Password that is used to log
	in to the containing registry.</ul>
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=257398">257398</a></b>:
	When attempting to publish
	a business, service or service interface to the XMethods UDDI Registry, you
	may get an error message regarding an "SSL Handshake Failure". XMethods UDDI
	registry should be used for discovery purposed only.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=132850">132850</a></b>:
	The Web Services Explorer
	does not support invocation of Web services via authenticating proxy servers
	that use a protocol other then HTTP Basic Authentication, such as NTLM. If
	the Web Services Explorer fails to connect to the chosen Web service for this
	or any other reason, it will display in its results pane the error <kbd class="userinput">IWAB0135E
	An unexpected error has occurred</kbd> followed by information about
	the failure as retrieved from the HTTP response. To resolve this issue, switch
	to an HTTP Basic Authenticating proxy server.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=145615">145615</a></b>:
	Web Services Explorer
	has problems when switching from the source view to the form view when the
	schema uses choices containing sequences. If you are using a choice element
	in a complexType, the choice contains two or more elements including a sequence,
	and you switch from the form view to the source view, the Web Services Explorer
	may be unable to correctly convert the corresponding XML fragment in the source
	view back into the form view without losing data. To resolve this, invoke
	the sequence from the form view when the data is initially entered. When this
	configuration occurs, it is not recommended the source view be used. If the
	source view is used, do not switch back to the form view.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=150666">150666</a></b>:
	The Web Services Explorer
	imports WSDL without resolving relative import URLs. When using the Web Services
	Explorer, there is an issue when importing a WSDL from the WSDL Page to the
	workspace. If the option <span class="uicontrol">Import as a service reference to a WSIL
	document</span> is chosen, this will refer to the original URL of the
	WSDL and therefore all relative imports will be reachable. If <span class="uicontrol">Import
	WSDL Document</span> is chosen and the WSDL file contains relative imports
	these will no longer be reachable, leaving the copy of the WSDL difficult
	or impossible to process elsewhere in the tools. It is recommended that if
	there are relative imports in the WSDL you are importing the WSIL method should
	be used. If the there is a need for a copy of the WSDL a check for relative
	imports should be made manually after the import to resolve any broken links.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=161112">161112</a></b>:
	The Web Services Explorer cannot find business thru a proxy server that needs
	basic authentication.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=151174">151174</a></b>:
	Unpublished service interfaces
	show up after re-login in the Web Services Explorer. When a service interface
	(tModel) is unpublished, it is removed from the Publish Service Interface
	node, but after re-logging in to the UDDI registry the removed service interface
	is still listed. To resolve this, delete the interface again or ignore it.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105089">105089</a></b>:
	The Web Service Explorer may run into error opening WSIL files containing Japanese
	characters. You might get an error indicating that the document "is not a valid WSIL URL
	or HTML URL" or corrupted characters in the Web Service Explorer WSIL page summary table.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105087">105087</a></b>:
	The Web Service Explorer is unable to publish objects with non-English name.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=106239">106239</a></b>:
	When using the Web Services Explorer with the IBM UDDI Test Registry to add business assertions,
	you might get an error message stating that the business in not owned by you.</li>

	</ul>
	<li>Web Services Ant Command line</li>
	<ul>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119964">119964</a></b>:
	The Web Services
	Ant tasks targetting the Axis runtime handle the generation of Web services,
	but not the deployment of them. As a result, Axis Web services created using
	the Ant tasks will not be reachable on the running server until you manually
	deploy your services using the Apache Axis native "AdminClient" utility.
	Deploy the generated deploy.wsdd (this can be found in subdirectories under
	the WebContent/WEB-INF directory of the Web project) to Axis manually using
	the Axis AdminClient tool . Refer to "Using the AdminClient " section of
	the Axis 1.3 User's Guide for more detail.
	</li>
	<li><b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=159283">159283</a></b>:
	When generating
	a Web service or Web service client using Ant on the command line, and the
	target runtime supports EAR association, the created project will not be associated
	with the EAR project. This occurs if the EAR is initially empty, or when the
	EAR does not exist in the workspace at all. This results in validation errors
	against the EAR because it must have at least one associated module. The errors,
	which are seen in the wsgen.txt output file, looks like the following:
	<pre>
	* ERROR *: Thu Sep 28 15:11:14 EDT 2006 org.eclipse.emf.common.util.WrappedException:
	org.xml.sax.SAXParseException: cvc-complex-type.2.4.b: The content of element
	'application' is not complete. One of '{"http://java.sun.com/xml/ns/j2ee":display-name,
	"http://java.sun.com/xml/ns/j2ee":icon, "http://java.sun.com/xml/ns/j2ee":module}'
	is expected.
	</pre>
	<p>To workaround the problem, associate the project to the EAR manually before running
	the Web Serive Ant command line.</p>
	</li>

	</ul>

	</ul>
	</td>
	</tr>
	</table>


	</body>
	</html>