WO2004053634A2 - Generating java bean code - Google Patents

Generating java bean code Download PDF

Info

Publication number
WO2004053634A2
WO2004053634A2 PCT/US2003/037229 US0337229W WO2004053634A2 WO 2004053634 A2 WO2004053634 A2 WO 2004053634A2 US 0337229 W US0337229 W US 0337229W WO 2004053634 A2 WO2004053634 A2 WO 2004053634A2
Authority
WO
WIPO (PCT)
Prior art keywords
ejb
annotation
class
description
variable
Prior art date
Application number
PCT/US2003/037229
Other languages
French (fr)
Other versions
WO2004053634A3 (en
Inventor
Cedric Beust
Original Assignee
Bea Systems, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bea Systems, Inc. filed Critical Bea Systems, Inc.
Priority to AU2003295747A priority Critical patent/AU2003295747A1/en
Publication of WO2004053634A2 publication Critical patent/WO2004053634A2/en
Publication of WO2004053634A3 publication Critical patent/WO2004053634A3/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Devices For Executing Special Programs (AREA)
  • Cash Registers Or Receiving Machines (AREA)

Abstract

A system and method for generating code for an Enterprise Java Bean comprising generating at least one output based on a description of at least one Enterprise Java Bean, wherein the description is attended by at least one annotation. A system and method for generating an annotated description of an Enterprise Java Bean based on at least one input, wherein the description can be used to generate the at least one input.

Description

SYSTEM AND METHOD FOR GENERATING ENTERPRISE JAVA BEAN CODE
CROSS REFERENCES
The following related documents are hereby incorporated by reference in their entirety: BEAWEBLOGIC SERVER®: ASSEMBLING AND CONFIGURING WEB APPLICATIONS (Release 7.0, June 28, 2002); BEAWEBLOGIC SERVER®: PROGRAMMING WEBLOGIC ENTERPRISE JAVABEANS (Release 7.0, June 28,
2002); BEAWEBLOGIC SERVER®: DEVELOPING WEBLOGIC SERVER APPLICATIONS (Release 7.0, June 28, 2002); BEAWEBLOGIC SERVER®: WEBLOGIC BUILDER ONLINE HELP (Release 7.0, June 28, 2002); BEAWEBLOGIC SERVER®: PROGRAMMING WEBLOGIC XML (Release 7.0, June 28, 2002); BEAWEBLOGIC SERVER® : PROGRAMMING WEBLOGIC WEB SERVICES (Release
7.0, June 28, 2002); BEAWebLogic Server®: Programming WebLogic Enterprise JavaBeans (Release 7.0, June 28, 2002).
COPYRIGHT NOTICE A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
FIELD OF THE DISCLOSURE The present invention disclosure relates to the field of automatic code generation, in particular, automatic generation of Enterprise Java™ Bean source code files from an annotated class definition and the reverse. BACKGROUND
Enterprise Java™ Beans are reusable software components written in the
Java™ programming language. An Enteφrise Java™ Bean (EJB) is typically declared in a number of separate source files which define various aspects of the EJB, such as its class, interfaces and deployment behavior. Each time a modification is made to one EJB source file, the other associated EJB source files must also be modified accordingly. This activity is cumbersome and error prone, since the changes must be manually propagated to different files. What is needed is a way to generate source files for EJB 's with minimal editing and duplication of information.
BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a block diagram of an EJB code generation system in accordance to one embodiment of the invention. Figure 2 is a block diagram of a reverse EJB code generation system in accordance to one embodiment of the invention.
DETAILED DESCRIPTION
The invention is illustrated by way of example and not by way of limitation in the figures of the accompanying drawings in which like references indicate similar elements. It should be noted that references to "an" or "one" embodiment in this disclosure are not necessarily to the same embodiment, and such references mean at least one.
In one embodiment, instead of having to edit and maintain several EJB files for each EJB (e.g., the bean class, remote and home classes, deployment descriptors, etc.), editing is limited to a single file that contains an annotated description of one or more EJB class definitions. EJB's are declared in the
Java™ programming language. The Java™ programming language and run-time environment are available from Sun Microsystems, Inc., of Palo Alto, California. The annotated description file is processed in accordance to one embodiment and the EJB files required for deployment on a server are automatically generated. Annotations are directives that contain information needed to create an EJB's source files. In one embodiment, amiotations are interspersed between Java™ source code statements. In another embodiment, annotations are embedded in Java™ comments. In yet another embodiment, an annotation is a Javadoc tag. Javadoc is the tool for generating source code documentation in hypertext markup language ("HTML") format from tags embedded in Java™ source code comments. Javadoc is available from Sun Microsystems, Inc. In another embodiment, annotations are provided separately from the description of one or more EJB classes. For example, annotations can be provided in a graphical user interface, a separate file, or created dynamically based on run-time properties a user has associated with an EJB. hi one embodiment, by way of example, annotations can take the form:
@ejbgen-nα e [attribute^ expression]] ... attribute[= expression]], where items in square brackets are optional arguments. Name can be the type of annotation and the optional attribute=expression list can be comprised of one or more attribute-expression pairs. In one embodiment, attribute is the name of a required or optional parameter associated with an annotation and the optional expression can be, for example, an infix, postfix or prefix expression that evaluates to a constant (e.g., a number or an alpha-numeric string), hi another embodiment, an expression's operators can be arithmetic, logical and string-based. For example, the following Java™ code segment has a comment block that contains three annotations:
* *
* ©ejbgen: c p-field column = acct_id * @ejbgen:primkey-field
* ©ejbgen:remote-method transaction-attribute = Required
*/ abstract public String getAccountld O ;
Conventionally, an EJB's abstract accessor methods define container- managed persistence ("CMP") data fields of the same name. For example, in the code segment above, assuming the accessor method getAccountId() was an EJB method, a corresponding data field called "accountld" would be defined upon deployment of the EJB. In one embodiment, the annotation "@ejbgen:cmp-field" specifies that the Accountld CMP field will be stored in column named "acct_id" of a database upon deployment of the EJB. The annotation "@ejbgen:primkey- field" indicates that Accountld will be a primary key in the database. Finally, the annotation "@ejbgen:remote-method" specifies that transaction isolation is required for the method getAccountId(). All three annotations can be considered method annotations since they come before the declaration of a method.
Figure 1 is a block diagram in accordance to one embodiment of the invention. An annotated description 1 is processed by analyzer 2. Annotated description 1 can include one or more EJB definitions. In one embodiment, annotated description 1 can reside in a computer file, hi another embodiment, annotated description 1 can reside in a computer memory. In yet a further embodiment, annotated description 1 can be transmitted via a computer network (not shown) to analyzer 2. Analyzer 2 employs parser 4 to divide the Java™ source text in annotated description 1 into discrete units and extract annotations therefrom. Analyzer 2 may perform preprocessing of annotated description 1 before making use of parser 4. hi one embodiment, parser 4 can exploit the doclet application programming interface available in Javadoc. The Javadoc doclet interface provides programmatic access to a parsed representation of a Java™ source file. In one embodiment, parser 4 can process the entire annotated description 1 at once. In another embodiment, parser 4 can be employed repeatedly by analyzer 2 to incrementally process annotated description 1. Each annotation is verified by comparing what was found in the annotated description 1 with a formal definition in annotation library 5. In one embodiment, by way of example, annotation library 5 can be a database that includes the definition of each annotation (e.g., its required and optional parameters, permissible values, etc.). In another embodiment, annotation library 5 can be implemented as a cache, tree or any other suitable data structure without departing from the spirit or scope of the present disclosure.
If the annotation and its arguments are proper, analyzer 2 evaluates any attribute-expression arguments provided. The can be done during the validation of each annotation, or in another embodiment, after all annotations have been verified. Values for variable names that occur in expressions are retrieved from variable library 6. In one embodiment, variable library 6 can be implemented in a similar fashion to annotation library 5. In a further embodiment, variable names can be constructed dynamically from expressions using string concatenation operators. In one embodiment, each attribute-expression is evaluated, comparing the value of the expression to permissible values allowed for a given attribute as dictated by annotation library 5. If an expression's value is out of range or erroneous, an error can be declared. In another embodiment, a suitable default value can be provided in place of the errant expression. The form of expressions can be, for example, infix, postfix and prefix. Means for parsing and evaluating such expressions are well known in the art. Based on the parsed annotations, code generator 3 emits the classes or files 7 necessary to deploy the EJB(s) described in annotated description 1.
In one embodiment, annotations can be described in terms of their attributes, their scope (e.g., class or method) and the type of EJB they are applicable to (e.g., message, stateless session, stateful session, entity, etc.). Annotations having class scope come before a class declaration and annotations having method scope come before a method declaration. Annotations can also be adjacent to or associated with other Java™ elements such as fields or variables. In a further embodiment, and byway of illustration, annotations can be defined as in the following tables . The Annotation/Attribute column contains the annotation name in the first row of each table and any associated attribute names in the subsequent rows. The Description column contains a description of the annotation or attribute. The For column indicates whether the annotation is applicable to a class or a method. Finally, the EJB Type column indicates the type of EJB the annotation is applicable to (e.g., session, message, entity, etc.). It will be apparent to those skilled in the art that many such annotations are possible and therefore this illustration is illustrative and should not be construed to be limiting in any respect.
EJB
Annotation/ Attribute Description For Type
@ejbgen: automatic- Automatically generate database keys for new Class Entity key- entity objects. generation cache-size The size of the key cache. (Required) Name The name of the key generator. (Required) Type The type of the key generator. (Required)
EJB
Annotation/ Attribute Description For Type
@ejbgen:cmp-fιeld Specifies a container-managed field. Method Entity
Column The column where this CMP field will be mapped. (Required) column-type (OracleClob|OracleBlob) The type of this column. group-names The names of the groups this field belongs to, separated by commas. ordering-number (0..n) The number where this field must appear in signatures and constructors. For this ordering to work, all CMR and CMP fields must have this attribute to a distinct numeric value. EJB
Annotation/Attribute Description For Tyje
@ejbgen: c r-field Specifies a container-managed relationship. Method Entity group-names The names of the groups this field belongs to separated by commas. ordering-number (0..n) The number where this field must appear in signatures and constructors. For this ordering to work, all CMR and CMP fields must have this attribute to a distinct numeric value.
EJB
Annotation/Attribute Description For Type
@ejbgen:create- Automatically create required database tables. Class Entity default- rdbms-tables
EJB
Annotation/ Attribute Description For Type
@ejbgen: ejb-client-j ar Specify the name of the jar file to generate. Class All file-name The name of the client jar to generate. If more than one EJB's have this tag, only one of the specified j r files will be included in the deployment descriptor. (Required)
For EJB
Annotation/Attribute Description Type
@ejbgen: ejb-local-ref Declare a reference to an EJB that is in the Class All same container and EJB JAR file.
Home Logal class of the bean. jndi-name The JNDI name of the reference.
Link Link of the bean.
Local Home class of the bean.
Name Name of the reference.
Type (Entity|Session)
EJB
Annotation/Attribute Description For ΪΪEe
@ejbgen:ejb-ref Define a reference to another EJB within the Class All
Java™ Naming and Directory Interface
("JNDI") Environment Naming Context
("ENC").
Home Home class of the bean. jndi-name The JNDI name of the reference. Link Link of the bean. Name Name of the reference. Remote Remote class of the bean. Type (Entity|Session)
EJB
Annotation/Attribute Description For ϊϊEe
@ejbgen: entity Declare an entity bean. Class Entity ejb-name The name of this Entity bean. (Required) prim-key-class The Java™ class of the primary key. In case of a compound primary key, this class will be generated. (Required)
Sometimes, a simple (e.g. java.lang.String) primary key class will not be enough to identify an EJB uniquely. In such a case, a primary key is needed. A primary key is a custom Java class containing several fields. All of the fields together identify an EJB uniquely.
There are certain constraints associated with the compound primary key class (e.g it must be Serializable, implement hashCodeQ, equals(), etc.).
A compound primary key class can contain fields that form a subset of the CMP fields of the EJB. In order to define a compound primary key class:
Annotate each CMP field that should be part of the primary key class with @primkey-field. abstract-schema-name The abstract schema name for this EJB. If not specified, the ejb-name value will be used. cache-between- (True|False) Whether to cache the persistent transactions data of an entity bean across (between) transactions. check-exists-on- (True|False) Whether the container checks for method the existence of a bean for each method call. concurrency-strategy (Read Only|Exclusive|Database) Defines the concurrency strategy for this bean. data-source-name The name of the data source (as it was declared in config.xml). database-type The type of the database. db-is-shared (True|False) Whether the database is shared. default-transaction The transaction attribute to be applied to all methods that do not have a more specific transaction attribute setting. delay-database-insert- (ejb Create|ejbPost Create) until delay-updates-until- (True|False) Whether updates will be sent after end-of-tx the transaction has committed. enable-dynamic- (True|False) Whether dynamic queries are queries enabled. finders-load-bean (True|False) If this is set to True, the beans will immediately be loaded into the cache by the finder. home-call-router-class- Class to be used for routing home method calls. name home-is-clusterable (True|False) Whether this bean can be deployed from multiple servers in a cluster. home-load-algoritlim (RoundlRobin|Random|WeightBased) The algorithm to use for load-balancing between replicas of this home. idle-timeout-seconds Maximum duration an EJB should stay in the cache. invalidation-target The ejb-name of a read-only Entity bean that should be invalidated when this Container- Managed Persistence Entity EJB has been modified. max-beans-in-cache The maximum number of beans in the cache. Optimistic-column The column that holds the time stamp for optimistic concurrency persistence-type (cmp]bmp) The type of this Entity bean (default: cmp) prim-key-class-nogen (True|False). If this keyword is specified, EJB Gen will not generate the primary key class. read-timeout-seconds The number of seconds between each ejbLoad() call on a Read-Only Entity bean. reentrant (True|False) Whether the class methods are reentrant. run-as Specifies the role-name for this EJB. run-as identity- The name of the principal in case the role maps principal to several principals. table-name The name of the table this Entity bean is mapped to. trans-timeout-seconds The transaction timeout (in seconds). use-caller-identity (True|False) Whether this EJB uses caller's identity. verify-columns (Read|Modified|Version|Timestamp) How optimistic concurrency verifies that the columns modified during the transactions have not been modified.
EJB
Annotation/Attribute Description For Tyj>e
@ejbgen:env-entry Declare an environment entry to be made Class All available through JNDI ENC.
Name The name of this environment entry.
(Required) Type The Java type for this environment entry (must be fully qualified, even if java.lang). (Required)
Value The value for this environment entry.
(Required)
EJB
Annotation/Attribute Description For ΪΪES
@ejbgen:file- Control which files are generated. Class All generation local-class (True|False) Whether to generate the local interface for this EJB. local-home (True|False) Whether to generate the local home interface for this EJB. pk-class (TruejFalse) Whether to generate the primary key class for this EJB. remote-class (TruejFalse) Whether to generate the remote interface for this EJB. remote-home (True|False) Whether to generate the remote home interface for this EJB. value-class (TruejFalse) Whether to generate the value class for this EJB
EJB
Annotation/Attribute Description For Type
@ejbgen:finder Specify finder method attributes. Class Entity caching-name The name of an eager relationship caching. ejb-ql The EJB QL request as it will appear in the deployment descriptor. group-name Name of the group for the WebLogic query include-updates (True|False) Whether updates made during the current transaction must be reflected in the result of a query. isolation-level The type of transaction isolation for this method. max-elements The maximum number of elements that should be returned by a multi-valued query. Signature It must match exactly the signature generated on the Home class. sql-select-distinct (True|False) Whether the generated SQL
'SELECT' will contain a 'DISTINCT' qualifier. transaction-attribute The transaction attribute for this local method.
If not specified, the default transaction attribute will be used. Methods with this tag will be generated on the Local class. Weblogic-ejb-ql The Weblogic EJB QL request as it will appear in the deployment descriptor. EJB
Annotation/Attribute Description For Type
@ejbgen:foreign jms- Specify the provider of a Java™ Message Class Message- provider Service ("JMS") Driven connection-factory- The connection factory JNDI name. jndi-name (Required) initial context-factory The initial JNDI context factory. (Required) provider-url The provider URL. (Required)
EJB
Annotation/Attribute Description For Type
@ejbgen:isolation- Specify transaction isolation level in the Class All level pattern server. isolation-level The isolation level for the methods specified in the pattern tag. (Required)
Pattern The pattern that matches all methods that will receive this isolation level (e.g. "*").
(Required)
EJB
Annotation/Attribute Description For Type
@ejbgen:jndi-name Specify the JNDI name of this bean. Class All Local The local JNDI name of this EJB. If not specified, local interfaces will not be generated.
Remote The remote JNDI name of this EJB. If not specified, remote interfaces will not be generated.
EJB
Annotation/Attribute Description For Type
@ejbgen:local-home Specify attributes of this local home method. Method Entity, method Session
Roles Comma-separated list of roles that are allowed to invoke this method. transaction-attribute The transaction attribute for this local method. If not specified, the default transaction attribute will be used. Methods with this tag will be generated on the Local class.
EJB
Annotation/Attribute Description For Tyjje
@ejbgen:local-method Specify attributes of this local method. Method Entity, Session isolation-level The type of transaction isolation for this method.
Roles Comma-separated list of roles that are allowed to invoke this method. transaction-attribute The transaction attribute for this local method. If not specified, the default transaction attribute will be used. Methods with this tag will be generated on the Local class.
EJB
Annotation/Attribute Description For Type
@ejbgen:message- Declare a message-driven EJB. Class Message- driven Driven destination-jndi-name The JNDI name of the destination. (Required) ejb-name The name of this Message-Driven bean. (Required) acknowledge-mode (auto-acknowledge-ok-acknowledge) The acknowledgement mode. default-transaction The transaction attribute to be applied to all methods that do not have a more specific transaction attribute setting. destination-type (javax.jms.QueuelJavax.jms.Topic). initial-beans-in-free- The initial number of beans in the free pool. pool max-beans-in-free-pool The maximum number of beans in the free pool. message-selector The JMS message selector. run-as Specifies the role-name for this EJB. run-as-identity- The name of the principal in case the role principal maps to several principals. trans-timeout-seconds The transaction timeout (in seconds). transaction-type (Bean|Container) Who manages the transactions for this EJB. use-caller-identity (True|False) Whether this EJB uses caller's identity.
EJB
Annotation/Attribute Description For Tyjje.
@ejbgen:method- Specify a permission pattern for this class. Class All permission-pattern
Pattern The pattern that matches all methods that will receive this method permission (e.g. "*").
Roles The roles for the methods specified in the pattern tag. Separated by a comma.
EJB
Annotation/ Attribute Description For Type
@ejbgen:primkey-field Specify the primary key field for an entity bean. Method Entity Annotation/ Attribute Description For EJB Type
@ejbgen:relation Specify an entity bean relationship. Class Entity
Unidirectional relationships are achieved by specifying only the first three parameters (i.e, no cmr-field, no fk-column, no joint-table).
Many to many relationships must specify an extra table ("joint-table") which must contain at least two columns. The names of these columns must match the names of the columns containing the foreign keys of the two EJB's being joined. multiplicity (one|many) Specifies the multiplicity of the relationship. (Required) Name The name of the relationship. Use the same name on both ends of a relationship for the roles to be generated properly (note that this constraint applies to unidirectional as well). (Required) target-ejb The EJB name of the target of this relationship. (Required) cascade-delete (True|False) cmr-field The CMR field where this relationship will be kept. If it not specified, the relationship is unidirectional. If specified, the attribute fk- column must be specified as well. db-cascade-delete (True|False) Whether a cascade delete will use the built-in cascade delete facilities of the underlying database. fk-column Only needed in a relationship having at least one side. In that case, the non-one side EJB must declare a column that it will use to store the primary key of its counterpart. joint-table Only needed in a Many-Many relationship. It must be the name of an existing table that will be used to hold the joint table containing die relationships. If using a compound primary key, specify a set of corresponding foreign keys separated by commas. role-name The name of this role (such as "ParentHasChildren"). If no role name is given, will generate one. EJB
Annotation/ Attribute Description For ΪΣEe
@ejbgen:relationship- Specify cache information for relationship. Class Entity caching-element caching-name The name of an eager relationship cashing.
(Required) cmr-field The name of the CMR field. (Required) group-name The name of the group to be loaded for the CMR field.
EJB
Annotation/ Attribute Description For Type
@ejbgen:remote- Specify roles allowed to invoke this home Method Entity, home- method. Session method
The method name must start with
"ejbHome".
Note: Home Methods do not apply to message EJB's Beans. The "throws
RemoteException" in the EJB class will be automatically generated in the home class.
Roles Comma-separated list of roles that are allowed to invoke this method. transaction-attribute The transaction attribute for this remote method. If not specified, the default transaction attribute will be used. Methods with this tag will be generated on the Remote class.
EJB
Annotation/Attribute Description For Type
@ejbgen:remote- Specify a method available in a remote Method Entity, method interface. Session isolation-level The type of transaction isolation for this method.
Roles Comma-separated list of roles that are allowed to invoke this method. transaction-attribute The transaction attribute for this remote method. If not specified, the default transaction attribute will be used. Methods with this tag will be generated on the Remote class.
EJB
Annotation/Attribute Description For Type
@ejbgen:resource- Specify the name of a resource environment Class All env-ref reference. (Required) Name Name of the resource environment reference. (Required)
Type Type of the environment resource references (e.g. javax.jms.Queue). (Required) jndi-name JNDI name of the resource.
EJB
Annotation/Attribute Description For Type
@ejbgen:resource-ref Specify the JNDI name of a resource. Class All
Auth (Application|Container) (Required) jndi-name JNDI name of the resource. (Required)
Name Name of the resource. (Required)
Type Tyoe of the resource (e.g. javax.sql.DataSource). (Required) sharing-scope (Shareable|Unshareable)
EJB
Annotation/Attribute Description For Type
@ejbgen:role-mapping Specify roles. Class All Principals The names of the principals in this role (separated by commas). (Required) role-name The name of the role. (Required)
EJB
Annotation/ Attribute Description For Type
@ejbgen: select Specify attributes of select method. Method Entity ejb-ql The EJB-QL defining this select method.
Note: the method name must start with ejbSelect. (Required) caching-name The name of an eager relationship caching. group-name Name of the group for the WebLogic query. include-updates (True|False) Whether updates made during the current transaction must be reflected in the result of a query. max-elements The maximum number of elements that should be returned by a multi-valued query. result-type-mapping (Remote|Local) Whether the returned objects are mapped to EJBLocalObject or EJBObject. sql-select-distinct (True|False) Whether the generated SQL
'SELECT' will contain a 'DISTINCT' qualifier.
Weblogic-ejb-ql The Weblogic EJB QL request as it will appear in the deployment descriptor. EJB
Annotation/Attribute Description For ϊϊβe
@ejbgen:session Declare a session bean. Class Session ejb-name The name of this Session bean. (Required) bean-load-algorithm The algorithm to use for load-balancing between replicas of this bean. call-router-class-name Class name to be used for routing home method calls default-transaction The transaction attribute to be applied to all methods that do not have a more specific transaction attribute setting. home-call-router-class- Class to be used for routing home method name calls. home-is-clusterable (True|False) Whether this bean can be deployed from multiple servers in a cluster. home-load-algorithm (RoundRobin|Random|WeightBased) The algorithm to use for load-balancing between replicas of this home. idle-timeout-seconds Maximum duration an EJB should stay in the cache initial-beans-in-free- The initial number of beans in the free pool. pool is-clusterable (True|False) Whether this bean is cluster- able. load-algorithm (RoundRobin|Random|WeightBased) The name of the algorithm used to balance replicas of this home. max-beans-in-cache The maximum number of beans in the cache. max-beans-in-free-pool The maximum number of beans in the free pool. methods-are- (True|False) Whether the methods for this idempotent stateless session bean are idem potent or not. replication-type (InMemory|None) How to replicate stateful session beans in a cluster. run-as Specifies the role-name for this EJB. run-as-identity- The name of the principal in case the role principal maps to several principals. trans-timeout-seconds The transaction timeout (in seconds). transaction-type (Bean|Counter) Who manages the transactions for this EJB.
Type (Stateless|Stateful) The type of the Session bean. If this attribute is not specified, EJBGen will guess the right type by looking at the ejbCreate() methods on the class. use-caller-identity (True|False) Whether this EJB uses caller's identity.
EJB
Annotation/Attribute Description For Type @ejbgen:value-object Specify objects to be referenced by the value Class All object class. Reference (Local|Value) Specify what objects the value object class should reference when accessing other EJB's. (Required)
In one embodiment, byway of example, the following class annotations accompany a Java™ code fragment that declares a stateless session EJB "Trader" having a JNDI name of "ejb20-statelessSession-TraderHome", and an environment variable "tradeLimit" with a default value of 500.
/**
* ©ejbgen - session * ejb-name = statelessSession
* max-beans-in-free-pool = 100
* is-clusterable = false
* load-algorithm = Random * * ©ejbgen: jndi-name
* remote = ejb20-statelessSession-TraderHome *
* ©ejbge :env-entry
* name = tradeLimit * type = java.lang. Integer
* value = 500
* */ public class TraderEJB implements SessionBean { private static final boolean VERBOSE = true; private SessionContext ctx; private int tradeLimit; ejbCreate() ;
The type of session EJB (e.g., stateful or stateless) can be automatically determined. For example, if there is an ejbCreate() method having a non-empty parameter list, the EJB is stateful. Otherwise, the EJB is stateless. Two methods associated with this EJB are declared below with method annotations indicating that they are available through a remote interface (i.e., to clients residing outside of the Java™ application server in which this EJB is deployed). Notice that both methods make use of the environment variable "tradeLimit" which was declared in the class annotation. X
* Buys shares of a stock for a named customer.
* ©ejbgen: emote-method
*/ public TradeResult buy (String stockSymbol, int shares) { if (shares > tradeLimit) { log ("Attempt to buy "+shares+" is greater than limit of
"+tradeLimit) ; shares = tradeLimit;
} log ("Buying "+shares+" shares of "+stockSymbol) ; return new TradeResult (shares, stockSymbol);
* Sells shares of a stock for a named customer. *
* ©ejbgen: emote-method
*
*/ public TradeResult sell (String stockSymbol, int shares) { if (shares > tradeLimit) { log ("Attempt to sell "+shares+" is greater than limit of "+tradeLimit) ; shares = tradeLimit;
} logC'Selling "+shares+" shares of "+stockSymbol) ; return new TradeResult (shares, stockSymbol);
}
}
The @ejbgen:remote-method annotation indicates that a method will be available in a remote interface. A remote interface declares an EJB's methods that are accessible to applications outside of an EJB's container. Two Java™ files and two deployment descriptors are automatically generated in accordance to an embodiment based on the code fragment above:
Figure imgf000019_0001
Figure imgf000020_0001
Deployment <ejb-name>statelessSession</ejb-name> <stateless-session-descriptor> Descriptor <pool>
<max-beans-in-free-pool>100</max-beans-in- free-pool>
</pool>
<stateless-clustering> <stateless-bean-is- clusterable>false</stateless-bean-is-clusterable> </stateless-clustering> </stateless-session-descriptor> <jndi-name>ejb20-statelessSession- TraderHome</jndi-name>
</weblogic-enterprise-bean> </weblogic-ejb-j ar>
In one embodiment, a value associated with an attribute can be specified with a constant or a variable. In another embodiment, a variable definition can be separate from the EJB definition (e.g., in another file). For example, the variable "remote-jndi-name" can be defined as "Account" as follows: remote-jndi-name = Account
Within the annotated description, variables can be accessed with the delimiters "${" and "}". For example: ©ejbgen: jndi-name remote = $ {remote-jndi-name}
Thus, "remote" would be equal to "Account".
In another embodiment, variables can be used anywhere after an annotation and can contain whole annotation definitions. Assuming the following variable definition: jndi-name-1ag remote = RemoteAccount local = LocalAccount
The following annotation:
@ejbgen : jndi-name ${jndi-name-tag} would expand to:
@ejbgen: jndi-name remote = RemoteAccount Local LocalAccount
In another embodiment, predefined variables are recognized. Predefined variables have default values that can be overridden. In one embodiment, predefined variables can be defined as follows:
Figure imgf000022_0001
h another embodiment, predefined variables can be prefixed with a class name. For example, if the following predefined variables are overridden as follows:
Account .home.baseClass = Base ccountHome home.baseClass = BaseHome value.package = value containerManaged . value . ackage=valuePackageForContainerManaged
Thus, all home interfaces generated will extend the class BaseHome except the home of EJB "Account", which will extend BaseAccountHome. In another embodiment, EJB annotations can be inherited according to
Java™ class inheritance. For example, if an EJB named AccountEJB has abase class BaseAccount:
/**
* ©ejbgen: jndi-name * remote="BaseRemote"
* ©ejbgen:entity
* max-beans-in-cache = 300
*/ public class BaseAccount implements EntityBean {
} **
* ©ejbgen: entity * ejb-name = containerManaged
* table-name = ejbAccounts
* data-source-name = examples-dataSource-demoPool
* max-beans-in-cache = 400 * */ public class AccountEJB extends BaseAccount {
The JNDI remote name "BaseRemote" and max-beans-in-cache of 300 that are defined in the class BaseAccount are inherited by the subclass
AccountEJB. The subclass can optionally override these values. For example, the value of max-beans-in-cache is overridden to be 400 instead of 300.
In another embodiment, EJB relations can be inherited if a value for the attribute 'role-name' is specified. All "role-name" attributes in the Java™ inheritance path can be merged. For example, the following parent class defines a partial relation:
/**
* ©ejbgen: elation
* name = Manyl-Many2 * role-name = ManylHasMany2
* multiplicity = many * role-name = ManylHasMany2
* target-ejb = Many2EJB
* fk-column = many2_fk
* joint-table = join_table
*/ abstract public class BaseManyl extends BaseEntityBean {
The following subclass inherits the above relation and completes its definition:
* ©ejbgen:relation
* role-name = ManylHasMany2 * cmr-field = many2
*
*/ abstract public class anylΞJB extends BaseManyl {
It will be apparent to those skilled in the art that the process of generating
EJB source files from an annotated description of an EJB can be performed in reverse. All of the files or classes needed to deploy an EJB can be reduced into a single annotated description of the EJB which can, in accordance to one embodiment, be used in turn to reproduce the EJB source files. Annotations can be generated automatically based information contained in the class definitions, deployment descriptors and relationships between classes.
Figure 2 is a block diagram in accordance to one embodiment of the invention. A plurality of input files 7 containing EJB classes and deployment information is processed by analyzer 8. Input files 7 can include one or more EJB class definitions. In one embodiment, input files 7 can reside in a single file, such as a Java™ Archive File ("JAR"). In another embodiment, input files 7 can reside in a computer memory, hi yet a further embodiment, input files 7 can be transmitted via a computer network (not shown) to analyzer 8. Analyzer 8 employs parser 10 to extract information related to class structure, class relationships and deployment from input files 7. Analyzer 8 may perform preprocessing of input files 7 before making use of parser 10. In one embodiment, parser 10 can exploit the doclet application programming interface available in Javadoc. hi one embodiment, parser 10 can process all input files 7 at once. In another embodiment, parser 10 can be employed repeatedly by analyzer 8 to incrementally process input files 7. During or after parsing, analyzer 8 builds an EJB database 11 containing all of the extracted information pertaining to each EJB represented by input files 7. The EJB database 11 information is then examined to identify which annotation(s) from annotation library 5 adequately describe the EJB's. The these annotations (not shown) along with the EJB database 11 information are provided to code generator 9. Code generator 9 then emits annotated Java™ code 1 to describe the EJB class(s) in input files 7.
The foregoing description of the preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to the practitioner skilled in the art. Embodiments were chosen and described in order to best describe the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention, the various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.

Claims

What is claimed is:
1. A method for generating Enterprise Java Beans, comprising: generating at least one output based on a description of at least one Enterprise Java Bean (EJB), wherein the description is attended by at least one annotation and the at least one annotation includes at least one variable.
2 The method of claim 1 wherein: the at least one annotation can be inherited.
3. The method of claim 1 wherein: the at least one output includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
4. The method of claim 1 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
5. The method of claim 4 wherein: an entity EJB includes at least one of the following relationships: one-to- one, one-to-many, many-to-many, unidirectional, and bi-directional.
6. The method of claim 1 wherein: the at least one annotation includes at least one attribute.
The method of claim 6 wherein: the at least one attribute is associated with at least one expression.
8. The method of claim 2 wherein: annotation inheritance is based on Java class inheritance.
9. The method of claim 1 wherein: the at least one variable is one of user-specified and predefined.
10. The method of claim 9 wherein: the at least one predefined variable can be redefined.
11. The method of claim 9 wherein: the at least one predefined variable can be prefixed with a class name.
12. The method of claim 1 wherein: the at least one annotation is one of a class annotation and a method annotation.
13. The method of claim 1 wherein: the at least one annotation is a Javadoc tag.
14. The method of claim 1 wherein: the at least one variable can be defined separately from the description of the at least one EJB.
15. The method of claim 1 wherein: the at least one output can be used to generate the description of the at least one EJB.
16. A method for generating Enterprise Java Beans, comprising: generating at least one output based on a description of at least one
Enterprise Java Bean (EJB), wherein the description includes at least one annotation and the at least one annotation can be inherited.
17. The method of claim 16 wherein: the at least one output includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
18. The method of claim 16 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
19. The method of claim 18 wherein: an entity EJB includes at least one of the following relationships: one-to- one, one-to-many, many-to-many, unidirectional, and bi-directional.
20. The method of claim 16 wherein: the at least one annotation includes at least one attribute.
21. The method of claim 20 wherein: the at least one attribute is associated with at least one expression.
22. The method of claim 16 wherein: annotation inheritance is based on Java class inheritance.
23. The method of claim 16 wherein: the at least one annotation includes at least one variable.
24. The method of claim 23 wherein: the at least one variable is one of user-specified and predefined.
25. The method of claim 24 wherein: the at least one predefined variable can be redefined.
26. The method of claim 24 wherein: the at least one predefined variable can be prefixed with a class name.
27. The method of claim 16 wherein: the at least one annotation is one of a class annotation and a method annotation.
28. The method of claim 16 wherein: the at least one annotation is a Javadoc tag.
29. The method of claim 23 wherein: the at least one variable can be defined separately from the description of the at least one EJB.
30. The method of claim 16 wherein: the at least one output can be used to generate the description of the at least one EJB.
31. A method comprising: generating a description of at least one Enterprise Java Bean (EJB) from at least one input, wherein the description includes at least one annotation and the description can be used to generate the at least one input.
32. The method of claim 31 wherein: the at least one annotation can be inherited.
33. The method of claim 31 wherein: the at least one input includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
34. The method of claim 31 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
35. The method of claim 34 wherein: an entity EJB includes at least one of the following relationships: one-to- one, one-to-many, many-to-many, unidirectional, and bi-directional.
36. The method of claim 31 wherein: the at least one annotation includes at least one attribute.
37. The method of claim 36 wherein: the at least one attribute is associated with at least one expression.
38. The method of claim 32 wherein: annotation inheritance is based on Java class inheritance.
39. The method of claim 31 wherein: the at least one annotation is one of a class annotation and a method annotation.
40. The method of claim 31 wherein: the at least one annotation is a Javadoc tag.
41. A system for generating Enterprise Java Beans, comprising: an analyzer to process a description of at least one Enterprise Java Beans
(EJB); and a code generator coupled to the analyzer, the code generator to generate at least one output; and wherein the description includes at least one annotation and the at least one annotation includes at least one variable.
42. The system of claim 41 wherein: the analyzer includes at least one of a parser, a annotation library, and a variable library.
43. The system of claim 41 wherein: the at least one annotation can be inherited.
44. The system of claim 41 wherein: the at least one output includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
45. The system of claim 41 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
46. The system of claim 45 wherein: an entity EJB includes at least one of the following relationships: one- to-one, one-to-many, many-to-many, unidirectional, and bi-directional.
47. The system of claim 41 wherein: the at least one annotation includes at least one attribute.
48. The system of claim 47 wherein: the at least one attribute is associated with at least one expression.
49. The system of claim 43 wherein: annotation inheritance is based on Java class inheritance.
50. The system of claim 41 wherein: the at least one variable is one of user-specified and predefined.
51. The system of claim 50 wherein: the at least one predefined variable can be redefined.
52. The system of claim 50 wherein: the at least one predefined variable can be prefixed with a class name.
53. The system of claim 41 wherein: the at least one annotation is one of a class annotation and a method annotation.
54. The system of claim 41 wherein: the at least one annotation is a Javadoc tag.
55. The system of claim 41 wherein: the at least one variable can be defined separately from the description of the at least one EJB.
56. The system of claim 41 wherein: the at least one output can be used to generate the description of the at least one EJB.
57. A system for generating Enterprise Java Beans, comprising: an analyzer to process a description of at least one Enterprise Java Beans
(EJB); and a code generator coupled to the analyzer, the code generator to generate at least one output; and wherein the description includes at least one annotation and the at least one annotation can be inherited.
58. The system of claim 57 wherein: the analyzer includes at least one of a parser, a annotation library, and a variable library.
59. The system of claim 57 wherein: the at least one annotation includes at least one variable.
60. The system of claim 57 wherein: the at least one output includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
61. The system of claim 57 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
62. The system of claim 61 wherein: an entity EJB includes at least one of the following relationships: one-to- one, one-to-many, many-to-many, unidirectional, and bi-directional.
63. The system of claim 57 wherein: the at least one annotation includes at least one attribute.
64. The system of claim 63 wherein: the at least one attribute is associated with at least one expression.
65. The system of claim 57 wherein: annotation inheritance is based on Java class inheritance.
66. The system of claim 59 wherein: the at least one variable is one of user-specified and predefined.
67. The system of claim 66 wherein: the at least one predefined variable can be redefined.
68. The system of claim 66 wherein: the at least one predefined variable can be prefixed with a class name.
69. The system of claim 57 wherein: the at least one annotation is one of a class annotation and a method annotation.
70. The system of claim 57 wherein: the at least one annotation is a Javadoc tag.
71. The system of claim 59 wherein: the at least one variable can be defined separately from the description of the at least one EJB.
72. The system of claim 57 wherein: the at least one output can be used to generate the description of the at least one EJB.
73. A system for generating an annotated description of an Enterprise Java
Bean, comprising: an analyzer to process at least one input; and a code generator coupled to the analyzer, the code generator to generate a description of at least one Enterprise Java Bean (EJB) from the at least one input; and wherein the description includes at least one annotation; and wherein the description can be used to generate the at least one input.
74. The system of claim 73 wherein: the analyzer includes at least one of a parser, a annotation library, and a database.
75. The system of claim 73 wherein: the at least one annotation can be inherited.
76. The system of claim 73 wherein: the at least one input includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
77. The system of claim 73 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
78. The system of claim 77 wherein: an entity EJB includes at least one of the following relationships: one-to- one, one-to-many, many-to-many, unidirectional, and bi-directional.
79. The system of claim 73 wherein: the at least one annotation includes at least one attribute.
80. The system of claim 79 wherein: the at least one attribute is associated with at least one expression.
81. The system of claim 75 wherein: annotation inheritance is based on Java class inheritance.
82. The system of claim 73 wherein: the annotation is one of a class annotation and a method annotation.
83. The system of claim 73 wherein: the annotation is a Javadoc tag.
84. A machine readable medium having instructions stored thereon that when executed by a processor cause a system to: generate at least one output based on a description of at least one
Enterprise Java Bean (EJB), wherein the description is attended by at least one annotation and the at least one annotation includes at least one variable.
85 The machine readable medium of claim 84 wherein: the at least one annotation can be inherited.
86. The machine readable medium of claim 84 wherein: the at least one output includes one of a local interface class, a home interface class, a remote interface class, and a deployment descriptor.
87. The machine readable medium of claim 84 wherein: the at least one EJB is one of an entity EJB, a stateful session EJB, a stateless session EJB, and a message driven EJB.
88. The machine readable medium of claim 87 wherein: an entity EJB includes at least one of the following relationships: one- to-one, one-to-many, many-to-many, unidirectional, and bi-directional.
89. The machine readable medium of claim 84 wherein: the at least one annotation includes at least one attribute.
90. The machine readable medium of claim 89 wherein: the at least one attribute is associated with at least one expression.
91. The machine readable medium of claim 85 wherein: annotation inheritance is based on Java class inheritance.
92. The machine readable medium of claim 84 wherein: the at least one variable is one of user-specified and predefined.
93. The machine readable medium of claim 92 wherein: the at least one predefined variable can be redefined.
94. The machine readable medium of claim 92 wherein: the at least one predefined variable can be prefixed with a class name.
95. The machine readable medium of claim 84 wherein: the annotation is one of a class annotation and a method annotation.
96. The machine readable medium of claim 84 wherein: the annotation is a Javadoc tag.
97. The machine readable medium of claim 84 wherein: the at least one variable can be defined separately from the description of the at least one EJB.
98. The machine readable medium of claim 84 wherein: the at least one output can be used to generate the description of the at least one EJB.
PCT/US2003/037229 2002-12-05 2003-11-19 Generating java bean code WO2004053634A2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003295747A AU2003295747A1 (en) 2002-12-05 2003-11-19 Generating java bean code

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/310,605 2002-12-05
US10/310,605 US7707544B2 (en) 2002-12-05 2002-12-05 System and method for generating and reusing software application code with source definition files

Publications (2)

Publication Number Publication Date
WO2004053634A2 true WO2004053634A2 (en) 2004-06-24
WO2004053634A3 WO2004053634A3 (en) 2005-05-26

Family

ID=32468069

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/037229 WO2004053634A2 (en) 2002-12-05 2003-11-19 Generating java bean code

Country Status (3)

Country Link
US (1) US7707544B2 (en)
AU (1) AU2003295747A1 (en)
WO (1) WO2004053634A2 (en)

Families Citing this family (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030163460A1 (en) * 2002-01-18 2003-08-28 Matthew Shinn Systems and methods for dynamic querying
US7290250B2 (en) * 2003-02-28 2007-10-30 Bea Systems, Inc. System and method for determining when an EJB compiler needs to be executed
NO20032418D0 (en) * 2003-05-27 2003-05-27 Ericsson Telefon Ab L M Aggregation of non-blocking, durable state machines on an "EnterpriseJava Bean" platform
NO20032419D0 (en) * 2003-05-27 2003-05-27 Ericsson Telefon Ab L M Non-blocking, durable state machines in an "Enterprise Java Bean" platform
US7827527B1 (en) * 2004-02-12 2010-11-02 Chiluvuri Raju V System and method of application development
US7500221B2 (en) * 2004-04-08 2009-03-03 Sap Ag Filter-based comments in source code
US7624115B1 (en) * 2004-04-30 2009-11-24 Sap Ag Backward reference in a persistent data target object within a unidirectional relational database relationship
US20060136373A1 (en) * 2004-05-21 2006-06-22 Bea Systems, Inc. Systems and methods for plain old java object (POJO) retrieval
US7546579B2 (en) * 2004-05-21 2009-06-09 Bea Systems, Inc. Systems and methods for plain old java object (POJO) persistence
US7774776B2 (en) * 2004-07-13 2010-08-10 International Business Machines Corporation Single port initial context access to enterprise java bean
US20060225053A1 (en) * 2004-10-21 2006-10-05 Microsoft Corporation Programming language improvements
US7734653B2 (en) * 2004-12-29 2010-06-08 International Business Machines Corporation Framework to allow one CMP EJB to connect to multiple data sources
US20060230019A1 (en) * 2005-04-08 2006-10-12 International Business Machines Corporation System and method to optimize database access by synchronizing state based on data access patterns
US8438468B2 (en) * 2005-04-15 2013-05-07 International Business Machines Corporation Annotation management
US7480666B2 (en) * 2005-08-11 2009-01-20 International Business Machines Corporation Method for navigating beans using filters and container managed relationships
US7523442B2 (en) * 2006-01-06 2009-04-21 International Business Machines Corporation JNDI validation
US8081647B2 (en) * 2006-02-27 2011-12-20 Oracle International Corporation Method and apparatus for buffering requests to web services using annotations
US20070234316A1 (en) * 2006-03-07 2007-10-04 Sap Ag Methods and systems for development of software for complex systems
US20070214113A1 (en) * 2006-03-13 2007-09-13 Yang Lei Method to support multiple data sources connecting to a persistent object
US20070226251A1 (en) * 2006-03-24 2007-09-27 Rocket Software, Inc. Method of augmenting and controlling utility program execution for a relational database management system
US20070234318A1 (en) * 2006-04-04 2007-10-04 International Business Machines Corporation Method, system, and program product for generating source code for a function
US8141035B2 (en) * 2006-07-05 2012-03-20 International Business Machines Corporation Method for accessing internal states of objects in object oriented programming
US20080052671A1 (en) * 2006-08-03 2008-02-28 Frederic Plante System, method and program product for providing content based designations for programming objects
US7779429B2 (en) * 2006-08-18 2010-08-17 Research In Motion Limited Method and machine-readable medium for building distributed software
EP1890227A1 (en) * 2006-08-18 2008-02-20 Research In Motion Limited Method, system and machine-readable medium for building distributed software
US8214813B2 (en) * 2007-01-12 2012-07-03 Microsoft Corporation Code optimization across interfaces
US8010941B2 (en) * 2007-05-07 2011-08-30 International Business Machines Corporation Method and system for dynamically generating enterprise java beans during installation of a service component architecture application
US9009699B2 (en) * 2007-05-31 2015-04-14 Red Hat, Inc. Providing a POJO-based microcontainer for an application server
US8806324B2 (en) * 2007-08-03 2014-08-12 Sap Ag Annotation data filtering of computer files
US8930356B2 (en) * 2007-09-20 2015-01-06 Yahoo! Inc. Techniques for modifying a query based on query associations
US8181165B2 (en) * 2007-10-30 2012-05-15 International Business Machines Corporation Using annotations to reuse variable declarations to generate different service functions
US8612930B2 (en) * 2009-01-30 2013-12-17 Oracle America, Inc. Methods and apparatus for dynamic class reloading and versioning
US8418155B2 (en) * 2009-02-10 2013-04-09 International Business Machines Corporation Generating parallel SIMD code for an arbitrary target architecture
US8756564B2 (en) 2009-05-29 2014-06-17 International Business Machines Corporation Techniques for providing environmental impact information associated with code
US9684491B2 (en) * 2013-04-30 2017-06-20 Wal-Mart Stores, Inc. Annotation-based item description
US9471345B2 (en) * 2013-09-25 2016-10-18 Sap Se Runtime generation and injection of java annotations
US9696968B2 (en) * 2014-01-17 2017-07-04 Microsoft Technology Licensing, Llc Lightweight optionally typed data representation of computation
US9600342B2 (en) * 2014-07-10 2017-03-21 Oracle International Corporation Managing parallel processes for application-level partitions
US10489213B2 (en) * 2014-10-01 2019-11-26 Red Hat, Inc. Execution of a method at a cluster of nodes
US9720659B2 (en) * 2015-02-12 2017-08-01 International Business Machines Corporation Sparse object instantiation
US10353534B2 (en) 2016-05-13 2019-07-16 Sap Se Overview page in multi application user interface
US10579238B2 (en) 2016-05-13 2020-03-03 Sap Se Flexible screen layout across multiple platforms
CN107480537A (en) * 2017-06-28 2017-12-15 北京小度信息科技有限公司 Authority the Resources list automatic generation method and device

Family Cites Families (49)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5070478A (en) * 1988-11-21 1991-12-03 Xerox Corporation Modifying text data to change features in a region of text
US5140521A (en) * 1989-04-26 1992-08-18 International Business Machines Corporation Method for deleting a marked portion of a structured document
US5079700A (en) * 1989-04-26 1992-01-07 International Business Machines Corporation Method for copying a marked portion of a structured document
US5339433A (en) * 1992-11-19 1994-08-16 Borland International, Inc. Symbol browsing in an object-oriented development system
US5559942A (en) * 1993-05-10 1996-09-24 Apple Computer, Inc. Method and apparatus for providing a note for an application program
CA2643234C (en) * 1993-10-29 2012-05-15 Microsoft Corporation Method and system for generating a computer program
US5485618A (en) * 1993-12-15 1996-01-16 Borland International, Inc. Methods and interface for building command expressions in a computer system
US5734749A (en) * 1993-12-27 1998-03-31 Nec Corporation Character string input system for completing an input character string with an incomplete input indicative sign
US5513305A (en) * 1994-03-01 1996-04-30 Apple Computer, Inc. System and method for documenting and displaying computer program code
JPH0816514A (en) * 1994-07-01 1996-01-19 Hitachi Ltd Coopperation support system
US5603021A (en) * 1994-09-02 1997-02-11 Borland International, Inc. Methods for composing formulas in an electronic spreadsheet system
EP0702294A3 (en) * 1994-09-13 1997-05-02 Sun Microsystems Inc Method and apparatus for diagnosing lexical errors
US6226785B1 (en) * 1994-09-30 2001-05-01 Apple Computer, Inc. Method and apparatus for storing and replaying creation history of multimedia software or other software content
US5694559A (en) * 1995-03-07 1997-12-02 Microsoft Corporation On-line help method and system utilizing free text query
US5748963A (en) * 1995-05-12 1998-05-05 Design Intelligence, Inc. Adaptive binding
US5754737A (en) * 1995-06-07 1998-05-19 Microsoft Corporation System for supporting interactive text correction and user guidance features
US5778402A (en) * 1995-06-07 1998-07-07 Microsoft Corporation Method and system for auto-formatting a document using an event-based rule engine to format a document as the user types
US5822588A (en) * 1995-06-09 1998-10-13 Sun Microsystem, Inc. System and method for checking the use of synchronization locks in a multi-threaded target program
US5752058A (en) * 1995-07-06 1998-05-12 Sun Microsystems, Inc. System and method for inter-token whitespace representation and textual editing behavior in a program editor
US5748975A (en) * 1995-07-06 1998-05-05 Sun Microsystems, Inc. System and method for textual editing of structurally-represented computer programs with on-the-fly typographical display
US5813019A (en) * 1995-07-06 1998-09-22 Sun Microsystems, Inc. Token-based computer program editor with program comment management
US5857212A (en) * 1995-07-06 1999-01-05 Sun Microsystems, Inc. System and method for horizontal alignment of tokens in a structural representation program editor
US5978583A (en) * 1995-08-07 1999-11-02 International Business Machines Corp. Method for resource control in parallel environments using program organization and run-time support
US5805889A (en) * 1995-10-20 1998-09-08 Sun Microsystems, Inc. System and method for integrating editing and versioning in data repositories
GB9600854D0 (en) * 1996-01-16 1996-03-20 British Telecomm Distributed processing
US5845300A (en) * 1996-06-05 1998-12-01 Microsoft Corporation Method and apparatus for suggesting completions for a partially entered data item based on previously-entered, associated data items
US6026233A (en) * 1997-05-27 2000-02-15 Microsoft Corporation Method and apparatus for presenting and selecting options to modify a programming language statement
US5966532A (en) * 1997-07-10 1999-10-12 National Instruments Corporation Graphical code generation wizard for automatically creating graphical programs
US6253370B1 (en) * 1997-12-01 2001-06-26 Compaq Computer Corporation Method and apparatus for annotating a computer program to facilitate subsequent processing of the program
US6208339B1 (en) * 1998-06-19 2001-03-27 International Business Machines Corporation User-interactive data entry display system with entry fields having distinctive and changeable autocomplete
US6308315B1 (en) * 1998-10-14 2001-10-23 Sun Microsystems, Inc. System and method for automatically and selectively promoting object variables to method fields and variables in a digital computer system
US6305008B1 (en) * 1998-11-13 2001-10-16 Microsoft Corporation Automatic statement completion
US6289512B1 (en) * 1998-12-03 2001-09-11 International Business Machines Corporation Automatic program installation
US6298478B1 (en) * 1998-12-31 2001-10-02 International Business Machines Corporation Technique for managing enterprise JavaBeans (™) which are the target of multiple concurrent and/or nested transactions
US6591272B1 (en) * 1999-02-25 2003-07-08 Tricoron Networks, Inc. Method and apparatus to make and transmit objects from a database on a server computer to a client computer
US6269373B1 (en) * 1999-02-26 2001-07-31 International Business Machines Corporation Method and system for persisting beans as container-managed fields
US6546554B1 (en) * 2000-01-21 2003-04-08 Sun Microsystems, Inc. Browser-independent and automatic apparatus and method for receiving, installing and launching applications from a browser on a client computer
US6684388B1 (en) * 2000-08-22 2004-01-27 International Business Machines Corporation Method for generating platform independent, language specific computer code
US6665861B1 (en) * 2000-08-24 2003-12-16 International Business Machines Corporation Apparatus and method for providing metadata for the creation of semi-deployed enterprise java beans
US7752214B2 (en) * 2000-09-01 2010-07-06 Op40, Inc. Extended environment data structure for distributed digital assets over a multi-tier computer network
AU2001296866A1 (en) * 2000-09-05 2002-03-22 Zaplet, Inc. Methods and apparatus providing electronic messages that are linked and aggregated
US6910128B1 (en) * 2000-11-21 2005-06-21 International Business Machines Corporation Method and computer program product for processing signed applets
US6817009B2 (en) * 2000-11-30 2004-11-09 Hewlett-Packard Development Company, L.P. Method and apparatus for verifying data local to a single thread
KR100428715B1 (en) * 2001-01-12 2004-04-27 한국전자통신연구원 An Apparatus and Method for Generating Enterprise Java Beans based a Class Diagram
US8065219B2 (en) * 2001-06-13 2011-11-22 Sungard Energy Systems Inc. System architecture and method for energy industry trading and transaction management
US7080361B2 (en) * 2001-07-30 2006-07-18 Lockheed Martin Corporation Process for generating enterprise java bean components from an SQL database
US6993487B2 (en) * 2002-02-22 2006-01-31 Maxima Blue Ltd. Software code comments management method and system supporting speech recognition technology
KR100501410B1 (en) * 2002-11-27 2005-07-18 한국전자통신연구원 System and method of generating EJB component from reusable business logic in servlet
US7051322B2 (en) * 2002-12-06 2006-05-23 @Stake, Inc. Software analysis framework

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PICON J. ET AL.: 'Enterprise JavaBeans development using VisualAge for Java' IMB REDBOOKS June 1999, pages 1 - 423, XP002983410 *

Also Published As

Publication number Publication date
US20040111701A1 (en) 2004-06-10
AU2003295747A1 (en) 2004-06-30
WO2004053634A3 (en) 2005-05-26
US7707544B2 (en) 2010-04-27
AU2003295747A8 (en) 2004-06-30

Similar Documents

Publication Publication Date Title
US7707544B2 (en) System and method for generating and reusing software application code with source definition files
US7580946B2 (en) Smart integration engine and metadata-oriented architecture for automatic EII and business integration
Dowler et al. Table access protocol version 1.0
US7496599B2 (en) System and method for viewing relational data using a hierarchical schema
US7287247B2 (en) Instrumenting a software application that includes distributed object technology
US6418448B1 (en) Method and apparatus for processing markup language specifications for data and metadata used inside multiple related internet documents to navigate, query and manipulate information from a plurality of object relational databases over the web
US8615731B2 (en) System and method for automating the development of web services that incorporate business rules
US6356920B1 (en) Dynamic, hierarchical data exchange system
US6571232B1 (en) System and method for browsing database schema information
US7552151B2 (en) System, method and program product for adding, updating and removing RDF statements stored on a server
US7606792B2 (en) System and method for efficient evaluation of a query that invokes a table valued function
US5758348A (en) Method for generically manipulating properties of objects in an object oriented repository
US8060863B2 (en) Conformance control module
US7426503B2 (en) System and method for an improved type inference
US20040230667A1 (en) Loosely coupled intellectual capital processing engine
KR20050000352A (en) Common query runtime system and application programming interface
US20060085461A1 (en) System &amp; method for using web based applications to manipulate data with manipulation functions
WO2003073327A1 (en) Eager relationship caching of entity beans
US7499956B1 (en) Annotation processing from source files and class files
US6963863B1 (en) Network query and matching system and method
US20040230982A1 (en) Assembly of business process using intellectual capital processing
Rodriguez-Martinez et al. Automatic deployment of application-specific metadata and code in MOCHA
Dowler et al. IVOA recommendation: table access protocol version 1.0
US7469249B2 (en) Query-driven partial materialization of relational-to-hierarchical mappings
US20040230691A1 (en) Evolutionary development of intellectual capital in an intellectual capital management system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP