Sachin Thapa

Class data sharing (CDS) a feature introduced in J2SE 5.0 reduces the startup time for Java programming language applications. When the JRE is installed on 32-bit platforms using the Sun provided installer, the installer loads a set of classes from the system jar file into a private internal representation, and dumps that representation to a file, called a "shared archive".Class data sharing is not supported in Microsoft Windows 95/98/ME. During subsequent JVM invocations, the shared archive is memory-mapped in, saving the cost of loading those classes and allowing much of the JVM's metadata for these classes to be shared among multiple JVM processes. The primary motivation for including CDS in the 5.0 release is the decrease in startup time it provides. CDS produces better results for smaller applications because it eliminates a fixed cost: that of loading certain core classes. The smaller the application relative to the number of core classes it uses, the larger the sav

XML is the base of Web 2.0 development. While writing a web service to integrate products, I learned some best practices with XML naming conventions. An XML element is everything from (including) the element's start tag to (including) the element's end tag. An element can contain other elements, simple text or a mixture of both. Elements can also have attributes. <bookstore> <book category="CHILDREN"> <author>J K. Rowling</author> <year>2005</year> <price>29.99</price> </book> <book category="WEB"> <author>Erik T. Ray</author>> <year>2003</year> <price>39.95</price> </book> </bookstore>> In the example above, and have element contents, because they contain other elements. has text content because it contains text. In the example above only has an attribute (category="CHILDREN"). XML Naming Rules XML elements mus

This article covers details about writing a web service client using Apache AXIS2 API. The article explains the various API using code snippets and covers parameters require by various methods of web service client API. Apache AXIS2 web service API mainly consists of two type of objects ServiceClient and OperationClient. ServiceClient provides basic APIs to send and receive SOAP messages, for advanced methods you require Operation Client. To provide target URL you need to define a EndPointReference type of object. EndpointReference targetEPR = new EndpointReference(http://localhost:8080/axis2/services/helloworld); Various options can be given to web service client by creating an Options object. The reference point defined is set into the options along with the Transport protocol. Options options = new Options(); options.setTo(targetEPR); options.setTransportInProtocol(Constants.TRANSPORT_HTTP); Now create a service client and pass these options to service client usi