releases/1.5/newandnoteworthy/webservices.html - www.eclipse.org/webtools - Git at Google

 <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

 		<html>
 			<head>
 				<link type="text/css"

 				href="{$root}/development/news/default_style.css"

 				rel="stylesheet" />
 				<title>Web Tools Platform <xsl:value-of select="$release" /> News</title>
 			</head>
 			<body>
 			<table xmlns:fn="http://www.w3.org/2005/02/xpath-functions"><tbody valign="top"><tr><td align="left"><h1>Eclipse Web Tools Platform 1.5 - New and Noteworthy</h1><blockquote/></td><td align="right" valign="top"><img src="../../../images/wtplogosmall.jpg" alt="Small WTP logo"/></td></tr></tbody></table><blockquote xmlns:fn="http://www.w3.org/2005/02/xpath-functions"/><table xmlns:fn="http://www.w3.org/2005/02/xpath-functions" border="0" cellpadding="10" cellspacing="0" width="80%"><tbody><!--separating row--><tr><td colspan="2"><hr/></td></tr><tr><td colspan="2"><h2>Web Services</h2></td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>New look for Web services wizards</b></td><td valign="top" width="70%">
 				<p>
 					The Web Service wizard and Web Service Client wizard have a
 					new look.  The first page of these wizards now combines the
 					first three pages of the same wizards in WTP 1.0.
 				</p>
 				<p>
 					On this first page of the wizard, the user can:
 				</p>
 				<ul>
 					<li>Use the drop down combo to select the type of Web service to create.</li>
 					<li>Use the <b>Browse</b> button to browse for the service implementation or
 					service definition.</li>
 					<li>Move the service and client scales on the right-hand side to select whether to
 					develop, assemble, deploy, install, start and test the Web service and Web service client.</li>
 					<li>Obtain a summary of the <b>Server</b>, <b>Web service runtime</b>, <b>project</b> and
 					<b>EAR</b> that will be used for both service and client side.</li>
 					<li>Click on the <b>Server</b>, <b>Web service runtime</b>, <b>project</b> or <b>EAR</b>
 					hyper-links to modify the respective settings.</li>
 				</ul>
 				<p>
 					<img src="webservices/WebserviceWizard.png" border="0" alt="placeholder"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Axis 1.3 support</b></td><td valign="top" width="70%">
 				<p>
 					The Axis emitters and JARs used by the Web Services wizards
 					are now based on Axis 1.3.
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Axis emitter preference page</b></td><td valign="top" width="70%">
 				<p>
 					A new Axis emitter preference has been added to control Axis emitter settings
 					for Wsdl2Java and Java2Wsdl.  This include setting timeout and analysing the service class
 					for compliance to JAX-RPC.
 				</p>
 				<p>
 					<img src="webservices/AxisPreference.png" border="0" alt="placeholder"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Skeleton merge</b></td><td valign="top" width="70%">
 				<p>
 					A new checkbox is added to the Web services Resource preference
 					to enable the user to turn on skeleton merge.  When creating top-down
 					Web service with this preference enabled, the newly generated skeleton
 					implementation file will be merged with the existing implementation files
 					if they exist.  This enables the user to preserve user-modified code between
 					different invocation of the Web Services wizards.
 				</p>
 				<p>
 					<img src="webservices/SkeletonMerge.png" border="0" alt="placeholder"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Enhancements in Web Services Explorer</b></td><td valign="top" width="70%">
 					<p>When users click the <b>Browse</b> button in the WSDL page, they can now select
 					different categories of WSDL documents to display:</p>
 					<ul>
 					<li>All</li>
 					<li>Favorites</li>
 					<li>Apache Axis Components</li>
 					<li>WorkspaceWSDL documents</li>
 					</ul>
 				<p>
 					<img src="webservices/WSDLCategories.png" border="0" alt="placeholder"/>
 				</p>
 				<p>Other enhancements in the Web Services Explorer include:</p>
 					<ul>
 					<li>Support for nillables and attributes in the schemas of the WSDL documents.</li>
 					<li>Login support in UDDI page.</li>
 					</ul>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Web Services Ant tasks</b></td><td valign="top" width="70%">
 				<p>Starting in WTP 1.0, users can create bottom-up Web service, top-down Web service and Web service client using Ant tasks.
 			Refer to the
 			<b><a href="../../../jst/components/ws/1.0/tutorials/WebServiceAntTask/WebServiceAntTask.html">Web Service Ant Tasks tutorial</a></b>
 			for instructions on how to use the Ant tasks.

 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><tr><td colspan="2"><h2>WSDL Editing Tools</h2></td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Simplified Design View</b></td><td valign="top" width="70%">
 				<p>
 					For WTP 1.5, the Design View has been simplified.  It has been restructured to
 					de-emphasize Bindings and Messages and to emphasize Operations and Elements/Types.
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/WSDLEditor15.jpg" alt="WSDL Editor in WTP1.5"/>
 				</p>


 				<p>
 					<b>De-Emphasizing Bindings</b>
 				</p>
 				<p>
 					Binding information in the Design View has been reworked.  They have been de-emphasized
 					because they are expert objects	that many users maintain via the Binding generator.
 					By default, the Binding is collapsed and is seen as a single icon.
 					<img src="../../../wst/components/wsdl/1.5/images/Binding.jpg" alt="SOAP Binding Icon"/>
 				</p>
 				<p>
 					Users can expand them (by double clicking on them) and they will show up as a ruler next
 					to it's associated PortType.  See below:
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/BindingAttached.jpg" alt="Binding attached to the corresponding PortType"/>
 				</p>
 				<p>
 					To edit the Binding, users would click on the Binding object they wish to edit and a
 					corresponding Property Sheet will appear.  For example, if the user clicks on a Binding
 					Operation, the Extensions Tab can be used to edit the detailed information for the
 					Binding object.  See the Extensions section below for more information.
 				</p>

 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Navigation</b></td><td valign="top" width="70%">
 				<p>
 					The editor has hyperlink support in the source view. Hold down the Ctrl key and move the
 					mouse pointer over some reference (ie. reference to some other PortType),
 					and a link appears. If you mouse click on the link, context changes to that reference.
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/SourceHyperlink.jpg" alt="Hyperlink via source view"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Extensions</b></td><td valign="top" width="70%">
 				<p>
 					You can provide specialized extension information to your WSDLs via the extensions tab of
 					the Properties View. Use the 'Add..' button to choose from categories of available extensions.
 					Then use the Tree View and the details view to edit the extension information.
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/ExtensionsTab.jpg" alt="Extenstions Tab used to edit Extensibility Elements"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>XML Schema Integration</b></td><td valign="top" width="70%">
 				<p>
 					In WTP 1.0, XML Schema content was viewed and edited by 'drilling into' the schema object.
 					The XML Schema Editor would then appear within the WSDL Editor.  In WTP 1.5, the
 					XML Schema Editor will no longer appear within the WSDL Editor.  Instead, a separate
 					XML Schema Editor will be opened on the desired XML Schema object.  To launch the XML Schema
 					Editor, the user clicks on the link icon which appears to the right hand side of each
 					Input/Output/Fault Part.  This link icon will only appear if the associated type is not
 					a built-in XML Schema Type.  See below:
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/LinkIcon.jpg" alt="XML Schema Editor Link Icon"/>
 				</p>
 				<p>
 					A new external XML Schema Editor is shown below:
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/InlineSchema.jpg" alt="Newly opened XML Schema Editor"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Smart Editing</b></td><td valign="top" width="70%">
 				<p>
 					In practise WSDL documents are authored using a number of different patterns (html :get
 					and put, soap doc-literal, doc-literal wrapped, rpc-encoded etc.).   When creating new
 					content via the graphical view the WSDL editor (e.g. when adding an operation)  will
 					recognize the authoring pattern and create new content accordingly.
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/SmartAddOperation-MessageReference.jpg" alt="Newly added Operation with MessageReferences following existing patterns"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Refactoring</b></td><td valign="top" width="70%">
 				<p>
 					In WTP 1.5, there is inter-file refactoring in addition to pre-existing intra-file refactoring
 					support. This means that if you rename a top level component such as a PortType, any references
 					to it from other WSDLs in the current project or workspace will be updated.
 				</p>
 				<br/>
 				<br/>
 				Inter-file refactoring can be done in two ways:
 				<ul>
 					<li>The refactor context menu option for the WSDL object in the Design or Outline view</li>
 					<li>by clicking on the light bulb icon located beside the "Name" text field in the
 						Properties View of the WSDL object (See Figure below)</li>
 				</ul>
 				<p>
 					If the user simply renames a component without invoking an explicit refactoring the editor behaves just
 					like it did in WTP 1.0.  References to renamed components are updated only within the current wsdl file.
 				</p>
 				<p>
 					<img src="../../../wst/components/wsdl/1.5/images/RefactoringSupport.jpg" alt="Property sheet with refactoring support"/>
 				</p>
 			</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr></tbody></table><blockquote xmlns:fn="http://www.w3.org/2005/02/xpath-functions"/><p xmlns:fn="http://www.w3.org/2005/02/xpath-functions" align="center"><a href="index.html">
 					Up
 				</a></p>
 		</body></html>
	<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

	<html>
	<head>
	<link type="text/css"

	href="{$root}/development/news/default_style.css"

	rel="stylesheet" />
	<title>Web Tools Platform <xsl:value-of select="$release" /> News</title>
	</head>
	<body>
	<table xmlns:fn="http://www.w3.org/2005/02/xpath-functions"><tbody valign="top"><tr><td align="left"><h1>Eclipse Web Tools Platform 1.5 - New and Noteworthy</h1><blockquote/></td><td align="right" valign="top"><img src="../../../images/wtplogosmall.jpg" alt="Small WTP logo"/></td></tr></tbody></table><blockquote xmlns:fn="http://www.w3.org/2005/02/xpath-functions"/><table xmlns:fn="http://www.w3.org/2005/02/xpath-functions" border="0" cellpadding="10" cellspacing="0" width="80%"><tbody><!--separating row--><tr><td colspan="2"><hr/></td></tr><tr><td colspan="2"><h2>Web Services</h2></td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>New look for Web services wizards</b></td><td valign="top" width="70%">
	<p>
	The Web Service wizard and Web Service Client wizard have a
	new look. The first page of these wizards now combines the
	first three pages of the same wizards in WTP 1.0.
	</p>
	<p>
	On this first page of the wizard, the user can:
	</p>
	<ul>
	<li>Use the drop down combo to select the type of Web service to create.</li>
	<li>Use the <b>Browse</b> button to browse for the service implementation or
	service definition.</li>
	<li>Move the service and client scales on the right-hand side to select whether to
	develop, assemble, deploy, install, start and test the Web service and Web service client.</li>
	<li>Obtain a summary of the <b>Server</b>, <b>Web service runtime</b>, <b>project</b> and
	<b>EAR</b> that will be used for both service and client side.</li>
	<li>Click on the <b>Server</b>, <b>Web service runtime</b>, <b>project</b> or <b>EAR</b>
	hyper-links to modify the respective settings.</li>
	</ul>
	<p>
	<img src="webservices/WebserviceWizard.png" border="0" alt="placeholder"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Axis 1.3 support</b></td><td valign="top" width="70%">
	<p>
	The Axis emitters and JARs used by the Web Services wizards
	are now based on Axis 1.3.
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Axis emitter preference page</b></td><td valign="top" width="70%">
	<p>
	A new Axis emitter preference has been added to control Axis emitter settings
	for Wsdl2Java and Java2Wsdl. This include setting timeout and analysing the service class
	for compliance to JAX-RPC.
	</p>
	<p>
	<img src="webservices/AxisPreference.png" border="0" alt="placeholder"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Skeleton merge</b></td><td valign="top" width="70%">
	<p>
	A new checkbox is added to the Web services Resource preference
	to enable the user to turn on skeleton merge. When creating top-down
	Web service with this preference enabled, the newly generated skeleton
	implementation file will be merged with the existing implementation files
	if they exist. This enables the user to preserve user-modified code between
	different invocation of the Web Services wizards.
	</p>
	<p>
	<img src="webservices/SkeletonMerge.png" border="0" alt="placeholder"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Enhancements in Web Services Explorer</b></td><td valign="top" width="70%">
	<p>When users click the <b>Browse</b> button in the WSDL page, they can now select
	different categories of WSDL documents to display:</p>
	<ul>
	<li>All</li>
	<li>Favorites</li>
	<li>Apache Axis Components</li>
	<li>WorkspaceWSDL documents</li>
	</ul>
	<p>
	<img src="webservices/WSDLCategories.png" border="0" alt="placeholder"/>
	</p>
	<p>Other enhancements in the Web Services Explorer include:</p>
	<ul>
	<li>Support for nillables and attributes in the schemas of the WSDL documents.</li>
	<li>Login support in UDDI page.</li>
	</ul>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Web Services Ant tasks</b></td><td valign="top" width="70%">
	<p>Starting in WTP 1.0, users can create bottom-up Web service, top-down Web service and Web service client using Ant tasks.
	Refer to the
	<b><a href="../../../jst/components/ws/1.0/tutorials/WebServiceAntTask/WebServiceAntTask.html">Web Service Ant Tasks tutorial</a></b>
	for instructions on how to use the Ant tasks.

	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><tr><td colspan="2"><h2>WSDL Editing Tools</h2></td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Simplified Design View</b></td><td valign="top" width="70%">
	<p>
	For WTP 1.5, the Design View has been simplified. It has been restructured to
	de-emphasize Bindings and Messages and to emphasize Operations and Elements/Types.
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/WSDLEditor15.jpg" alt="WSDL Editor in WTP1.5"/>
	</p>


	<p>
	<b>De-Emphasizing Bindings</b>
	</p>
	<p>
	Binding information in the Design View has been reworked. They have been de-emphasized
	because they are expert objects that many users maintain via the Binding generator.
	By default, the Binding is collapsed and is seen as a single icon.
	<img src="../../../wst/components/wsdl/1.5/images/Binding.jpg" alt="SOAP Binding Icon"/>
	</p>
	<p>
	Users can expand them (by double clicking on them) and they will show up as a ruler next
	to it's associated PortType. See below:
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/BindingAttached.jpg" alt="Binding attached to the corresponding PortType"/>
	</p>
	<p>
	To edit the Binding, users would click on the Binding object they wish to edit and a
	corresponding Property Sheet will appear. For example, if the user clicks on a Binding
	Operation, the Extensions Tab can be used to edit the detailed information for the
	Binding object. See the Extensions section below for more information.
	</p>

	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Navigation</b></td><td valign="top" width="70%">
	<p>
	The editor has hyperlink support in the source view. Hold down the Ctrl key and move the
	mouse pointer over some reference (ie. reference to some other PortType),
	and a link appears. If you mouse click on the link, context changes to that reference.
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/SourceHyperlink.jpg" alt="Hyperlink via source view"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Extensions</b></td><td valign="top" width="70%">
	<p>
	You can provide specialized extension information to your WSDLs via the extensions tab of
	the Properties View. Use the 'Add..' button to choose from categories of available extensions.
	Then use the Tree View and the details view to edit the extension information.
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/ExtensionsTab.jpg" alt="Extenstions Tab used to edit Extensibility Elements"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>XML Schema Integration</b></td><td valign="top" width="70%">
	<p>
	In WTP 1.0, XML Schema content was viewed and edited by 'drilling into' the schema object.
	The XML Schema Editor would then appear within the WSDL Editor. In WTP 1.5, the
	XML Schema Editor will no longer appear within the WSDL Editor. Instead, a separate
	XML Schema Editor will be opened on the desired XML Schema object. To launch the XML Schema
	Editor, the user clicks on the link icon which appears to the right hand side of each
	Input/Output/Fault Part. This link icon will only appear if the associated type is not
	a built-in XML Schema Type. See below:
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/LinkIcon.jpg" alt="XML Schema Editor Link Icon"/>
	</p>
	<p>
	A new external XML Schema Editor is shown below:
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/InlineSchema.jpg" alt="Newly opened XML Schema Editor"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Smart Editing</b></td><td valign="top" width="70%">
	<p>
	In practise WSDL documents are authored using a number of different patterns (html :get
	and put, soap doc-literal, doc-literal wrapped, rpc-encoded etc.). When creating new
	content via the graphical view the WSDL editor (e.g. when adding an operation) will
	recognize the authoring pattern and create new content accordingly.
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/SmartAddOperation-MessageReference.jpg" alt="Newly added Operation with MessageReferences following existing patterns"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr><!--new item--><tr><td align="left" valign="top" width="30%"><b>Refactoring</b></td><td valign="top" width="70%">
	<p>
	In WTP 1.5, there is inter-file refactoring in addition to pre-existing intra-file refactoring
	support. This means that if you rename a top level component such as a PortType, any references
	to it from other WSDLs in the current project or workspace will be updated.
	</p>
	<br/>
	<br/>
	Inter-file refactoring can be done in two ways:
	<ul>
	<li>The refactor context menu option for the WSDL object in the Design or Outline view</li>
	<li>by clicking on the light bulb icon located beside the "Name" text field in the
	Properties View of the WSDL object (See Figure below)</li>
	</ul>
	<p>
	If the user simply renames a component without invoking an explicit refactoring the editor behaves just
	like it did in WTP 1.0. References to renamed components are updated only within the current wsdl file.
	</p>
	<p>
	<img src="../../../wst/components/wsdl/1.5/images/RefactoringSupport.jpg" alt="Property sheet with refactoring support"/>
	</p>
	</td></tr><!--separating row--><tr><td colspan="2"><hr/></td></tr></tbody></table><blockquote xmlns:fn="http://www.w3.org/2005/02/xpath-functions"/><p xmlns:fn="http://www.w3.org/2005/02/xpath-functions" align="center"><a href="index.html">
	Up
	</a></p>
	</body></html>