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

Bug 377424

Summary:	Hooking an Entrypoint to a branding does not work
Product:	[RT] RAP	Reporter:	Holger Staudacher <holger.staudacher>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	sa
Version:	1.5
Target Milestone:	2.0 M3
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:	393419
Bug Blocks:

Description Holger Staudacher

2012-04-23 12:05:16 EDT

Stepps to reproduce: 

1) Register a Entrypoint by extension. Add a path attribute
2) create a branding
3) set the defaultEntryPointId of the branding to the previously created Entrypoint
4) Launch app and use the servletName from the branding in the browser
5) Enjoy the 500

Comment 1 Ralf Sternberg

2012-04-24 08:37:45 EDT

Apparently, entrypoints registered by *path* don't work as default entrypoints in a branding. Only entrypoints registered by *parameter* can be used as default entrypoint. IApplications also work as expected. So we don't have a regression.

Entrypoints by path are meant as an alternative to brandings with default entrypoint. So using an entrypoint-by-path as default entrypoint doesn't seem to make much sense. However, this restriction is not obvious and should at least be documented.

Thoughts?

Comment 2 Rüdiger Herrmann

2012-11-04 09:32:08 EST

From my understanding this bug has become obsolete since default entry points are gone (see bug 393419).
Please reopen if you disagree.