Re: [Soaplab2-dev] description for the dashboard

[Peter E. <P....@dk...>]

On Wed, 31 May 2006, Martin Senger wrote:

> > Martin, do we have any plans to use literal encoding in Soaplab2?
> >
>    I do not know. Some times ago I spoke with Peter about it - but I am
> still not sure. Perhaps for derived services.


I changed the derived services to document/literal and left the others to
rpc/rpc. 

I am using derived services only, but the Soaplab building process
communicates with /axis/services/AnalysisFactory, and this communication
failed, when I changed the style of non-derived services to
document/literal.

I did not investigate this problem any further.


In general, what are the reasons to stick with the (more complicated) 
rpc/rpc compared to document/literal? 

Does rpc/rpc provide features, missing in document/literal but
necessary or good to have in Soaplab?

In fact, I don't think that the communication style is an important
issue for Soaplab code. I guess that most, if not all, differences
between those 2 styles can be hidden from Soaplab by Axis.

I believe, it will be easy to make the style configurable to the
site administrator.

I have not commit it to the soaplab-cvs-branch, yet, but I added to my
building process (build.xml) a deployment-descriptor-template, that
contains the information about the style to use by Axis, e.g.:

 <service xmlns:tns="{$nsURI}" name="{$xmlFullName}" provider="java:RPC" style="wrapped" use="literal">

  <parameter name="wsdlServiceElement" value="{$shortName}Service"/>
  <parameter name="allowedMethods" value="runAndWaitFor createAndRun waitFor getStatus getResults"/>
 [.....]
 </service>

Regards,

	Peter