Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321360 - Application support fails if entry points have the same unqualified name
Summary: Application support fails if entry points have the same unqualified name
Status: RESOLVED FIXED
Alias: None
Product: RAP
Classification: RT
Component: Workbench (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 1.4 M1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 303352
  Show dependency tree
 
Reported: 2010-07-30 11:16 EDT by Matthias Kempka CLA
Modified: 2010-08-31 09:50 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Kempka CLA 2010-07-30 11:16:35 EDT 
Build Identifier: org.eclipse.rap.runtime.sdk_1.3.0.20100615-1704

i.e. include p2 bundles in your launch configuration. They have multiple applications, all with the unqualified name "application". 
This leads to a situation where my application won't start even though I have a unique unqualified application ID.

Reproducible: Always
Comment 1 Ralf Sternberg CLA 2010-08-04 06:51:27 EDT 
This is a common naming pattern.
I don't see an alternative to changing the IApplication support to use fully qualified application ids in the URL. This makes URLs look ugly, but you will use a branding in productive use anyway.
Comment 2 Ivan Furnadjiev CLA 2010-08-11 05:22:23 EDT 
Changes are in CVS HEAD. IApplication support now uses fully qualified application ids in the URL.
Comment 3 Ralf Sternberg CLA 2010-08-31 09:50:51 EDT 
I think we should announce this change, e.g. in some "breaking changes" document.