hi
Have you ever noticed that there are several out-of-the-box warnings when running an ADF application in JDeveloper?
Some of them occur for even the simplest straightforward ADF applications [1].
I wonder how to best interpret these warnings.
If the warning is there it must have some importance, otherwise is should not be there.
So, one approach could be to consider a warning as something that you better try to do something about.
Taking the warning into consideration, making some change, so that the warning is no longer there.
Another approach could be to consider those warnings as something you can ignore because they don't seem to have a significant impact.
But, how then will you recognize/distinguish a warning (among the other warnings) that does have an impact on what you are trying to achieve?
Any suggestions?
And if you choose not to ignore warnings, the question is [1] what can be done to "resolve" them, make them go away?
- [1] see e.g. these JIRA issues
-- "
12c : Warning : The sensors should be created in a valid ADFContext."
at
https://java.net/jira/browse/ADFEMG-228-- "
12c : Warning : No Main-Class defined in the manifest file of Java Module: empty.jar."
at
https://java.net/jira/browse/ADFEMG-229-- "
12c : Warning : WLServlet annotation is deprecated ... AdsServlet"
at
https://java.net/jira/browse/ADFEMG-230-- "
12c : Warning : The skin selector AFIndexedIcon is not a Skin Icon Object"
at
https://java.net/jira/browse/ADFEMG-231many thanks
Jan Vervecken