barcode programming in c# Eclipse in Java

Develop ECC200 in Java Eclipse

The TCP channel, which is created by specifying <channel ref= tcp >, supports the same properties as the HTTP channel (except the security properties) and the following additional property:

< xml version="1.0" encoding="utf-8" > <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="1024" minHeight="768"> <fx:Script> <![CDATA[ import import import import import import import import import

package flexUnitTests { import org.flexunit.asserts.assertEquals; import utils.GetEmployeesInfo; public class GetEmployeesInfoTester { // Reference declaration for class to test public var classToTestRef : utils.GetEmployeesInfo; [Before] public function setUpBeforeClass():void { classToTestRef = new GetEmployeesInfo(); } [After] public function tearDownAfterClass():void { classToTestRef = null; } [Test] public function testAddItem():void { classToTestRef.addItem("John Do", "212-222-2222", "25", "john.do@gmail.com"); assertEquals( classToTestRef.employeesCollection.getItemAt(0).name, "John Do" ); } } }

You can preserve the contents and schema of a dataset in one XML file using the dataset s WriteXml method or in separate files using WriteXml() and WriteXmlSchema(). WriteXml() is overloaded, and in this example we ll show a version that extracts both data and schema. 1. Add a new Console Application project named WriteXml to your 08 solution. 2. Replace the code in Module1.vb with the code in Listing 8-9.

stream.Close(); if (checkBox1.Checked) { Process.Start(Application.StartupPath + @"\employee.xml"); } } The code creates an instance of the Employee class and sets its properties to the values entered in the text boxes. A FileStream object is then created and creates a file to which the serialized data is to be written. Then a SoapFormatter object is created. The Serialize() method of SoapFormatter accepts two parameters: a stream to which the serialized data is to be written and the object that is to be serialized. The counterpart of this operation is performed in the Click event handler of the Deserialize button and is shown in Listing 8-19. Listing 8-19. Deserialization by Using the SoapFormatter Class private void button2_Click(object sender, EventArgs e) { Employee emp; FileStream stream = new FileStream(Application.StartupPath + @"\employee.xml", FileMode.Open); SoapFormatter formatter = new SoapFormatter(); emp=(Employee)formatter.Deserialize(stream); textBox1.Text = emp.EmployeeID.ToString(); textBox2.Text = emp.FirstName; textBox3.Text = emp.LastName; textBox4.Text = emp.HomePhone; textBox5.Text = emp.Notes; stream.Close(); } The code declares a variable of type Employee. It then opens a stream pointing to the same file to which the object was serialized before. An instance of SoapFormatter is then created. The Deserialize() method of SoapFormatter reads the stream and deserializes the object. The return value of Deserialize() is of type object and hence it is type converted to the Employee class. After the Employee object is retrieved, its property values are assigned to the corresponding text boxes. If you run the application and serialize the Employee object, you should see output similar to Figure 8-8. As you can see, the XML output is now in SOAP format. There is also mention of some namespaces related to SOAP. There is another important difference: the names given to various elements containing data correspond to private variable names that hold the actual value and not the property names. Unlike XML serialization, which is shallow by nature, SOAP serialization done via the SoapFormatter class is deep serialization. It serializes private, protected, and public data.

try { if( conn != null) conn.close(); } catch( SQLException e ) { log.log(Level.SEVERE,"Problem closing connection",e); } } } Compare this with Listing 4-4, which shows the implementation taking advantage of the helper classes.

Runs a query on your database using SQL statements defined in $sql. Returns the result of the query if it is successful, and false if a failure occurred. Returns a row of data as requested in the result of sql_query(), or false if a failure occurred. Use this function when you expect only one row of results. The data returned by sql_fetchrow() is an array indexed by field name. For example, to access the field user_name in the returned variable foo, use the notation $foo['user_name']. Works just like sql_fetchrow(), except it returns a multidimensional array containing multiple rows of data. Access the data returned by sql_fetchrowset() by using the notation $foo[$i]['field_name'], where $i is the number (starting with zero) of the result you wish to access. For example, to access the third result of a query on usernames, use the notation $foo[2]['user_name']. Clears out the result of a query and enables you to start fresh. This is a good cleanup method to use, particularly after a large query, to help free memory and keep things running smoothly. Simply pass a result from sql_query() into the function to make it work. Returns true if successful, and false if a failure occurred.