You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/07/23 18:29:08 UTC

DO NOT REPLY [Bug 21831] New: - Mismatch between handler interfaces

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=21831>.
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=21831

Mismatch between handler interfaces

           Summary: Mismatch between handler interfaces
           Product: Axis
           Version: 1.1
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Basic Architecture
        AssignedTo: axis-dev@ws.apache.org
        ReportedBy: arh14@cornell.edu


Axis seems to have a mismatch between client and server handler interfaces it 
supports.  On the client side it requires the Sun-style 
javax.xml.rpc.handler.Handler interface for client handlers 
(HandlerChainImpl.newHandler:177).  On the server side, it requires the Axis-
specific org.apache.axis.Handler interface 
(WSDDDeployableItem.makeNewInstance:338).  If the classes do not match, 
ClassCastExceptions are thrown.

This requires maintaining handlers that support distinct and incompatible 
(neither extends the other) Handler interfaces.

I would prefer that Axis be standardized the Sun java.xml.rpc.handler.Handler 
interface, or at least some extension thereof.