You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 30, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 30, 2019. It is now read-only.
IllegalArgumentException from MergingSearchEngine.merge(MergingSearchEngine.java:91) #22
jglick said:
Obviously a high priority; 252 duplicates.
Error reporting in jh.jar is abysmal. MergingSearchEngine.engines is apparently
permitted to contain null, which it should not;
MergingSearchEngine(NavigatorView) ought to throw IAE in case it cannot
construct the engine. makeEngine can just return null, which it should not -
should throw IAE with a descriptive message in case params == null, or in case
!params.containsKey("data"), or in case konstructor.newInstance(args) throws
InvocationTargetException (do not use System.err or printStackTrace). Should
assume JDK 1.4+ and use exception causes properly - never swallow a throwable
and throw a fresh Error!
Activity
glassfishrobot commentedon Feb 26, 2008
Reported by mslama
glassfishrobot commentedon Feb 26, 2008
Was assigned to javahelp-issues
glassfishrobot commentedon Dec 12, 2008
jglick said:
Obviously a high priority; 252 duplicates.
Error reporting in jh.jar is abysmal. MergingSearchEngine.engines is apparently
permitted to contain null, which it should not;
MergingSearchEngine(NavigatorView) ought to throw IAE in case it cannot
construct the engine. makeEngine can just return null, which it should not -
should throw IAE with a descriptive message in case params == null, or in case
!params.containsKey("data"), or in case konstructor.newInstance(args) throws
InvocationTargetException (do not use System.err or printStackTrace). Should
assume JDK 1.4+ and use exception causes properly - never swallow a throwable
and throw a fresh Error!
glassfishrobot commentedon Apr 26, 2017
This issue was imported from java.net JIRA JAVAHELP-22