Description Sureshbabu Thyagarajan 2003-10-21 12:10:53 EDT

While using IBM's WSADv511 in RedHat8.0 GTK we had a NPE error. We reported
to IBM developemt. They came back and said that it as a Bugzilla defect. Please
find the our comments as follows. Please let us know if you need more 
information.
==============
In 924_1915 Linux AD build, Running in RedHat8.0 GTK:
After importing an EAR file V5SurveyEAR.ear  (which works fine in AD v51  & 
also in ADv511), While
changing the Server Target options we see NPE errors in the command prompt 
window.
Please let us know if you need this EAR file. We can mail it to you. You could 
create it instantly.

Steps to Recreate the Error:
Before importing the Appln,  Make sure that the J2EE 1.3 is selected & Server 
targeting is Enabled under J2EE preferences.  
While importing the Appln: Choose "<none> No Target Server" as the server. 
Right click the EAR module and Select the "Target Server" option. Then Modify 
the server target as "Exp5.1".  As soon as we do 
that, we see lots of error throw in the task view. This is understandable since 
Express cannot handle EJBs.
Then, Right click the EJB module and Select the "Target Server" option. Then 
Modify the server target as "WAS5.1".  
 
At this time, we also noticed a NPE thrown in the command prompt window.
====================
java.lang.NullPointerException
        at java.lang.Throwable.<init>(Throwable.java)
        at java.lang.Throwable.<init>(Throwable.java)
        at java.lang.NullPointerException.<init>(NullPointerException.java:63)
        at org.eclipse.jdt.internal.core.index.impl.Util.quickSort(Util.java)
        at org.eclipse.jdt.internal.core.index.impl.Util.sort(Util.java:292)
        at org.eclipse.jdt.internal.core.index.impl.InMemoryIndex.getSortedWordE
ntries(InMemoryIndex.java:134)
        at org.eclipse.jdt.internal.core.index.impl.SimpleIndexInput.open(Simple
IndexInput.java:118)
        at org.eclipse.jdt.internal.core.index.impl.MergeFactory.merge(MergeFact
ory.java:78)
        at org.eclipse.jdt.internal.core.index.impl.Index.merge(Index.java:243)
        at org.eclipse.jdt.internal.core.index.impl.Index.save(Index.java:348)
        at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(
IndexManager.java:453)
        at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execu
te(AddJarFileToIndex.java)
        at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobMan
ager.java:360)
        at java.lang.Thread.run(Thread.java:802)

    <Note by suresht (Thyagarajan, Sureshbabu), 2003/09/25 17:44:52, seq: 2 
rel: 0  action: assign>
Assigning as per my ST chat with Vijay. Please
assign to the right team. Thx for yr help Vijay.
Old Owner: couch
New Owner: danberg

Old Component: wsa.etools.rsc.subuilder
New Component: wsa.ejb.projectsupport



    <Note by danberg (Berg, Daniel), 2003/09/25 19:32:13, seq: 3 rel: 0  
action: assign>
This is a JDT problem and not a problem
with a WSAD component.  A Bugzilla defect
should be opened.
Old Component: wsa.ejb.projectsupport
New Component: wsa.prereq.workbench