You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "willem Jiang (JIRA)" <ji...@apache.org> on 2006/10/24 10:01:17 UTC
[jira] Commented: (CXF-164) EndpointInvocationHandler doesn't
support cache mechanism
[ http://issues.apache.org/jira/browse/CXF-164?page=comments#action_12444240 ]
willem Jiang commented on CXF-164:
----------------------------------
JCA Application server implementation had an connection pool to cache the created connection, so the hash() method will be called by Application Server .
In the EndpointInvocationHandler the hash() method was treated as the proxy object wsdl operation,
and will throw a WebServiceException "Could not find operation info for web method"
so we need to take out Object class base method in the Handler when the proxy object was created by container to avoid this execption.
> EndpointInvocationHandler doesn't support cache mechanism
> ---------------------------------------------------------
>
> Key: CXF-164
> URL: http://issues.apache.org/jira/browse/CXF-164
> Project: CXF
> Issue Type: Bug
> Affects Versions: 2.0-M1
> Reporter: unrealjiang
> Attachments: jaxws_Endpoint_CXF-164.patch
>
>
> EndpointInvocationHandler doesn't support cache mechanism. If an application need cache an endpoint like jca connection management, EndpintInvocation can not return a correct result.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira