Overview

1. Overview StationPulsedFiberTestUI 1) Read in module barcode from scanner processBarCode 2) Create a PulsedFiberTestDetails object from files entered by user CreateDetailsForModule – File chooser 3) Check if this test has already been entered into the db using the details object and a native query. CheckDBForTestTransaction 4) Quit if the test already exists, otherwise create a ReadNOVAModuleTransaction. executeAfterNormalCompletion 5) Read the NOvA module object from the db and create a task for the pulsed fiber test. ReadNOVAModuleTransaction 6) Set the local NOvA module object and get the objectkey from the task that was created. Create a InsertPulsedFiberTestTransaction to insert pft data. executeAfterNormalCompletion 7) Insert the pulsed fiber test into the db and link it to the task that was created above. InsertPulsedFiberTestTransaction 8) Display to the user the created test. executeAfterNormalCompletion This design has the down side that if anything goes wrong after ReadNOVAModuleTransaction, the task created by it will still exist in the database when it should be deleted.

2. Server Side Client Entities can be used Details objects can only be used StationPulsedFiberTestUI Used named query to search db for test with scan times found in pft data files. Should return null if there are no entries in the db already for this test. processBarCode CreateDetailsForModule – File chooser WorkerRemote (getEJBHome) WorkerBean checkIfTestExistsInDB checkIfTestExistsInDB CheckDBForTestTransaction executeAfterNormalCompletion ReadNOVAModuleTransaction PulsedFiberTestLocal PulsedFiberTestBean executeAfterNormalCompletion checkIfTestExistsInDB checkIfTestExistsInDB InsertPulsedFiberTestTransaction em.createNamedQuery(PulsedFiberTest.SEARCH_SCANTIMES_QUERY) Return existingPFTDetails if exists. executeAfterNormalCompletion PulsedFiberTestDetails Client and server can use details objects

3. Server Side Client Entities can be used Details objects can only be used StationPulsedFiberTestUI Read the nova module from the database and create the task. Return a list of task objectkeys that are created (usually just 1 objectkey). processBarCode CreateDetailsForModule – File chooser CheckDBForTestTransaction executeAfterNormalCompletion WorkerRemote (getEJBHome) WorkerBean ReadNOVAModuleTransaction readNOVAModuleCheckTestsCreateTask readNOVAModuleCheckTestsCreateTask 2 executeAfterNormalCompletion 3 1 InsertPulsedFiberTestTransaction NOvAModuleLocal NOvAModuleBean executeAfterNormalCompletion readNOVAModule readNOVAModule addTaskPartAssemblyToModule addTaskPartAssemblyToModule Now creates a list of objectkeys from the tasks created to return in DTO object. TaskLocal TaskBean checkAllModuleTasksAndTestsForStation checkAllModuleTasksAndTestsForStation Triggers often cause db to throw errors here.

4. Server Side Client Entities can be used Details objects can only be used StationPulsedFiberTestUI Return PulsedFiberTestDetails with all info from inserted data. processBarCode CreateDetailsForModule – File chooser PulsedFiberTestDetails CheckDBForTestTransaction Client and server can use details objects executeAfterNormalCompletion ReadNOVAModuleTransaction executeAfterNormalCompletion WorkerRemote (getEJBHome) WorkerBean createPulsedFiberTestsAndTasks createPulsedFiberTestsAndTasks InsertPulsedFiberTestTransaction executeAfterNormalCompletion PulsedFiberTestLocal PulsedFiberTestBean createTest createTest 1) Call createTestAndTask first. 2) Use named query PulsedFiberTest.UPDATE_CELL_VALUES_QUERY and PulsedFiberTestDetailsobject to update the array values in db. createPulsedFiberTest createPulsedFiberTest 1) Create pulsedfibertest here. This is where all the copying of details to persistence object and vice versa goes on. TestLocal TestBean createTestAndTask createTestAndTask 1) Call createPulsedFiberTest 2) Create test and moduletest objects, then return PulsedFiberTestDetailsobject.