Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 359361

Summary:

Default handler created in the default package displays blank in VE

Product:

z_Archived

Reporter:

fahua jin <jinfahua>

Component:

EDT

Assignee:

Huang Ji Yong <hjiyong>

Status:

CLOSED FIXED

QA Contact:

Severity:

major

Priority:

CC:

chenzhh, hjiyong, huozz, smythew, svihovec

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
fix	lasher: iplog+

Description fahua jin

2011-09-29 04:11:57 EDT

Build Identifier: 0.7.0.v201109282102

In a new workspace, create an RUIHandler in the default workspace, and the RUI handler will be opened automatically. You'll find the RUIHandler is a blank page even after cleaning workspace & pressing refresh button.

Reproducible: Always

Comment 1 Huo Zhen Zhong

2011-10-13 04:46:15 EDT

Hi, Brian

I remember RUI does not support a handler in default package, is that right?

Comment 2 Brian Svihovec

2011-10-13 14:39:29 EDT

I ran a test in RBD, and you are allowed to define a part in the Default package, and it will render correctly.  

I think what we are remembering an issue with RBD where someone was trying to import parts from the Default package from a part that was not in the default package.  In RBD and EDT, the only parts that can 'import' parts from the default package are those parts that are already defined in the default package.  

This particular issue appears to be related to the fact that there is no package name, so references to the generated part are incorrect:

egl.rootHandler = new egl..DefaultTest(); 

This should probably be routed to deployment.

Comment 3 Huo Zhen Zhong

2011-10-14 02:12:56 EDT

Change the owner to Scott because it is the generated js problem.

Comment 4 fahua jin

2011-11-02 21:10:21 EDT

(In reply to comment #3)
> Change the owner to Scott because it is the generated js problem.

Set the component to the JSGen according to the comment 3.

Comment 5 Will Smythe

2011-11-03 23:23:09 EDT

Think this needs to be fixed for 0.7. If the fix is too risky, we should at least prevent the developer from creating handlers/widgets in the default package (so, don't let developer complete the wizard if the package name is not set). We should only do this if the real problem cannot be resolved for 0.7.

Also, not sure it's the same issue, but if you have a widget defined in the default package and try to reference that widget from a handler defined in another package, you get a compile error in the handler (The type myFirstWidgtet cannot be resolved.)

Comment 6 Brian Svihovec

2011-11-04 10:41:32 EDT

It is not valid to reference a part in the default package from a non-default package:
http://publib.boulder.ibm.com/infocenter/rbdhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.egl.lr.doc%2Ftopics%2Fregl_core_package.html

Comment 7 Huang Ji Yong

2011-11-06 22:18:44 EST

Created attachment 206504 [details]
fix

Comment 8 Huang Ji Yong

2011-11-06 22:19:34 EST

Fix both problem for html gen and js gen when package name is empty.

Comment 9 fahua jin

2011-11-07 21:25:24 EST

Verified in 0.7.0.v201111071403.