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

Bug 422030

Summary:	Updating the migration help guide
Product:	[RT] RAP	Reporter:	Daniel Keck <danielkeck>
Component:	Website	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	ivan, rsternberg
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Daniel Keck

2013-11-19 04:02:48 EST

Could someone please update the migration guide http://eclipse.org/rap/noteworthy/2.0/migration-guide/ so that in case the following error occurs:
"Could not register entry point 'package.Class' with id 'package.entrypoint'.
java.lang.NullPointerException: The parameter 'path' must not be null."
Google pushes one to the page mentioned above. Background: It took me too much time to figure out what was wrong while migrating parts of a project from 1.4 to 2.1 since I thought internal paths became obsolete.

Comment 1 Ivan Furnadjiev

2013-11-19 04:13:50 EST

I read the "Migration Guide" again it's up to date. Did you read "Register EntryPoint and IApplication" chapter. Could you provide your plugin.xml?

Comment 2 Daniel Keck

2013-11-19 04:25:46 EST

Yes, its up to date. It would be nice if the occurring error could be indexed by google search engine so if one types at Google search "NullPointerException path must not be null RAP" the migration guide will be under the first pages to be shown as the search result. The problem is that it I came just by chance across the migration guide to find the proper solution there.

Comment 3 Ralf Sternberg

2013-11-19 06:16:03 EST

You've already put a trace for search engines by creating this bug report ;-)

Honestly, I don't think that we should include all possible exceptions into the developer's guide. But there are two options:

1) We (or you) could add an entry to the troubleshooting section of our FAQ [1] and point to the migration guide.

2) If the exception is not understandable (e.g. because you're using an extension point), we could think about throwing a more self-explanatory exception.

Would that help?

[1] http://wiki.eclipse.org/RAP/FAQ#Troubleshooting

Comment 4 Daniel Keck

2013-11-19 07:35:45 EST

I agree with you in every point (search engine trace, error msg). I think suggestion 2 is nice for any further release. I just asked for that specific error because it would have been so easy to solve by just applying Rule#1: RTFM.
Thanks Ivan and Ralf.