Information systems modelling UML and service description languages

Transcription

1 Internet Engineering Tomasz Babczyński, Zofia Kruczkiewicz Tomasz Kubik Information systems modelling UML and service description languages Laboratory 4

2 Design patterns used to build the Integration nad ResourcesTiers D.Alur, J.Crupi, D. Malks, Core J2EE. Desin Patterns Outline of creating the Library Catalogue Java Application 1. Create a database in the Derby database system 2. Create Annotations in the object model of the Business Tier 3. Creating a Persistence Unit 4. Create the following classes of the Integration Tier: TTitle_bookController and the TBookController 5. Link tiers together: the Integration Tier with the LibraryWeb1 application 6. Run the final web multitier application

3 1. Create a database in the Derby database system 1. Check a directory where you should create an empty database of the Derby database system by using the NetBeans - the default directory is a directory of Windows users \. Netbeansderby (slide 1) 2. Select the Services tab and then expand the Databases node. Then right-click on Java DB item and select Create Database (slide 2) 3. In the form for creating a database (slide 3), enter the data as follows: Database Name, User, Password and the Database Location (default or selected by the user). In the selected directory will be created a directory named database with an empty database (slide 4) 4. Check a directory where you have created from NetBeans an empty database in the system database Derby - - you can see the new katalogue Library1 (slide 4) 5. To connect to the database: Right-click the database connection node and choose the Connect item (slide 6) - jdbc:derby://localhost:1527/library1:[library1 on LIBRARY1] (jdbc:derby://localhost:1527/database_name:[user on DataBaseSchema] ). 6. Now expand the database connection node to browse the database until disconnect from the database. Then expand the database node to see the empty Library Database (slide 7) p the Library1 node is lacking.

4 1)

5 2)

6 3)

7 4)

8 5)

9 6)

10 7)

11 2. Create Annotations in the object model Mapping Entity Classes (Help of the NetBeans) An entity class is used to represent a table in a database, and the fields in an entity class correspond to columns in that table. In an entity class, you can use annotations to specify how fields in an entity class are mapped to the corresponding database columns and tables. If the name of the mapped database column is the same as the field or property name because they are mapped by default. The following annotations are commonly used when mapping entity defines the Entity Specifies the primary key property or field of an Allows you to specify the strategy that automatically generates the values of primary keys. Specifies a mapped column for a persistent property or Defines a many-valued association with many-to-many Defines a single-valued association to another entity class that has many-to-one Defines a many-valued association with one-to-many multiplicity. For more on using annotations and annotation elements to map entities in an enterprise application, see the Java EE 5 Tutorial Insert the annotations shown in the next slides to the TTitle_book, TTitle_book_on_tape, TBook, TBook_period

12

13

14

15

16 3. Creating a Persistence Unit To create a persistence unit: 1. In the Projects window, right-click a Library1project node and choose New > Other. 2. Select Persistence Unit in the Persistence category and click Next. 3. Specify a unique Persistence Unit Name. In most cases you can keep the default name suggested by the IDE. 4. Select a the TopLink library by choosing New Persistence Library. 5. Select a datasource from the drop-down menu. The data source can be the Library1 database connection. To appear in the list, the data source needs to be registered with the IDE. 6. Specify a table generation strategyas Createfor your database. 7. Click Finish. When you click Finish, the file persistence.xml opens in the Source Editor. 8. Click the Add Class and select all classes as the Entity classes(slide 7)

17 1)

18 2)

19 4) 5)

20 6), 7)

21 8)

22 Facade Factory Flyweight Strategy

23 4. Create the following classes of the Integration Tier: TTitle_bookController anf the TBookController for persisting of objects. Facade of the Integration Tier

24 4.1. Creating the new package domainstore in the source packages in the Library1 project To create a new package: 1) In the Projects window, right-click a Library1 Source Package node and choose New >. 2) Select Java Package. 3) Specify a unique Package Namedomainstore. In most cases you can keep the default name suggested by the IDE. 4) Click Finish. Note: If you can t see the Java Package item, you select Other and click it. In the New File dialog box select the Java Categories item and the Java Package as the File Types item. Click the Next button. In the New Java Package dialog box you should go to the p.3

25 To create a new Java Class file: 1) In the Projects window, right-click a Library1 Source Package node and choose New. 2) Select Java Class. 3 )Specify a unique Class Name TTile_bookController. In most cases you can keep the default name suggested by the IDE. 4) Click Finish. 5) Repeat these activities to create the TBookController Java Class (p.4.3). Note: If you can t see the Java Java Class item, you select Other and click it. In the New File dialog box select the Java Categories item and the Java Class as the File Types item. Click the Next button. In the New Java Class dialog box you should go to the p.3

