Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EDT:v07 green threads"
| Line 16: | Line 16: | ||
|- | |- | ||
| Create RUI handler and the default handler created by the wizard can be opened successfully by VE.<br> | | Create RUI handler and the default handler created by the wizard can be opened successfully by VE.<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| | | | ||
'''MAJOR:''' Bug 356039 - VE prints 'document.write("could not open %handler_name%");' when opening the RUI handlers - Forest | '''MAJOR:''' Bug 356039 - VE prints 'document.write("could not open %handler_name%");' when opening the RUI handlers - Forest | ||
| Line 22: | Line 22: | ||
'''MAJOR: '''Bug 356151 - The widget parts defined in the org.eclipse.edt.rui.widgets_0.7.0 cannot be resolved - Paul<br> | '''MAJOR: '''Bug 356151 - The widget parts defined in the org.eclipse.edt.rui.widgets_0.7.0 cannot be resolved - Paul<br> | ||
| − | '''MAJOR: '''Bug 356153 - The default RUI handler created by RUIHandler creation wizard cannot be displayed in the VE - Forest/Jimmy<br> | + | '''MAJOR: '''Bug *356153 - The default RUI handler created by RUIHandler creation wizard cannot be displayed in the VE - Forest/Jimmy<br> |
|- | |- | ||
| The button, input box & grid can be drag/drop in VE.<br> | | The button, input box & grid can be drag/drop in VE.<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| '''MAJOR: '''* 355624 - Compile Error after creating a client project - Scott/Forest<br> | | '''MAJOR: '''* 355624 - Compile Error after creating a client project - Scott/Forest<br> | ||
|- | |- | ||
| The properties, outline, data view etc can be used.<br> | | The properties, outline, data view etc can be used.<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| * 355624<br> | | * 355624<br> | ||
|- | |- | ||
| Line 42: | Line 42: | ||
|- | |- | ||
| Run service call in preview mode.<br> | | Run service call in preview mode.<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| Service Invocation problem in the preview tab of visual editor - Joe/Justin <br> | | Service Invocation problem in the preview tab of visual editor - Joe/Justin <br> | ||
|- | |- | ||
| Debug RUI handler & service (step over & into etc)<br> | | Debug RUI handler & service (step over & into etc)<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| * 355624<br> | | * 355624<br> | ||
|- | |- | ||
| Deploy the RUI handler to the Tomcat<br> | | Deploy the RUI handler to the Tomcat<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| * 355624<br> | | * 355624<br> | ||
|- | |- | ||
| Deploy the service to the Tomcat<br> | | Deploy the service to the Tomcat<br> | ||
| − | | bgcolor="#ffff99" | Failed<br> | + | | bgcolor="#ffff99" | Failed in P2 build<br> |
| | | | ||
'''MAJOR''': Bug 356140 - The runtime JAR file is not copied in the service deployment - Jimmy<br> | '''MAJOR''': Bug 356140 - The runtime JAR file is not copied in the service deployment - Jimmy<br> | ||
| Line 62: | Line 62: | ||
|- | |- | ||
| Run the application<br> | | Run the application<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| * 355624<br> | | * 355624<br> | ||
|- | |- | ||
| The service call with database<br> | | The service call with database<br> | ||
| − | | bgcolor="#ff0066" | Blocked<br> | + | | bgcolor="#ff0066" | Blocked in dev & p2<br> |
| Not know the test scenario - Tony/Zhi<br> | | Not know the test scenario - Tony/Zhi<br> | ||
|} | |} | ||
Revision as of 02:15, 30 August 2011
Last update: 2011/08/30, By Rocky
Overview
Note: By default, I use the P2 installable build to test the green thread. However, if the defects marked with * mean tested by development workspace.
| Capability |
Status |
Defects |
| Create EGL web client with service project. |
Blocked in P2 build |
MAJOR: CQ has been finished, waiting for including it into the nightly build - Jiyong |
| Create RUI handler and the default handler created by the wizard can be opened successfully by VE. |
Blocked in dev & p2 |
MAJOR: Bug 356039 - VE prints 'document.write("could not open %handler_name%");' when opening the RUI handlers - Forest MAJOR: Bug 356151 - The widget parts defined in the org.eclipse.edt.rui.widgets_0.7.0 cannot be resolved - Paul MAJOR: Bug *356153 - The default RUI handler created by RUIHandler creation wizard cannot be displayed in the VE - Forest/Jimmy |
| The button, input box & grid can be drag/drop in VE. |
Blocked in dev & p2 |
MAJOR: * 355624 - Compile Error after creating a client project - Scott/Forest |
| The properties, outline, data view etc can be used. |
Blocked in dev & p2 |
* 355624 |
| Create interface, service part & set binding information in the dd file. |
Failed in P2 build |
Middle: 356046: The Java code for EGL interfaces cannot be generated. - Matt - Resolved, but not included in the nightly build |
| Run service call in preview mode. |
Blocked in dev & p2 |
Service Invocation problem in the preview tab of visual editor - Joe/Justin |
| Debug RUI handler & service (step over & into etc) |
Blocked in dev & p2 |
* 355624 |
| Deploy the RUI handler to the Tomcat |
Blocked in dev & p2 |
* 355624 |
| Deploy the service to the Tomcat |
Failed in P2 build |
MAJOR: Bug 356140 - The runtime JAR file is not copied in the service deployment - Jimmy Minor: Bug 356141 - The contents of web.xml is not correct if no RUIHandler is configured in the DD file - Jimmy |
| Run the application |
Blocked in dev & p2 |
* 355624 |
| The service call with database |
Blocked in dev & p2 |
Not know the test scenario - Tony/Zhi |
Green thread scenario
1. Create EGL web client with service project
1. Create an EGL Project
2. type base package "org.eclipse.edt.greenthread.helloworld"
3. Select "Web Client With Service Project" as the project template
4. Add "Dojo Widget" (dojotoolkit.org) and RUI UI widgets (0.7.0) into the RUI widget libraries list
5. Press "Finish"
6. There should be a directory whose structure as follows
[base package name].client (configured for JavaScript gen)
[base package name].server (configured for Java gen)
[base package name].common (configured for both JavaScript and Java gen)"
2. Create RUI handler and the default handler created by the wizard can be opened successfully by VE
1. User enters name and package for a new RUIHandler.
2. System creates the EGL part and then opens it in the Rich UI Editor
3. Switch to Design, Source and preview tab to check if editor shows the proper content
3. The button, input box & grid can be drag/drop in VE
1. Drag a Button in the grid layout from palette, Set the text to "Call Service" in properties view
2. Use the EGL Source editor to instantiate a Dialog whose children include a Box named "content".
3. Drag an input box and set the properties
4. The properties, outline, data view etc can be used
1. In properties view, add a click event process function for the button we created above.
2. Show the dialog in the click event function above.
3. Check outline and preview view
5. Create service part & set binding information in the dd file.
1. Create an interface
2. Create a new service and implement the interface created in previous step, specifying package and part name.
3. Use the EGL editor to implement a function that returns a string by concatenating Hello, to whatever is passed in.
4. Extract EGL Service interface
5. Add a service client binding in egl dd file
6. Run service call in preview mode.
1. Open RUI handler, in the event handler function (created above), use code completion to instantiate the service.
2. Use EGL's call statement to invoke the service, specifying that it returns to a callback function that does not yet exist.
3. Use the EGL Editor's Quick Fix to automatically define the callback function.
4. Implement the callback function to instantiate a textfield containing the service result and programmatically add it to the children of the dialog's UI (which again is a Box named content)
5. switch back to preview tab to exercise a running instance of their UI.
7. Debug RUI handler & service (step over) & (step into) etc.
1. In the EGL Editor, the User sets breakpoints on both the service invocation as well as the function that implements the service.
2. From the preview pane, the user hits the Debug button to launch the UI in an external instance of their system browser.
3. exercise Step into/step return/step over feature
4. exercise resume/suspend/terminate feature
5. verify the debug call stack tree, variables, breakpoints and expression view for the above debug operation
8. Deploy the RUI handler/service to the Tomcat
1. User right clicks on the egl dd file and chooses "Deploy".
2. System responds that there is no target (project), and prompts user to create one. From the deployment descriptor, the user specifies the target project by creating a new Dynamic Web Project and chooses Tomcat 6.0 as their target runtime.
3. User clicks on the Deploy button in the descriptor to deploy the project to the target Dynamic Web Project.
9. Run the application
1. User right-clicks on the UI HTML file that was generated in the target project, and chooses Run as... Run on Server.
2. System gives the user a choice of web servers on which to run, and then publishes to that server and launches the HTML in a browser.