jst/components/ws/1.0M8/news/jst-ws-1.0M8news.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.0M8 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.0M8.
 <p>
 Here are the highlights of the changes to the Web services tools for 1.0M8:


 		<ul>
 			<li>A new page was added to the Web Service wizard to start the
 			server asynchronously. Refer to defect <b><a
 				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=107141">107141</a></b></li>

 			<li>The option to do wizard WSDL validation was added to Web Service
 			wizard for top-down scenario and Web Service client wizard. You can
 			enable it in the <b>Web Service -> Profile Validation</b> preference.
 			Refer to <b><a
 				href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=107673">107673</a></b>
 			for more detail.</li>

 			<li>The default use and style for creating bottom-up Web service had been changed from RPC encoded
 			to document literal wrapped.</li>

 		</ul>
 		<p>
 Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.7 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.0M8 release:
 <ul>
 <li>
 <a href="../../1.0M8/tutorials/BottomUpWebService.html">Bottom up Web Service supporting
 flexible projects</a></li>

 <li>
 <a href="../../1.0M8/tutorials/TopDownWebService.html">Top down Web Service supporting
 flexible projects</a></li>

 <li>
 <a href="../../1.0M8/tutorials/WebServiceClient.html">Web Service Client supporting
 flexible projects</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=110361">110361</a></b>:
 Going through Web Service top down scenario on a WSDL file in a path containing
 a space would result in an error:
 <br/><tt>Failed to copy WSDL file.  Detail:
 java.net.URISyntaxException </tt>.
 <br/>The workaround is to avoid using spaces or special characters not
 allowed in java.net.URI  as specified in <b><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396: Uniform Resource Identifiers (URI):
 Generic Syntax </a></b> in the path where the WSDL file is located in
 (e.g. installation directory, project and workspace name).
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110212">110212</a></b>:
 When the <b>Browse...</b> button is clicked in the Web Services Explorer to launch
 the WSDL Browser to browse the WSDL files in the workspace,
 no WSDL files are listed.  The workaround is not to use <b>Browse...</b> button
 but instead manually enter the WSDL location in the WSDL URL field.
 </li>
 <li>
 <b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=108575">108575</a></b>:
 When creating Web service, if you choose <b>Test the Web service</b>, you will need to select
 <b>Generate Proxy</b> as well.  Otherwise, if the client project does not already exist, you
 will get the error:
 <br/><tt>Unexpected exception occured </tt> .
 <br/> If this happens, you can either
 create the client project manually before going through the Web service wizard or
 select/deselect both options together.</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=105462">105462</a></b>:
 When going through the Web services wizard, you might run into an intermitten problem where
 the error dialog "Errors during build.  Resource .deployable does not exist" may pop up.
 When that happens, just dismiss the dialog and continue.
 </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=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=94010">94010</a></b>:
 Do not create bottom-up Web services from beans in the default package.
 Otherwise, you will get "Error in getting method from bean" when going
 through the Web Service wizard. Instead, put your service bean in a Java
 package before creating a Web service from it.&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=100677">100677</a>,
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103198">103198</a>,
 <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105151">105151</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>

 </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.0M8.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.0M8 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.0M8.
	<p>
	Here are the highlights of the changes to the Web services tools for 1.0M8:


	<ul>
	<li>A new page was added to the Web Service wizard to start the
	server asynchronously. Refer to defect <b><a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=107141">107141</a></b></li>

	<li>The option to do wizard WSDL validation was added to Web Service
	wizard for top-down scenario and Web Service client wizard. You can
	enable it in the <b>Web Service -> Profile Validation</b> preference.
	Refer to <b><a
	href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=107673">107673</a></b>
	for more detail.</li>

	<li>The default use and style for creating bottom-up Web service had been changed from RPC encoded
	to document literal wrapped.</li>

	</ul>
	<p>
	Aside from the items listed above, the focus has been on stabilizing existing function since WTP 0.7 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.0M8 release:
	<ul>
	<li>
	<a href="../../1.0M8/tutorials/BottomUpWebService.html">Bottom up Web Service supporting
	flexible projects</a></li>

	<li>
	<a href="../../1.0M8/tutorials/TopDownWebService.html">Top down Web Service supporting
	flexible projects</a></li>

	<li>
	<a href="../../1.0M8/tutorials/WebServiceClient.html">Web Service Client supporting
	flexible projects</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=110361">110361</a></b>:
	Going through Web Service top down scenario on a WSDL file in a path containing
	a space would result in an error:
	<br/><tt>Failed to copy WSDL file. Detail:
	java.net.URISyntaxException </tt>.
	<br/>The workaround is to avoid using spaces or special characters not
	allowed in java.net.URI as specified in <b><a href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396: Uniform Resource Identifiers (URI):
	Generic Syntax </a></b> in the path where the WSDL file is located in
	(e.g. installation directory, project and workspace name).
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=110212">110212</a></b>:
	When the <b>Browse...</b> button is clicked in the Web Services Explorer to launch
	the WSDL Browser to browse the WSDL files in the workspace,
	no WSDL files are listed. The workaround is not to use <b>Browse...</b> button
	but instead manually enter the WSDL location in the WSDL URL field.
	</li>
	<li>
	<b><a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=108575">108575</a></b>:
	When creating Web service, if you choose <b>Test the Web service</b>, you will need to select
	<b>Generate Proxy</b> as well. Otherwise, if the client project does not already exist, you
	will get the error:
	<br/><tt>Unexpected exception occured </tt> .
	<br/> If this happens, you can either
	create the client project manually before going through the Web service wizard or
	select/deselect both options together.</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=105462">105462</a></b>:
	When going through the Web services wizard, you might run into an intermitten problem where
	the error dialog "Errors during build. Resource .deployable does not exist" may pop up.
	When that happens, just dismiss the dialog and continue.
	</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=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=94010">94010</a></b>:
	Do not create bottom-up Web services from beans in the default package.
	Otherwise, you will get "Error in getting method from bean" when going
	through the Web Service wizard. Instead, put your service bean in a Java
	package before creating a Web service from it. </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=100677">100677</a>,
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=103198">103198</a>,
	<a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=105151">105151</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>

	</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.0M8.html">Up</a>
	<!--<font color="#808080"><a href="../../../ws/1.0M8/news/jst-ws-1.0M8news.html">Next</a></font>-->
	</p>


	</body>
	</html>