<?xml version="1.0" encoding="iso-8859-1"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
	<channel>
		<title>Exforsys.com</title>
		<description>Exforsys Free Training Tutorials. Visit http://www.exforsys.com for your training needs. Interview Questions : http://www.geekinterview.com</description>
		<link>http://www.exforsys.com</link>
		<lastBuildDate>Thu, 24 Jul 2008 21:57:31 +0100</lastBuildDate>
		<generator>FeedCreator 1.7.2</generator>
		<image>
			<url>http://www.exforsys.com/images/M_images/rss20.gif</url>
			<title>by Exforsys.com</title>
			<link>http://www.exforsys.com</link>
			<description>Exforsys Free Training Tutorials. Visit http://www.exforsys.com for your training needs. Interview Questions : http://www.geekinterview.com</description>
		</image>
		<item>
			<title>SOA Web Services - IT Evolution</title>
			<link>http://www.exforsys.com/tutorials/sws/it-evolution.html</link>
			<description>IT Evolution 
Looking at current business needs, the IT environments in today's world need to be more flexible, and must quickly adapt to the constantly changing business requirements. </description>
			<category>Tutorials - SWS</category>
			<pubDate>Wed, 23 Jul 2008 21:53:44 +0100</pubDate>
		</item>
		<item>
			<title>SOA Web Services - SOA Evolution</title>
			<link>http://www.exforsys.com/tutorials/sws/soa-evolution.html</link>
			<description>SOA Evolution 
In the 1980s, applications were mostly vertical, built to meet the customer requirements in a vertical market segment. The software solutions were sufficient to meet the needs of a vertical industry. </description>
			<category>Tutorials - SWS</category>
			<pubDate>Wed, 23 Jul 2008 21:49:55 +0100</pubDate>
		</item>
		<item>
			<title>SOA Web Services - SOA and Web Services Approach for Integration</title>
			<link>http://www.exforsys.com/tutorials/sws/soa-and-web-services-approach-for-integration.html</link>
			<description>SOA and Web Services Approach for Integration 
In Chapter 2, you were introduced to how Service-Oriented Architecture (SOA) can be used for application integration. We saw that the integration itself may be restricted within an Enterprise or may involve third parties (B2B or B2C). Service-Oriented Architectures are complex. </description>
			<category>Tutorials - SWS</category>
			<pubDate>Wed, 23 Jul 2008 21:38:56 +0100</pubDate>
		</item>
		<item>
			<title>SOA Approach to Integration Book Review</title>
			<link>http://www.exforsys.com/reviews/books/soa-approach-to-integration-book-review.html</link>
			<description>Book Review: SOA Approach to Integration 
XML, Web services, ESB, and BPEL in real-world SOA projects 
Businesses will always need highly efficient applications which have ability to provide outstanding user experience while maintaining security. Most of the developers today thrive in a business setting and have worked for many years to improve business transactions between the client and end users. </description>
			<category>Reviews - Books</category>
			<pubDate>Wed, 23 Jul 2008 21:34:21 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The Data Validation Test</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-data-validation-test.html</link>
			<description>The Data Validation Test
The Ok button of the SaveAsDialog should only be enabled if the name that has been entered is valid. A name can be invalid if it contains an illegal character, or if it has already been used. </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Sat, 12 Jul 2008 08:41:14 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The name() Test</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-name-test.html</link>
			<description>The name() Test
Like the wasCancelled()method, the name() method is not thread-safe, so our test class needs another boilerplate helper method: </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Sat, 12 Jul 2008 08:39:13 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The wasCancelled() Test</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-wascancelled-test.html</link>
			<description>The wasCancelled() Test 
The first of our API tests is to check the wasCancelled() method. We will basically do three investigations. The first test will call wasCancelled()before the dialog has been cancelled. The second test will cancel the dialog and then call the method. In the third test we will enter a name, cancel the dialog, and then call wasCancelled(). </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Sat, 12 Jul 2008 08:37:28 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The Constructor Test</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-constructor-test.html</link>
			<description>The Constructor Test 
A freshly constructed SaveAsDialog should be in a known state, and we need to check the things we listed at the start of this chapter. </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Fri, 11 Jul 2008 03:35:04 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The init() Method</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-init-method.html</link>
			<description>The init() Method 
The job of the init() method is to create and show the SaveAsDialog instance so that it can be tested: </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Fri, 11 Jul 2008 03:03:22 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - The ShowerThread Class</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/the-showerthread-class.html</link>
			<description>The ShowerThread Class 
Since SaveAsDialog.show() blocks, we cannot call this from our main thread; instead we spawn a new thread. This thread could just be an anonymous inner class in the init()method: </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Fri, 11 Jul 2008 02:03:22 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - Unit Test Infrastructure</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/unit-test-infrastructure.html</link>
			<description>Unit Test Infrastructure 
