Hi Dan,
I went through the code and debug the test.
Current CXF treat the wrong SEI as POJO SEI. It creates the client proxy
and service model for the Foo.class, and so the test will not get the
excepted WebServiceException from Jaxws API.
And ManagedConnectionImpl.getCXFServiceFromBus() will not throw the
ResourceAdapterInternalException for it.
I think it is OK to disable this test, because CXF now can create client
for POJO SEI.
Cheers,
Willem.
Willem Jiang wrote:
Hi Dan,
The test is for getting the connection when it was passed a wrong SEI
class.
The exception is thrown by
ManagedConnectionImpl.getCXFServiceFromBus() which use the Jaxws API
to create the client proxy.
Cheers,
Willem.
Dan Diephouse wrote:
Hiya,
I made some changes to consolidate the code in ServiceImpl &
JaxWsProxy/ClientFactoryBeans. However, this seems to have broken a JCA
test. The code is this:
try {
mci.getConnection(subj, cri);
fail("Expected ResourceAdapterInternalException");
} catch (ResourceAdapterInternalException raie) {
assertTrue("asserting ResourceException.", raie.getMessage()
.indexOf("Failed to create proxy") != -1);
}
Why should there be a ResourceAdapterInternalException? I don't
really see
where this could even be throw from. Can anyone point me into the right
direction so I can fix this?
Thanks,
- Dan
