You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2002/10/24 23:19:51 UTC
DO NOT REPLY [Bug 1930] -
Problem with extensions using Weblogic 6.X and JBoss
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1930>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1930
Problem with extensions using Weblogic 6.X and JBoss
mkwan@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From mkwan@ca.ibm.com 2002-10-24 21:19 -------
This is most likely a problem in the way WebLogic did the class renaming. It is
not a problem in Xalan itself.
The piece of code that triggers the exception is in
MethodResolver.getElementMethod():
if ( (paramTypes.length == 2)
&& paramTypes[1].isAssignableFrom
(org.apache.xalan.templates.ElemExtensionCall.class)
&& paramTypes[0].isAssignableFrom
(org.apache.xalan.extensions.XSLProcessorContext.class) )
The only possibility for the failure is that when WebLogic renamed the Xalan
classes, they forgot to rename some of the hard-coded class names (like
org.apache.xalan.templates.ElemExtensionCall) in the java code, thus the class
matching criteria failed.