Refers

3. Every request to a REST web service happens in complete isolation

4. Resources are manipulated by exchanging representations of the resources

5. REST web services typically allow for the resource representation to be in a format selected by the client at the time of the request

8. To retrieve a resource, use GET .

9. To change the state of a resource or to update it, use PUT .

12. Hide the server-side scripting technology file extensions, Substitute spaces with hyphens or underscores, Avoid query strings as much as you can, Instead of using the 404 code always provide a default page or resource as a response

15. Such web services can be JAX-WS web services or REST web services

16. JSON text can be dynamically executed as JavaScript

17. JSON is not as verbose as XML while retaining some of the flexibility and extensibility

21. A caching infrastructure can be leveraged for performance

22. The service producer and service consumer have a mutual understanding of the context and content being passed along

23. Bandwidth is particularly important and needs to be limited. PDAs and mobile phones

25. The architecture must address complex nonfunctional requirements

26. The architecture needs to handle asynchronous processing and invocation

29. Clients are AJAX clients.

30. Bandwidth usage needs to be minimized

32. Better tooling is required

33. Reuse of existing data structure definitions is desired

35. supports the Extensible Stylesheet Language Transformations (XSLT) standard

36. JAXP also provides namespace support, allowing you to work with DTDs that might otherwise have naming conflicts

38. SAXParser : The SAXParser interface defines several kinds of parse() methods

39. SAXReaderIt is the SAXReader that carries on the conversation with the SAX event handlers you define

41. ContentHandler : are invoked when an XML tag is recognized

42. ErrorHandler : are invoked in response to various parsing errors

43. DTDHandler : Defines methods you will generally never be called upon to use

45. With a pull parser, you get the next node, whatever it happens to be, at any point in the code that you ask for it

46. SAX requires much less memory than DOM, because SAX does not construct an internal representation

47. SAX Overview

48. SAX Example public static void main(String argv[]) { // Use an instance of ourselves as the SAX event handler DefaultHandler handler = new Echo(); // Use the default (non-validating) parser SAXParserFactory factory = SAXParserFactory.newInstance(); try { // Set up output stream out = new OutputStreamWriter(System.out, "UTF8"); // Parse the input SAXParser saxParser = factory.newSAXParser(); saxParser.parse(new File(argv[0]), handler); } catch (Throwable t) { t.printStackTrace(); } }

50. DocumentBuilder.newDocument() : method to create an empty Document that implements the org.w3c.dom.Document interface

52. allows extreme flexibility in parsing, navigating, and updating the contents of a document

53. high memory requirements and the need for more powerful processing capabilities

54. DOM Overview

55. DOM Example public static void buildDom() { DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); try { DocumentBuilder builder = factory.newDocumentBuilder(); document = builder.newDocument(); Element root = (Element) document.createElement("rootElement"); document.appendChild(root); root.appendChild(document.createTextNode("Some")); root.appendChild(document.createTextNode(" ")); root.appendChild( document.createTextNode("text") ); } catch (ParserConfigurationException pce) { // Parser with specified options can't be built pce.printStackTrace();}}

59. javax.xml.transform.sax : Defines the SAXSource and SAXResult classes, which let you use a SAX event generator as input to a transformation, or deliver SAX events as output to a SAX event processor

61. XSLT Overview

62. XSLT Example Example : j avax.xml.transform.dom Document document; try { File f = new File(argv[0]); DocumentBuilder builder = factory.newDocumentBuilder(); document = builder.parse(f); // Use a Transformer for output TransformerFactory tFactory = TransformerFactory.newInstance(); Transformer transformer = tFactory.newTransformer(); DOMSource source = new DOMSource(document); StreamResult result = new StreamResult(System.out); transformer.transform(source, result); }

65. the cursor API is more efficient.

66. XML processing pipelines, use the iterator API

67. modify the event stream, use the iterator API

69. is that StAX is difficult to use if you return XMLdocuments that follow complex schema