jst/components/ws/1.0M9/news/jst-ws-1.0M9news.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.0M8 News and Noteworthy for Web Services
 Tools</title>
 <link rel="stylesheet"
 	href="../../../../../development/news/default_style.css" />
 </head>
 <body>

 <h1>
 Web Tools Platform 1.0M9 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">Below you will find details about enhancements to the Web
 services tools in 1.0M9.
 <p>
 Here are the highlights of the changes to the Web services tools for 1.0M9:


 		<ul>
 			<li>The Web service and Web service client creation framework had been updated to be based
 			on project facet.  The support for multiple modules per project had also been removed from the
 			framework and from the Web service and Web service client wizards. Refer to the
 			 <b><a
 				href="http://eclipse.org/webtools/wst/components/ws/designs/108595.html">design document</a></b>
 				for enhancement 108595.</li>

 			<li>The user can create bottom-up Web service, top-down Web service and Web service client using Ant task.
 			Refer to <b><a
 				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=98921">98921</a></b>
 			for more detail.  Refer to the
 			<b><a href="../../1.0M9/tutorials/WebServiceAntTask.html">Web Service Ant Tasks tutorial</a></b>
 			for instructions on how to use the
 			Ant tasks.</li>
 		</ul>
 		<p>
 Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.8 milestone.

 </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.0M9/tutorials/BottomUpWebService.html">Creating bottom-up Web Service</a></li>

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

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

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

 <li>
 <a href="../../1.0M8/tutorials/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 href="#Known Problems">
 <h3>
 Known Problems</h3>
 </td>
 </tr>

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

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

 <ul>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=113933">113933</a></b>:
 When creating a Web service, you might get "Error occured when adding the module, null, to the server".
 Simply dismiss the error dialog and continue since the Web service scenario is successful despite
 the message.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=114852">114852</a></b>:
 When specifying <b>Test Web service</b> when going through the Web service or
 Web service client wizard, you might run into an intermittent problem where
 the generated sample JSP does not compile.  The workaround is to restart the server manually and
 refresh the sample JSP page.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=102117">102117</a></b>:
 When creating a Web service, you might get "Error when deploying Web service to Axis runtime"
 when the component/project containing the Web service had already
 been added to a started server.  The workaround is to restart the server manually
 before going through Web service wizard.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117742">117742</a></b>:
 When creating a Web service or Web service client using the Tomcat 4.1 server, if the Web project do
 not already exist, you will get "Error occured when adding the module to the server".
 The workaround is to manually create the Web project first before going through the
 Web service wizard.  When using the dynamic Web project wizard to create the Web project, hit <b>Next</b>
 to go to the second page and manually choose dynamic Web module version 2.3.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117073">117073</a></b>:
 When creating a bottom-up Web service, if the compiler compliance level of the Web
 project containing the service bean is not at the same level as the JRE used to launch
 Eclipse, you might get "Error in generating WSDL form Java:  java.lang.ClassNotFoundException".
 Change the compiler compliance level of the Web project by right-clicking on the project, select
 <b>Properties -> Java compiler</b> and select a compiler compliance level that matches with the JRE
 used to launch Eclipse.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85823">85823</a></b>:
 When creating a Web service from Java bean, if you specify <b>Generate
 proxy</b> and <b>Test the Web service</b>, compilation errors may show
 up in the server console the first time the server is started complaining
 about "package org.eclipse.jst.ws.util does not exist". This is a timing
 problem because webserviceUtils.jar, which contains the class org.eclipse.jst.ws.util.JspUtils,
 is not added to the WEB-INF/lib directory of the Web project in time for
 the JSP compile. Despite the error, eventually the sample JSPs come up
 OK and the Web service can be invoked successfully.&nbsp;</li>

 <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=86552">86552</a></b>:
 If the service name in the WSDL file used in Web service client scenario
 does not follow Java naming convention, e.g. having a lowercase first letter,
 the Proxy class generated by the Web service client wizard may not be able
 to correctly reference the generated type and may have compile errors.&nbsp;</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=99728">99728</a></b>:
 The Axis 1.1 runtime included in WTP is configured to support creation
 of Web services in projects targeted to Apache Tomcat or Geronimo. The
 Web service wizard will fail with "IWAB0234E An internal error occurred.
 Details: null java.lang.IllegalArgumentException" if the selected artifact,
 be it a Java bean or WSDL file, is contained in a project with a runtime
 target other than Tomcat or Geronimo.</li>

 <li>
 <b>
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117138">117138</a>,
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103999">103999</a>
 </b>:
 The Geronimo 1.0 Server is enabled for the Web service wizard but not yet fully
 functional due to these significant defects.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105090">105090</a></b>:
 Sample JSP launches with incorrect URL on SLES 9.0 when using the default browser
 "Konqueror".  The workaround is to manualy update the URL starting with "http:/localhost" to
 "http://localhost".</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105611">105611</a></b>:
 When running Web services scenarios, you might get a warning in the Tomcat
 console with the warning that "Attachment support is disabled".  This is expected
 and would not affect the running of the Web service.</li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105459">105459</a></b>:
 When creating Web service using Tomcat 4.1, if the server does not already exist,
 there may be an intermitten problem of "Error in starting server".  The workaround
 is delete the Tomcat 4.1 server created by the Web service wizard, create a Tomcat 4.1
 server manually before launching the Web service wizard.</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>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=104993">104993</a></b>:
 When creating bottom-up Web service, you might get the exception:<br/><tt>Unexpected exception occured.
 Detail: java.lang.NoClassDefFoundError: javax/activation/DataSource</tt>.
 <br/>Refer to comment #8 of the defect for workarounds.
 </li>

 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116025">116025</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. This means the user would be allowed to make an invalid
 selection without being stopped.
 </li>

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

 <p align="center">
 <!--<font color="#808080"><a href="../../../server/M8/new_and_noteworthy/server-M8.html">Previous</a></font>-->
 &nbsp;&nbsp;&nbsp;&nbsp;<a href="../../../../../development/news/1.0M9.html">Up</a>&nbsp;&nbsp;&nbsp;&nbsp;
 <!--<font color="#808080"><a href="../../../ws/1.0M8/news/jst-ws-1.0M8news.html">Next</a></font>-->
 </p>


 </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.0M8 News and Noteworthy for Web Services
	Tools</title>
	<link rel="stylesheet"
	href="../../../../../development/news/default_style.css" />
	</head>
	<body>

	<h1>
	Web Tools Platform 1.0M9 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">Below you will find details about enhancements to the Web
	services tools in 1.0M9.
	<p>
	Here are the highlights of the changes to the Web services tools for 1.0M9:


	<ul>
	<li>The Web service and Web service client creation framework had been updated to be based
	on project facet. The support for multiple modules per project had also been removed from the
	framework and from the Web service and Web service client wizards. Refer to the
	<b><a
	href="http://eclipse.org/webtools/wst/components/ws/designs/108595.html">design document</a></b>
	for enhancement 108595.</li>

	<li>The user can create bottom-up Web service, top-down Web service and Web service client using Ant task.
	Refer to <b><a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=98921">98921</a></b>
	for more detail. Refer to the
	<b><a href="../../1.0M9/tutorials/WebServiceAntTask.html">Web Service Ant Tasks tutorial</a></b>
	for instructions on how to use the
	Ant tasks.</li>
	</ul>
	<p>
	Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.8 milestone.

	</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.0M9/tutorials/BottomUpWebService.html">Creating bottom-up Web Service</a></li>

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

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

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

	<li>
	<a href="../../1.0M8/tutorials/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 href="#Known Problems">
	<h3>
	Known Problems</h3>
	</td>
	</tr>

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

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

	<ul>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=113933">113933</a></b>:
	When creating a Web service, you might get "Error occured when adding the module, null, to the server".
	Simply dismiss the error dialog and continue since the Web service scenario is successful despite
	the message.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=114852">114852</a></b>:
	When specifying <b>Test Web service</b> when going through the Web service or
	Web service client wizard, you might run into an intermittent problem where
	the generated sample JSP does not compile. The workaround is to restart the server manually and
	refresh the sample JSP page.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=102117">102117</a></b>:
	When creating a Web service, you might get "Error when deploying Web service to Axis runtime"
	when the component/project containing the Web service had already
	been added to a started server. The workaround is to restart the server manually
	before going through Web service wizard.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117742">117742</a></b>:
	When creating a Web service or Web service client using the Tomcat 4.1 server, if the Web project do
	not already exist, you will get "Error occured when adding the module to the server".
	The workaround is to manually create the Web project first before going through the
	Web service wizard. When using the dynamic Web project wizard to create the Web project, hit <b>Next</b>
	to go to the second page and manually choose dynamic Web module version 2.3.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117073">117073</a></b>:
	When creating a bottom-up Web service, if the compiler compliance level of the Web
	project containing the service bean is not at the same level as the JRE used to launch
	Eclipse, you might get "Error in generating WSDL form Java: java.lang.ClassNotFoundException".
	Change the compiler compliance level of the Web project by right-clicking on the project, select
	<b>Properties -> Java compiler</b> and select a compiler compliance level that matches with the JRE
	used to launch Eclipse.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=85823">85823</a></b>:
	When creating a Web service from Java bean, if you specify <b>Generate
	proxy</b> and <b>Test the Web service</b>, compilation errors may show
	up in the server console the first time the server is started complaining
	about "package org.eclipse.jst.ws.util does not exist". This is a timing
	problem because webserviceUtils.jar, which contains the class org.eclipse.jst.ws.util.JspUtils,
	is not added to the WEB-INF/lib directory of the Web project in time for
	the JSP compile. Despite the error, eventually the sample JSPs come up
	OK and the Web service can be invoked successfully. </li>

	<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=86552">86552</a></b>:
	If the service name in the WSDL file used in Web service client scenario
	does not follow Java naming convention, e.g. having a lowercase first letter,
	the Proxy class generated by the Web service client wizard may not be able
	to correctly reference the generated type and may have compile errors. </li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=99728">99728</a></b>:
	The Axis 1.1 runtime included in WTP is configured to support creation
	of Web services in projects targeted to Apache Tomcat or Geronimo. The
	Web service wizard will fail with "IWAB0234E An internal error occurred.
	Details: null java.lang.IllegalArgumentException" if the selected artifact,
	be it a Java bean or WSDL file, is contained in a project with a runtime
	target other than Tomcat or Geronimo.</li>

	<li>
	<b>
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=117138">117138</a>,
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103999">103999</a>
	</b>:
	The Geronimo 1.0 Server is enabled for the Web service wizard but not yet fully
	functional due to these significant defects.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105090">105090</a></b>:
	Sample JSP launches with incorrect URL on SLES 9.0 when using the default browser
	"Konqueror". The workaround is to manualy update the URL starting with "http:/localhost" to
	"http://localhost".</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105611">105611</a></b>:
	When running Web services scenarios, you might get a warning in the Tomcat
	console with the warning that "Attachment support is disabled". This is expected
	and would not affect the running of the Web service.</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105459">105459</a></b>:
	When creating Web service using Tomcat 4.1, if the server does not already exist,
	there may be an intermitten problem of "Error in starting server". The workaround
	is delete the Tomcat 4.1 server created by the Web service wizard, create a Tomcat 4.1
	server manually before launching the Web service wizard.</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>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=104993">104993</a></b>:
	When creating bottom-up Web service, you might get the exception:<br/><tt>Unexpected exception occured.
	Detail: java.lang.NoClassDefFoundError: javax/activation/DataSource</tt>.
	<br/>Refer to comment #8 of the defect for workarounds.
	</li>

	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=116025">116025</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. This means the user would be allowed to make an invalid
	selection without being stopped.
	</li>

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

	<p align="center">
	<!--<font color="#808080"><a href="../../../server/M8/new_and_noteworthy/server-M8.html">Previous</a></font>-->
	<a href="../../../../../development/news/1.0M9.html">Up</a>
	<!--<font color="#808080"><a href="../../../ws/1.0M8/news/jst-ws-1.0M8news.html">Next</a></font>-->
	</p>


	</body>
	</html>