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

Bug 359762

Summary:	[user] do we need util.setUserName
Product:	[ECD] Orion	Reporter:	Susan McCourt <susan>
Component:	Client	Assignee:	Susan McCourt <susan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	malgorzata.tomczyk, Szymon.Brandys
Version:	unspecified
Target Milestone:	0.4 M2
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:	359619
Bug Blocks:

Description Susan McCourt

2011-10-03 15:58:25 EDT

we have code right now that caches the user name (and I just added code to ensure the LoginDialog keeps it up to date).

But do we really need this utility any more at all?

We were using it to show the user name in places like breadcrumbs, etc.  If we decide we aren't showing the user name in places like that anymore, we should remove the methods and the code that keeps the cache up to date.

I'd like to see the outcome of bug 349531 before we toss this.

Comment 1 Szymon Brandys

2011-10-04 03:57:25 EDT

AFAIK it is not used anymore. User names are displayed by plug-ins. Gosia?

Comment 2 Malgorzata Janczarska

2011-10-04 05:41:08 EDT

First of all I think since we support more than one user service at the time there shouldn't be such a method at all. I can see it is used now only if there's only one user service available, for more than one we wouldn't even know which user name to pass to it.
But I can see that there are still some calls of util.getUserName in navigator. We should first finish discussion on Bug 359619, then go on with removing those util functions.

Comment 3 Susan McCourt

2012-01-22 01:42:15 EST

fixed (nav no longer uses these methods).