26 4.2. Creating the the TBookController.java in the domainstore package for persisting TTitle_book and TTitle_book_on_tape objects. Applying of design patterns Domain Store i Transfer Object (1) The TTitle_bookControllerclass: creating the EntityManager object private EntityManager getentitymanager()

27

28 (2) The TTitle_bookController class: creating the EntityManager object private EntityManager getentitymanager() public class TTitle_bookController { private EntityManagerFactory emf = null; private EntityManager getentitymanager() { if (emf == null) { emf = Persistence.createEntityManagerFactory("Library1PU"); } return emf.createentitymanager(); }

29 (1) The TTitle_bookController class: Adding a title in the database public boolean addttitle_book(ttitle_book title_book)

30 (2) The TTitle_bookController class: Adding a title in the database public boolean addttitle_book(ttitle_book title_book) public boolean addttitle_book(ttitle_book title_book) { EntityManager em = getentitymanager(); try { em.gettransaction().begin(); em.persist(title_book); em.gettransaction().commit(); } finally { em.close(); return false; } }

31 (1) The TTitle_bookController class: Adding titles in the database public boolean addttitle_books (ArrayList<TTitle_book> titles)

32 (2) The TTitle_bookController class: Adding titles in the database public boolean addttitle_books (ArrayList<TTitle_book> titles) public boolean addttitle_books(arraylist<ttitle_book> titles) { EntityManager em = getentitymanager(); TTitle_book newttitle_book = null; try { Iterator it = titles.iterator(); em.gettransaction().begin(); while (it.hasnext()) { newttitle_book = (TTitle_book) it.next(); if (newttitle_book.getid() == null) { em.persist(newttitle_book); } } em.gettransaction().commit(); } finally { em.close(); return false; } }

33 (1) Getting TTitle_book and TTitle_book_on_tape objects from the database (design pattern Transfer Object TTitle_book[0..*]) public List<TTitle_book> getttitle_books() public TTitle_book[] getttitle_books_()

34 (2) Getting TTitle_book and TTitle_book_on_tape objects from the database (design pattern Transfer Object TTitle_book[0..*]) public TTitle_book[] getttitle_books_() { return (TTitle_book[]) getttitle_books().toarray(new TTitle_book[0]); } public List<TTitle_book> getttitle_books() { EntityManager em = getentitymanager(); try { javax.persistence.query q = em.createquery("select c from TTitle_book as c"); return q.getresultlist(); } finally { em.close(); } } }// end of TTitle_bookController

35

36 4.3. Creating the TBookController.java in the domainstore package import javax.persistence.persistence; import library1.tbook; public class TBookController { private EntityManagerFactory emf = null; private EntityManager getentitymanager() { if (emf == null) { emf = Persistence.createEntityManagerFactory("Library1PU"); } return emf.createentitymanager(); }

37 The TBookController class: Getting books from the database public TBook[] gettbooks_(), public List<TBook> gettbooks() public TBook[] gettbooks_() { return (TBook[]) gettbooks().toarray(new TBook[0]); } public List<TBook> gettbooks() { EntityManager em = getentitymanager(); try { javax.persistence.query q = em.createquery("select c from TBook as c"); return q.getresultlist(); } finally { em.close(); } }

38 The TBookController class: Adding a book in the database public boolean addttitle_books (ArrayList<TTitle_book> titles) public boolean addtbook(tbook book) { EntityManager em = getentitymanager(); try { em.gettransaction().begin(); em.persist(book); em.gettransaction().commit(); } finally { em.close(); return false; } }

39 The TBookController class: Adding books in the database public boolean addtbooks (ArrayList<TTitle_book> titles) public boolean addtbooks(arraylist<ttitle_book> titles) { EntityManager em = getentitymanager(); TBook newbook = null; Iterator it = titles.iterator(); em.gettransaction().begin(); try { while (it.hasnext()) { TTitle_book newtitle_book = (TTitle_book) it.next(); if (newtitle_book.getid() == null) continue; Iterator it_ = newtitle_book.getmbooks().iterator(); while (it_.hasnext()) { newbook = (TBook) it_.next(); if (newbook.getid() == null) em.persist(newbook); } } em.gettransaction().commit(); } finally { em.close(); return false; } } }// end of TBookController

40

41

42 5. Link tiers together: the Integration Tier with the LibraryWeb1 application 5.1. Create the two arrays: titles and books and generate the setter and getter methods: right-click and select the Insert code item from the poup menu. Next, select the setter andgetter items from the list.

43 5.2. In the Project Window, select the TitlesDataBase.jspf. In the Design view right-click the table component and select the Bind to Data item from the poup menu.