Having seen the broad outline of the test class and the UI methods needed, we can look closely at the implementation of the test. We'll start with the UI Wrapper class and the init() and cleanup()methods. </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Thu, 10 Jul 2008 13:55:36 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - Getting the Text of a Text Field</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/getting-the-text-of-a-text-field.html</link>
			<description>Getting the Text of a Text Field
The method is getText(), and there is a variant to retrieve just the selected text: </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Thu, 10 Jul 2008 12:55:36 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing - Outline of the Unit Test</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/outline-of-the-unit-test.html</link>
			<description>Outline of the Unit Test
The things we want to test are: 

    Initial settings:
    
        The text field is empty. 
        The text field is a sensible size. 
        The Ok button is disabled. 
        The Cancel button is enabled. 
        The dialog is a sensible size. 
    
    
</description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Thu, 10 Jul 2008 11:32:14 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing</title>
			<link>http://www.exforsys.com/tutorials/swing-testing/swing-extreme-testing.html</link>
			<description>Swing Extreme Testing by Tim Lavers, Lindsay Peters 
This book is a practical guide to automated software testing for extreme Java programming using Swing GUIs, with lots of ready-to-use real-life examples and source code for automated testing of the software components usually regarded as too hard to test automatically. </description>
			<category>Tutorials - Swing Testing</category>
			<pubDate>Thu, 10 Jul 2008 10:45:54 +0100</pubDate>
		</item>
		<item>
			<title>Swing Extreme Testing Book Review</title>
			<link>http://www.exforsys.com/reviews/books/swing-extreme-testing-book-review.html</link>
			<description>Swing Extreme Testing Book Review 
Swing used to be a simple component offered as an add-on for Java. This plug-in can be used as a GUI (graphical user interface) to develop as an add-on for the Java application. It has the ability to emulate certain platforms eventually building a powerful application. With this plug-in, users will experience the full potential of Java as it uses its native capability and with the help of Swing, different web development languages are added to the application. Swing&amp;rsquo;s ability to emulate eventually made this plug-in one of the most popular and important tools in Java development that it eventually became part of Java development package. </description>
			<category>Reviews - Books</category>
			<pubDate>Thu, 10 Jul 2008 08:20:14 +0100</pubDate>
		</item>
		<item>
			<title>Access WSDL</title>
			<link>http://www.exforsys.com/tutorials/java-soa/access-wsdl.html</link>
			<description>Access WSDL and Generate Axis Stubs to Access the Web Service Remotely
Now for the really cool stuff. As we discussed earlier, we have set up the ServiceMix as a separate web service gateway in front of the actual web service deployment. Now we have to check whether we can access the WSDL from the ServiceMix. For this, we can point our browser using the standard WSDL query string, like:</description>
			<category>Tutorials - Java SOA</category>
			<pubDate>Fri, 20 Jun 2008 18:08:15 +0100</pubDate>
		</item>
		<item>
			<title>XBean based servicemix http Binding</title>
			<link>http://www.exforsys.com/tutorials/java-soa/xbean-based-servicemix-http-binding.html</link>
			<description>XBean-based servicemix-http Binding
For XBean-based deployment of servicemix-http, our xbean.xml matches the following:</description>
			<category>Tutorials - Java SOA</category>
			<pubDate>Fri, 20 Jun 2008 18:05:56 +0100</pubDate>
		</item>
		<item>
			<title>Deploy the Web Service</title>
			<link>http://www.exforsys.com/tutorials/java-soa/deploy-the-web-service.html</link>
			<description>Deploy the Web Service
As a first step, if you haven't done it before, edit examples.PROPERTIES (provided along with the code download for this chapter), and change the paths there to match your development environment. The code download for this chapter also includes a README.txt file, which gives detailed steps to build and run the samples.</description>
			<category>Tutorials - Java SOA</category>
			<pubDate>Wed, 18 Jun 2008 07:47:05 +0100</pubDate>
		</item>
		<item>
			<title>servicemix http Lightweight Configuration</title>
			<link>http://www.exforsys.com/tutorials/java-soa/servicemix-http-lightweight-configuration.html</link>
			<description>servicemix-http Lightweight Configuration
In addition to the XBean-based configuration, servicemix-http can also be deployed based on the lightweight mode to use in an embedded ServiceMix. The configuration would be as follows:</description>
			<category>Tutorials - Java SOA</category>
			<pubDate>Wed, 18 Jun 2008 07:45:05 +0100</pubDate>
		</item>
		<item>
			<title>servicemix-http XBean Configuration</title>
			<link>http://www.exforsys.com/tutorials/java-soa/servicemix%11http-xbean-configuration.html</link>
			<description>servicemix-http XBean Configuration
The servicemix-http components supports the XBean-based deployment. Since the servicemix-http component can be configured in both the consumer and provider roles, we have two sets of configuration parameters for the component. Let us look into the main configuration parameters:</description>
			<category>Tutorials - Java SOA</category>
			<pubDate>Fri, 13 Jun 2008 19:27:01 +0100</pubDate>
		</item>
	</channel>
</rss>
