Home

Product

Buy

Support

News

Press

Downloads

Contact

Company

Partners

Resources

Index    Previous   <<>>  Next
5.1 Main view
5.1.1 Database tree view
5.1.2 Database object view
5.1.3 Configuration dialogs (Tools menu)
5.2 Building applications and components
5.2.1 Entity
5.2.2 Business object
5.2.3 ViewSet
5.2.4 Model Source
5.1  Main view	To top of page
When you start JCodeBox you are presented with the main view window. From here you can access all of the features available in the program. The main view window is split into two halves: Database tree view (left hand side) Database object view (right hand side)
5.1.1  Database tree view	To top of page
The database tree view provides a tree view of all of the database drivers and connections you have registered with JCodeBox. It allows you to navigate into connections to see available schemas and schema objects. You can apply different actions to different objects displayed in the tree view i.e. You can generate applications from schema/catalogs (right mouse click on the schema/catalog or use the action menu) You can generate individual components from tables (right mouse click on the table or use the action menu) From a connection you can start the query tool which allows you to interrogate the database using SQL (right mouse click on the connection or use the action menu)
5.1.2  Database object view	To top of page
The database object view displays information about a specific schema object i.e. a table. To populate the database object view simply double click on the schema object in the database tree view.
5.1.3  Configuration dialogs (Tools menu)	To top of page
JCodeBox can be configured for your environment via a number of configuration dialogs that are accessible from the Tools menu on the main view window. The following are available: Enterprise server setup - configures you enterprise application servers Web application server setup - configures you web application servers JCodeBox options - configures JCodeBox itself Classpath - configures the JCodeBox classpath
5.2  Building applications and components	To top of page
One of the main features of JCodeBox is the ability to build Java enterprise, web and web services applications and components. The different types of applications and components you can generate are discussed in chapter 15.Generating individual J2EE components and chapter 14.Building a (web/enterprise) J2EE application. You define applications via the define application dialog and components via the define <<component type>> dialog. In general the steps to build an application are as follows: Invoke the define application dialog (optionally from a database schema) Set properties for your application Add components (entities, EJBs, JSP, etc) to your application Press the create button Choose build options in the build dialog and press OK In general the steps to build an individual component are as follows: Invoke the define <<component type>> dialog (optionally from a database schema object) Set properties for your component Press the OK button Set build properties in the generation details dialog and press OK
5.2.1  Entity	To top of page
In JCodeBox an entity represents a business entity in your application (i.e. customer, account, etc). Entities in JCodeBox are purely logical i.e. there is no physical representation of an entity in the generated J2EE framework. Manual entities (ManEntity) will generate the scripts required to generate the tables required to store the entity in the database. Relational Database entities (RDBEntity), are actually stored in tables in the relational database. The JCodeBox RDBEntity maps directly to these tables.
5.2.2  Business object	To top of page
A business object is an object that contains business functionality. The object could manage a (logical) business entity (see previous section) or it could contain workflow functionality. Currently business objects are implemented as Enterprise Java Beans (EJBs). Generally objects that manage entities are implemented as entity EJBs and objects that provide workflow are implemented as session beans.
5.2.3  ViewSet	To top of page
A JCodeBox ViewSet provides a set of basic views on a component. These views are implemented using JSP/servlets in the web/presentation tier. Example A ViewSet on an entity EJB could include the following views: Create (multiple if additional creators are defined) Maintain (Incorporating read and Update) Delete Finders (primary key and additional) Relationships Business methods
5.2.4  Model Source	To top of page
In JCodeBox, a Model Source is a component that can provide data and state information to another component Example An EJB can be a Model Source (i.e. provide data and state for) a ViewSet. So when defining a ViewSet you need to select it's modelsource, i.e. select the component that this ViewSet is going to get its data and state information from. Example An entity can be a Model Source for an entity EJB. So when defining an entity EJB, you need to select an (JCodeBox) entity that will provide the data and state information for the entity EJB
Index    Previous   <<>>  Next