This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 220639 - Provide integration with Run on Server to launch web UI in Eclipse web browser
Summary: Provide integration with Run on Server to launch web UI in Eclipse web browser
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David Whiteman CLA
QA Contact:
URL: http://wiki.eclipse.org/COSMOS_Design...
Whiteboard:
Keywords:
Depends on: 226381 234379
Blocks:
  Show dependency tree
 
Reported: 2008-02-27 14:10 EST by David Whiteman CLA
Modified: 2012-01-03 13:53 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Whiteman CLA 2008-02-27 14:10:56 EST
It would be very nice to automatically launch the COSMOS web UI within the integrated Eclipse web browser when the developer selects Run on Server for the data manager project built using the toolkit.
Comment 1 David Whiteman CLA 2008-02-27 14:20:38 EST
Note that this is only applicable to the J2EE flavor of the toolkit using WTP.  It's possible we could provide similar capability in the OSGi flavor of the toolkit, but the implementation and externals would be different.
Comment 2 David Whiteman CLA 2008-03-05 12:01:25 EST
investigate whether this works on linux
Comment 3 David Whiteman CLA 2008-04-14 20:06:01 EDT
This has been moved to "future" due to instability in the design.  We have developed a plugin to display the web UI, but there is still the missing piece of registering the MDR with a broker so that it will be available in the UI.  In the absence of having a full review of this design change, and so I can focus on bug 224215, this will have to wait.
Comment 4 David Whiteman CLA 2008-04-30 10:39:53 EDT
Mark would like this to launch the web UI as part of Run on Server, since this is the pattern for how dynamic web projects work.  The initial impl would just allow you to see the MDR and execute a query against it.  In the future we would like to support incremental development with this.

To make the MDR visible to the web UI, we will need to register the MDR with the broker, and also modify some config files.  Sheldon, can you please identify what needs to be configured for the MDR to function in the web UI?
Comment 5 Sheldon Lee-Loy CLA 2008-04-30 11:45:31 EDT
So the UI directly talks with the MDR and does not need a broker.  If this is the case then We need to develop a data feed that will return the epr for the mdr.

I guess when you call run on server you send a request that contains the epr for the mdr.  

You probably will have to override the Run On Server menu option to send that information.

It would probably take 1 week to configure, package and modify the COSMOSUI to show a single MDR.  I can create a flavor of our COSMOSUI to directly talk to a single MDR.
Comment 6 David Whiteman CLA 2008-04-30 11:59:44 EDT
Why do you say it does not need to register the MDR with a broker?  Wouldn't doing so make it work with less change to the UI code?
Comment 7 Sheldon Lee-Loy CLA 2008-04-30 12:46:48 EDT
There would be less code for the COSMOSUI however probably more code on the eclipse tooling since now you have to deploy the broker and register with the broker.  

I was just thinking of making the environment simpler.

The COSMOS UI code would be an additional JSP, a POJO and some configuration files.
Comment 8 David Whiteman CLA 2008-04-30 13:06:08 EDT
Moved to i11 per Mark's request.
Comment 9 Bill Muldoon CLA 2008-05-16 12:12:53 EDT
I'm assuming that integration with "Run on server" also implies integration with "Debug on Server". And that "debug on server" will include access to the source code (for effective debugging).    Thanks, Bill
Comment 10 David Whiteman CLA 2008-05-16 12:16:50 EDT
Bill, we might want to track the inclusion of source code as a separate task, since we currently didn't have that work in plan for i11.  Unless someone in CA wants to investigate doing this...
Comment 11 David Whiteman CLA 2008-06-13 17:01:39 EDT
Marking as fixed because the code is written, and *should* be written correctly.  Awaiting resolution of a build issue in order to verify it.
Comment 12 David Whiteman CLA 2008-11-05 14:58:02 EST
closing to cleanup bugzilla