<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/xsl/rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lorraine's podcast</title>
    <link>https://www.podomatic.com/podcasts/thiodre26</link>
    <description>
      <![CDATA[]]>
    </description>
    <language>en-us</language>
    <generator>Podomatic RSS Generator</generator>
    <pubDate>Thu, 21 Apr 2022 07:06:49 +0000</pubDate>
    <itunes:keywords>Education</itunes:keywords>
    <copyright>Copyright 2022 Lorraine Harris</copyright>
    <itunes:subtitle>Give it a listen!</itunes:subtitle>
    <itunes:type>Episodic</itunes:type>
    <itunes:explicit>false</itunes:explicit>
    <itunes:block>no</itunes:block>
    <itunes:image href="https://thiodre26.podomatic.com/images/default/L-3000.png"/>
    <image>
      <url>https://thiodre26.podomatic.com/images/default/L-3000.png</url>
      <title>Lorraine's podcast</title>
      <link>https://www.podomatic.com/podcasts/thiodre26</link>
    </image>
    <itunes:author>Lorraine Harris</itunes:author>
    <itunes:summary></itunes:summary>
    <itunes:category text="Education"></itunes:category>
    <atom:link href="https://thiodre26.podomatic.com/rss2.xml" rel="self" title="Lorraine's podcast" type="application/rss+xml"/>
    <item>
      <title>WSDL</title>
      <description>
        <![CDATA[WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate.

A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations. The concrete protocol and data format specifications for a particular port type constitute a reusable binding. A port is defined by associating a network address with a reusable binding, and a collection of ports define a service. A WSDL document uses the following elements in the definition of network services:
•	Types– a container for data type definitions using some type system (such as XSD). 
•	Message– an abstract, typed definition of the data being communicated. 
•	Operation– an abstract description of an action supported by the service. 
•	Port Type–an abstract set of operations supported by one or more endpoints. 
•	Binding– a concrete protocol and data format specification for a particular port type. 
•	Port– a single endpoint defined as a combination of a binding and a network address. 
•	Service– a collection of related endpoints. 
]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-23T12_33_46-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_33_46-07_00</comments>
      <pubDate>Tue, 23 May 2006 19:33:46 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_33_46-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-23T12_33_46-07_00.mp3" length="399488" type="audio/mpeg"/>
      <itunes:duration>99</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>1</itunes:order>
      <itunes:summary>WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what message formats or network protocols are used to communicate.

A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations. The concrete protocol and data format specifications for a particular port type constitute a reusable binding. A port is defined by associating a network address with a reusable binding, and a collection of ports define a service. A WSDL document uses the following elements in the definition of network services:
&#8226;	Types&#8211; a container for data type definitions using some type system (such as XSD). 
&#8226;	Message&#8211; an abstract, typed definition of the data being communicated. 
&#8226;	Operation&#8211; an abstract description of an action supported by the service. 
&#8226;	Port Type&#8211;an abstract set of operations supported by one or more endpoints. 
&#8226;	Binding&#8211; a concrete protocol and data format specification for a particular port type. 
&#8226;	Port&#8211; a single endpoint defined as a combination of a binding and a network address. 
&#8226;	Service&#8211; a collection of related endpoints. 
</itunes:summary>
      <itunes:subtitle>WSDL is an XML format for describing network services as a set of endpoints operating on messages...</itunes:subtitle>
    </item>
    <item>
      <title>SOAP</title>
      <description>
        <![CDATA[SOAP, which stands for Simple Object Access Protocol, is a protocol for exchanging XML based messages over a computer network, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on. SOAP can be used to facilitate a Service Oriented architectural pattern.

There are several different types of messaging patterns in SOAP, but by far the most common is the Remote Procedure Call (RPC) pattern, where one network node (the client) sends a request message to another node (the server), and the server immediately sends a response to the client.  The general features of SOAP are:

•	Supports most of the SOAP v1.1 specification. 
•	Supports the SOAP Messages with Attachments W3C Note. 
•	Provides server-side infrastructure for deploying, managing and running SOAP enabled services. 
•	Provides client-side API for invoking SOAP services. 
•	Release includes full source under the Apache Software License. 
•	Supports three encoding styles: SOAP v1.1 Encoding, Literal XML and XMI. 
•	XMI encoding (available when using Java 1.2.2) supports automatic marshalling and unmarshalling of arbitrary objects. 
•	SOAP encoding: built-in support is provided for encoding/decoding primitive types, Strings, arbitrary JavaBeans (using reflection) and 1-dimensional arrays of these types. For other types user can hand-write encoder/decoder and register with XML-SOAP runtime. 
•	Literal XML encoding: allows one to send XML elements (DOM org.w3c.dom.Element objects) as parameters by embedding the literal XML serialization of the DOM tree. No code needs to be written to support this (see the addressbook demo to see a sample use of it). 
•	Supports messaging and RPC over two transports: HTTP and SMTP. 
•	Supports authoring services in scripting languages. 
]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-23T12_30_56-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_30_56-07_00</comments>
      <pubDate>Tue, 23 May 2006 19:30:56 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_30_56-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-23T12_30_56-07_00.mp3" length="430208" type="audio/mpeg"/>
      <itunes:duration>107</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>2</itunes:order>
      <itunes:summary>SOAP, which stands for Simple Object Access Protocol, is a protocol for exchanging XML based messages over a computer network, normally using HTTP. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on. SOAP can be used to facilitate a Service Oriented architectural pattern.

There are several different types of messaging patterns in SOAP, but by far the most common is the Remote Procedure Call (RPC) pattern, where one network node (the client) sends a request message to another node (the server), and the server immediately sends a response to the client.  The general features of SOAP are:

&#8226;	Supports most of the SOAP v1.1 specification. 
&#8226;	Supports the SOAP Messages with Attachments W3C Note. 
&#8226;	Provides server-side infrastructure for deploying, managing and running SOAP enabled services. 
&#8226;	Provides client-side API for invoking SOAP services. 
&#8226;	Release includes full source under the Apache Software License. 
&#8226;	Supports three encoding styles: SOAP v1.1 Encoding, Literal XML and XMI. 
&#8226;	XMI encoding (available when using Java 1.2.2) supports automatic marshalling and unmarshalling of arbitrary objects. 
&#8226;	SOAP encoding: built-in support is provided for encoding/decoding primitive types, Strings, arbitrary JavaBeans (using reflection) and 1-dimensional arrays of these types. For other types user can hand-write encoder/decoder and register with XML-SOAP runtime. 
&#8226;	Literal XML encoding: allows one to send XML elements (DOM org.w3c.dom.Element objects) as parameters by embedding the literal XML serialization of the DOM tree. No code needs to be written to support this (see the addressbook demo to see a sample use of it). 
&#8226;	Supports messaging and RPC over two transports: HTTP and SMTP. 
&#8226;	Supports authoring services in scripting languages. 
</itunes:summary>
      <itunes:subtitle>SOAP, which stands for Simple Object Access Protocol, is a protocol for exchanging XML based mess...</itunes:subtitle>
    </item>
    <item>
      <title>XML</title>
      <description>
        <![CDATA[XML is the Extensible Markup Language that improves the functionality of the Web by letting you identify your information in a more accurate, flexible, and adaptable way.  It is extensible because it is not a fixed format like HTML (which is a single, predefined markup language.  Instead, XML is actually a metalanguage—a language for describing other languages—which lets you design your own markup languages for limitless different types of documents. XML can do this because it's written in SGML, the international standard metalanguage for text document markup (ISO 8879). 

A markup language is a set of words and symbols for describing the identity of pieces of a document (for example ‘this is a paragraph’, ‘this is a heading’, ‘this is a list’, ‘this is the caption of this figure’, etc). Programs can use this with a stylesheet to create output for screen, print, audio, video, Braille, etc. 

Some markup languages (eg those used in wordprocessors) only describe appearances (‘this is italics’, ‘this is bold’), but this method can only be used for display, and is not normally re-usable for anything else.  XML is sometimes referred to as ‘self-describing data’ because the names of the markup elements should represent the type of content they hold.  Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML. 

Despite early attempts, browsers never allowed other SGML, only HTML (although there were plugins), and they allowed it (even encouraged it) to be corrupted or broken, which held development back for over a decade by making it impossible to program for it reliably. XML fixes that by making it compulsory to stick to the rules, and by making the rules much simpler than SGML. 

But XML is not just for Web pages: in fact it's very rarely used for Web pages on its own because browsers still don't provide reliable support for formatting and transforming it. 
Common uses for XML include the following:
•	Information identification 
•	Information storage 
•	Information 
•	Publishing 
•	Messaging and data transfer 
•	Web services 

]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-23T12_26_47-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_26_47-07_00</comments>
      <pubDate>Tue, 23 May 2006 19:26:47 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-23T12_26_47-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-23T12_26_47-07_00.mp3" length="589952" type="audio/mpeg"/>
      <itunes:duration>146</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>3</itunes:order>
      <itunes:summary>XML is the Extensible Markup Language that improves the functionality of the Web by letting you identify your information in a more accurate, flexible, and adaptable way.  It is extensible because it is not a fixed format like HTML (which is a single, predefined markup language.  Instead, XML is actually a metalanguage&#8212;a language for describing other languages&#8212;which lets you design your own markup languages for limitless different types of documents. XML can do this because it's written in SGML, the international standard metalanguage for text document markup (ISO 8879). 

A markup language is a set of words and symbols for describing the identity of pieces of a document (for example &#8216;this is a paragraph&#8217;, &#8216;this is a heading&#8217;, &#8216;this is a list&#8217;, &#8216;this is the caption of this figure&#8217;, etc). Programs can use this with a stylesheet to create output for screen, print, audio, video, Braille, etc. 

Some markup languages (eg those used in wordprocessors) only describe appearances (&#8216;this is italics&#8217;, &#8216;this is bold&#8217;), but this method can only be used for display, and is not normally re-usable for anything else.  XML is sometimes referred to as &#8216;self-describing data&#8217; because the names of the markup elements should represent the type of content they hold.  Its goal is to enable generic SGML to be served, received, and processed on the Web in the way that is now possible with HTML. XML has been designed for ease of implementation and for interoperability with both SGML and HTML. 

Despite early attempts, browsers never allowed other SGML, only HTML (although there were plugins), and they allowed it (even encouraged it) to be corrupted or broken, which held development back for over a decade by making it impossible to program for it reliably. XML fixes that by making it compulsory to stick to the rules, and by making the rules much simpler than SGML. 

But XML is not just for Web pages: in fact it's very rarely used for Web pages on its own because browsers still don't provide reliable support for formatting and transforming it. 
Common uses for XML include the following:
&#8226;	Information identification 
&#8226;	Information storage 
&#8226;	Information 
&#8226;	Publishing 
&#8226;	Messaging and data transfer 
&#8226;	Web services 

</itunes:summary>
      <itunes:subtitle>XML is the Extensible Markup Language that improves the functionality of the Web by letting you i...</itunes:subtitle>
    </item>
    <item>
      <title>J2EE Design Patterns Summary</title>
      <description>
        <![CDATA[This podcast discusses J2EE design patterns. 

A pattern describes a proven solution to a recurring design problem, placing particular emphasis on the context and forces surrounding the problem, and the consequences and impact of the solution.
J2EE design patterns are useful for several reasons.  Perhaps, the most notable are the following:  
•	They have been proven. Patterns reflect the experience, knowledge and insights of developers who have successfully used these patterns in their own work.
•	They are reusable. Patterns provide a ready-made solution that can be adapted to different problems as necessary.
•	They are expressive. Patterns provide a common vocabulary of solutions that can express large solutions succinctly.
It is important remember that patterns do not guarantee success. A pattern description indicates when the pattern may be applicable, but only experience can provide understanding of when a particular pattern will improve a design.  You can view a graphic of the architecture of the J2EE design patterns on this podcast.  Additionally, the J2EE design patterns are discussed here.  

INTERCEPTING FILTER:  Facilitates preprocessing and post-processing of a request.
CONTEXT:  The presentation-tier request handling mechanism receives many different types of requests, which require varied types of processing. Some requests are simply forwarded to the appropriate handler component, while other requests must be modified, audited, or uncompressed before being further processed.
SOLUTION:  Pluggable filters can be used to process common services in a standard manner without requiring changes to core request processing code. The filters intercept incoming requests and outgoing responses, allowing preprocessing and post-processing. We are able to add and remove these filters unobtrusively, without requiring changes to our existing code.

FRONT CONTROLLER: Provides a centralized controller for managing the handling of requests.
CONTEXT:  The presentation-tier request handling mechanism must control and coordinate processing of each user across multiple requests. Such control mechanisms may be managed in either a centralized or decentralized manner.
SOLUTION:  Use a controller as the initial point of contact for handling a request. The controller manages the handling of the request, including invoking security services such as authentication and authorization, delegating business processing, managing the choice of an appropriate view, handling errors, and managing the selection of content creation strategies.

COMPOSITE VIEW : Creates an aggregate View from atomic subcomponents.
CONTEXT:  Sophisticated Web pages present content from numerous data sources, using multiple subviews that comprise a single display page. Additionally, a variety of individuals with different skill sets contribute to the development and maintenance of these Web pages.
SOLUTION:  Use composite views that are composed of multiple atomic subviews. Each component of the template may be included dynamically into the whole and the layout of the page may be managed independently of the content.

VIEW HELPER : Encapsulates logic that is not related to presentation formatting into Helper components. 
CONTEXT:  The system creates presentation content, which requires processing of dynamic business data.
SOLUTION:   A view contains formatting code, delegating its processing responsibilities to its helper classes, implemented as JavaBeans or custom tags. Helpers also store the view's intermediate data model and serve as business data adapters.

DISPATCHER VIEW : Combines a Dispatcher component with the Front Controller and View Helper patterns, deferring many activities to View processing. 
CONTEXT:  System controls flow of execution and access to presentation processing, which is responsible for generating dynamic content.  
SOLUTION:  Combine a controller and dispatcher with views and helpers to handle client requests and prepare a dynamic presentation as the response. Controllers do not delegate content retrieval to helpers, because these activities are deferred to the time of view processing. A dispatcher is responsible for view management and navigation and can be encapsulated either within a controller, a view, or a separate component.

SERVICE TO WORKER:  Combines a Dispatcher component with the Front Controller and View Helper patterns. 
CONTEXT:  The system controls flow of execution and access to business data, from which it creates presentation content.  The Service to Worker pattern, like the Dispatcher View pattern, describes a common combination of other patterns from the catalog.  Both of these macro patterns describe the combination of a controller and dispatcher with views and helpers.  While describing this common structure, they emphasize related but different usage patterns.
SOLUTION:  Combine a controller and dispatcher with views and helpers  to handle client requests and prepare a dynamic presentation as the response. Controllers delegate content retrieval to helpers, which manage the population of the intermediate model for the view. A dispatcher is responsible for view management and navigation and can be encapsulated either within a controller or a separate component.

BUSINESS DELEGATE:  Reduces coupling between presentation-tier clients and business services. It hides the underlying Implementation details of the business service, such as lookup and access details of the EJB architecture.
CONTEXT:  A multi-tiered, distributed system requires remote method invocations to send and receive data across tiers. Clients are exposed to the complexity of dealing with distributed components.
SOLUTION:  Use a Business Delegate to reduce coupling between presentation-tier clients and business services. The Business Delegate hides the underlying implementation details of the business service, such as lookup and access details of the EJB architecture.

SESSION FACADE:  Encapsulate the complexity of interactions between the business objects participating in a workflow. The Session Facade manages the business objects, and provides a uniform coarse-grained service access layer to clients.
CONTEXT:  Enterprise beans encapsulate business logic and business data and expose their interfaces, and thus the complexity of the distributed services, to the client tier.
SOLUTION:  Use a session bean as a facade to encapsulate the complexity of interactions between the business objects participating in a workflow. The Session Facade manages the business objects, and provides a uniform coarse-grained service access layer to clients.

SERVICE LOCATOR:  Multiple clients can reuse the Service Locator object to reduce code complexity, provide a single point of control, and improve performance by providing a caching facility.
CONTEXT:  Service lookup and creation involves complex interfaces and network operations.
SOLUTION:  Use a Service Locator object to abstract all JNDI usage and to hide the complexities of initial context creation, EJB home object lookup, and EJB object re-creation. Multiple clients can reuse the Service Locator object to reduce code complexity, provide a single point of control, and improve performance by providing a caching facility.

TRANSFER OBJECT ASSEMBLER :  It is used to build the required model or submodel. The Transfer Object Assembler uses Transfer Objects to retrieve data from various business objects and other objects that define the model or part of the model.
CONTEXT:  In a Java 2 Platform, Enterprise Edition (J2EE) application, the server-side business components are implemented using session beans, entity beans, DAOs, and so forth. Application clients frequently need to access data that is composed from multiple objects.
SOLUTION:  Use a Transfer Object Assembler to build the required model or submodel. The Transfer Object Assembler uses Transfer Objects to retrieve data from various business objects and other objects that define the model or part of the model.

VALUE LIST HANDLER :  The most critical concern in a distributed paradigm is the latency time. Value List Handler Pattern suggests an alternate approach of using ejb-finder methods. The pattern is used to control the search, cache the results and provide the results to the client using a lightweight mechanism.
CONTEXT:  The client requires a list of items from the service for presentation. The number of items in the list is unknown and can be quite large in many instances.
SOLUTION:  Use a Value List Handler to control the search, cache the results, and provide the results to the client in a result set whose size and traversal meets the client's requirements.

COMPOSITE ENTITY :  It model, represent, and manage a set of interrelated persistent objects rather than representing them as individual fine-grained entity beans. A Composite Entity bean represents a graph of objects.
CONTEXT:  Entity beans are not intended to represent every persistent object in the object model. Entity beans are better suited for coarse-grained persistent business objects.
SOLUTION:  Use Composite Entity to model, represent, and manage a set of interrelated persistent objects rather than representing them as individual fine-grained entity beans. A Composite Entity bean represents a graph of objects.

TRANSFER OBJECT:  Encapsulate the business data. A single method call is used to send and retrieve the Transfer Object. When the client requests the enterprise bean for the business data, the enterprise bean can construct the Transfer Object, populate it with its attribute values, and pass it by value to the client.
CONTEXT:  Application clients need to exchange data with enterprise beans.
SOLUTION:  Use a Transfer Object to encapsulate the business data. A single method call is used to send and retrieve the Transfer Object. When the client requests the enterprise bean for the business data, the enterprise bean can construct the Transfer Object, populate it with its attribute values, and pass it by value to the client.

SERVICE ACTIVATOR:  Service Activator enables asynchronous access to enterprise beans and other business services. It receives asynchronous client requests and messages. On receiving a message, the Service Activator locates and invokes the necessary business methods on the business service components to fulfill the request asynchronously. In EJB2.0, Message Driven beans can be used to implement Service Activator for message based enterprise applications. The Service Activator is a JMS Listener and delegation service that creates a message façade for the EJBs.
CONTEXT:  Enterprise beans and other business services need a way to be activated asynchronously.
SOLUTION:  Use a Service Activator to receive asynchronous client requests and messages. On receiving a message, the Service Activator locates and invokes the necessary business methods on the business service components to fulfill the request asynchronously.

DATA ACCESS OBJECT:  Abstracts and encapsulate all access to the data source. The DAO manages the connection with the data source to obtain and store data.
CONTEXT:  Access to data varies depending on the source of the data. Access to persistent storage, such as to a database, varies greatly depending on the type of storage (relational databases, object-oriented databases, flat files, and so forth) and the vendor implementation.
SOLUTION:  Use a Data Access Object (DAO) to abstract and encapsulate all access to the data source. The DAO manages the connection with the data source to obtain and store data.
]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-13T09_37_53-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-13T09_37_53-07_00</comments>
      <pubDate>Sat, 13 May 2006 16:37:53 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-13T09_37_53-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-13T09_37_53-07_00.mp3" length="1198208" type="audio/mpeg"/>
      <itunes:duration>298</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>4</itunes:order>
      <itunes:summary>This podcast discusses J2EE design patterns. 

A pattern describes a proven solution to a recurring design problem, placing particular emphasis on the context and forces surrounding the problem, and the consequences and impact of the solution.
J2EE design patterns are useful for several reasons.  Perhaps, the most notable are the following:  
&#8226;	They have been proven. Patterns reflect the experience, knowledge and insights of developers who have successfully used these patterns in their own work.
&#8226;	They are reusable. Patterns provide a ready-made solution that can be adapted to different problems as necessary.
&#8226;	They are expressive. Patterns provide a common vocabulary of solutions that can express large solutions succinctly.
It is important remember that patterns do not guarantee success. A pattern description indicates when the pattern may be applicable, but only experience can provide understanding of when a particular pattern will improve a design.  You can view a graphic of the architecture of the J2EE design patterns on this podcast.  Additionally, the J2EE design patterns are discussed here.  

INTERCEPTING FILTER:  Facilitates preprocessing and post-processing of a request.
CONTEXT:  The presentation-tier request handling mechanism receives many different types of requests, which require varied types of processing. Some requests are simply forwarded to the appropriate handler component, while other requests must be modified, audited, or uncompressed before being further processed.
SOLUTION:  Pluggable filters can be used to process common services in a standard manner without requiring changes to core request processing code. The filters intercept incoming requests and outgoing responses, allowing preprocessing and post-processing. We are able to add and remove these filters unobtrusively, without requiring changes to our existing code.

FRONT CONTROLLER: Provides a centralized controller for managing the handling of requests.
CONTEXT:  The presentation-tier request handling mechanism must control and coordinate processing of each user across multiple requests. Such control mechanisms may be managed in either a centralized or decentralized manner.
SOLUTION:  Use a controller as the initial point of contact for handling a request. The controller manages the handling of the request, including invoking security services such as authentication and authorization, delegating business processing, managing the choice of an appropriate view, handling errors, and managing the selection of content creation strategies.

COMPOSITE VIEW : Creates an aggregate View from atomic subcomponents.
CONTEXT:  Sophisticated Web pages present content from numerous data sources, using multiple subviews that comprise a single display page. Additionally, a variety of individuals with different skill sets contribute to the development and maintenance of these Web pages.
SOLUTION:  Use composite views that are composed of multiple atomic subviews. Each component of the template may be included dynamically into the whole and the layout of the page may be managed independently of the content.

VIEW HELPER : Encapsulates logic that is not related to presentation formatting into Helper components. 
CONTEXT:  The system creates presentation content, which requires processing of dynamic business data.
SOLUTION:   A view contains formatting code, delegating its processing responsibilities to its helper classes, implemented as JavaBeans or custom tags. Helpers also store the view's intermediate data model and serve as business data adapters.

DISPATCHER VIEW : Combines a Dispatcher component with the Front Controller and View Helper patterns, deferring many activities to View processing. 
CONTEXT:  System controls flow of execution and access to presentation processing, which is responsible for generating dynamic content.  
SOLUTION:  Combine a controller and dispatcher with views and helpers to handle client requests a(continued)</itunes:summary>
      <itunes:subtitle>This podcast discusses J2EE design patterns. 

A pattern describes a proven solution to a recur...</itunes:subtitle>
    </item>
    <item>
      <title>REVIEWS THE GENERATED OUTPUT AFTER THE CHANGES </title>
      <description>
        <![CDATA[Here, the structure of the generated business components in a model is shown.  The diagram is first reviewed in Designer.  To create a diagram, select the tables and drag them onto the surface.  These are generated as Entity Objects in JDeveloper.  The module structure can then be reviewed diagrammatically.  The application module is made up of two base table usages and the relationship that binds them.  These are generated as the Application Module and View Objects in JDeveloper.  In JDeveloper, you can create one or more diagrams for the generated output.  Select the Entity Objects and drag them onto your diagram.  New diagrams can be created or you can drag them onto the same page.  The example in the demo is quite straightforward.  Each of the module components only had one base table usage.  It is more likely that each View Object (or module component) has multiple usages.  The diagram would reflect this.  The Application Module can also be added to the same page.  As in Designer, the Application Module reflects the two view objects and the relationship that binds them.  The application can be tested by using the diagram context menus.  The context menu has other diagramming capabilities as well.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_34_20-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_34_20-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:34:20 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_34_20-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_34_20-07_00.mp3" length="276608" type="audio/mpeg"/>
      <itunes:duration>68</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>5</itunes:order>
      <itunes:summary>Here, the structure of the generated business components in a model is shown.  The diagram is first reviewed in Designer.  To create a diagram, select the tables and drag them onto the surface.  These are generated as Entity Objects in JDeveloper.  The module structure can then be reviewed diagrammatically.  The application module is made up of two base table usages and the relationship that binds them.  These are generated as the Application Module and View Objects in JDeveloper.  In JDeveloper, you can create one or more diagrams for the generated output.  Select the Entity Objects and drag them onto your diagram.  New diagrams can be created or you can drag them onto the same page.  The example in the demo is quite straightforward.  Each of the module components only had one base table usage.  It is more likely that each View Object (or module component) has multiple usages.  The diagram would reflect this.  The Application Module can also be added to the same page.  As in Designer, the Application Module reflects the two view objects and the relationship that binds them.  The application can be tested by using the diagram context menus.  The context menu has other diagramming capabilities as well.  </itunes:summary>
      <itunes:subtitle>Here, the structure of the generated business components in a model is shown.  The diagram is fir...</itunes:subtitle>
    </item>
    <item>
      <title>MAKING CHANGES IN DESIGNER AND REGENERATING </title>
      <description>
        <![CDATA[In this demo, part 3, we return to the Designer Design Editor to update the module definition before regenerating the business components.  Working with the original module that was generated, a Where clause is added and a second base table usage.  Items are added to the new base table.  An additional Where clause is added to the already generated base table.  Additional items can also be added to the already generated base table usage.  In JDeveloper, the ADF Business Components are regenerated via a wizard.  In the wizard, the modules to be regenerated must be selected.  Additional links are created as a result of the new relationship in Designer.  The additional base table usage is reflected in the new View Object.  The new Where clause is appended to the existing clause.  The additional View Usages are also displayed in the Structure pane.  The additional attribute has also been added.  Detail records were also generated.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_31_14-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_31_14-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:31:14 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_31_14-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_31_14-07_00.mp3" length="221312" type="audio/mpeg"/>
      <itunes:duration>55</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>6</itunes:order>
      <itunes:summary>In this demo, part 3, we return to the Designer Design Editor to update the module definition before regenerating the business components.  Working with the original module that was generated, a Where clause is added and a second base table usage.  Items are added to the new base table.  An additional Where clause is added to the already generated base table.  Additional items can also be added to the already generated base table usage.  In JDeveloper, the ADF Business Components are regenerated via a wizard.  In the wizard, the modules to be regenerated must be selected.  Additional links are created as a result of the new relationship in Designer.  The additional base table usage is reflected in the new View Object.  The new Where clause is appended to the existing clause.  The additional View Usages are also displayed in the Structure pane.  The additional attribute has also been added.  Detail records were also generated.</itunes:summary>
      <itunes:subtitle>In this demo, part 3, we return to the Designer Design Editor to update the module definition bef...</itunes:subtitle>
    </item>
    <item>
      <title>REVIEWS THE GENERATED OUTPUT </title>
      <description>
        <![CDATA[Part 1 of this demo showed how Designer ADF Business Component Generator generated business components based on a module defined in Designer.  This demo goes through the generated output.  An Entity Object was generated.  The Entity Object attributes are generated from Designer table definitions.  The attributes are displayed in the Structure Pane.  The validation is generated from the domains associated with columns in Designer.  The View Object attributes are generated from the Designer Module Component base table usages.   The Application Module is made up of the general View objects.  The properties of the components can be reviewed and updated.  From the Entity Objects Editor, you can also see a full list of the attributes.  Validation rules also appear in the Entity Objects Editor.  You can add or modify validate rules in the Editor.  The View Object dialog displays selected attributes generated from the Designer Module Component Basic Table usages.  You can also modify the Where clause and the Order By Clause from this editor.  These clauses are generated based on the Designer property set.  To preview generated results, use the JDeveloper Tester.  With the Tester, you can verify that hints and validations are working.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_28_58-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_28_58-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:28:58 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_28_58-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_28_58-07_00.mp3" length="282752" type="audio/mpeg"/>
      <itunes:duration>70</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>7</itunes:order>
      <itunes:summary>Part 1 of this demo showed how Designer ADF Business Component Generator generated business components based on a module defined in Designer.  This demo goes through the generated output.  An Entity Object was generated.  The Entity Object attributes are generated from Designer table definitions.  The attributes are displayed in the Structure Pane.  The validation is generated from the domains associated with columns in Designer.  The View Object attributes are generated from the Designer Module Component base table usages.   The Application Module is made up of the general View objects.  The properties of the components can be reviewed and updated.  From the Entity Objects Editor, you can also see a full list of the attributes.  Validation rules also appear in the Entity Objects Editor.  You can add or modify validate rules in the Editor.  The View Object dialog displays selected attributes generated from the Designer Module Component Basic Table usages.  You can also modify the Where clause and the Order By Clause from this editor.  These clauses are generated based on the Designer property set.  To preview generated results, use the JDeveloper Tester.  With the Tester, you can verify that hints and validations are working.</itunes:summary>
      <itunes:subtitle>Part 1 of this demo showed how Designer ADF Business Component Generator generated business compo...</itunes:subtitle>
    </item>
    <item>
      <title>REVIEWS A BASIC DESIGNER MODULE </title>
      <description>
        <![CDATA[In this module, the ADF Business Component Generator in JDeveloper is used to generate business components based on a module defined in Oracle 9i Designer.  There are three parts to this demo.  Parts 2 and 3 will show modifications made to the module in Designer and are capture in the business components in JDeveloper during regeneration.  The Designer’s modules are first reviewed.  A Designer module is made up of one or more module components.  In this demo, the module component has a single base table.  You can edit the base table usage by selecting items from the available columns.  Prompt, width, and height information is generated into the ADF Business Components from the Designer properties set.  Before you can start generating the Designer module, there are a few initial tasks that need to be performed.  The following items need to be created:  (1) an application workspace and project if they don’t already exist, (2) a connection to the Designer repository, to the work area which contains the modules you want to generate,  and (3) a database connection for the completed application to connect to.  These tasks can be done separately.  To create a new Designer Workarea Connection, you can invoke the connection wizard.  From the connection wizard, select a database connection or create a new one.  Once the wizard is complete, ADF Business Components are created and added to the project.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_26_24-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_26_24-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:26:24 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_26_24-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_26_24-07_00.mp3" length="317568" type="audio/mpeg"/>
      <itunes:duration>78</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>8</itunes:order>
      <itunes:summary>In this module, the ADF Business Component Generator in JDeveloper is used to generate business components based on a module defined in Oracle 9i Designer.  There are three parts to this demo.  Parts 2 and 3 will show modifications made to the module in Designer and are capture in the business components in JDeveloper during regeneration.  The Designer&#8217;s modules are first reviewed.  A Designer module is made up of one or more module components.  In this demo, the module component has a single base table.  You can edit the base table usage by selecting items from the available columns.  Prompt, width, and height information is generated into the ADF Business Components from the Designer properties set.  Before you can start generating the Designer module, there are a few initial tasks that need to be performed.  The following items need to be created:  (1) an application workspace and project if they don&#8217;t already exist, (2) a connection to the Designer repository, to the work area which contains the modules you want to generate,  and (3) a database connection for the completed application to connect to.  These tasks can be done separately.  To create a new Designer Workarea Connection, you can invoke the connection wizard.  From the connection wizard, select a database connection or create a new one.  Once the wizard is complete, ADF Business Components are created and added to the project.</itunes:summary>
      <itunes:subtitle>In this module, the ADF Business Component Generator in JDeveloper is used to generate business c...</itunes:subtitle>
    </item>
    <item>
      <title>WEB SERVICES BASED APPLICATION (WEB SERVICES-STRUTS-JSP) </title>
      <description>
        <![CDATA[In this section of the Reviewer’s Guide, it provided guidance on integrating a Web service into your application.   Oracle JDeveloper makes it easy to consume existing Web services as well as to develop and publish new Web services from any Java class or PL/SQL stored procedure.  An existing Web service is used to create a simple application.  The Web service will function as a business service, and the ADF Model layer will let us use it in the same way we worked with the database based business service.  The interesting thing to note is the similar development experience you get with Oracle ADF.  This section requires Internet access. If you are using proxy to connect to the Internet make sure to set this in the tools->preferences->Web Browser and Proxy settings menu option.  To consume an existing an Web service, first locate an existing Web service by browsing a UDDI repository by doing the following:  (1) Create a new application and choose the Web Application [JSP, Struts, EJB] technology stack for it, (2) Switch to the Connections Navigator Ctrl+shift+O, (3) Expand the UDDI node and continue through Microsoft Public UDDI->Xmethods->Services->Xmethods Delayed Stock Quotes->htpp…->Xmethods Simple Stock Quote, (4) Right click on Xmethods Simple Stock Quote and choose Create Data Control.  The steps you just followed created a java class that acts as a data control based on the existing Web service. You can look at the code for this class to see the calls to the Web service. The next few steps will simply create a Web application that will activate the Web service pass a parameter to it and get a value back.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_23_24-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_23_24-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:23:24 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_23_24-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_23_24-07_00.mp3" length="407680" type="audio/mpeg"/>
      <itunes:duration>101</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>9</itunes:order>
      <itunes:summary>In this section of the Reviewer&#8217;s Guide, it provided guidance on integrating a Web service into your application.   Oracle JDeveloper makes it easy to consume existing Web services as well as to develop and publish new Web services from any Java class or PL/SQL stored procedure.  An existing Web service is used to create a simple application.  The Web service will function as a business service, and the ADF Model layer will let us use it in the same way we worked with the database based business service.  The interesting thing to note is the similar development experience you get with Oracle ADF.  This section requires Internet access. If you are using proxy to connect to the Internet make sure to set this in the tools-&gt;preferences-&gt;Web Browser and Proxy settings menu option.  To consume an existing an Web service, first locate an existing Web service by browsing a UDDI repository by doing the following:  (1) Create a new application and choose the Web Application [JSP, Struts, EJB] technology stack for it, (2) Switch to the Connections Navigator Ctrl+shift+O, (3) Expand the UDDI node and continue through Microsoft Public UDDI-&gt;Xmethods-&gt;Services-&gt;Xmethods Delayed Stock Quotes-&gt;htpp&#8230;-&gt;Xmethods Simple Stock Quote, (4) Right click on Xmethods Simple Stock Quote and choose Create Data Control.  The steps you just followed created a java class that acts as a data control based on the existing Web service. You can look at the code for this class to see the calls to the Web service. The next few steps will simply create a Web application that will activate the Web service pass a parameter to it and get a value back.</itunes:summary>
      <itunes:subtitle>In this section of the Reviewer&#8217;s Guide, it provided guidance on integrating a Web service into y...</itunes:subtitle>
    </item>
    <item>
      <title>EJB BASED APPLICATION (EJB-STRUTS-JSP) </title>
      <description>
        <![CDATA[In this section of the JDevelop 10g Reviewer’s Guide, it was shown how to create a couple of Entity Enterprise Java Beans, a session façade and DTO design patterns for them and a JSP application that uses these to access data in the database.  Entity EJB is another way to create Java objects that interact with a database.  There are several design patterns that you should implement when working with Entity EJB. The session façade and Data Transfer Object (DTO) are two of the more important.  As was seen this section you use the same modeling and data binding technique you used when working with Oracle ADF Business Components when you work with EJBs as your business service layer.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_19_30-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_19_30-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:19:30 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_19_30-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_19_30-07_00.mp3" length="610432" type="audio/mpeg"/>
      <itunes:duration>152</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>10</itunes:order>
      <itunes:summary>In this section of the JDevelop 10g Reviewer&#8217;s Guide, it was shown how to create a couple of Entity Enterprise Java Beans, a session fa&#231;ade and DTO design patterns for them and a JSP application that uses these to access data in the database.  Entity EJB is another way to create Java objects that interact with a database.  There are several design patterns that you should implement when working with Entity EJB. The session fa&#231;ade and Data Transfer Object (DTO) are two of the more important.  As was seen this section you use the same modeling and data binding technique you used when working with Oracle ADF Business Components when you work with EJBs as your business service layer.  </itunes:summary>
      <itunes:subtitle>In this section of the JDevelop 10g Reviewer&#8217;s Guide, it was shown how to create a couple of Enti...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE ADF BUSINESS COMPONENTS BASED APPLICATION &#8211; VIEW LAYER (UIX) </title>
      <description>
        <![CDATA[Oracle ADF lets you plug and play different technologies in each of its layers. In this tutorial, Oracle ADF UIX is used to create another View layer on top of the Oracle ADF Business Components based business services layer. Oracle ADF UIX is a user interface development framework; its main benefits include an extensive set of graphical HTML components and an easy way of defining a page structure. ADF UIX will evolve to become the Oracle implementation of JavaServer Faces (JSF), and will offer a rich set if JSF components.   ADF UIX automatically provides you with range browsing for both the departments and employees.  So you can scroll 10 records at a time, and even jump to a specific record range.  Select different departments on the page to view their employee’s details.  Notice that when you change a department and the new department employees get displayed – only the employees part of the page is rendered from scratch and not the whole HTML page – this unique ADF UIX feature is called Partial Page Rendering.  Click on the heading of the different columns in the tables to order the records by the specific column.  These are only some of the features you get with the rich set of user interface components that Oracle ADF UIX offers. The ADF UIX look and feel can be customized to suite your needs. ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_13_34-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_13_34-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:13:34 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_13_34-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_13_34-07_00.mp3" length="344192" type="audio/mpeg"/>
      <itunes:duration>85</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>11</itunes:order>
      <itunes:summary>Oracle ADF lets you plug and play different technologies in each of its layers. In this tutorial, Oracle ADF UIX is used to create another View layer on top of the Oracle ADF Business Components based business services layer. Oracle ADF UIX is a user interface development framework; its main benefits include an extensive set of graphical HTML components and an easy way of defining a page structure. ADF UIX will evolve to become the Oracle implementation of JavaServer Faces (JSF), and will offer a rich set if JSF components.   ADF UIX automatically provides you with range browsing for both the departments and employees.  So you can scroll 10 records at a time, and even jump to a specific record range.  Select different departments on the page to view their employee&#8217;s details.  Notice that when you change a department and the new department employees get displayed &#8211; only the employees part of the page is rendered from scratch and not the whole HTML page &#8211; this unique ADF UIX feature is called Partial Page Rendering.  Click on the heading of the different columns in the tables to order the records by the specific column.  These are only some of the features you get with the rich set of user interface components that Oracle ADF UIX offers. The ADF UIX look and feel can be customized to suite your needs. </itunes:summary>
      <itunes:subtitle>Oracle ADF lets you plug and play different technologies in each of its layers. In this tutorial,...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE ADF BUSINESS COMPONENTS BASED APPLICATION &#8211; VIEW/CONTROLLER LAYER (STRUTS/JSP) </title>
      <description>
        <![CDATA[The View layer provides the user interface to the application. The view layer uses HTML, rich Java components, or XML and its variations to render the user interface. The View layer can be Web-based, client server-based, or even a wireless implementation.   The Controller layer controls the application’s flow. Web-based applications are composed of multiple Web pages with dynamic content. The controller layer manages the flow between these pages. Different models can be used when building this layer. The most prominent architecture for Java-based Web applications relies on a servlet that acts as the controller. The Apache Jakarta Struts controller, an open source framework controller, is the de facto standard.  In this section we’ll create a simple application that manipulates the data exposed by the Oracle ADF Business Components business services layer. The application will enable users to browse departments and update an employee’s details. We’ll use Struts to control the flow between two JSP pages that bind to our business services via the Model layer. Oracle ADF delivers a very easy way to bind the Control and View Layers to Business Services of any type through its Model abstraction layer. This innovative architecture is the base for JSR-227.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T13_10_23-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_10_23-07_00</comments>
      <pubDate>Fri, 05 May 2006 20:10:23 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T13_10_23-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T13_10_23-07_00.mp3" length="321664" type="audio/mpeg"/>
      <itunes:duration>80</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>12</itunes:order>
      <itunes:summary>The View layer provides the user interface to the application. The view layer uses HTML, rich Java components, or XML and its variations to render the user interface. The View layer can be Web-based, client server-based, or even a wireless implementation.   The Controller layer controls the application&#8217;s flow. Web-based applications are composed of multiple Web pages with dynamic content. The controller layer manages the flow between these pages. Different models can be used when building this layer. The most prominent architecture for Java-based Web applications relies on a servlet that acts as the controller. The Apache Jakarta Struts controller, an open source framework controller, is the de facto standard.  In this section we&#8217;ll create a simple application that manipulates the data exposed by the Oracle ADF Business Components business services layer. The application will enable users to browse departments and update an employee&#8217;s details. We&#8217;ll use Struts to control the flow between two JSP pages that bind to our business services via the Model layer. Oracle ADF delivers a very easy way to bind the Control and View Layers to Business Services of any type through its Model abstraction layer. This innovative architecture is the base for JSR-227.  </itunes:summary>
      <itunes:subtitle>The View layer provides the user interface to the application. The view layer uses HTML, rich Jav...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE ADF BUSINESS COMPONENTS BASED APPLICATION &#8211; BUSINESS SERVICES LAYER </title>
      <description>
        <![CDATA[Oracle ADF is based on four layers.  One of the layers, the Business Services layer provides access to data from various sources.  Oracle ADF lets developers choose the technology they prefer to use when implementing each of the layers. Oracle ADF provides the same visual and declarative development experience regardless of the technology stack used.  The Business Services layer manages interaction with a data persistence layer.  It provides such services as data persistence, object/relational mapping, transaction management, and business logic execution.  The Business Services layer in Oracle ADF can be implemented as simple Java classes, EJB, Web services, TopLink objects, or Oracle ADF Business Components.  The Model layer connects the Business Services to the objects that use them in the other layers. Oracle ADF provides a Model layer implementation that sits on top of Business Services, providing a single interface that can be used to access any type of Business Service. Developers get the same development experience when binding any type of Business Service layer implementation to the View and Controller layers. ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T12_41_11-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_41_11-07_00</comments>
      <pubDate>Fri, 05 May 2006 19:41:11 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_41_11-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T12_41_11-07_00.mp3" length="579712" type="audio/mpeg"/>
      <itunes:duration>144</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>13</itunes:order>
      <itunes:summary>Oracle ADF is based on four layers.  One of the layers, the Business Services layer provides access to data from various sources.  Oracle ADF lets developers choose the technology they prefer to use when implementing each of the layers. Oracle ADF provides the same visual and declarative development experience regardless of the technology stack used.  The Business Services layer manages interaction with a data persistence layer.  It provides such services as data persistence, object/relational mapping, transaction management, and business logic execution.  The Business Services layer in Oracle ADF can be implemented as simple Java classes, EJB, Web services, TopLink objects, or Oracle ADF Business Components.  The Model layer connects the Business Services to the objects that use them in the other layers. Oracle ADF provides a Model layer implementation that sits on top of Business Services, providing a single interface that can be used to access any type of Business Service. Developers get the same development experience when binding any type of Business Service layer implementation to the View and Controller layers. </itunes:summary>
      <itunes:subtitle>Oracle ADF is based on four layers.  One of the layers, the Business Services layer provides acce...</itunes:subtitle>
    </item>
    <item>
      <title>A SRUTS/JSP APPLICATION</title>
      <description>
        <![CDATA[To get to know the basic concepts of Struts, you can create an application using basic JSP combined with a simple Struts page flow.  You can also see how the view and control layers are separated.  The sample application is a simple password verification process. Once a new application has been in the Applications Navigator, you will notice that the application is divided into a model and a view/controller section. This will help you separate the different layers.  The next step would be to design the page flow diagram.  The page flow modeler provides a visual representation of the content of this XML file.  The steps can be found in the Oracle JDeveloper 10g Reviewers Guide on Page 14.  From the page flow modeler you can directly access the source of the pages to edit them.  These steps are also found in the Oracle JDeveloper 10g Reviewers Guide.  To edit other pages, switch back to the Struts-config.xml tab to see the page flow diagram and follow the steps on pages 16 in the Oracle JDeveloper 10g Reviewers Guide.  Next, you can add the business logic to the Controller layer that will define the application flow.  When this is done, the actual logic must be added.  Upon completion, you will notice that you only needed to do Java coding to implement the actual business logic that is used to validate the password. This is the benefit of Oracle ADF – it takes care of the plumbing for you and let you focus on writing the business logic.
]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T12_35_35-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_35_35-07_00</comments>
      <pubDate>Fri, 05 May 2006 19:35:35 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_35_35-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T12_35_35-07_00.mp3" length="346240" type="audio/mpeg"/>
      <itunes:duration>86</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>14</itunes:order>
      <itunes:summary>To get to know the basic concepts of Struts, you can create an application using basic JSP combined with a simple Struts page flow.  You can also see how the view and control layers are separated.  The sample application is a simple password verification process. Once a new application has been in the Applications Navigator, you will notice that the application is divided into a model and a view/controller section. This will help you separate the different layers.  The next step would be to design the page flow diagram.  The page flow modeler provides a visual representation of the content of this XML file.  The steps can be found in the Oracle JDeveloper 10g Reviewers Guide on Page 14.  From the page flow modeler you can directly access the source of the pages to edit them.  These steps are also found in the Oracle JDeveloper 10g Reviewers Guide.  To edit other pages, switch back to the Struts-config.xml tab to see the page flow diagram and follow the steps on pages 16 in the Oracle JDeveloper 10g Reviewers Guide.  Next, you can add the business logic to the Controller layer that will define the application flow.  When this is done, the actual logic must be added.  Upon completion, you will notice that you only needed to do Java coding to implement the actual business logic that is used to validate the password. This is the benefit of Oracle ADF &#8211; it takes care of the plumbing for you and let you focus on writing the business logic.
</itunes:summary>
      <itunes:subtitle>To get to know the basic concepts of Struts, you can create an application using basic JSP combin...</itunes:subtitle>
    </item>
    <item>
      <title>DATABASE SCHEMA MODELER</title>
      <description>
        <![CDATA[The purpose of this demo was to illustrate the latest database modeling features in JDeveloper.  To create a new diagram, you use the context menu.  The tables that are to appear in the diagram must be selected.  After the tables are selected, they are dragged to the diagram.  For large, complex schema diagrams, thumbnail diagrams are useful.   The thumbnail diagram can also be used to move to different locations.  To fine tune the layout of the diagram, you can use the options on the context menu.  Using the Component Palette, you can add objects to the diagram.  At this point, the DDL script can be generated.  This is done via a Generate SQL from Offline Database Objects wizard.  Step 2 of the wizards asks if you want to create or update a chosen object.  At this point you can also generate the script or perform the action directly within the database.  Once you click finish, you will have completed the wizard.  To execute the SQL against the required schema, use the contest menu.  To review the updates, return to the database connection.  The table will reflect the change.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T12_31_30-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_31_30-07_00</comments>
      <pubDate>Fri, 05 May 2006 19:31:30 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_31_30-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T12_31_30-07_00.mp3" length="252032" type="audio/mpeg"/>
      <itunes:duration>62</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>15</itunes:order>
      <itunes:summary>The purpose of this demo was to illustrate the latest database modeling features in JDeveloper.  To create a new diagram, you use the context menu.  The tables that are to appear in the diagram must be selected.  After the tables are selected, they are dragged to the diagram.  For large, complex schema diagrams, thumbnail diagrams are useful.   The thumbnail diagram can also be used to move to different locations.  To fine tune the layout of the diagram, you can use the options on the context menu.  Using the Component Palette, you can add objects to the diagram.  At this point, the DDL script can be generated.  This is done via a Generate SQL from Offline Database Objects wizard.  Step 2 of the wizards asks if you want to create or update a chosen object.  At this point you can also generate the script or perform the action directly within the database.  Once you click finish, you will have completed the wizard.  To execute the SQL against the required schema, use the contest menu.  To review the updates, return to the database connection.  The table will reflect the change.</itunes:summary>
      <itunes:subtitle>The purpose of this demo was to illustrate the latest database modeling features in JDeveloper.  ...</itunes:subtitle>
    </item>
    <item>
      <title>JAVA CLASS MODELING</title>
      <description>
        <![CDATA[The Java Class Modeling demonstration uses Java files generated by JDeveloper 10g to create a Java client for a Google Search Web service based on a Google API WSDL.  First, a diagram of the search google package must be created.  A Java class must be created and the name of the package in which the diagram will be created must be changed.  In the GUI interface, the component palette takes up a little too much space, so it is a good idea to look at the icons only and make that pane narrower.  To visualize the package that was created, drag and drop it onto the diagram and to visualize the classes in the package, select Drill Down from the context menu.  You don’t need to visualize the package first.  You can just drag and drop the classes directly from the navigator.  It should be noted that JDeveloper supports a number of styles of diagram autolayout.  They are hierarchical (top to bottom), hierarchical (bottom to top), hierarchical (right to left), hierarchical (left to right), symmetrical, and grid.  The Java class modeler automatically synchronizes the diagram and the code, regardless of where you make the changes.  The structure pane exposes the content of the class.  Double-clicking a node in the structure pane opens the Java class file and navigates to the relevant point in the code.  A SaveAll operation writes the whole project to disk and resets to normal text any italic items.  There are a number of attributes and methods in the project that reference the demo class.  The refactoring process identifies the dependencies, implements the changes and recompiles the project.  All of which can be driven directly from the program.  The thumbnail view can be used to move around the diagram quickly and easily.  More than one package can be displayed in a diagram and dependencies can be drawn between them.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T12_28_42-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_28_42-07_00</comments>
      <pubDate>Fri, 05 May 2006 19:28:42 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T12_28_42-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T12_28_42-07_00.mp3" length="426112" type="audio/mpeg"/>
      <itunes:duration>106</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>16</itunes:order>
      <itunes:summary>The Java Class Modeling demonstration uses Java files generated by JDeveloper 10g to create a Java client for a Google Search Web service based on a Google API WSDL.  First, a diagram of the search google package must be created.  A Java class must be created and the name of the package in which the diagram will be created must be changed.  In the GUI interface, the component palette takes up a little too much space, so it is a good idea to look at the icons only and make that pane narrower.  To visualize the package that was created, drag and drop it onto the diagram and to visualize the classes in the package, select Drill Down from the context menu.  You don&#8217;t need to visualize the package first.  You can just drag and drop the classes directly from the navigator.  It should be noted that JDeveloper supports a number of styles of diagram autolayout.  They are hierarchical (top to bottom), hierarchical (bottom to top), hierarchical (right to left), hierarchical (left to right), symmetrical, and grid.  The Java class modeler automatically synchronizes the diagram and the code, regardless of where you make the changes.  The structure pane exposes the content of the class.  Double-clicking a node in the structure pane opens the Java class file and navigates to the relevant point in the code.  A SaveAll operation writes the whole project to disk and resets to normal text any italic items.  There are a number of attributes and methods in the project that reference the demo class.  The refactoring process identifies the dependencies, implements the changes and recompiles the project.  All of which can be driven directly from the program.  The thumbnail view can be used to move around the diagram quickly and easily.  More than one package can be displayed in a diagram and dependencies can be drawn between them.</itunes:summary>
      <itunes:subtitle>The Java Class Modeling demonstration uses Java files generated by JDeveloper 10g to create a Jav...</itunes:subtitle>
    </item>
    <item>
      <title>UML ACTIVITY MODELER</title>
      <description>
        <![CDATA[Oracle JDeveloper 10g supports UML Activity Modeling.  Here, and order management business process modeled in a UML activity model is shown.  The model is unfinished.  The process that checks and returns customer details is missing.  In the demo, there is an entire customer validation system missing and the Defer Order process flow needs to be terminated.  First, the thumbnail view will be used to zoom in to the model.  Forward on the mouse wheel zooms in and backwards zooms out.  Next a swimlane is created to support the Customer System, which results in a new object flow state.  Afterwards, transitions were created that connected the activity and state with the rest of the model.  Double-clicking components make it ‘sticky’, which allow you to create multiple instances one after the other.  After another transition is created, an AND join is needed to synchronize the transitions.  The transition is then attached to the join.  The diagram can be easily navigated with the thumbnail view.  The flow is completed with a Final State.  The diagram is completed by placed guard conditions at the OR decision point.  The completed diagram can be refined by decomposing or drilling down into existing activities and creating new diagrams from this diagram.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T10_18_07-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_18_07-07_00</comments>
      <pubDate>Fri, 05 May 2006 17:18:07 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_18_07-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T10_18_07-07_00.mp3" length="303232" type="audio/mpeg"/>
      <itunes:duration>75</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>17</itunes:order>
      <itunes:summary>Oracle JDeveloper 10g supports UML Activity Modeling.  Here, and order management business process modeled in a UML activity model is shown.  The model is unfinished.  The process that checks and returns customer details is missing.  In the demo, there is an entire customer validation system missing and the Defer Order process flow needs to be terminated.  First, the thumbnail view will be used to zoom in to the model.  Forward on the mouse wheel zooms in and backwards zooms out.  Next a swimlane is created to support the Customer System, which results in a new object flow state.  Afterwards, transitions were created that connected the activity and state with the rest of the model.  Double-clicking components make it &#8216;sticky&#8217;, which allow you to create multiple instances one after the other.  After another transition is created, an AND join is needed to synchronize the transitions.  The transition is then attached to the join.  The diagram can be easily navigated with the thumbnail view.  The flow is completed with a Final State.  The diagram is completed by placed guard conditions at the OR decision point.  The completed diagram can be refined by decomposing or drilling down into existing activities and creating new diagrams from this diagram.</itunes:summary>
      <itunes:subtitle>Oracle JDeveloper 10g supports UML Activity Modeling.  Here, and order management business proces...</itunes:subtitle>
    </item>
    <item>
      <title>UML USE CASE MODELER</title>
      <description>
        <![CDATA[UML Use Case Modeling in JDeveloper 10g is introduced in this demo.  Modeling use cases allows you to capture the requirements of your system in terms of the functionality it offers to external actors (persons, organizations, or software systems).  To create a UML Use Case Diagram, open the Create UML Use Case Diagram dialog box, in which you will define the name and package for a new diagram.  Where a use case requires a great deal of detail, make use of the “fully dressed” option.  The underlying document created uses a more detailed template.  Invoke the properties menu for the use case to add requirements details in the HTML editor.  You will see the document that JDeveloper produces for a “fully dressed” use case.  The template can be modified if desired.  The diagram and the HTML file are continually synchronized by JDeveloper.  The detailed scenario of the use case must be defined in terms of a set of shapes.  You should return to the diagram to define another use case that is related to the previous one.  On the second occurrence, the use case requires less specification so a casual template was used.  Various functions are available for tidying up the diagram:  auto-layout, align and distribute.  For further documentation, notes can be added to diagrams, as can be url links to external documents.  The requirements captured can be easily published in JavaDoc HTML form and placed on a server for reference and validation.  JavaDoc published on a web server can be reviewed by users with their favorite browser.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T10_14_55-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_14_55-07_00</comments>
      <pubDate>Fri, 05 May 2006 17:14:55 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_14_55-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T10_14_55-07_00.mp3" length="374912" type="audio/mpeg"/>
      <itunes:duration>93</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>18</itunes:order>
      <itunes:summary>UML Use Case Modeling in JDeveloper 10g is introduced in this demo.  Modeling use cases allows you to capture the requirements of your system in terms of the functionality it offers to external actors (persons, organizations, or software systems).  To create a UML Use Case Diagram, open the Create UML Use Case Diagram dialog box, in which you will define the name and package for a new diagram.  Where a use case requires a great deal of detail, make use of the &#8220;fully dressed&#8221; option.  The underlying document created uses a more detailed template.  Invoke the properties menu for the use case to add requirements details in the HTML editor.  You will see the document that JDeveloper produces for a &#8220;fully dressed&#8221; use case.  The template can be modified if desired.  The diagram and the HTML file are continually synchronized by JDeveloper.  The detailed scenario of the use case must be defined in terms of a set of shapes.  You should return to the diagram to define another use case that is related to the previous one.  On the second occurrence, the use case requires less specification so a casual template was used.  Various functions are available for tidying up the diagram:  auto-layout, align and distribute.  For further documentation, notes can be added to diagrams, as can be url links to external documents.  The requirements captured can be easily published in JavaDoc HTML form and placed on a server for reference and validation.  JavaDoc published on a web server can be reviewed by users with their favorite browser.</itunes:summary>
      <itunes:subtitle>UML Use Case Modeling in JDeveloper 10g is introduced in this demo.  Modeling use cases allows yo...</itunes:subtitle>
    </item>
    <item>
      <title>UML CLASS MODELER</title>
      <description>
        <![CDATA[UML Class modeling enables the capture of requirements in a technology neutral visual model to validate user requirements and document complex applications.  In this demo, the components of a simple order entry application in an abstract UML Class diagram were created and generated a Java Class diagram and implementation files.  A basic Class diagram was created with classes and associations between them.  Some attributes and methods were added to the Order class.  Attributes can also be added using the Class dialog.  The diagram layout can be fine-tuned with the align and distribute functionality.  Several auto-layout options are also available.  JDeveloper 10g supports Model Driven Architecture (MDA) style transformations between a UML analysis model and a Java or ADF Business Components design model.  A UML analysis model was transformed into a visual Java design model and implementation files.  The generated Java design model and implementation files reflect the properties of the UML analysis model with associations implemented as java references.  The developer can navigate directly to the code to add method bodies and further implementation functionality at this level.  Apart from the MDA style transformations, JDeveloper 10g also supports linking of diagrams for rapid traversal of models.  In the demo, a link was inserted from the analysis diagram to the design model.  By clicking on the diagram, details for the link can be inserted in the create link dialog.  In order to publish visual models for review or reference, UML models can be published as graphics files or inserted in a JavaDoc HTML document.  JDeveloper generated an HTML index file.  By clicking on a class in the embedded Java diagram, you can navigate directly to its documentation.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T10_05_56-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_05_56-07_00</comments>
      <pubDate>Fri, 05 May 2006 17:05:56 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_05_56-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T10_05_56-07_00.mp3" length="473216" type="audio/mpeg"/>
      <itunes:duration>117</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>19</itunes:order>
      <itunes:summary>UML Class modeling enables the capture of requirements in a technology neutral visual model to validate user requirements and document complex applications.  In this demo, the components of a simple order entry application in an abstract UML Class diagram were created and generated a Java Class diagram and implementation files.  A basic Class diagram was created with classes and associations between them.  Some attributes and methods were added to the Order class.  Attributes can also be added using the Class dialog.  The diagram layout can be fine-tuned with the align and distribute functionality.  Several auto-layout options are also available.  JDeveloper 10g supports Model Driven Architecture (MDA) style transformations between a UML analysis model and a Java or ADF Business Components design model.  A UML analysis model was transformed into a visual Java design model and implementation files.  The generated Java design model and implementation files reflect the properties of the UML analysis model with associations implemented as java references.  The developer can navigate directly to the code to add method bodies and further implementation functionality at this level.  Apart from the MDA style transformations, JDeveloper 10g also supports linking of diagrams for rapid traversal of models.  In the demo, a link was inserted from the analysis diagram to the design model.  By clicking on the diagram, details for the link can be inserted in the create link dialog.  In order to publish visual models for review or reference, UML models can be published as graphics files or inserted in a JavaDoc HTML document.  JDeveloper generated an HTML index file.  By clicking on a class in the embedded Java diagram, you can navigate directly to its documentation.  </itunes:summary>
      <itunes:subtitle>UML Class modeling enables the capture of requirements in a technology neutral visual model to va...</itunes:subtitle>
    </item>
    <item>
      <title>XML SCHEMA REGISTRATION AND THE XML EDITOR </title>
      <description>
        <![CDATA[To be able to use and help with a new schema, JDeveloper requires the schema to be registered.  The registration process is done from the Preferences panel.  Go to Tools, Preferences, XML Schemas.  In this demo, a line will be added in the bottom JTable and the schema will be associated with an extension for the future instance documents.  Since the file that will be referred to is on the file system, it can be referred to using the Browse button.  The schema will be associated with the xml extension.  The new schema was parsed and registered.  Afterwards, you are ready to create an xml document matching the definition of the schema that was just registered.  You begin by clicking XML and XML document from the New Gallery dialog box.  You must then give the file a name and an extension matching the schema registration.  In this case, it was an xml extension.  An empty document is created.  The Structure Pane will report any errors right away.  The tricky part to this is creating a root before being able to mention any namespaces.  After clicking in the line of code, a group of namespaces associated with the file extension pops us.  The namespaces were selected and a ‘/’ was entered to close whatever has to be closed.  A new element was opened by entering the character ‘<’.  A list of the available namespace prefixes popped up.  A namespace was selected and an element was inserted.  When a value is entered that doesn’t match the constraint, an error is reported.  That can be and was fixed.  Because there was a restricted parameter, possible values were suggested in a list.   As the schema is registered with JDeveloper, the document can also be validated against the schema by right-clicking on it and choosing Validate XML.  Possible errors would be reported in the Messages Log.  Registering a schema also offers the possibility to use the component palette to manipulate XML Elements.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T10_01_03-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_01_03-07_00</comments>
      <pubDate>Fri, 05 May 2006 17:01:03 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T10_01_03-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T10_01_03-07_00.mp3" length="465024" type="audio/mpeg"/>
      <itunes:duration>115</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>20</itunes:order>
      <itunes:summary>To be able to use and help with a new schema, JDeveloper requires the schema to be registered.  The registration process is done from the Preferences panel.  Go to Tools, Preferences, XML Schemas.  In this demo, a line will be added in the bottom JTable and the schema will be associated with an extension for the future instance documents.  Since the file that will be referred to is on the file system, it can be referred to using the Browse button.  The schema will be associated with the xml extension.  The new schema was parsed and registered.  Afterwards, you are ready to create an xml document matching the definition of the schema that was just registered.  You begin by clicking XML and XML document from the New Gallery dialog box.  You must then give the file a name and an extension matching the schema registration.  In this case, it was an xml extension.  An empty document is created.  The Structure Pane will report any errors right away.  The tricky part to this is creating a root before being able to mention any namespaces.  After clicking in the line of code, a group of namespaces associated with the file extension pops us.  The namespaces were selected and a &#8216;/&#8217; was entered to close whatever has to be closed.  A new element was opened by entering the character &#8216;&lt;&#8217;.  A list of the available namespace prefixes popped up.  A namespace was selected and an element was inserted.  When a value is entered that doesn&#8217;t match the constraint, an error is reported.  That can be and was fixed.  Because there was a restricted parameter, possible values were suggested in a list.   As the schema is registered with JDeveloper, the document can also be validated against the schema by right-clicking on it and choosing Validate XML.  Possible errors would be reported in the Messages Log.  Registering a schema also offers the possibility to use the component palette to manipulate XML Elements.</itunes:summary>
      <itunes:subtitle>To be able to use and help with a new schema, JDeveloper requires the schema to be registered.  T...</itunes:subtitle>
    </item>
    <item>
      <title>VISUAL XML SCHEMA EDITOR</title>
      <description>
        <![CDATA[In order to get started with this demo, and existing XML Schema with JDeveloper 10g was opened.  By default, the xsd extension is the default associated with XML schemas.  When opening the schema, its code can be opened also by flipping to the Source tab at the bottom of the Editor Pane.  When using the XML Schema Visual Editor, several panes of JDeveloper are synchronized.  The Schema Components Palette is on the right of the GUI.  The Schema Property Inspector is below that.  The Structure Pane is to the bottom left of the GUI.  In this demo and in Visual XML Schema Editor, the artifact represents a ComplexType.  Selecting the artifact will possibly display the annotation associated with it, if any.  Selecting it also updates the Structure pane, as well as the Property Inspector.  There was another artifact that represented an Element.  You can tell this by also looking at the Structure Pane.  All subcomponents can be expanded or collapsed by clicking on the + or – sign next to the object.  Another artifact represented a SimpleType.  A restriction was applied to this artifact which represented an enumeration.  There are also other object types that are represented with a white background.  The properties of a given object can be edited within a dialog box available on a right-click on the object you want the properties of.  Attributes are also represented in the Editor.  Two types of attributes are non-mandatory and forbidden.  Cardinalities are also represented in the Editor.  In the XML Schema Visual Editor, the Grab Scroll is also available.  It can be activated by pressing and holding down the space bar.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_56_13-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_56_13-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:56:13 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_56_13-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_56_13-07_00.mp3" length="397440" type="audio/mpeg"/>
      <itunes:duration>99</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>21</itunes:order>
      <itunes:summary>In order to get started with this demo, and existing XML Schema with JDeveloper 10g was opened.  By default, the xsd extension is the default associated with XML schemas.  When opening the schema, its code can be opened also by flipping to the Source tab at the bottom of the Editor Pane.  When using the XML Schema Visual Editor, several panes of JDeveloper are synchronized.  The Schema Components Palette is on the right of the GUI.  The Schema Property Inspector is below that.  The Structure Pane is to the bottom left of the GUI.  In this demo and in Visual XML Schema Editor, the artifact represents a ComplexType.  Selecting the artifact will possibly display the annotation associated with it, if any.  Selecting it also updates the Structure pane, as well as the Property Inspector.  There was another artifact that represented an Element.  You can tell this by also looking at the Structure Pane.  All subcomponents can be expanded or collapsed by clicking on the + or &#8211; sign next to the object.  Another artifact represented a SimpleType.  A restriction was applied to this artifact which represented an enumeration.  There are also other object types that are represented with a white background.  The properties of a given object can be edited within a dialog box available on a right-click on the object you want the properties of.  Attributes are also represented in the Editor.  Two types of attributes are non-mandatory and forbidden.  Cardinalities are also represented in the Editor.  In the XML Schema Visual Editor, the Grab Scroll is also available.  It can be activated by pressing and holding down the space bar.</itunes:summary>
      <itunes:subtitle>In order to get started with this demo, and existing XML Schema with JDeveloper 10g was opened.  ...</itunes:subtitle>
    </item>
    <item>
      <title>VIEW:  ADF UIX</title>
      <description>
        <![CDATA[This demo shows how easy it is to build an ADF UIX application using Oracle JDeveloper 10g Production.  The necessary business service was already created as well as a simple Struts page flow diagram.  The demo focused on building the view based on ADF UIX technology.  By double-clicking on the Data Page node (/main) in the Struts page flow diagram, the Data Page can be mapped to a specific page.  By default, the page name will the same as the Data Page action node, and depending on technologies selected for the project, there will be a list of available file types.  Alternatively, the Browse button can be used to wire an already existing page to the action.  A Master detail page was created using the Department form and an Employee table.  The titles of the Master and the Detail areas were changed.  By selecting an item in the page, the item’s properties will be displayed in the Property Inspector.  It should be noted that the Structure Window is in sync with the selection.  A Delete button was added so that the user can delete records from the Employee table.  When you drag and drop a delete operation from the Data Control palette, a submit button will be automatically created that will perform the delete action on a specific table.  You can also add a submit button from the component palette.  The button is not wired with a specific operation or action.  By specifying an event, an event result can be sent to the Struts controller that can interpret as an edge out from the Data Page action wired to the page.  ADF UIX contains a set of components that helps with the layout of a page.  In the ADF technology, there is a term called Named Children.. You can look at Named Children as slots where you can add components.  In the visual editor, you can hide and/or show empty slots.  You can also edit the page in the XML code editor and preview the page by clicking on the Preview tab.  One of the great features for building applications with Oracle JDeveloper 10g and ADF UIX is partial page rendering (PPR).  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_49_49-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_49_49-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:49:49 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_49_49-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_49_49-07_00.mp3" length="512128" type="audio/mpeg"/>
      <itunes:duration>127</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>22</itunes:order>
      <itunes:summary>This demo shows how easy it is to build an ADF UIX application using Oracle JDeveloper 10g Production.  The necessary business service was already created as well as a simple Struts page flow diagram.  The demo focused on building the view based on ADF UIX technology.  By double-clicking on the Data Page node (/main) in the Struts page flow diagram, the Data Page can be mapped to a specific page.  By default, the page name will the same as the Data Page action node, and depending on technologies selected for the project, there will be a list of available file types.  Alternatively, the Browse button can be used to wire an already existing page to the action.  A Master detail page was created using the Department form and an Employee table.  The titles of the Master and the Detail areas were changed.  By selecting an item in the page, the item&#8217;s properties will be displayed in the Property Inspector.  It should be noted that the Structure Window is in sync with the selection.  A Delete button was added so that the user can delete records from the Employee table.  When you drag and drop a delete operation from the Data Control palette, a submit button will be automatically created that will perform the delete action on a specific table.  You can also add a submit button from the component palette.  The button is not wired with a specific operation or action.  By specifying an event, an event result can be sent to the Struts controller that can interpret as an edge out from the Data Page action wired to the page.  ADF UIX contains a set of components that helps with the layout of a page.  In the ADF technology, there is a term called Named Children.. You can look at Named Children as slots where you can add components.  In the visual editor, you can hide and/or show empty slots.  You can also edit the page in the XML code editor and preview the page by clicking on the Preview tab.  One of the great features for building applications with Oracle JDeveloper 10g and ADF UIX is partial page rendering (PPR).  </itunes:summary>
      <itunes:subtitle>This demo shows how easy it is to build an ADF UIX application using Oracle JDeveloper 10g Produc...</itunes:subtitle>
    </item>
    <item>
      <title>VIEW: SWING &#8211; ADF JCLIENT </title>
      <description>
        <![CDATA[ADF JClient in Oracle JDeveloper 10g supports declarative development of Rich Client applications using Java Swing.   This demo is an example of how to develop a master/detail JClient application in Oracle JDeveloper 10g using ADF Business Components.  The same development steps are used when building JClient applications for other datasources like TopLink or Enterprise Java Beans.  To create an employ JClient form, you use the context menu that is accessible through the right mouse button.  The Project Technologies Scope determines the entries shown in the New gallery selection.  Starting the application using the ADF JClient Template creates a view specific for building JClient applications.  An Empty JClient Form is a subclass of the Java Swing JFrame class that implements the JClient interface.  Swing components in ADF JClient are bound to Business Services like ADF Business Components by using Data Control Palette.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_45_14-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_45_14-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:45:14 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_45_14-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_45_14-07_00.mp3" length="264320" type="audio/mpeg"/>
      <itunes:duration>65</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>23</itunes:order>
      <itunes:summary>ADF JClient in Oracle JDeveloper 10g supports declarative development of Rich Client applications using Java Swing.   This demo is an example of how to develop a master/detail JClient application in Oracle JDeveloper 10g using ADF Business Components.  The same development steps are used when building JClient applications for other datasources like TopLink or Enterprise Java Beans.  To create an employ JClient form, you use the context menu that is accessible through the right mouse button.  The Project Technologies Scope determines the entries shown in the New gallery selection.  Starting the application using the ADF JClient Template creates a view specific for building JClient applications.  An Empty JClient Form is a subclass of the Java Swing JFrame class that implements the JClient interface.  Swing components in ADF JClient are bound to Business Services like ADF Business Components by using Data Control Palette.</itunes:summary>
      <itunes:subtitle>ADF JClient in Oracle JDeveloper 10g supports declarative development of Rich Client applications...</itunes:subtitle>
    </item>
    <item>
      <title>VIEW:  JSP</title>
      <description>
        <![CDATA[The View: JSP demo began with creating a Business Service data model from existing Web Service in a public UDDI.  All t hat was needed was a pointer to the WSDL.  Classes were automatically generated based on the WSDL.  Then, a Struts page flow diagram was created for the application.  There was a Welcome page to get the parameter, an action to invoke the Web service and another JSP page to show the results.  The next step was to assign the Web service activation to the Struts action.  In this page, the JSP page was edited and a Struts form tag was added that invoked an action.  There are several ways to edit the code.  It can be done from the property inspector or it can be changed directly and the visual editor will be kept in synch.  The parameters of the Struts action must be set.  Getting the results of a Web service in the JSP page is a simple drag-and-drop operation.  The completed application was run on the embedded J2EE container.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_42_21-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_42_21-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:42:21 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_42_21-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_42_21-07_00.mp3" length="231552" type="audio/mpeg"/>
      <itunes:duration>57</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>24</itunes:order>
      <itunes:summary>The View: JSP demo began with creating a Business Service data model from existing Web Service in a public UDDI.  All t hat was needed was a pointer to the WSDL.  Classes were automatically generated based on the WSDL.  Then, a Struts page flow diagram was created for the application.  There was a Welcome page to get the parameter, an action to invoke the Web service and another JSP page to show the results.  The next step was to assign the Web service activation to the Struts action.  In this page, the JSP page was edited and a Struts form tag was added that invoked an action.  There are several ways to edit the code.  It can be done from the property inspector or it can be changed directly and the visual editor will be kept in synch.  The parameters of the Struts action must be set.  Getting the results of a Web service in the JSP page is a simple drag-and-drop operation.  The completed application was run on the embedded J2EE container.  </itunes:summary>
      <itunes:subtitle>The View: JSP demo began with creating a Business Service data model from existing Web Service in...</itunes:subtitle>
    </item>
    <item>
      <title>CONTROLLER:  STRUTS</title>
      <description>
        <![CDATA[This demo provided an overview of the Apache Struts Page Flow editor in Oracle JDeveloper 10g.  The Struts page flow can be opened by editing the struts-config.xmi file directly or by using the Open Struts Page Flow context menu option on any project with the Struts technology scope enabled.  The Page Flow Diagram provides a visual way of editing and documenting your page flow.  Actions, Page Forward Actions and Data-bound pages are all represented as shapes on the diagram.  Action Forwards, defined in the Struts XML are show as solid lines linking the Action shapes.  They are labeled with the name of the Forward.  Explicit links between pages or between pages and Actions.  The diagram provides various tools to help with the layout of the flow, such as snap to grid and alignment modes.  Additionally, the developer can customize the colors and fonts used and add annotations to the diagram.  Source view gives you access to the underlying Struts XML configuration file.  The XML view is fully validated and synchronized with the diagram view.  You are able to edit the Struts definition in either mode.  As well as the diagram and XML views, the JDeveloper property inspector can be used to edit the Struts metadata.  Values can be directly edited in the property inspector, which is synchronized with the underlying XML.  The Structure Pane provides an alternative view on the configuration’s structure and provides a useful way of navigating to some of the non-visual Struts elements.  You can also create new Struts elements from the Structure Pane.  Visual elements can be created directly in the diagram.  The diagram can be used as an application workbench, allowing drill-down into code or the visual page editor as appropriate for t he node type.  You can also create a form bean as needed.  In the Create Struts Action dialog box, all of the common super classes are listed for convenience.  The Page Flow editing in JDeveloper 10g provides the Struts developer with a highly intuitive authoring environment combined with the flexibility to edit the Struts XML directly if required.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_39_00-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_39_00-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:39:00 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_39_00-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_39_00-07_00.mp3" length="510080" type="audio/mpeg"/>
      <itunes:duration>127</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>25</itunes:order>
      <itunes:summary>This demo provided an overview of the Apache Struts Page Flow editor in Oracle JDeveloper 10g.  The Struts page flow can be opened by editing the struts-config.xmi file directly or by using the Open Struts Page Flow context menu option on any project with the Struts technology scope enabled.  The Page Flow Diagram provides a visual way of editing and documenting your page flow.  Actions, Page Forward Actions and Data-bound pages are all represented as shapes on the diagram.  Action Forwards, defined in the Struts XML are show as solid lines linking the Action shapes.  They are labeled with the name of the Forward.  Explicit links between pages or between pages and Actions.  The diagram provides various tools to help with the layout of the flow, such as snap to grid and alignment modes.  Additionally, the developer can customize the colors and fonts used and add annotations to the diagram.  Source view gives you access to the underlying Struts XML configuration file.  The XML view is fully validated and synchronized with the diagram view.  You are able to edit the Struts definition in either mode.  As well as the diagram and XML views, the JDeveloper property inspector can be used to edit the Struts metadata.  Values can be directly edited in the property inspector, which is synchronized with the underlying XML.  The Structure Pane provides an alternative view on the configuration&#8217;s structure and provides a useful way of navigating to some of the non-visual Struts elements.  You can also create new Struts elements from the Structure Pane.  Visual elements can be created directly in the diagram.  The diagram can be used as an application workbench, allowing drill-down into code or the visual page editor as appropriate for t he node type.  You can also create a form bean as needed.  In the Create Struts Action dialog box, all of the common super classes are listed for convenience.  The Page Flow editing in JDeveloper 10g provides the Struts developer with a highly intuitive authoring environment combined with the flexibility to edit the Struts XML directly if required.</itunes:summary>
      <itunes:subtitle>This demo provided an overview of the Apache Struts Page Flow editor in Oracle JDeveloper 10g.  T...</itunes:subtitle>
    </item>
    <item>
      <title>MODEL:  ADF BUSINESS COMPONENTS</title>
      <description>
        <![CDATA[When modeling ADF Business Components, a database connection is needed.  The connection is established via the Create Database Connection Wizard.  The wizard prompts for the username, password, and role.  There is also a checkbox for Deploy Password.  After this information is supplied, you can complete the wizard by testing the connection to see if the information that was specified successfully established a connection.  Once the database connection is established, you open the Create Business Components Diagram dialog, in which you define the name and package for a new diagram.  Business Component diagrams should be used to visibly create objects, view objects, application modules, and domains.  Creating business components are based on existing tables in the database.  Once a Business Component has been created, it can be tested using a simple Swing based tester.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_34_33-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_34_33-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:34:33 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_34_33-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_34_33-07_00.mp3" length="204928" type="audio/mpeg"/>
      <itunes:duration>51</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>26</itunes:order>
      <itunes:summary>When modeling ADF Business Components, a database connection is needed.  The connection is established via the Create Database Connection Wizard.  The wizard prompts for the username, password, and role.  There is also a checkbox for Deploy Password.  After this information is supplied, you can complete the wizard by testing the connection to see if the information that was specified successfully established a connection.  Once the database connection is established, you open the Create Business Components Diagram dialog, in which you define the name and package for a new diagram.  Business Component diagrams should be used to visibly create objects, view objects, application modules, and domains.  Creating business components are based on existing tables in the database.  Once a Business Component has been created, it can be tested using a simple Swing based tester.</itunes:summary>
      <itunes:subtitle>When modeling ADF Business Components, a database connection is needed.  The connection is establ...</itunes:subtitle>
    </item>
    <item>
      <title>MODEL:  TOPLINK</title>
      <description>
        <![CDATA[In the demo for Model: TopLink, a new Java class diagram was made for the sample HR application.  The new Java class diagram was created by right-clicking on Model under Applications.  Then, from the New Gallery dialog box, Diagram was selected, then Java Class Diagram was selected.  Afterwards, a Create Database Diagram dialog box appeared in which you define the name and the package for a new diagram.  JDeveloper automatically reverse-engineered the TopLink mappings from a Java class diagram.  However, the TopLink mapping editor also supports forward engineering and meet-in-the-middle use cases.  During the process, JDeveloper adds tables to the diagram and creates all necessary relationships.  JDeveloper created the .java class files for the tables that were used in the demo and added them to the application model.  The TopLink Mappings editor was opened and the TopLink mappings that were created by JDeveloper were reviewed.  In the Structure window, the TopLink Mappings elements can be expanded and the TopLink descriptors for each Java class can be reviewed.  JDeveloper created the TopLink descriptors for each class and mapped each attribute.  The TopLink Mapping editor also allows you to configure your deployment information and sequencing information.  You can also configure TopLink’s other runtime defaults.  When you select a TopLink descriptor, the Mapping editor displays the descriptor’s information.  You can also define custom queries and query keys for each descriptor.  In addition, all of TopLink’s advanced properties are available.  The Mapping editor also provides a Mapping Report that will identify any problems in your model.  When creating deployment descriptors, JDeveloper compiles the source, verifies the mappings, and generates the deployment descriptor.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_32_17-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_32_17-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:32:17 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_32_17-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_32_17-07_00.mp3" length="424064" type="audio/mpeg"/>
      <itunes:duration>105</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>27</itunes:order>
      <itunes:summary>In the demo for Model: TopLink, a new Java class diagram was made for the sample HR application.  The new Java class diagram was created by right-clicking on Model under Applications.  Then, from the New Gallery dialog box, Diagram was selected, then Java Class Diagram was selected.  Afterwards, a Create Database Diagram dialog box appeared in which you define the name and the package for a new diagram.  JDeveloper automatically reverse-engineered the TopLink mappings from a Java class diagram.  However, the TopLink mapping editor also supports forward engineering and meet-in-the-middle use cases.  During the process, JDeveloper adds tables to the diagram and creates all necessary relationships.  JDeveloper created the .java class files for the tables that were used in the demo and added them to the application model.  The TopLink Mappings editor was opened and the TopLink mappings that were created by JDeveloper were reviewed.  In the Structure window, the TopLink Mappings elements can be expanded and the TopLink descriptors for each Java class can be reviewed.  JDeveloper created the TopLink descriptors for each class and mapped each attribute.  The TopLink Mapping editor also allows you to configure your deployment information and sequencing information.  You can also configure TopLink&#8217;s other runtime defaults.  When you select a TopLink descriptor, the Mapping editor displays the descriptor&#8217;s information.  You can also define custom queries and query keys for each descriptor.  In addition, all of TopLink&#8217;s advanced properties are available.  The Mapping editor also provides a Mapping Report that will identify any problems in your model.  When creating deployment descriptors, JDeveloper compiles the source, verifies the mappings, and generates the deployment descriptor.</itunes:summary>
      <itunes:subtitle>In the demo for Model: TopLink, a new Java class diagram was made for the sample HR application. ...</itunes:subtitle>
    </item>
    <item>
      <title>MODEL:   ENTERPRISE JAVA BEANS DEVELOPMENT</title>
      <description>
        <![CDATA[Oracle JDeveloper 10g is a J2EE development environment with end-to-end support for developing, debugging, and deploying J2EE applications and Web services.  This demo shows the user how to build business services with Enterprise Java Beans using Oracle JDeveloper 10g.  A new application workspace is created that will use JSP Struts and the EJB application template.  The application template is configured for building a data-bound web application.  It consists of one project for the view and controller components (JSP and Struts), and another project for the data model (EJB).  In the demo, the JSP, Struts, EJB application template created an application with two projects-Model and View Controller.  The EJB Modeler enables modeling session, entity, and message driven beans.  Users can model session beans, add properties and business methods which are synchronized with the source files.  Users can model entity beans and forward engineer them as database tables or reverse engineer database tables as Container Managed Persistence (CMP) entity beans with a simple drag-and-drop action.  Foreign key relationships in the database are also reverse engineered as Container Managed Relationships (CMR).  In the demo, a session bean was created which acted as a façade for the entity beans for two tables (Departments and Employees).  Using the EJB Modeler, users can model the relationships between entity beans or references between EJBs.  Adding a reference between EJBs automatically synchronize the deployment descriptor by generating the appropriate tags along with the lookup code in the bean class.  JDeveloper provides an easy mechanism to generate Data Transfer Object design patter for CMP Entity beans.  The EJB Module Editor provides a common user interface for editing all the EJBs.  The EJB Module Editor lets developers easily make changes to different types of bean properties such as security roles, method permissions, and container transactions in the deployment descriptor.  All modifications made in the EJB Module Editor are synchronized with model, source, and deployment descriptor.  The EJB verifier provides an easy way to detect deploy-time errors.  It also validates against the Document Type Definition (DTD) and verifies the EJB classes for inconsistencies.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_28_21-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_28_21-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:28:21 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_28_21-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_28_21-07_00.mp3" length="581760" type="audio/mpeg"/>
      <itunes:duration>145</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>28</itunes:order>
      <itunes:summary>Oracle JDeveloper 10g is a J2EE development environment with end-to-end support for developing, debugging, and deploying J2EE applications and Web services.  This demo shows the user how to build business services with Enterprise Java Beans using Oracle JDeveloper 10g.  A new application workspace is created that will use JSP Struts and the EJB application template.  The application template is configured for building a data-bound web application.  It consists of one project for the view and controller components (JSP and Struts), and another project for the data model (EJB).  In the demo, the JSP, Struts, EJB application template created an application with two projects-Model and View Controller.  The EJB Modeler enables modeling session, entity, and message driven beans.  Users can model session beans, add properties and business methods which are synchronized with the source files.  Users can model entity beans and forward engineer them as database tables or reverse engineer database tables as Container Managed Persistence (CMP) entity beans with a simple drag-and-drop action.  Foreign key relationships in the database are also reverse engineered as Container Managed Relationships (CMR).  In the demo, a session bean was created which acted as a fa&#231;ade for the entity beans for two tables (Departments and Employees).  Using the EJB Modeler, users can model the relationships between entity beans or references between EJBs.  Adding a reference between EJBs automatically synchronize the deployment descriptor by generating the appropriate tags along with the lookup code in the bean class.  JDeveloper provides an easy mechanism to generate Data Transfer Object design patter for CMP Entity beans.  The EJB Module Editor provides a common user interface for editing all the EJBs.  The EJB Module Editor lets developers easily make changes to different types of bean properties such as security roles, method permissions, and container transactions in the deployment descriptor.  All modifications made in the EJB Module Editor are synchronized with model, source, and deployment descriptor.  The EJB verifier provides an easy way to detect deploy-time errors.  It also validates against the Document Type Definition (DTD) and verifies the EJB classes for inconsistencies.</itunes:summary>
      <itunes:subtitle>Oracle JDeveloper 10g is a J2EE development environment with end-to-end support for developing, d...</itunes:subtitle>
    </item>
    <item>
      <title>MODEL:  WEB SERVICES</title>
      <description>
        <![CDATA[This demo illustrates how to create a Data Control from a web service and use it in a Struts Controlled JSP application.  A live connection to a UDDI registry of a partner company is shown.  It contains a number of web services.  The WSDLL file of the service can be viewed.  When looking at the WSDL you can see that it has one operation that takes a String parameter.  A Data Control for this web service can be created using its context menu.  The required files are generated into a selected project and the Data Control is displayed in the Palette.  Now, the data control can be used in a Struts Page Flow.  The first page in the page flow is a JSP to capture some data in a form.  After inserting another page, the Data Page is bound to a Struts action.  The JSP page can be edited.  A Struts HTML form should be added to be aware of the struts actions.  Afterwards, a link and a text field should be added to the form.  The Property Inspector can be used to add properties.  At this point, the diagram can be refreshed to display the link.  After defining the JSP page, you can display the result returned by the web service on the page.    The Editor can be used to add style and content to the page. The page flow can be tested using the embedded OC4J and the web service should return the expected greeting.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_23_02-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_23_02-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:23:02 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_23_02-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_23_02-07_00.mp3" length="327808" type="audio/mpeg"/>
      <itunes:duration>81</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>29</itunes:order>
      <itunes:summary>This demo illustrates how to create a Data Control from a web service and use it in a Struts Controlled JSP application.  A live connection to a UDDI registry of a partner company is shown.  It contains a number of web services.  The WSDLL file of the service can be viewed.  When looking at the WSDL you can see that it has one operation that takes a String parameter.  A Data Control for this web service can be created using its context menu.  The required files are generated into a selected project and the Data Control is displayed in the Palette.  Now, the data control can be used in a Struts Page Flow.  The first page in the page flow is a JSP to capture some data in a form.  After inserting another page, the Data Page is bound to a Struts action.  The JSP page can be edited.  A Struts HTML form should be added to be aware of the struts actions.  Afterwards, a link and a text field should be added to the form.  The Property Inspector can be used to add properties.  At this point, the diagram can be refreshed to display the link.  After defining the JSP page, you can display the result returned by the web service on the page.    The Editor can be used to add style and content to the page. The page flow can be tested using the embedded OC4J and the web service should return the expected greeting.</itunes:summary>
      <itunes:subtitle>This demo illustrates how to create a Data Control from a web service and use it in a Struts Cont...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE ADF OVERVIEW</title>
      <description>
        <![CDATA[Oracle JDeveloper comes with a complete J2EE Framework:  Oracle ADF.   Oracle ADF provides productivity with choice when developing a J2EE application.  Oracle ADF is a comprehensive productivity layer for J2EE developers.  It simplifies building applications as a set of business services with Web, Wireless, and Rich Client Interfaces.  It accelerates development with ready-to-use J2EE Design Pattern implementations and metadata-driven components that you’d otherwise have to code, test, and debug by hand.  Since its implementation is based on standards and its features embody years of experience from Oracle’s own business application developers, your ADF powered applications are high performance, well architected, and portable.  Oracle ADF provides time-saving functionality in all four architectural layers of your J2EE business applications:  The key features of Oracle ADF are (1) Business Services- The ADF Business Components technology provides declarative building blocks you can use to implement scalable business services, data access objects, and business objects that enforce business rules and handle database persistence, (2) Model: The ADF Model layer provides consistent, declarative data-binding against multiple backend technologies accommodating business services implemented as ADF Application Modules, custom JavaBeans, EJBs, and Web services, (3)View: The ADF UIX technology provides declarative page definition and a rich UI component set for HTML and wireless UIs, complementing ADFs support for JSP pages and JSP tag libraries like JSTL, Jakarta Struts, ADF DataTags, and others. The ADF JClient layer dovetails with Swing to simplify building sophisticated rich client UIs. As highlighted in the ADF UIX Roadmap, in the future the ADF UIX technology will change to use the standard JavaServer Faces (JSF) APIs, and the ADF UIX components will evolve to become the ADF Faces components. An early adopter release of ADF Faces is available for download on OTN, and (4) Controller: Integrated support for Apache/Jakarta Struts allows data binding and business services to work seamlessly with this popular controller-layer framework. ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_19_56-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_19_56-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:19:56 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_19_56-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_19_56-07_00.mp3" length="577664" type="audio/mpeg"/>
      <itunes:duration>144</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>30</itunes:order>
      <itunes:summary>Oracle JDeveloper comes with a complete J2EE Framework:  Oracle ADF.   Oracle ADF provides productivity with choice when developing a J2EE application.  Oracle ADF is a comprehensive productivity layer for J2EE developers.  It simplifies building applications as a set of business services with Web, Wireless, and Rich Client Interfaces.  It accelerates development with ready-to-use J2EE Design Pattern implementations and metadata-driven components that you&#8217;d otherwise have to code, test, and debug by hand.  Since its implementation is based on standards and its features embody years of experience from Oracle&#8217;s own business application developers, your ADF powered applications are high performance, well architected, and portable.  Oracle ADF provides time-saving functionality in all four architectural layers of your J2EE business applications:  The key features of Oracle ADF are (1) Business Services- The ADF Business Components technology provides declarative building blocks you can use to implement scalable business services, data access objects, and business objects that enforce business rules and handle database persistence, (2) Model: The ADF Model layer provides consistent, declarative data-binding against multiple backend technologies accommodating business services implemented as ADF Application Modules, custom JavaBeans, EJBs, and Web services, (3)View: The ADF UIX technology provides declarative page definition and a rich UI component set for HTML and wireless UIs, complementing ADFs support for JSP pages and JSP tag libraries like JSTL, Jakarta Struts, ADF DataTags, and others. The ADF JClient layer dovetails with Swing to simplify building sophisticated rich client UIs. As highlighted in the ADF UIX Roadmap, in the future the ADF UIX technology will change to use the standard JavaServer Faces (JSF) APIs, and the ADF UIX components will evolve to become the ADF Faces components. An early adopter release of ADF Faces is available for download on OTN, and (4) Controller: Integrated support for Apache/Jakarta Struts allows data binding and business services to work seamlessly with this popular controller-layer framework. </itunes:summary>
      <itunes:subtitle>Oracle JDeveloper comes with a complete J2EE Framework:  Oracle ADF.   Oracle ADF provides produc...</itunes:subtitle>
    </item>
    <item>
      <title>GETTING TO KNOW THE IDE</title>
      <description>
        <![CDATA[This demo introduces you to JDevelopers Integrated Development Environment, commonly known as the IDE.  When you open JDeveloper for the first time, you encounter a welcome screen with three windows.  The large window which displays the welcome information is known as the Visual Editor or the Code Editor.  The top left window is the Application Navigator and the bottom left window is the Structure window.  You get started with JDeveloper by first creating a workspace in which to store your work.  To create a workspace, you select ‘Applications’ in the Application Navigator and choose File|New.  When creating a new workspace, ensure that Add A New Empty Project Box is checked.  You can accept the default name or rename your project.  The workspace and project names appear in the Navigator.  A project is a sub-division of a workspace and helps you organize your work within the workspace.  As you work with JDeveloper, you build up a collection of workspaces and projects within them.  The Application Navigator allows you to view your workspaces and projects and their contents in a hierarchical fashion.  The names of the workspaces and projects are italicized until they are saved.  Once you have a workspace and a project, you can build an application.  To create a new JSP project, right click on the new project.  The New Gallery dialog box appears.  (A JSP is an HTML page with embedded Java code).  Expand the Web Tier node and choose JSP page.  The empty Hello.jsp page displays in the visual editor.  It also appears under the new project node in the Navigator.  Additionally, the Structure window is synchronized with the other windows.  You will see that two new windows have opened on the right, the Component Palette and the Property Inspector.  The text on the page can be formatted with the tool bar.  Style sheets and HTML components can be added to the page.  The source code can be viewed.  There is also a split view where you can see the design and source views simultaneously.  All windows are synchronized.  JDeveloper has a code inset feature that offering suggestions in the appropriate context.  To run the page to see how it will look in a browser, select Run from the context menu.  Many applications require connections to other devices and machines so you may have to run the Database Connection Wizard.  When this wizard is run, you have to supply the Driver, Host Name, JDBC Port, and SID.  The database connection can be tested.   If successfully, the new database connection will appear in the Navigator.  ]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_13_49-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_13_49-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:13:49 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_13_49-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_13_49-07_00.mp3" length="589952" type="audio/mpeg"/>
      <itunes:duration>146</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>31</itunes:order>
      <itunes:summary>This demo introduces you to JDevelopers Integrated Development Environment, commonly known as the IDE.  When you open JDeveloper for the first time, you encounter a welcome screen with three windows.  The large window which displays the welcome information is known as the Visual Editor or the Code Editor.  The top left window is the Application Navigator and the bottom left window is the Structure window.  You get started with JDeveloper by first creating a workspace in which to store your work.  To create a workspace, you select &#8216;Applications&#8217; in the Application Navigator and choose File|New.  When creating a new workspace, ensure that Add A New Empty Project Box is checked.  You can accept the default name or rename your project.  The workspace and project names appear in the Navigator.  A project is a sub-division of a workspace and helps you organize your work within the workspace.  As you work with JDeveloper, you build up a collection of workspaces and projects within them.  The Application Navigator allows you to view your workspaces and projects and their contents in a hierarchical fashion.  The names of the workspaces and projects are italicized until they are saved.  Once you have a workspace and a project, you can build an application.  To create a new JSP project, right click on the new project.  The New Gallery dialog box appears.  (A JSP is an HTML page with embedded Java code).  Expand the Web Tier node and choose JSP page.  The empty Hello.jsp page displays in the visual editor.  It also appears under the new project node in the Navigator.  Additionally, the Structure window is synchronized with the other windows.  You will see that two new windows have opened on the right, the Component Palette and the Property Inspector.  The text on the page can be formatted with the tool bar.  Style sheets and HTML components can be added to the page.  The source code can be viewed.  There is also a split view where you can see the design and source views simultaneously.  All windows are synchronized.  JDeveloper has a code inset feature that offering suggestions in the appropriate context.  To run the page to see how it will look in a browser, select Run from the context menu.  Many applications require connections to other devices and machines so you may have to run the Database Connection Wizard.  When this wizard is run, you have to supply the Driver, Host Name, JDBC Port, and SID.  The database connection can be tested.   If successfully, the new database connection will appear in the Navigator.  </itunes:summary>
      <itunes:subtitle>This demo introduces you to JDevelopers Integrated Development Environment, commonly known as the...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE ADF QUICK TOUR</title>
      <description>
        <![CDATA[Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications and Web services using the latest industry standards for Java, XML, and SQL. Oracle JDeveloper supports the complete development life cycle with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.  A visual and declarative approach and the innovative Oracle Application Development Framework (Oracle ADF) work together to simplify application development and reduce mundane coding tasks, offering developers unparalleled productivity and their choice of technology stacks.  JDeveloper supports the complete development life cycle, with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications, either from scratch or using the Oracle Application Development Framework (Oracle ADF). Additionally, software configuration management support provides a useful infrastructure in which to develop applications in a team environment. Whatever implementation you choose, JDeveloper offers all the productivity tools you need to get the job done: UML modelers, visual editors, wizards, dialogs, and code editors.  The key features of JDeveloper include enhanced Java coding capabilities, along with a more visual and declarative development environment, offering the ease and productivity previously associated with 4GL tools in an open and standard Java IDE.  With Oracle ADF and Oracle JDevelope 10g, you can develop user interfaces for web applications, rich client applications, or wireless applications, all using the same set of Business Services.  JDeveloper also includes a visual Page Flow diagrammer for visually constructing the page flow of Struts applications.  The JDeveloper environment can be highly customized to fit user requirements.  You can disable features that won’t be used.  You can also develop your own extensions to supplement the JDeveloper feature set.   Some of the key features of JDeveloper are J2EE and Web Services Development, Productive XML Coding Environment, Database Development, UML Modeling, and Oracle Application Development Framework (ADF).  Some of the new and updated features are Visual Editor, Application Navigator, Technology Scopes, Window Management, Data Binding Palette, Page Flow Diagram, Database Modeler, Use Case Modeler, and Model Driven Architecture Support.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_08_57-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_08_57-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:08:57 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_08_57-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_08_57-07_00.mp3" length="315520" type="audio/mpeg"/>
      <itunes:duration>78</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>32</itunes:order>
      <itunes:summary>Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications and Web services using the latest industry standards for Java, XML, and SQL. Oracle JDeveloper supports the complete development life cycle with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.  A visual and declarative approach and the innovative Oracle Application Development Framework (Oracle ADF) work together to simplify application development and reduce mundane coding tasks, offering developers unparalleled productivity and their choice of technology stacks.  JDeveloper supports the complete development life cycle, with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications, either from scratch or using the Oracle Application Development Framework (Oracle ADF). Additionally, software configuration management support provides a useful infrastructure in which to develop applications in a team environment. Whatever implementation you choose, JDeveloper offers all the productivity tools you need to get the job done: UML modelers, visual editors, wizards, dialogs, and code editors.  The key features of JDeveloper include enhanced Java coding capabilities, along with a more visual and declarative development environment, offering the ease and productivity previously associated with 4GL tools in an open and standard Java IDE.  With Oracle ADF and Oracle JDevelope 10g, you can develop user interfaces for web applications, rich client applications, or wireless applications, all using the same set of Business Services.  JDeveloper also includes a visual Page Flow diagrammer for visually constructing the page flow of Struts applications.  The JDeveloper environment can be highly customized to fit user requirements.  You can disable features that won&#8217;t be used.  You can also develop your own extensions to supplement the JDeveloper feature set.   Some of the key features of JDeveloper are J2EE and Web Services Development, Productive XML Coding Environment, Database Development, UML Modeling, and Oracle Application Development Framework (ADF).  Some of the new and updated features are Visual Editor, Application Navigator, Technology Scopes, Window Management, Data Binding Palette, Page Flow Diagram, Database Modeler, Use Case Modeler, and Model Driven Architecture Support.</itunes:summary>
      <itunes:subtitle>Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications an...</itunes:subtitle>
    </item>
    <item>
      <title>ORACLE JDEVELOPER 10G QUICK TOUR </title>
      <description>
        <![CDATA[Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications and Web services using the latest industry standards for Java, XML, and SQL. Oracle JDeveloper supports the complete development life cycle with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.  A visual and declarative approach and the innovative Oracle Application Development Framework (Oracle ADF) work together to simplify application development and reduce mundane coding tasks, offering developers unparalleled productivity and their choice of technology stacks.  JDeveloper supports the complete development life cycle, with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications, either from scratch or using the Oracle Application Development Framework (Oracle ADF). Additionally, software configuration management support provides a useful infrastructure in which to develop applications in a team environment. Whatever implementation you choose, JDeveloper offers all the productivity tools you need to get the job done: UML modelers, visual editors, wizards, dialogs, and code editors.  The key features of JDeveloper include enhanced Java coding capabilities, along with a more visual and declarative development environment, offering the ease and productivity previously associated with 4GL tools in an open and standard Java IDE.  With Oracle ADF and Oracle JDevelope 10g, you can develop user interfaces for web applications, rich client applications, or wireless applications, all using the same set of Business Services.  JDeveloper also includes a visual Page Flow diagrammer for visually constructing the page flow of Struts applications.  The JDeveloper environment can be highly customized to fit user requirements.  You can disable features that won’t be used.  You can also develop your own extensions to supplement the JDeveloper feature set.   Some of the key features of JDeveloper are J2EE and Web Services Development, Productive XML Coding Environment, Database Development, UML Modeling, and Oracle Application Development Framework (ADF).  Some of the new and updated features are Visual Editor, Application Navigator, Technology Scopes, Window Management, Data Binding Palette, Page Flow Diagram, Database Modeler, Use Case Modeler, and Model Driven Architecture Support.]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-05-05T09_04_41-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_04_41-07_00</comments>
      <pubDate>Fri, 05 May 2006 16:04:41 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-05-05T09_04_41-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-05-05T09_04_41-07_00.mp3" length="540800" type="audio/mpeg"/>
      <itunes:duration>134</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>33</itunes:order>
      <itunes:summary>Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications and Web services using the latest industry standards for Java, XML, and SQL. Oracle JDeveloper supports the complete development life cycle with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.  A visual and declarative approach and the innovative Oracle Application Development Framework (Oracle ADF) work together to simplify application development and reduce mundane coding tasks, offering developers unparalleled productivity and their choice of technology stacks.  JDeveloper supports the complete development life cycle, with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications, either from scratch or using the Oracle Application Development Framework (Oracle ADF). Additionally, software configuration management support provides a useful infrastructure in which to develop applications in a team environment. Whatever implementation you choose, JDeveloper offers all the productivity tools you need to get the job done: UML modelers, visual editors, wizards, dialogs, and code editors.  The key features of JDeveloper include enhanced Java coding capabilities, along with a more visual and declarative development environment, offering the ease and productivity previously associated with 4GL tools in an open and standard Java IDE.  With Oracle ADF and Oracle JDevelope 10g, you can develop user interfaces for web applications, rich client applications, or wireless applications, all using the same set of Business Services.  JDeveloper also includes a visual Page Flow diagrammer for visually constructing the page flow of Struts applications.  The JDeveloper environment can be highly customized to fit user requirements.  You can disable features that won&#8217;t be used.  You can also develop your own extensions to supplement the JDeveloper feature set.   Some of the key features of JDeveloper are J2EE and Web Services Development, Productive XML Coding Environment, Database Development, UML Modeling, and Oracle Application Development Framework (ADF).  Some of the new and updated features are Visual Editor, Application Navigator, Technology Scopes, Window Management, Data Binding Palette, Page Flow Diagram, Database Modeler, Use Case Modeler, and Model Driven Architecture Support.</itunes:summary>
      <itunes:subtitle>Oracle JDeveloper 10g is an Integrated Development Environment (IDE) for building applications an...</itunes:subtitle>
    </item>
    <item>
      <title>HERE'S A LITTLE INFO ABOUT REGGIE WILHELM</title>
      <description>
        <![CDATA[&nbsp;]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-04-29T12_01_00-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-04-29T12_01_00-07_00</comments>
      <pubDate>Sat, 29 Apr 2006 19:01:00 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-04-29T12_01_00-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-04-29T12_01_00-07_00.mp3" length="155776" type="audio/mpeg"/>
      <itunes:duration>38</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>34</itunes:order>
      <itunes:summary>&amp;nbsp;</itunes:summary>
      <itunes:subtitle>&amp;nbsp;</itunes:subtitle>
    </item>
    <item>
      <title>A LITTLE BIT ABOUT ME!</title>
      <description>
        <![CDATA[&nbsp;]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-04-29T11_53_00-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-04-29T11_53_00-07_00</comments>
      <pubDate>Sat, 29 Apr 2006 18:53:00 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-04-29T11_53_00-07_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-04-29T11_53_00-07_00.mp3" length="241792" type="audio/mpeg"/>
      <itunes:duration>60</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>35</itunes:order>
      <itunes:summary>&amp;nbsp;</itunes:summary>
      <itunes:subtitle>&amp;nbsp;</itunes:subtitle>
    </item>
    <item>
      <title>W</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_42_18-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_42_18-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:42:18 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_42_18-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_42_18-08_00.mp3" length="56424" type="audio/mpeg"/>
      <itunes:duration>14</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>36</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>V</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_41_27-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_41_27-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:41:27 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_41_27-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_41_27-08_00.mp3" length="24033" type="audio/mpeg"/>
      <itunes:duration>6</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>37</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>U</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_40_58-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_40_58-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:40:58 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_40_58-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_40_58-08_00.mp3" length="68023" type="audio/mpeg"/>
      <itunes:duration>17</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>38</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>T</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_40_09-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_40_09-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:40:09 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_40_09-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_40_09-08_00.mp3" length="168647" type="audio/mpeg"/>
      <itunes:duration>42</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>39</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>S</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_38_35-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_38_35-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:38:35 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_38_35-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_38_35-08_00.mp3" length="393091" type="audio/mpeg"/>
      <itunes:duration>98</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>40</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>R</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_35_19-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_35_19-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:35:19 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_35_19-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_35_19-08_00.mp3" length="236565" type="audio/mpeg"/>
      <itunes:duration>59</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>41</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>P</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_33_08-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_33_08-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:33:08 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_33_08-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_33_08-08_00.mp3" length="188813" type="audio/mpeg"/>
      <itunes:duration>47</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>42</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>O</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_31_18-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_31_18-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:31:18 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_31_18-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_31_18-08_00.mp3" length="39811" type="audio/mpeg"/>
      <itunes:duration>9</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>43</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>N</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_30_35-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_30_35-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:30:35 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_30_35-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_30_35-08_00.mp3" length="125597" type="audio/mpeg"/>
      <itunes:duration>31</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>44</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>M</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_29_06-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_29_06-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:29:06 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_29_06-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_29_06-08_00.mp3" length="144509" type="audio/mpeg"/>
      <itunes:duration>36</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>45</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>L</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_27_08-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_27_08-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:27:08 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_27_08-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_27_08-08_00.mp3" length="163840" type="audio/mpeg"/>
      <itunes:duration>40</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>46</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>J</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_24_39-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_24_39-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:24:39 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_24_39-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_24_39-08_00.mp3" length="32496" type="audio/mpeg"/>
      <itunes:duration>8</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>47</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>I</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_23_53-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_23_53-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:23:53 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_23_53-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_23_53-08_00.mp3" length="167393" type="audio/mpeg"/>
      <itunes:duration>41</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>48</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>H</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_20_56-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_20_56-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:20:56 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_20_56-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_20_56-08_00.mp3" length="46289" type="audio/mpeg"/>
      <itunes:duration>11</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>49</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>F</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_20_00-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_20_00-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:20:00 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_20_00-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_20_00-08_00.mp3" length="32183" type="audio/mpeg"/>
      <itunes:duration>8</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>50</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>E</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_19_17-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_19_17-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:19:17 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_19_17-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_19_17-08_00.mp3" length="43259" type="audio/mpeg"/>
      <itunes:duration>10</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>51</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>D</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_18_23-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_18_23-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:18:23 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_18_23-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_18_23-08_00.mp3" length="359131" type="audio/mpeg"/>
      <itunes:duration>89</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>52</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>C</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_09_28-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_09_28-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:09:28 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_09_28-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_09_28-08_00.mp3" length="242939" type="audio/mpeg"/>
      <itunes:duration>60</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>53</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>A</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_03_15-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_03_15-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:03:15 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_03_15-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_03_15-08_00.mp3" length="46498" type="audio/mpeg"/>
      <itunes:duration>11</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>54</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>B</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_03_02-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_03_02-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:03:02 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_03_02-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_03_02-08_00.mp3" length="88712" type="audio/mpeg"/>
      <itunes:duration>22</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>55</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
    <item>
      <title>INTRODUCTION</title>
      <description>
        <![CDATA[]]>
      </description>
      <guid isPermaLink="true">https://thiodre26.podomatic.com/entry/2006-01-31T15_02_08-08_00</guid>
      <comments>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_02_08-08_00</comments>
      <pubDate>Tue, 31 Jan 2006 23:02:08 +0000</pubDate>
      <dcterms:modified>2022-04-19</dcterms:modified>
      <dcterms:created>2013-12-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/thiodre26/episodes/2006-01-31T15_02_08-08_00</link>
      <dc:creator>Lorraine Harris</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://thiodre26.podomatic.com/enclosure/2006-01-31T15_02_08-08_00.mp3" length="85786" type="audio/mpeg"/>
      <itunes:duration>21</itunes:duration>
      <itunes:explicit>false</itunes:explicit>
      <itunes:order>56</itunes:order>
      <itunes:summary></itunes:summary>
      <itunes:subtitle></itunes:subtitle>
    </item>
  </channel>
</rss>