44 5.3. Next, select the titles item from the list and select a fewattributes to be displayed in the table component (move the attributes to the Available list on the left side by selecting each attribute and clicking the < button).

45 5.4. As the result, you can see the new view of the table component including the selected attributes

46 5.5. In the Project Window, select the BooksDataBase.jspf. In the Design view right-clickthe table component and select the Bind to Data item from the poup menu.

47 5.6. Next, select the books item from the list. Eventually choose a few attributes to be displayed in the table component (move the selected attributes to the Available list on the left side by clicking the < button). Click OK.

48 5.7. As the result, you can see the new view of the table component including selected attributes.

49 5.8. Add thecodeshown belowto the initmethod of the ApplicationBean1.java. The init method inits the data in the application this method is called only once during the life of the LibraryWeb1 application.

50 5.9. Add thecode shown on the rightto the updatetitles and updatebooks methods of the ApplicationBean1.java. These methods get data from the Library1 databaseand store the data in the titles and books arrays.

51 5.10. Add the code shown below to the updatetfacade method of the ApplicationBean1.java. The updatetfacade method inits the data of the facade object. It gets data from titles and books arrays.

52 5.11. Events handling for Add titles in databases a) The prerender method is used for last activities before the Response phase: disable the link to itself -refresh the view of table component by calling the updatetitles methods, which updating the titles array. The titles is binded to this component. Add the codeshown belowto the DataBaseTitles.java. b) The addtitles _database_action method is used to the event handle of the click of the addtitles_database button. It calls the addtitles_database of the ApplicatioBean1 object. Add the code shown below to the DataBaseTitles.java.

53 c) The addtitles _DataBase method is used to store data of the TTitle_book or TTitle_book_on_tape objects in the Library1 database. It stores the objects of the facade object in the Library1 database by using addttitle_books method of the TTitle_bookController object.

54 5.12 Events handling for Add tbooks in databases a) The prerender method is used for last activities before the Response phase: disable the link to itself and refresh the view of table component by calling the updatebooks methods, which updating the books array. The books is binded to this component - add the code shown belowto the DataBaseBooks.java. b) The addbooks _database_action method is used to the event handle of the click of the addbooks_database button. It calls the addbooks_database from the ApplicationBean1 object.

55 c) The addbooks _DataBase method is used to store data of the TBook or TBook_period objects in the Library1 database. It stores the objects of the facade object in the Library1 database by using addtbooks method of the TBookController object..

56 5.13. Event handling for Add title in databases a) The prerender method is used for last activities before the Response phase: disable the link to itself and clear the form fields (refresh_form method of the FormTitle fragment) - add the codeshown on the right to the DataBaseTitle.java. b) The addtitle _database_action method is used to the event handle of the click of the addtitle Database button. It must get data of the title (the form_title method of the FormTitle fragment) and deliver it to the addtitle_database method of the ApplicatioBean1 object. Add the code shown on the rightto the DataBaseTitle.java.

57 c) The addtitle _DataBase method is used to store data of the TTitle_book or TTitle_book_on_tape object in the TFacade object. If it finishes successfuly, it stores the same title object in the Library1 database by using addttitle_book method of the TTitle_bookController object.

58 6. Run the final web multitier application 6.1. Click the Add titles in application link you can see the view of the Titles page. Add a few titles.

59 6.2. Next, click the Add titles in DataBase link you can see the view of the DataBaseTitles page. You must click the addtitles_database button as the result, you can see new titles in the table component. These titles have been stored in the Library1 database.

60 6.3. Next, click the Add books in application link you can see the view of the Books page. Add a few new books.

61 6.4. Next click the Add books in DataBase link you can see the view of the DataBaseBooks page.

62 6.5. You must click the addbooks_database button as the result, you can see new books in the table component. These books have been stored in the Library1 database.

63 6.6. You must click the Add title in DataBase link you can see the view of the DataBaseTitle page Fill the form to store a new title object. Next, click the addtitle_database button.

64 6.8. As the result, you can see a new title in the table component. This title have been stored in the Library1 database.

65 6.9. You must click the Add title in application link you can see the view of the Titles page As the result, you can see a new title in the drop down component. This title also have been stored in the facade object in the application.

66 6.11. Click the Services tab. In the Services Window connect to the Library1 database, if it is disconnected - right-click the Library1 node, select the Connect item and click it Expand the Library1 node. Then, expand the Tables node. Right-click the TTitle_book node and select the View Data. Then click it. Repeat these activities for the TTitle_book table. As the result, you can see data stored in the Library1 database (next slides).

67

68

69