With the last installment of this series on integrating ExtJS with Seam, Client-side Form Handling, we looked at a way to pass the form as an instance of Seam.Remoting.Map. With this solution the SeamSubmitAction bound the form fields to the map, using the form field name the key to hold the form field value. The map instance passed over the Seam Remoting framework to the action method that accepts the Map as its sole argument.

If you had read the documentation for the SeamRemotingJsonReader in the code from my post Integrating ExtJS with Seam: Loading stores with Json, you might have noticed mention to error handling in Seam's Remoting framework. Seam is a relatively new framework so it should be expected that there are going to be peripheral areas of it that are still being fleshed out. Error handling in the Remoting framework is one place that the Seam team has recognized as an area that needs some attention.

As I mentioned in an earlier post the Seam framework has sparked my curiosity. To help me better understand some of its inner workings I wanted to figure out how to integrate Seam with the ExtJS framework for populating client side stores. Many of the Ext widgets are backed by stores so this was a logical place to start. What are stores? Quite simply stores, aka Ext.data.Stores, are the Ext construct for storing client side record data. Think of it as client-side MVC; where the record data is the Model, the widget is a View of the model, and event handlers are the Controllers.

Greetings and welcome to McDaniel Consulting's internet presence. I'm Sean McDaniel, owner of McDaniel consulting, and well frankly I'm a blogging noob. I sift through a lot of blogs and read a few religiously but I never really felt compelled to blog myself. I'm still sorting out what the content will be here but one thing is for certain and that is the focus will be software development.