In Part 2 of this two-part series (Part 1 appeared in Vol. 9, issue 4) I
shall try to construct an XML Schema, take you through the steps required to
convert an XML document into its corresponding Java classes and interfaces,
and also show how to generate an XML document (by using the generated Java
classes and interfaces) from a Java object tree, in a programmatic fashion.
A Brief Recap
Part 1 introduced the fundamental concepts of Java Architecture for XML
Binding (JAXB) and gave some insights into how it can be used in a typical
J2EE-based enterprise application.
The power of JAXB comes from the fact that it removes the developer from the
shackles of arduous XML-to-Java (and vice versa) conversion. Its feature-rich
specification allows a Java developer to incorporate Java-specific
programming constructs as part of the XML Schema. Among the rich set of
features, t... (more)
It has been well proven over the past few years that the best form of
information exchange (in a typical B2B and B2C environment) is through XML.
There are various XML-based standards (schema) for both the horizontal and
vertical market sectors and there are ongoing efforts to move toward a
standardized format in the various industry sectors.
With the proliferation of an XML-based information exchange, the industry is
bound to write lots of Java code to consume XML Schema-based documents. Java
Architecture for XML Binding (JAXB) provides a convenient way to bind an XML
Schema to... (more)
JAXB (Java Architecture for XML Binding) provides a convenient way to bind an
XML Schema to a representation in Java code and makes it easy for developers
to incorporate XML data and processing functions into applications based on
Java technology without having to know much about XML itself.
It has been proven over the past few years that the best form of information
exchange (in a typical B2B or B2C scenario) is through XML. There are various
XML-based standards (schemas) for both the horizontal and vertical market
sectors, and there are ongoing efforts to move toward a standardi... (more)
Service Oriented Modeling and Architecture (SOMA) is a modeling and design
technique developed by IBM that provides prescriptive steps for how to enable
target business processes by defining and developing a service-based IT
solution. SOMA provides the communication link between the business
requirements and the IT solution. It provides guidance on how to use business
model and information as inputs to derive and define a service-based IT
model. SOMA, as a methodology, addresses the gap between SOA and object
orientation. This methodology approach provides modeling, analysis, des... (more)
Normal 0 false false false MicrosoftInternetExplorer4
In SOA, the main emphasis is on the identification of the right services
followed by their specification and realization. Although some might argue
that object-oriented analysis and design (OOAD) techniques can be used as a
good starting point for services, its main emphasis is on microlevel
abstractions. Services, on the other hand, are business-aligned entities and
therefore are at a much higher level of abstraction than are objects and
components.
In Part 1 of this book excerpt, we discussed the different layers of an SOA ... (more)