Abstract: A system and method for navigating relationships between beans using filters and container managed relationships are provided. With the system and method, filters are specified in the relationship definition of a deployment descriptor of a bean. The filters generate additional predicates to the WHERE clauses in SQL SELECT statements generated based on the contents of the deployment descriptor. Moreover, these filters may be defined such that method parameters may be passed into the resulting deployed code to thereby make them more flexible. Therefore, with the system and method, rather than defining filters programmatically in methods of a bean's implementation class, filters are defined declaratively in the deployment descriptor of the bean. Since these filters are specified in the deployment descriptor of the bean, they are accessible to clients of the bean through the local interface.

Abstract: A method, an apparatus, and computer instructions for generating service frameworks are provided by aspects of the present invention. One aspect of the present invention provides a system library, which includes strongly typed classes that enterprise applications may use in order to obtain code assist and compile time checking from IDE tools typically used by enterprise application developers. Another aspect of the present invention provides the ability to define platform independent models that enable service use cases in order to determine what basic services are needed by the enterprise application. Yet another aspect of the present invention includes an integrated generator that generates the strongly typed components and skeleton code from the platform independent models by applying best practice pattern usage for the target platform currently used with the system library functions.

Abstract: A method, apparatus, and computer instructions are provided for implementing container managed uses, ownerships, and references in an enterprise JavaBean™ environment. A user may specify a uses, ownership, reference relationships between entity beans and sessions in a deployment descriptor file. When the file is processed, the present embodiment generates methods on the entity beans and allows the container to recognize the relationships, such that the user may access the session beans based on the specified relationships.

Abstract: A method, apparatus, and computer instructions for implementing container managed streams in an enterprise JavaBean™ environment. Uses, ownership, reference relationships between entity beans and sessions are specified in a deployment descriptor file. When an input data stream is received for a batch job, the file is processed and a method is generated on the entity beans, wherein the method allows for creating a container managed ownership entity representing a stream object for the input data stream, associates an entity bean with the stream, and returns the last unprocessed object in the stream to the user. A method may also be generated on the entity beans for creating a stream object for an output data stream, associating an entity bean with the stream, rerouting an object to the stream object, and appending the stream object to the end of the batch job queue.

Abstract: An improved method, apparatus, and computer instructions for creating and running batch jobs in an object oriented environment, such as a J2EE environment. A request to execute a batch job is received. A deployment descriptor file is processed to identify a batch bean to be invoked. This batch job session bean processes the request, parses deployment descriptor file that comprises definitions of relationships between other helper classes, entity and session beans. The identified batch bean is invoked to execute the batch job step in the order described in the deployment descriptor applying checkpoints at intervals specified in the descriptor.

Abstract: View templates for use in generating application content are created by analyzing and categorizing existing application examples to derive reusable abstractions of application artifacts. Example application artifacts or source modules are categorized by role and function. Based on the categorized artifacts, a generalized, abstract view for the role and function is defined. View templates are created for each abstract view and contain static content and dynamic content that varies for each instance of the template. The view templates are stored in a template library for use in a model driven application generator.

Abstract: A method for protecting custom coding an application generation system. An application generator uses a view template to generate content based on a specified application definition. The view template contains one or more custom code blocks. As the application content is generated, custom code blocks are generated and each assigned a unique identifier. The resulting custom code block can be modified by an application developer. When application code is regenerated it first tests the output to determine whether custom code blocks having the generated code block identifier already exist. If matching custom code blocks exist they are not replaced. If they do not exists, the custom code blocks are generated into the content output.

Abstract: A process for developing a software application as a service using an open model drive architecture. The business problem is analyzed to develop an application definition in a first flexible grammar. A number of view templates are accessed using a controller definition that interprets the grammar to transform the application definition into content output. The output content is generated by applying application attributes to dynamic content descriptors.

Abstract: A method for generating application content includes specifying an application definition or model in a flexible grammar, defining a set of templates that define generalized content output forms, and specifying a control definition for transforming the application definition into application content based on the templates. A transformation engine accesses the application definition and performs output generation under the control of the control description.

Abstract: A batch component model is provided within a distributed object environment. The batch component is designed to capture the iterative logic of a batch program as it reads from one or more input streams, invokes operations on other business component functions, and generates output to one or more output streams. Deployment descriptors express declarative policies for the component that will influence how the component is managed including the streams it uses, business components it depends on, how processing costs are accounted for, the resource demands the job will put on the system, and the like. Input streams and output streams are encapsulated in objects that hide the actual source of input and output data so that the component can be redeployed in different execution environments to different physical data sources without requiring the program to be changed. A batch container enforces the deployment policies declared for the batch component.