Thank you for your reply Rajagopal,
The proceedure you describe is what I did first but it didn't work.
If you were to download the HTTPClient zip file, you may be able to see where I am going wrong.
After extracting all the files within it, you will see that the zip file doesn't contain any jar files. The directory structure is...
HTTPClient
|________ ( Files ) Lots of java/class files ( the main ones I need )
|________ ...
|________ ( Folder ) alt
|________ ( Folder )
doc |________ ( Folder ) http
|________ ( Folder ) https
|________ ( Folder ) shttp
In BlueJ, referencing the root HTTPClient folder is enough for BlueJ to recognize the files within the root folder HTTPClient as being 'importable'.
Netbeans is different though.
As you suggest, I create a new library called HTTPClient then..,
I reference folder HTTPClient for the classpath.
I reference folder HTTPClient for the source.
I reference folder HTTPClient.doc for the javadoc.
In the projects window, I add the new HTTPClient library to the libraries folder.
It creates the following file system..,
HTTPClient
|________ ( Folder ) default folder ( this contains the needed files )
|________ ( Folder ) alt
|________ ( Folder ) doc
|________ ( Folder ) http
|________ ( Folder ) https
|________ ( Folder ) shttp
When I use a class such as HTTPConnection which is at HTTPClient.HTTPConnection according to the javadoc, Netbeans says "package HTTPClient cannot be found". When I run fix imports, netbeans adds import statements such as import HTTPClient.HTTPConnection, then flags them as errors, saying "package HTTPClient cannot be found".
BlueJ just imports HTTPConnection from the root HTTPClient folder.
If you have the time, could you download HTTPClient and see if you can get it to work within netbeans as a library. The download is tiny and includes some small example source code files.
Thank you for your help so far.
Darren
[ January 31, 2006: Message edited by: D R Wilkinson ]