topic UnsupportedOperationException when invoking a ws in workflow in Alfresco Archive

UnsupportedOperationException when invoking a ws in workflow

bluerain — Wed, 06 Apr 2011 23:52:26 GMT

I am trying to invoke a webservice (soap 1.2 based) from my workflowand I am getting an error java.lang.UnsupportedOperationException: Only document-style SOAP 1.1 http are supported for auto-selection of endpoint; none were found.at org.apache.cxf.endpoint.ClientImpl.findEndpoint(ClientImpl.java:21

Re: UnsupportedOperationException when invoking a ws in workflow

ronald_van_kuij — Thu, 07 Apr 2011 06:26:18 GMT

Is your code similar or identical? Have you tried searching on google since it does not seem Activiti related and the real error seems kind of clear.

Re: UnsupportedOperationException when invoking a ws in workflow

bluerain — Thu, 07 Apr 2011 16:50:51 GMT

yes it is identical.
and what I think the reason for the error (found on google) is probably the webservice I am trying to invoke is a soap 1.2 compliant and I am using the JaxWsDynamicClientFactory dcf = JaxWsDynamicClientFactory.newInstance();
Client client = dcf.createClient(wsdlString);

which is for soap 1.1 compliant…Hence the error !!
So my question is what is activiti way of invoking a soap 1.2 compliant webservice?

Re: UnsupportedOperationException when invoking a ws in workflow

ronald_van_kuij — Thu, 07 Apr 2011 17:00:55 GMT

One of the options is to do it from java like in the example but use the cxf soap 1.2 way… But I think you already figured that out, tried it and failed, right?

Re: UnsupportedOperationException when invoking a ws in workflow

bluerain — Sat, 09 Apr 2011 20:47:52 GMT

I found out a way which is something like this

JaxWsProxyFactoryBean factory = new JaxWsProxyFactoryBean();
factory.setServiceClass(ChangePurchaseOrderPortType.class);
factory.setAddress(wsdlString);
ChangePurchaseOrderPortType service = (ChangePurchaseOrderPortType) factory.create();

Object response = service.changePurchaseOrder((ChangePurchaseOrderRequestType)parameters.getValue(execution));

But this approach is tightly coupled with the operation name. Is there anyother way that you can suggest?