JBuilder 2005 patch 4 and JBuilder 2006 compilation problem

[Carl J. Mosca]

I've got a project that compiles OK using JBuilder2005 11.0.236.0 (I
don't recall which update that is).

When I applied patch 4 a while back, I could no longer compile this
project. I got a whole bunch of "Fatal Error: Unable to find package
java.lang in classpath or bootclasspath" errors.

I checked (and changed JDKs) but had no success. After doing a good bit
of digging (and trying suggestions from other postings) I called support
and a case (606387) was opened but ultimately we did not get anywhere.
I was asked to install JBuilder along with the patch on another machine,
which I did. I got the same errors. I uninstalled JBuilder from both
machines and did not install the patch and it compiled OK again (this
may have been a fluke because this problem was intitially intermittent).
Also on both machines I reinstalled the patch, and the errors are back.

Because this could not be reproduced by the support technician, the case
was closed.

JBuilder 2006 arrived yesterday. I installed it and when I compile this
project, my errors are back:

"ADIUtil.java": Fatal Error: Unable to find package java.lang in
classpath or bootclasspath
.
.
.

I have tried JDKs 1.5.0_04_b05 and 1.5.0_03_b07 and both exhibit this
issue. I believe the latter came with 2006.

It's been a while since I played around with this issue. I thought I
would start a fresh attempt to find the problem using 2006. Does anyone
have any clues?

TIA,
Carl

[Lori M Olson [TeamB]]

Post by Carl J. Mosca
I've got a project that compiles OK using JBuilder2005 11.0.236.0 (I
don't recall which update that is).
When I applied patch 4 a while back, I could no longer compile this
project. I got a whole bunch of "Fatal Error: Unable to find package
java.lang in classpath or bootclasspath" errors.
I checked (and changed JDKs) but had no success. After doing a good bit
of digging (and trying suggestions from other postings) I called support
and a case (606387) was opened but ultimately we did not get anywhere. I
was asked to install JBuilder along with the patch on another machine,
which I did. I got the same errors. I uninstalled JBuilder from both
machines and did not install the patch and it compiled OK again (this
may have been a fluke because this problem was intitially intermittent).
Also on both machines I reinstalled the patch, and the errors are back.
Because this could not be reproduced by the support technician, the case
was closed.
JBuilder 2006 arrived yesterday. I installed it and when I compile this
"ADIUtil.java": Fatal Error: Unable to find package java.lang in
classpath or bootclasspath
.
.
.
I have tried JDKs 1.5.0_04_b05 and 1.5.0_03_b07 and both exhibit this
issue. I believe the latter came with 2006.
It's been a while since I played around with this issue. I thought I
would start a fresh attempt to find the problem using 2006. Does anyone
have any clues?
TIA,
Carl

AFAIK, this is always caused by one of 2 things.

1. fubar'd JDK install. I would make sure that you have NO JDK's/JRE's
installed, and then attempt the JBuilder 2006 install again.

2. really fubar'd project file. In this case, copy the source files
from your project into a new directory, and then recreate your project
from scratch in the new directory.

Hopefully one of those 2 things will work for you. I had the same
problem, itermittently, on only one machine last year. I know it is
frustrating.
--
Regards,

Lori Olson [TeamB]

------------

Save yourself, and everyone else, some time and search the
newsgroups and the FAQ-O-Matic before posting your next
question.

Google Advanced Newsgroup Search
http://www.google.ca/advanced_group_search
Other Newsgroup Searches:
http://www.borland.com/newsgroups/ngsearch.html
Joi Ellis's FAQ-O-Matic:
http://www.visi.com/~gyles19/fom-serve/cache/1.html

[Carl J. Mosca]

Post by Lori M Olson [TeamB]
AFAIK, this is always caused by one of 2 things.
1. fubar'd JDK install. I would make sure that you have NO JDK's/JRE's
installed, and then attempt the JBuilder 2006 install again.
2. really fubar'd project file. In this case, copy the source files
from your project into a new directory, and then recreate your project
from scratch in the new directory.
Hopefully one of those 2 things will work for you. I had the same
problem, itermittently, on only one machine last year. I know it is
frustrating.

Lori,

Thanks for the reply. I *think* I can rule out number 2 because (I know
I left out most of the details with the support person) I created a very
small new project and saw the same problem consistently (on two machines).

