Matthias Jacob wrote:
>Alex Boisvert wrote:
>> On Tue, Apr 14, 2009 at 8:26 AM, Matthieu Riou
>> <[email protected]>wrote:
>>
>>> On Tue, Apr 14, 2009 at 8:17 AM, Jacob, Matthias <
>>> [email protected]> wrote:
>>>
>>>> Hi all,
>>>>
>>>> I have to deploy processes automatically to ODE (I am using v1.2)
>>>> instead of copying the zip file manually into the right folder.
>>>> Therefore, I tried to use ODE`s DeploymentService and its "deploy"
>>>> operation, but both the Axis and JAX-WS client stubs are not able to
>>>> process the service response correctly (using the Apache Axis 1.4 Apr
>>>> 22, 2006 (06:55:48 PDT) WSDL2Java emitter and Metro with JAX-WS RI
>>>> 2.1.4.1).
>>>
>>> I believe this has been fixed in the 1.X branch.
>>
>>
>>
>> Correct. See https://issues.apache.org/jira/browse/ODE-517
>>
>> alex
>>
>
>Thanks for the hint. As I read from the ticket, the patch will be included in
>the 1.3 and the 2.0 releases. But there is currently no stable (beta) release
>that includes this patch, right? In that case, should I try the latest stable
>nightly build instead?
>
>Matthias
I have tried one of the latest stable nightly builds now, one that I downloaded
the day before yesterday (CEST). The DeploymentService responses are okay,
although there still seems to be a bug in the DeploymentService WSDL.
The DeploymentService is specified by the WSDL as the following:
...
<wsdl:service name="DeploymentService">
<wsdl:port name="DeploymentPort" binding="tns:DeploymentBinding">
<soap:address location="http://localhost:8080/ode/services/deploy"/>
</wsdl:port>
</wsdl:service>
...
However, the SOAP port for the DeploymentService is currently located under
http://localhost:8080/ode/processes/DeploymentService instead of
http://localhost:8080/ode/services/deploy.
Matthias
