Community
Participate
Working Groups
Integrated service oriented data management infrastructure with Test UI. The Test UI must be enhanced to leverage the new service oriented data management infrastructure as being delivered in https://bugs.eclipse.org/bugs/show_bug.cgi?id=169353. Specifically, the following Test Project components are impacted by this feature: -Test Execution model. -Test Execution harness. -Test Log Viewer. -BIRT report generators.
Created attachment 60614 [details] Patch to enable the RDB resources requires this debug option in an .option file org.eclipse.tptp.platform.models/debug/databaseResourcePostfix=__Cloudscape.trcadb or in the VMARGS section: -DModelDebugger.debugDatabaseResourcePostfix=__Cloudscape.trcadb
Once we get the end-to-end scenario in place we should replace the debug option check with something else. Also the Copy (or migrate) XMI to database action (now in org.eclipse.hyades.use.cases.popup.actions.CopyXMIToFromDatabase) should be moved to hyades.ui and extended to support other kind of resources if required. Joe we need to look at how to handle these cases: - id with UUID values are added to DB resources where was not available in the XMI - support for annotations files, if we intend to use BLOBs or not - the code from org.eclipse.hyades.resources.database.internal.impl.DBResourceImpl.attachedFacadeResourceImpl(EObject arg0) is required, I disabled for now (it may not be required but we need to investigate)
(In reply to comment #2) > Once we get the end-to-end scenario in place we should replace the debug option > check with something else. Just to clarify, with the current state of the code you can get in/out the execution result resource data in the database using Launch test or "Copy XMI resource -> to database" action. We need to change the Test Log viewer to avoid loading the whole resource in memory then we get scalability in that scenario, then we need to update the loaders to avoid keeping the whole resource in memory so we get scalability in that scenario also. Then the last part would be to move this implementation under the new DMS API and make the viewer leverage the query mechanism provided there.
Service oriented data management infrastructure WIKI Page: -http://wiki.eclipse.org/index.php/TPTP_Test_Log_Scalability The goals of the service oriented data management infrastructure include: -Handle more data than actual memory (limited only by disk space). -Support out current use cases with reasonable performance.
Updating sizing.
Paul, I think this defect should depend on 169353 not the inverse. The 169353 feature is intended to provide the model infrastructure and the way I understand this defect is to use that infrastructure. BTW, Joanna just removed the "plan" keyword on this defect, please add it back if it's still in plan.
(In reply to comment #7) Correct.
Sizings split into indivdual child work items (180986, 180990, 180995 and 180996).
Created attachment 64196 [details] Updated patch with paging list support and paging controls Be aware that some strings have not been externalized. Use /org.eclipse.tptp.platform.models/.options to controll the UI paging mechanism: org.eclipse.tptp.platform.models/debug/useEmbeddedPageControls = false org.eclipse.tptp.platform.models/debug/useSWTVirtualSupport = true
Created attachment 64197 [details] Some icons for previous patch.
Complete except for 180995 (the design and implementation can not be completed in 4.4). As such, re-targeting to future to be completed in stage 2.
Resolving as WONTFIX since there are no resources or plans for contribution of resources for this defect.
Closing.