As for number one, I've got three and four JDKs on my machines right
now. As it happens I will be installing new hard drive in one of them
and I will install the OS, JB 2006, and then my project and see what
happens (of course if that does not work, I can always try #2 again).

Because, like most of us I guess, I tend to set all my machines up the
same way, it stands to reason I would see this more than once. I still
need to find the magic combination because the JDKs and other
development stuff I have is all stuff I intend to put back.

Should have time this weekend...we'll see.

Carl

[Carl J. Mosca]

Well it was almost a week later but I finally got a new machine up and
running. This one is at home, running WinXP with no JDK installed.

I installed JB2006 and copied my project file and need libraries.

Unfortunately I still get the following:

Fatal Error: Unable to find package java.lang in classpath or bootclasspath

I have, in the past and at least on one machine, been able to reproduce
this error with other projects.

Still looking...

[Paul Nichols (TeamB)]

Post by Carl J. Mosca
Well it was almost a week later but I finally got a new machine up and
running. This one is at home, running WinXP with no JDK installed.
I installed JB2006 and copied my project file and need libraries.
Fatal Error: Unable to find package java.lang in classpath or
bootclasspath
I have, in the past and at least on one machine, been able to reproduce
this error with other projects.
Still looking...\

If you cannot find the java.lang package, then this is 9 times out of ten a
JDK problem. I am not saying you do not have a properly pathed JDK on your
machine, but rather that your project is not using a JDK that is complete
or can be found on your machine.

There could be one other problem, of course. I did not see what OS you were
using? Are you using an unsupported OS, like Windows 95, 98, or ME?


Go to Tools Configure and select JDKs. What JDK and version are showing up
as the default for your project? Are you sure that this jdk is on your
machine and pathed correctly?

Is so and you are still having problems, try another JDK. In the same
Window, click New. Point to the path of another JDK (not jre, JSDK).

JBuilder should auto recongnize the version. Does it? If so, save it.

Now go to Projet and Project Properties. Use the new JDK. Try to run again.
Did this solve the problem?

[Carl J. Mosca]

Post by Paul Nichols (TeamB)
If you cannot find the java.lang package, then this is 9 times out of ten a
JDK problem. I am not saying you do not have a properly pathed JDK on your
machine, but rather that your project is not using a JDK that is complete
or can be found on your machine.

I certainly tried that on the two machines back when I opened the ticket
with Borland support (and again recently). I also uninstalled the JDKs
and reinstalled them.

Post by Paul Nichols (TeamB)
There could be one other problem, of course. I did not see what OS you were
using? Are you using an unsupported OS, like Windows 95, 98, or ME?

XP Pro on the first two and XP home on the last one.

Post by Paul Nichols (TeamB)
Go to Tools Configure and select JDKs. What JDK and version are showing up
as the default for your project? Are you sure that this jdk is on your
machine and pathed correctly?

Yes, the versions show up correctly.

Post by Paul Nichols (TeamB)
Is so and you are still having problems, try another JDK. In the same
Window, click New. Point to the path of another JDK (not jre, JSDK).
JBuilder should auto recongnize the version. Does it? If so, save it.

Yes, it does (I've been using JBuilder on and off since it's initial
release so I'm fairly familiar with the process although you might not
think so with this thread). ;-)

Actually I kind of expected to be bitten by a path with a space in it or
an environment variable/path issue.

Post by Paul Nichols (TeamB)
Now go to Projet and Project Properties. Use the new JDK. Try to run again.
Did this solve the problem?

No, it did not.

Tech support also suggested Lori's second option which I had already
done when I called them.

This did not work with JBuilder 2005 and patch 4 but it worked earlier
today on the last machine I reference with JBuilder 2006.

One (significant) point I failed to mention in this thread (but I
certainly mentioned it to the tech support folks) is that this is Web
Service project. I was careful to remove the generated files (and I did
not copy them when I created new proejcts) but since this is the first
time I've gotten it to compiler on 2006, I noticed there are no
generated files (unless I am missing something).

Did this change with 2006 or 2005 patch 4 (or some other time)?

An additional point about the JDKs is that I also have JBuilder X
(Studio for Java 7) on these same two machines. The project (and
others) compiled OK pointing to those same JDKs (before and after
reinstalling them).

