DougBreaux 270007SMYJ Visits (1752)
Missing IBM Websphere SSL class
I was simply trying to install an Eclipse plugin from the Eclipse Marketplace into my RAD on one system and RSA on another, but I kept getting this error:
Some web searches find that text. After a few unsuccessful attempts, the "alternative" solution from Cann
I guess RAD started and loaded up the WAS SSL support, but RAD itself isn't fully able to use that.
Note also the warning to "reverse" that activity if you want to run WAS again under RAD.
Relevant but not successful
DougBreaux 270007SMYJ Visits (3849)
(I'm assuming this is the same in stock Eclipse, I don't have it installed right now to confirm.)
If you have any source code that is generated by tooling (say, JAX-WS proxy code), you might have compiler warnings for things that are not considered best-practice. (Maybe they were fine in an earlier version of Java that the tooling still supports but are redundant in a later version.)
If you're like me and you prefer to have clean packages & classes in your IDE, here's a small tip that I somehow missed until recently.
If you place your "generated" source code in a separate source folder, which I like for ease of build process as well as organizational utility, you can also tell RAD to ignore compiler warnings for that source folder.
To do this, right-click on the source folder and go to Properties. Under "Java Compiler", check the "Ignore optional compile problems" setting, and you're done.
DougBreaux 270007SMYJ Visits (7727)
I imagine most folks who use Eclipse or its variants already know about this, but just in case...
User Libraries are reusable groupings of jar files that compose a particular library to be used by an application. This is a much easier way to manage the jars needed by your projects than simply adding them one-at-a-time to the Build Path and/or the WEB-INF/lib directory for execution on a local server.
Creating and Managing User Libraries
Window > Preferences > Java > Build Path > User Libraries
Add as many User Libraries as your applications require. Name them so that you can distinguish versions from each other when you work with applications that use different versions of the same library.
Use the "New" button and type a meaningful name, then the "Add JARs" button to locate specific jar files to include.
You can attach a javadoc URL to a library, which will give you more useful help within Eclipse when you're using that library. Expand the added jar file (the small triangle), select the Javadoc location line, and click the "Edit" button. You can point at either local javadoc files or a remote URL.
Similarly, you can attach a source code file or folder to a library, which will enable you to trace into its source if necessary.
Adding User Libraries to the Build Path
Project > Properties > Java Build Path
Adding User Libraries to the Execution Path (JEE Deployment)
Project > Properties > Deployment Assembly