Re: [Mantisbt-soap-dev] Using mantis-axis-soap-client vs MantisConnect library

[Adi L. <al...@ap...>]

Hi Robert,
Thanks for the info.
I have a few questions related to the info you provided:
1. Maybe a trivial question, but how do you refresh the library when the
WSDL changes?
2. I suppose the client will not work with older versions of MantisBT
(hence its SOAP API) that were downloaded by people (which did not make the
effort to upgrade). Am I right? Do you know the change-log of the API?
3. Is it compatible both with the on-premise version and the hosted one
(MantisHub)?

Thanks,
Adi


On Fri, Jun 13, 2014 at 12:24 PM, Robert Munteanu <rob...@gm...
> wrote:

> Hi Adi,
>
> (+mantisbt-soap-dev, this might be interesting to more people )
>
> On Wed, Jun 11, 2014 at 10:41 AM, Adi Lavi <al...@ap...> wrote:
>
> > My question is what would you advise of using. I noticed that
> MantisConnect
> > is a lot moire active, but seems to lack some of the functionality that's
> > supported by the SOAP API, and do exist in your library. My concern is
> how
> > much (if any) do you maintain your code and keep it up-to-date with
> Mantis
> > API. The low activity level is a risk in my view.
>
> The mantis-axis-soap-project simply generates the Axis 1 stubs from
> the WSDL . It is refreshed whenever needed, that is when the WSDL
> changes in a MantisBT release. As such, it does not really see a high
> level of activity.
>
> As for MantisConnect, I don't expect it to work with the current
> MantisBT version, since its last release was in 2010 [1].
>
> So my advice is to use the mantis-axis-soap-project project.
>
> Thanks,
>
> Robert
>
>
> [1]: http://sourceforge.net/projects/mantisconnect/files/
>
>
> --
> http://robert.muntea.nu/
>