One final point to remember (I mention this in the first part of this
thread) is that this problem was intermittent on two machines for a good
bit before the project would not compile at all. I'm not totally sold
on the "create a new project" fix only because the tech had me do that
as well and I saw the same error on a small, newly created project and
that was after removing and reinstalling the JDKs. I imagine it's a
combination of these two possibilities as Lori said in her response.

At least I'm compiling with the latest version of JB again.

Thank you for your help Lori and Paul.

[Paul Nichols [TeamB]]

Post by Carl J. Mosca
One final point to remember (I mention this in the first part of this
thread) is that this problem was intermittent on two machines for a good
bit before the project would not compile at all. I'm not totally sold
on the "create a new project" fix only because the tech had me do that
as well and I saw the same error on a small, newly created project and
that was after removing and reinstalling the JDKs. I imagine it's a
combination of these two possibilities as Lori said in her response.
At least I'm compiling with the latest version of JB again.
Thank you for your help Lori and Paul.

If you are using a Web Services are you using the Axis Web Service and which
version?

I have had problems when I went from Axis 1.1 to 1.2 beta and then to 1.2
final, but I do not remember if they were the same problems as you are
describing or not.

I do remember what I did however. I got the latest version of Axis 1.2 and
copied the jar files into the place where the installed 1.2 Axis beta
version with JB 2005 were installed.

The final Axis 1.2 will not work correctly with the shipped version in JB
2005. I found this was a problem with the Axis beta itself and was
documented on the Apache Axis site. This may be at least part of your
problem as well.

Make a backup of the lib jars for Axis, and copy the new ones from
http://ws.apache.org/axis/ for 1.2 (I have not tried 1.3 and it may create
even more problems). Try a recompile and see what happens. This fixed most
of my Web service problems, hopefully it will work for you as well.

[Carl J. Mosca]

Post by Paul Nichols [TeamB]
If you are using a Web Services are you using the Axis Web Service and which
version?

Yes I am. Currently I am/was working with JB 2006 (I have not been able
to eliminate the compilation issue with JB 2005 patch 4.) I am using
Axis which shipped with 2006 which I believe is version 1.2.1 2349
August 8 2005.

Unfortunately, as of this morning, the project will no longer compile
using JB 2006. My Fatal Error: Unable to find package java.lang in
classpath or bootclasspath has returned.

The last thing I did before I got the error message was to add one more
Axis Web Services Server Configuration (there are now four).

I have three JDK 1.5 versions on this machine and all were usable before
this morning's change.

Post by Paul Nichols [TeamB]
I have had problems when I went from Axis 1.1 to 1.2 beta and then to 1.2
final, but I do not remember if they were the same problems as you are
describing or not.
I do remember what I did however. I got the latest version of Axis 1.2 and
copied the jar files into the place where the installed 1.2 Axis beta
version with JB 2005 were installed.

I'll give this a try using JB 2005.

Post by Paul Nichols [TeamB]
The final Axis 1.2 will not work correctly with the shipped version in JB
2005. I found this was a problem with the Axis beta itself and was
documented on the Apache Axis site. This may be at least part of your
problem as well.

I'm assuming "final Axis 1.2" means final as of JB 2005 shipping (or is
there a specific 1.2 I need to go after?)

Post by Paul Nichols [TeamB]
Make a backup of the lib jars for Axis, and copy the new ones from
http://ws.apache.org/axis/ for 1.2 (I have not tried 1.3 and it may create
even more problems). Try a recompile and see what happens. This fixed most
of my Web service problems, hopefully it will work for you as well.

Thank you Paul...me too.

[Paul Nichols [TeamB]]

Post by Carl J. Mosca

Post by Paul Nichols [TeamB]
If you are using a Web Services are you using the Axis Web Service and
which version?

Yes I am. Currently I am/was working with JB 2006 (I have not been able
to eliminate the compilation issue with JB 2005 patch 4.) I am using
Axis which shipped with 2006 which I believe is version 1.2.1 2349
August 8 2005.

I haven't tried compiling Web Services yet with 2006. Don;t know if any
problems exists or not.

Post by Carl J. Mosca
Unfortunately, as of this morning, the project will no longer compile
using JB 2006. My Fatal Error: Unable to find package java.lang in
classpath or bootclasspath has returned.

That is strange.. I do not know what java.lang would not load.

Post by Carl J. Mosca
The last thing I did before I got the error message was to add one more
Axis Web Services Server Configuration (there are now four).

