MantisConnect: method 'mc_issue_update' not defined

Post about your customizations to share with others.

Moderators: Developer, Contributor

Post Reply
gmichaud
Posts: 9
Joined: 22 Dec 2006, 09:29

MantisConnect: method 'mc_issue_update' not defined

Post by gmichaud »

1. I've downloaded from CVS the last MantisConnect *.cs files
2. I've used Nant to make a DLL successfully
3. I've downloaded from CVS the last Webservice PHP files
4. I've instanciated with success a Request object
5. Request.IssueGet method works fine, for example
6. But when a call is made to Request.IssueUpdate...

L'exception System.Web.Services.Protocols.SoapException n'a pas été gérée
Actor=""
Lang=""
Message="method 'mc_issue_update' not defined in service"
Node=""
Role=""
Source="System.Web.Services"
StackTrace:
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Futureware.MantisConnect.MantisConnectWebservice.MantisConnect.mc_issue_update(String username, String password, String issueId, IssueData issue)
at Futureware.MantisConnect.Request.IssueUpdate(Issue issue)
at QCM.M.Exists(Object s, Object Bug) in D:\Documents\Visual Studio 2005\Projects\QCM\QCM\M.vb:line 36
at QCM.M.SetDefects(Object s, Object BugList) in D:\Documents\Visual Studio 2005\Projects\QCM\QCM\M.vb:line 48
at QCM.Module1.Main() in D:\Documents\Visual Studio 2005\Projects\QCM\QCM\Module1.vb:line 56
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Any ideas?
:-)
vboctor
Site Admin
Posts: 1293
Joined: 13 Feb 2005, 22:11
Location: Redmond, Washington
Contact:

Post by vboctor »

The latest MantisConnect code is on SVN repository rather than the CVS repository.
gmichaud
Posts: 9
Joined: 22 Dec 2006, 09:29

SVN

Post by gmichaud »

Indeed, and I don't understand why CVS isn't used anymore :-)
Anyway, Nant has failed on my environment to compile the files extracted from SVN. But the problem noticed in my last post has been resolved: it was only because I was enough stupid to use a wrong version of the Webservice...
Post Reply