!! Warning on javax.security classes !!

Question

WARNING: be aware that weblogic.jar in WLS 6.1 contains at least one class
from the javax.security package that has been customized by Bea and is
significantly different (i.e. incompatible) from the class provided in the
'official' Sun J2EE library.
The particular class we have examined is javax.security.auth.Subject, which
is used to carry security details for a subject (person, etc). This is used
when authenticating client log-ins with WebLogic server security. No doubt
Bea obtained permission from Sun to break the usual licence agreements and
release a custom version of the class in the same package, but this seems to
negate the whole concept of Java packages and has cost us a lot of time and
expense to unravel.
We have spent considerable time trying to trace the cause of an
IncompatibleClassException thrown by WLS when our clients attempted to
log-in. We eventually discovered that the server was picking up the
'official' Sun version of javax.security.auth.Subject.class from the Java
bootclasspath, whereas the clients were sending the WebLogic custom version
of javax.security.auth.Subject.class from weblogic.jar. The two versions are
terminally incompatible.
I would be interested to hear a realistic justification for this kind of
package abuse...
Dave

Answer 1

Hi
Frank reply is as follows
Hi,
ADF UI components use peer classes to adopt to different browser behaviors. The request issued by ADF Faces for its server communication is through the XMLHttpRequest object (unless its a GET request for the initial page load. All subsequent requestst are either partial XMLHttpRequest requests of JSF postback requests)
Frank
I am not able to understand the solution what is he trying to say.. Could you please explain like what should i change in my code to avoid that security error
Regards
Zarrakh