Ah, then do not let the java.lang message fool you.. One of the things I
hate about XML based configurations, is that bugs are a P.I.T.A. to track
down. Struts, JSF, and Web Services, are a PITA when you have bugs. mOST
OFTEN THAN NOT the error messages you get are not where the errors lie. I
am willing to wager a beer or two :), that the problem is in the XML
deployment file, or in the web.xml file.

Post by Carl J. Mosca
I have three JDK 1.5 versions on this machine and all were usable before
this morning's change.

Don't doubt it, see above.

Post by Carl J. Mosca
I'll give this a try using JB 2005.

Post by Paul Nichols [TeamB]
The final Axis 1.2 will not work correctly with the shipped version in JB
2005. I found this was a problem with the Axis beta itself and was
documented on the Apache Axis site. This may be at least part of your
problem as well.

I'm assuming "final Axis 1.2" means final as of JB 2005 shipping (or is
there a specific 1.2 I need to go after?)

No, that is th one I had problems with when I tried to deploy to the latest
used in TC 5.5 and in JBoss 4.0.1. I changed the ones in JB 2005 to the
downloaded 1.2 final jar files I downloaded from the Apache site and my
problems were resolved. IMPORTANT, MAKE A BACKUP OF ALL REPLACED JAR FILES
FIRST, IN CASE YOU NEED TO REINSTALL AND/OR REPLACE.

[Carl J. Mosca]

Post by Paul Nichols [TeamB]
Ah, then do not let the java.lang message fool you.. One of the things I
hate about XML based configurations, is that bugs are a P.I.T.A. to track
down. Struts, JSF, and Web Services, are a PITA when you have bugs. mOST
OFTEN THAN NOT the error messages you get are not where the errors lie. I
am willing to wager a beer or two :), that the problem is in the XML
deployment file, or in the web.xml file.

It has for a while. Well I'm not getting out to BorCon this year (it's
a new FY) but I'll buy you one or two anyway next time for your time.

Yesterday I deleted all four Web Services Servers, cleaned, then I
recompiled but I still got the error. I restarted JB, did another
clean, still no luck. I repeated that last part and it compiled OK.
Then I recreated all four (one at a time compiling in between). I
compiled several times before I went home (I even got some coding done
in there).

This morning, my error message is back. I suspect you're right about
one of the XML files but I'm not (to my knowledge) changing these in any
way and I'm wondering how they could get corrupted. I do have a
customized server8080.xml file (in the project's tomcat/conf dir) for
debugging but that's got an August date/time stamp on it and I've been
using it all along.

Post by Paul Nichols [TeamB]
IMPORTANT, MAKE A BACKUP OF ALL REPLACED JAR FILES
FIRST, IN CASE YOU NEED TO REINSTALL AND/OR REPLACE.

I've got backups of backups on this one; yesterday I was playing around
with them in order to get CVS to (re)recognize my newly created project
of the same name but that's always a good reminder, thanks. :-)

[Paul Nichols (TeamB)]

Post by Carl J. Mosca
Yesterday I deleted all four Web Services Servers, cleaned, then I
recompiled but I still got the error. I restarted JB, did another
clean, still no luck. I repeated that last part and it compiled OK.
Then I recreated all four (one at a time compiling in between). I
compiled several times before I went home (I even got some coding done
in there).

Next time, try to copy ALL of the xml descriptor files (to another location
of course), BEFORE you compile. Then, compile. If it runs ok, then you are
ok.

Try again. If there is a corruption this time, compare the copied xml
descriptor files with the ones that blew. Are they different? If so, alas
problem solved.

JB has a nasty habit of changing XML descriptor files (Deployment EJB
descriptors, Web Services, and even web.xml files for no apparent reason
(well it has one, it thinks they are incorrect, or not well formed, even
when they may be. :) ).

If you find this to be a problem, I'll take a raincheck on the brew :)

I still believe the problem is the xml descriptor and/or deployment files. I
know, it will drive you NUTS, but it won't be the first time, I have had
similar problems when dealing with complex descriptor or deployment files.

[Carl J. Mosca]

This problem is once again intermittent. Currently I do not have to
delete the Web Services Server configurations. I am simply cleaning and
restarting JBuilder and it compiles OK.

I have not been able to find any differences in any of the XML files

(comparing them when I do and do not get the "Any/EveryClass.java":
Fatal Error: Unable to find package java.lang in classpath or
bootclasspath error)