mantisbt-soap-dev — MantisBT SOAP announcements DL

Re: [Mantisbt-soap-dev] [mantisbt-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Robert M. <rob...@gm...>]

On Thu, Nov 15, 2012 at 10:17 PM, Gianluca Sforna <gi...@gm...> wrote:
> On Thu, Nov 1, 2012 at 9:36 PM, Robert Munteanu
> <rob...@gm...> wrote:
>> 1. What is your opinion about the above plan? I'm interested in
>> developers and users alike
>> 2. If you use the SOAP API, are you able to use the php5 native soap
>> extension if we remove support for using nusoap?
>
> Entreprisey distributions like RHEL/CentOS do not have access to 5.4
> in the repos (both 5 and 6 have access to a 5.3, either in the
> official repository or in the EPEL one).
>
> If we want to play nice with those users we should keep the SOAP API
> workable without requiring 5.4.
>
> Not that I'm advocating keeping nusoap around :) maybe there is a
> compelling replacement implementation we can use instead with a nice
> fallback to the native code when available?

That's a very good point. The current status is

- the SOAP API defaults to the soap extension if available, otherwise
falls back to nusoap
- the soap extension is available on CentOS 5.7 - PHP 5.1 and SLES 11
SP2 - PHP 5.2

I think this should be enough.

Robert

>
> --
> Gianluca Sforna
>
> http://morefedora.blogspot.com
> http://identi.ca/giallu - http://twitter.com/giallu
>
> ------------------------------------------------------------------------------
> Monitor your physical, virtual and cloud infrastructure from a single
> web console. Get in-depth insight into apps, servers, databases, vmware,
> SAP, cloud infrastructure, etc. Download 30-day Free Trial.
> Pricing starts from $795 for 25 servers or applications!
> http://p.sf.net/sfu/zoho_dev2dev_nov
> _______________________________________________
> mantisbt-dev mailing list
> man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev



--
Sent from my (old) computer

Re: [Mantisbt-soap-dev] [mantisbt-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Gianluca S. <gi...@gm...>]

On Thu, Nov 1, 2012 at 9:36 PM, Robert Munteanu
<rob...@gm...> wrote:
> 1. What is your opinion about the above plan? I'm interested in
> developers and users alike
> 2. If you use the SOAP API, are you able to use the php5 native soap
> extension if we remove support for using nusoap?

Entreprisey distributions like RHEL/CentOS do not have access to 5.4
in the repos (both 5 and 6 have access to a 5.3, either in the
official repository or in the EPEL one).

If we want to play nice with those users we should keep the SOAP API
workable without requiring 5.4.

Not that I'm advocating keeping nusoap around :) maybe there is a
compelling replacement implementation we can use instead with a nice
fallback to the native code when available?

--
Gianluca Sforna

http://morefedora.blogspot.com
http://identi.ca/giallu - http://twitter.com/giallu

Re: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Robert M. <rob...@gm...>]

On Sun, Nov 4, 2012 at 10:25 PM, Raúl Luna <sup...@ya...> wrote:
>
>
> I have mantis deployed over windows xp server. If you let me know how to
> check it, I will do ASAP.

Run phpinfo(); inside a php page and see if the 'soap' extension is present.

Robert

>
>
> Raul Luna
> The man who whispered at computers
>
> Robert Munteanu <rob...@gm...> escribió:
>
> Hi Raul,
>
> (+cc back the lists)
>
> The API will remain unchanged after I get this change merged. I'd be
> interested to know if - to your knowledge - the platforms where you
> deploy MantisBT have access to the php soap extension.
>
> If you don't, that's fine :-)
>
> Robert
>
> On Sun, Nov 4, 2012 at 3:15 AM, Raul Luna <sup...@ya...>
> wrote:
>>
>> Hello Robert:
>>
>> I am developing in Java, accessing Mantis services through SOAP. If the
>> new
>> technology will have an easy integration with Java, for me it's okay.
>>
>> Regards,
>>
>> Enviado desde la nevera // Sent from the fridge
>> Raul Luna Rodríguez
>> sup...@ya...
>> ________________________________
>> De: Robert Munteanu <rob...@gm...>
>> Para: "man...@li..."
>> <man...@li...>; developer discussions
>> <man...@li...>
>> Enviado: Jueves, 1 de noviembre, 2012 9:36 P.M.
>> Asunto: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support
>> for
>> php5 native soap extension
>>
>> Hi,
>>
>> (Sorry for the cross-post, I would like to reach a wide audience )
>>
>> I've been working on refreshing the backend of our SOAP API. The API,
>> while reasonably featureful and well working, is based on nusoap. This
>> poses a maintenance burden on us ( see for instance 0014157: Array to
>> string conversion error on soap request with PHP 5.4 [1] which
>> requires to make changes again to support newer PHP versions ) and
>> also brings performance problems ( see 0014672: Slow performance of
>> SOAP calls due to nusuoap [2] ) .
>>
>> I have worked towards getting MantisBT to support both the php5 native
>> soap extension and the nusoap library. The code is now available at my
>> github fork [3]. There is a configuration setting which allows the
>> administrator to control which backend is used.
>>
>> I have the following plan:
>>
>> 1. After 1.2.12 is released, merge the code into master and
>> master-1.2.x . The configuration setting defaults to using nusoap . At
>> this point I would encourage SOAP API users to give it a test.
>> 2. After 1.2.13 is released, switch the configuration setting to
>> default to the soap extension.
>>
>> Depending on user feedback, I would like to remove nusoap completely.
>>
>> I'm interested in two things
>>
>> 1. What is your opinion about the above plan? I'm interested in
>> developers and users alike
>> 2. If you use the SOAP API, are you able to use the php5 native soap
>> extension if we remove support for using nusoap?
>>
>> Thanks,
>>
>> Robert
>>
>> [1]: http://www.mantisbt.org/bugs/view.php?id=14157
>> [2]: http://www.mantisbt.org/bugs/view.php?id=14672
>> [3]: https://github.com/rombert/mantisbt/tree/14871-soap-extension
>> --
>> Sent from my (old) computer
>>
>>
>> ------------------------------------------------------------------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_sfd2d_oct
>> _______________________________________________
>> Mantisbt-soap-dev mailing list
>> Man...@li...
>> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>>
>>
>
>
>
> --
> Sent from my (old) computer



--
Sent from my (old) computer

Re: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Raúl L. <sup...@ya...>]

I have mantis deployed over windows xp server. If you let me know how to check it, I will do ASAP.


Raul Luna
The man who whispered at computersRobert Munteanu <rob...@gm...> escribió:Hi Raul,

(+cc back the lists)

The API will remain unchanged after I get this change merged. I'd be
interested to know if - to your knowledge - the platforms where you
deploy MantisBT have access to the php soap extension.

If you don't, that's fine :-)

Robert

On Sun, Nov 4, 2012 at 3:15 AM, Raul Luna <sup...@ya...> wrote:
>
> Hello Robert:
>
> I am developing in Java, accessing Mantis services through SOAP. If the new
> technology will have an easy integration with Java, for me it's okay.
>
> Regards,
>
> Enviado desde la nevera // Sent from the fridge
> Raul Luna Rodríguez
> sup...@ya...
> ________________________________
> De: Robert Munteanu <rob...@gm...>
> Para: "man...@li..."
> <man...@li...>; developer discussions
> <man...@li...>
> Enviado: Jueves, 1 de noviembre, 2012 9:36 P.M.
> Asunto: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for
> php5 native soap extension
>
> Hi,
>
> (Sorry for the cross-post, I would like to reach a wide audience )
>
> I've been working on refreshing the backend of our SOAP API. The API,
> while reasonably featureful and well working, is based on nusoap. This
> poses a maintenance burden on us ( see for instance 0014157: Array to
> string conversion error on soap request with PHP 5.4 [1] which
> requires to make changes again to support newer PHP versions ) and
> also brings performance problems ( see 0014672: Slow performance of
> SOAP calls due to nusuoap [2] ) .
>
> I have worked towards getting MantisBT to support both the php5 native
> soap extension and the nusoap library. The code is now available at my
> github fork [3]. There is a configuration setting which allows the
> administrator to control which backend is used.
>
> I have the following plan:
>
> 1. After 1.2.12 is released, merge the code into master and
> master-1.2.x . The configuration setting defaults to using nusoap . At
> this point I would encourage SOAP API users to give it a test.
> 2. After 1.2.13 is released, switch the configuration setting to
> default to the soap extension.
>
> Depending on user feedback, I would like to remove nusoap completely.
>
> I'm interested in two things
>
> 1. What is your opinion about the above plan? I'm interested in
> developers and users alike
> 2. If you use the SOAP API, are you able to use the php5 native soap
> extension if we remove support for using nusoap?
>
> Thanks,
>
> Robert
>
> [1]: http://www.mantisbt.org/bugs/view.php?id=14157
> [2]: http://www.mantisbt.org/bugs/view.php?id=14672
> [3]: https://github.com/rombert/mantisbt/tree/14871-soap-extension
> --
> Sent from my (old) computer
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>
>



-- 
Sent from my (old) computer

Re: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Robert M. <rob...@gm...>]

Hi Raul,

(+cc back the lists)

The API will remain unchanged after I get this change merged. I'd be
interested to know if - to your knowledge - the platforms where you
deploy MantisBT have access to the php soap extension.

If you don't, that's fine :-)

Robert

On Sun, Nov 4, 2012 at 3:15 AM, Raul Luna <sup...@ya...> wrote:
>
> Hello Robert:
>
> I am developing in Java, accessing Mantis services through SOAP. If the new
> technology will have an easy integration with Java, for me it's okay.
>
> Regards,
>
> Enviado desde la nevera // Sent from the fridge
> Raul Luna Rodríguez
> sup...@ya...
> ________________________________
> De: Robert Munteanu <rob...@gm...>
> Para: "man...@li..."
> <man...@li...>; developer discussions
> <man...@li...>
> Enviado: Jueves, 1 de noviembre, 2012 9:36 P.M.
> Asunto: [Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for
> php5 native soap extension
>
> Hi,
>
> (Sorry for the cross-post, I would like to reach a wide audience )
>
> I've been working on refreshing the backend of our SOAP API. The API,
> while reasonably featureful and well working, is based on nusoap. This
> poses a maintenance burden on us ( see for instance 0014157: Array to
> string conversion error on soap request with PHP 5.4 [1] which
> requires to make changes again to support newer PHP versions ) and
> also brings performance problems ( see 0014672: Slow performance of
> SOAP calls due to nusuoap [2] ) .
>
> I have worked towards getting MantisBT to support both the php5 native
> soap extension and the nusoap library. The code is now available at my
> github fork [3]. There is a configuration setting which allows the
> administrator to control which backend is used.
>
> I have the following plan:
>
> 1. After 1.2.12 is released, merge the code into master and
> master-1.2.x . The configuration setting defaults to using nusoap . At
> this point I would encourage SOAP API users to give it a test.
> 2. After 1.2.13 is released, switch the configuration setting to
> default to the soap extension.
>
> Depending on user feedback, I would like to remove nusoap completely.
>
> I'm interested in two things
>
> 1. What is your opinion about the above plan? I'm interested in
> developers and users alike
> 2. If you use the SOAP API, are you able to use the php5 native soap
> extension if we remove support for using nusoap?
>
> Thanks,
>
> Robert
>
> [1]: http://www.mantisbt.org/bugs/view.php?id=14157
> [2]: http://www.mantisbt.org/bugs/view.php?id=14672
> [3]: https://github.com/rombert/mantisbt/tree/14871-soap-extension
> --
> Sent from my (old) computer
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_sfd2d_oct
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>
>



-- 
Sent from my (old) computer

[Mantisbt-soap-dev] MantisBT 1.2.13 planned change - add support for php5 native soap extension

[Robert M. <rob...@gm...>]

Hi,

(Sorry for the cross-post, I would like to reach a wide audience )

I've been working on refreshing the backend of our SOAP API. The API,
while reasonably featureful and well working, is based on nusoap. This
poses a maintenance burden on us ( see for instance 0014157: Array to
string conversion error on soap request with PHP 5.4 [1] which
requires to make changes again to support newer PHP versions ) and
also brings performance problems ( see 0014672: Slow performance of
SOAP calls due to nusuoap [2] ) .

I have worked towards getting MantisBT to support both the php5 native
soap extension and the nusoap library. The code is now available at my
github fork [3]. There is a configuration setting which allows the
administrator to control which backend is used.

I have the following plan:

1. After 1.2.12 is released, merge the code into master and
master-1.2.x . The configuration setting defaults to using nusoap . At
this point I would encourage SOAP API users to give it a test.
2. After 1.2.13 is released, switch the configuration setting to
default to the soap extension.

Depending on user feedback, I would like to remove nusoap completely.

I'm interested in two things

1. What is your opinion about the above plan? I'm interested in
developers and users alike
2. If you use the SOAP API, are you able to use the php5 native soap
extension if we remove support for using nusoap?

Thanks,

Robert

[1]: http://www.mantisbt.org/bugs/view.php?id=14157
[2]: http://www.mantisbt.org/bugs/view.php?id=14672
[3]: https://github.com/rombert/mantisbt/tree/14871-soap-extension
--
Sent from my (old) computer

Re: [Mantisbt-soap-dev] mc_issue_add wrong data

[Robert M. <rob...@gm...>]

Hi,

On Fri, Oct 12, 2012 at 11:51 PM, JR10 <jr...@jr...> wrote:
>      $username = "username";
>      $password = "password";
>      $category = "Feature";
>      $reproducibility = "N/A";
>      $severity = "feature";
>      $priority = "normal";
>      $summary = "Test";
>      $description = "test";
>      $reproducesteps = "test";
>
>      $issue_data = array(
>          "project" => array("id" => "1"),
>          "category" => $category,
>          "reproducibility" => array("name" => $reproducibility),
>          "severity" => array("name" => $severity),
>          "priority" => array("name" => $priority),
>          "summary" => $summary,
>          "description" => $description,
>          "steps_to_reproduce" => $reproducesteps
>      );
>
> I'm using the above php code to add an issue. It works but the data is
> wrong.
>
> If $category is "Feature", the data is correct, and the issue is added
> with the correct data.
> if $category is "Bug", the data is incorrect, and the issue is added
> with wrong data.
> For example, severity should be "feature", but it's "trivial". priority
> should be "normal", but it's "low".


This sounds pretty unusual, can you attach the raw XML sent to Mantis?
(Make sure to remove the username/password)

Robert

>
> Thanks.
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev



-- 
Sent from my (old) computer

[Mantisbt-soap-dev] mc_issue_add wrong data

[JR10 <jr...@jr...>]

     $username = "username";
     $password = "password";
     $category = "Feature";
     $reproducibility = "N/A";
     $severity = "feature";
     $priority = "normal";
     $summary = "Test";
     $description = "test";
     $reproducesteps = "test";

     $issue_data = array(
         "project" => array("id" => "1"),
         "category" => $category,
         "reproducibility" => array("name" => $reproducibility),
         "severity" => array("name" => $severity),
         "priority" => array("name" => $priority),
         "summary" => $summary,
         "description" => $description,
         "steps_to_reproduce" => $reproducesteps
     );

I'm using the above php code to add an issue. It works but the data is 
wrong.

If $category is "Feature", the data is correct, and the issue is added 
with the correct data.
if $category is "Bug", the data is incorrect, and the issue is added 
with wrong data.
For example, severity should be "feature", but it's "trivial". priority 
should be "normal", but it's "low".

Thanks.

Re: [Mantisbt-soap-dev] SOAP - Rest API

[Robert M. <rob...@gm...>]

Hi Valery,

On Wed, Sep 19, 2012 at 10:45 AM, Инж Донев <di...@ab...> wrote:
>
> Dear sirs,
>
> can anyone tell me is there a full Mantis Api that supports all important features that Mantis support like:
>
> - user creation
> - project creation
> - ticket creation etc.
>
> No matter if it's Soap or Rest or whatever Api.

Please see http://www.mantisbt.org/docs/master-1.2.x/en/developers.html#INTEGRATORS

Robert

>
> Regards
> valery
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>



--
Sent from my (old) computer

[Mantisbt-soap-dev] SOAP - Rest API

[Инж Д. <di...@ab...>]

 Dear sirs,

can anyone tell me is there a full Mantis Api that supports all important features that Mantis support like:

- user creation
- project creation
- ticket creation etc.

No matter if it's Soap or Rest or whatever Api.

Regards
valery

Re: [Mantisbt-soap-dev] create a connection to mantis

[Raul L. <sup...@ya...>]

Hello Kreindl K.: 


To connect to mantis I do the following (see below) and it works at least the connection. 


I didn't try this ConnectLocator, sorry. 




        try
        {
            URL url = new URL("http://localhost/mantis/api/soap/mantisconnect.php");
            
            MantisConnectLocator mcl = new MantisConnectLocator();
            portType = mcl.getMantisConnectPort( url ); 
        
        }catch( Exception e )
        {
            log.error( e );
            // do other stuff
        }



Enviado desde la nevera // Sent from the fridge

Raul Luna Rodríguez
sup...@ya...


________________________________
 De: Kreindl K. <kle...@gm...>
Para: man...@li... 
Enviado: Martes, 28 de agosto, 2012 3:09 P.M.
Asunto: [Mantisbt-soap-dev] create a connection to mantis
 
hello!

i've been trying to access our Mantis-Server for several hours 
up to now :(, util i decided to post a message here :P

now to my problem:
i try to acces Mantis using java (via mantis-axis-soap-client-1.2.9), 
but all i get are connection timeouts.
i have also tried a solution which was posted here, but i must be 
missing something.

my code:
URL url = 
new URL("http://www.feat.at/mantisbt/api/soap/mantisconnect.php");
MantisConnectLocator mcl = new MantisConnectLocator();

mcl.setMantisConnectPortEndpointAddress(
"https://www.myserver.com/mantisbt/api/soap/mantisconnect.php");
        
MantisConnectPortType mcpt = mcl.getMantisConnectPort();

System.out.println(mcpt.mc_version());

i hope you can give me a hint or some help how i get this thing 
working


kreindl k        

ps: excuse my bad english :)


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Mantisbt-soap-dev mailing list
Man...@li...
https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev

Re: [Mantisbt-soap-dev] create a connection to mantis

[Robert M. <rob...@gm...>]

Hello Kreindl K,

On Tue, Aug 28, 2012 at 4:09 PM, Kreindl K. <kle...@gm...> wrote:
> hello!
>
> i've been trying to access our Mantis-Server for several hours
> up to now :(, util i decided to post a message here :P
>

Try

        MantisConnectLocator locator = new MantisConnectLocator();
        MantisConnectPortType mantisConnector =
locator.getMantisConnectPort(new URL(url));
        String mantisVersion = mantisConnector.mc_version();


Robert

> now to my problem:
> i try to acces Mantis using java (via mantis-axis-soap-client-1.2.9),
> but all i get are connection timeouts.
> i have also tried a solution which was posted here, but i must be
> missing something.
>
> my code:
> URL url =
> new URL("http://www.feat.at/mantisbt/api/soap/mantisconnect.php");
> MantisConnectLocator mcl = new MantisConnectLocator();
>
> mcl.setMantisConnectPortEndpointAddress(
> "https://www.myserver.com/mantisbt/api/soap/mantisconnect.php");
>
> MantisConnectPortType mcpt = mcl.getMantisConnectPort();
>
> System.out.println(mcpt.mc_version());
>
> i hope you can give me a hint or some help how i get this thing
> working
>
>
> kreindl k
>
> ps: excuse my bad english :)
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev



-- 
Sent from my (old) computer

[Mantisbt-soap-dev] create a connection to mantis

[Kreindl K. <kle...@gm...>]

hello!

i've been trying to access our Mantis-Server for several hours 
up to now :(, util i decided to post a message here :P

now to my problem:
i try to acces Mantis using java (via mantis-axis-soap-client-1.2.9), 
but all i get are connection timeouts.
i have also tried a solution which was posted here, but i must be 
missing something.

my code:
URL url = 
new URL("http://www.feat.at/mantisbt/api/soap/mantisconnect.php");
MantisConnectLocator mcl = new MantisConnectLocator();

mcl.setMantisConnectPortEndpointAddress(
"https://www.myserver.com/mantisbt/api/soap/mantisconnect.php");
		
MantisConnectPortType mcpt = mcl.getMantisConnectPort();

System.out.println(mcpt.mc_version());

i hope you can give me a hint or some help how i get this thing 
working


kreindl k		

ps: excuse my bad english :)

Re: [Mantisbt-soap-dev] all the service become "not definded" if I pass "?wsdl" in the end the url

[Robert M. <rob...@gm...>]

Hi Antia,

On Tue, Aug 7, 2012 at 1:10 PM, antia <ant...@gm...> wrote:
> Hi
> My code worked fine if I just use
>
> $endpoint=http://testmantis.server/api/soap/mantisconnect.php in the
> $client=new soapclient($endpoint);
>
> I can use service that mantis provide to update issue, add project ...etc
> etc..
>
> But If i add "?wsdl" in the end the url, that is
> =>$endpoint=http://testmantis.server/api/soap/mantisconnect.php?wsdl
>
> I just keep getting error msg like =>
>
> Array ( [faultcode] => SOAP-ENV:Client [faultactor] => [faultstring] =>
> method 'mc_version'('mc_version') not defined in service('' '') [detail] =>
> )

Adding '?wsdl' to the URL instructs the server-side code to generate
the WSDL file. So it's not for calling API methods.

>
> and the 'mc_version' can be replaced with anyother service I tried to call .
>
> However, others seem alwasys add "?wsdl" in their code and codes work fine
> still... does that mean something wrong with my code or my environment?
>
> Because now I put my code in other server and I got "Parsing WSDL: Couldn't
> load from 'http://mymantis server/api/soap/mantisconnect.php' " this type
> msg
>
> Sorry about it if the question sound stupid.... I tried to google around but
> I couldn't find why we have to add ?wsdl in the end but everyone seem have
> it =( but when I add it ... my code crash .

You have two use cases here:

1. Generate WSDL file for e.g. creating stubs using Apache Axis or
loading into a web service design tool. For this one append ?wsdl
2. Invoke API methods on Mantis. For this one do not append ?wsdl

Robert

>
> Thanks
>
> Antia
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>



-- 
Sent from my (old) computer

[Mantisbt-soap-dev] all the service become "not definded" if I pass "?wsdl" in the end the url

[antia <ant...@gm...>]

Hi
My code worked fine if I just use

$endpoint=http://testmantis.server/api/soap/mantisconnect.php in
the $client=new soapclient($endpoint);

I can use service that mantis provide to update issue, add project ...etc
etc..

But If i add "?wsdl" in the end the url, that is =>$endpoint=
http://testmantis.server/api/soap/mantisconnect.php?wsdl

I just keep getting error msg like =>

Array ( [faultcode] => SOAP-ENV:Client [faultactor] => [faultstring] =>
method 'mc_version'('mc_version') not defined in service('' '') [detail] =>
)

and the 'mc_version' can be replaced with anyother service I tried to call .

However, others seem alwasys add "?wsdl" in their code and codes work fine
still... does that mean something wrong with my code or my environment?

Because now I put my code in other server and I got "Parsing WSDL: Couldn't
load from 'http://mymantis server/api/soap/mantisconnect.php' " this type
msg

Sorry about it if the question sound stupid.... I tried to google around
but I couldn't find why we have to add ?wsdl in the end but everyone seem
have it =( but when I add it ... my code crash .

Thanks

Antia

Re: [Mantisbt-soap-dev] Questions about mc_project_update & mc_issue_note_update

[antia <ant...@gm...>]

On Mon, Aug 6, 2012 at 9:45 AM, antia <ant...@gm...> wrote:

> Hej Robert
> Many thx for your reply.
>
> Since the  *mc_project_update* problem seems a bug, I will make them as
> required fields for now.
>
>
>> > Another problem I encounter is when I uesed mc_issue_note_update, if I
>> > include view_state this element in the array i send to update the
>> issue, no
>> > matter what is the contents inside   the view state of the issue note
>> will
>> > just become "private" even if  the array was like this
>> >
>> > $aNote= array(
>> > 'id'=>6, //issue note id
>> >                         'view_state'=> array('id'=>'10', 'name'=>''),
>> > 'text'=>'another update new note from SOAP ',
>> > );
>> >
>> >
>> > according to what I got from mc_enum_view_states to set view state to
>> public
>> > should be id=>10, but it just set it to "private".
>>
>> Are you sure that this works? Currently mc_issue_update always expects
>> some fields to be set ( altough that should change, I think )
>>
>
> The command I asked about was  *mc_issue_note_update*, I tried it again
> this morning and the view state of the note do just keep change to
> "Private".
> Even if  I tried to set it to public. My code is really simple:
>
> //a issue note data set (IssueNoteData)
> $aNote= array(
> 'id'=>2, //issue note id
>  *'view_state'=> array('id'=>'10', 'name'=>''),*
> // 'reporter'=>  ,
>  'text'=>'another update new note from SOAP ',
> );
>
> $function=*'mc_issue_note_update*';
> $param= array(
> 'username' => 'administrator',
>      'password' =>'root',
> 'note'=>$aNote,
>  );
>
> $client=new soapclient($endpoint);
>
> errcheck{
>      $result=$client->call($function,$param);
> }
>
> and I got $result = 1 as a return and the Note view state just got set to
> private (it was public).
>
>
>
>>         // fields which we expect to always be set
>>         $t_bug_data = bug_get( $p_issue_id, true );
>>         $t_bug_data->project_id = $t_project_id;
>>         $t_bug_data->reporter_id = $t_reporter_id;
>>         $t_bug_data->handler_id = $t_handler_id;
>>         $t_bug_data->category_id = $t_category_id;
>>         $t_bug_data->summary = $t_summary;
>>         $t_bug_data->description = $t_description;
>
>
>  Actually, the only clue I can follow about what parameters I should send
> for the cmd I want to use is the MantisConnect WSDL page and it didn't
> indicate which one is required parameters since all the minOccurs=0.So I
> usually just kinda .. try and error...Is there other place to check
> information like this?
>
> Btw could you tell me what is the first line *bug_get( $p_issue_id, true
> );*  for ?
>
>
> Thank you very much for your help
>

Re: [Mantisbt-soap-dev] Questions about mc_project_update & mc_issue_note_update

[Robert M. <rob...@gm...>]

Hi Antia,

On Fri, Aug 3, 2012 at 5:35 PM, antia <ant...@gm...> wrote:
> Hej :
>
> I am trying add issues from mantis SOAP interface.
> When I use mc_project_update to update a existed project, even if I just
> sent an array just include project name, I found other information about the
> project got modified ex: view status and status. those two fields show @1@
> when I checked on the mantis Manage> Manage Project view.
>
> This is the array I sent :
>
> $aproject= array(
> 'name'=>'New project add on mantis', //required field
> );
>
> as you see just a simple array

Looks like a bug to be, please file on at www.mantisbt.org/bugs/ ( api
soap category )

>
> Another problem I encounter is when I uesed mc_issue_note_update, if I
> include view_state this element in the array i send to update the issue, no
> matter what is the contents inside   the view state of the issue note will
> just become "private" even if  the array was like this
>
> $aNote= array(
> 'id'=>6, //issue note id
>                         'view_state'=> array('id'=>'10', 'name'=>''),
> 'text'=>'another update new note from SOAP ',
> );
>
>
> according to what I got from mc_enum_view_states to set view state to public
> should be id=>10, but it just set it to "private".

Are you sure that this works? Currently mc_issue_update always expects
some fields to be set ( altough that should change, I think )

	// fields which we expect to always be set
	$t_bug_data = bug_get( $p_issue_id, true );
	$t_bug_data->project_id = $t_project_id;
	$t_bug_data->reporter_id = $t_reporter_id;
	$t_bug_data->handler_id = $t_handler_id;
	$t_bug_data->category_id = $t_category_id;
	$t_bug_data->summary = $t_summary;
	$t_bug_data->description = $t_description;

Robert

Thanks,

Robert

>
> My mantis version is 1.2.11
> PHP Version 5.3.14
> MySQL 5.5.25a
>
> I am pretty new for SOAP,  so hope someone can help me.
>
> Thank you
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>



-- 
Sent from my (old) computer

[Mantisbt-soap-dev] Questions about mc_project_update & mc_issue_note_update

[antia <ant...@gm...>]

Hej :

I am trying add issues from mantis SOAP interface.
When I use *mc_project_update *to update a existed project, even if I just
sent an array just include project name, I found other information about
the project got modified ex: view status and status. those two fields show
@1@  when I checked on the mantis Manage> Manage Project view.

This is the array I sent :

$aproject= array(
'name'=>'New project add on mantis', //required field
);

as you see just a simple array

Another problem I encounter is when I uesed *mc_issue_note_update*, if I
include view_state this element in the array i send to update the issue, no
matter what is the contents inside   the view state of the issue note will
just become "private" even if  the array was like this

$aNote= array(
'id'=>6, //issue note id
                         'view_state'=> array('id'=>'10', 'name'=>''),
 'text'=>'another update new note from SOAP ',
);


according to what I got from* mc_enum_view_states *to set view state to
public should be id=>10, but it just set it to "private".

My mantis version is 1.2.11
PHP Version 5.3.14
MySQL 5.5.25a

I am pretty new for SOAP,  so hope someone can help me.

Thank you

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[Robert M. <rob...@gm...>]

On Wed, Aug 1, 2012 at 7:28 AM, brent timothy saner
<bre...@gm...> wrote:
> On 07/31/12 17:07, Robert Munteanu wrote:
>
>> looks like i'm just missing the "project" key, right?
>>
>>
>>> Right, the project is mandatory.
>
> there's definitely something odd going on here.
>
> can i get some clarification on what sort of values that mantisconnect
> is *expecting* for mc_issue_add()? or maybe just an example block so i
> know i'm not going crazy here?


See for instance our SOAP tests at [1] . There's plenty of examples there.

Robert

[1]: https://github.com/mantisbt/mantisbt/blob/83068d36a0e75e44bf42f1a92ab2d7cd740b27fe/tests/soap/IssueAddTest.php

>
> here's what i'm running now (along with a copious amount of testing;
> you'll notice that the $ticket() array successfully initializes).
>
> script: http://pastebin.com/M6xWVc3X
>
> output: http://pastebin.com/xcyiRYxc
>
> AND here's the relevant bit from the logs.
>
>
> [Wed Aug 01 00:10:38 2012] [error] [client XX.XX.XX.XX] PHP Fatal
> error:  Uncaught SoapFault exception: [Server] Error Type: SYSTEM
> NOTICE,\nError Description:\nUninitialized string offset: 0,\nStack
> Trace:\nmc_issue_api.php L518
> mci_get_project_id(<string>'')\nUnknownFile L?
> mc_issue_add(<string>'anonymous', <string>'*SCRUBBED*', <Array> {
> ['project'] => '', ['category'] => '1', ['summary'] => 'this is a test
> bug', ['description'] => 'livesite testing',
> ['additional_information'] => '(submitted via feedback.html)'
> })\nnusoap.php L4087 call_user_func_array(<string>'mc_issue_add',
> <Array> { [0] => 'anonymous', [1] => '*SCRUBBED*', [2] => <Array> {
> ['project'] => '', ['category'] => '1', ['summary'] => 'this is a test
> bug', ['description'] => 'livesite testing',
> ['additional_information'] => '(submitted via feedback.html)' }
> })\nnusoap.php L3718 invoke_method()\nmantisconnect.php L1542
> service(<string>'<?xml version="1.0"
> encoding="UTF-8"?>\n<SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:ns1="http://futureware.biz/mantisconnect"
> xmlns:xsd="http://www.w3.or in /path/to/mantis/site-anon_report.php on
> line 45, referer: http://URI/path/to/mantis/feedback.html
>
> But it's more or less the exact same error message as the pastebin.
>
> Should I try upgrading Mantis from 1.2.8 to 1.2.11 (and, I'm assuming,
> mantisconnect as a result of that)? I don't recall seeing this sort of
> issue as being one of the issues fixed.
>
> I just for the life of me cannot figure out why it's stripping the
> 'project' key.
>
>
> Additionally, I'm also curious how I would integrate custom fields
> into ticket creation as well using this method, as it seems
> mc_issue_add() wasn't accepting the way I was referencing them.
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev



-- 
Sent from my (old) computer

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[brent t. s. <bre...@gm...>]

On 07/31/12 17:07, Robert Munteanu wrote:

> looks like i'm just missing the "project" key, right?
> 
> 
>> Right, the project is mandatory.

there's definitely something odd going on here.

can i get some clarification on what sort of values that mantisconnect
is *expecting* for mc_issue_add()? or maybe just an example block so i
know i'm not going crazy here?

here's what i'm running now (along with a copious amount of testing;
you'll notice that the $ticket() array successfully initializes).

script: http://pastebin.com/M6xWVc3X

output: http://pastebin.com/xcyiRYxc

AND here's the relevant bit from the logs.


[Wed Aug 01 00:10:38 2012] [error] [client XX.XX.XX.XX] PHP Fatal
error:  Uncaught SoapFault exception: [Server] Error Type: SYSTEM
NOTICE,\nError Description:\nUninitialized string offset: 0,\nStack
Trace:\nmc_issue_api.php L518
mci_get_project_id(<string>'')\nUnknownFile L?
mc_issue_add(<string>'anonymous', <string>'*SCRUBBED*', <Array> {
['project'] => '', ['category'] => '1', ['summary'] => 'this is a test
bug', ['description'] => 'livesite testing',
['additional_information'] => '(submitted via feedback.html)'
})\nnusoap.php L4087 call_user_func_array(<string>'mc_issue_add',
<Array> { [0] => 'anonymous', [1] => '*SCRUBBED*', [2] => <Array> {
['project'] => '', ['category'] => '1', ['summary'] => 'this is a test
bug', ['description'] => 'livesite testing',
['additional_information'] => '(submitted via feedback.html)' }
})\nnusoap.php L3718 invoke_method()\nmantisconnect.php L1542
service(<string>'<?xml version="1.0"
encoding="UTF-8"?>\n<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ns1="http://futureware.biz/mantisconnect"
xmlns:xsd="http://www.w3.or in /path/to/mantis/site-anon_report.php on
line 45, referer: http://URI/path/to/mantis/feedback.html

But it's more or less the exact same error message as the pastebin.

Should I try upgrading Mantis from 1.2.8 to 1.2.11 (and, I'm assuming,
mantisconnect as a result of that)? I don't recall seeing this sort of
issue as being one of the issues fixed.

I just for the life of me cannot figure out why it's stripping the
'project' key.


Additionally, I'm also curious how I would integrate custom fields
into ticket creation as well using this method, as it seems
mc_issue_add() wasn't accepting the way I was referencing them.

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[Robert M. <rob...@gm...>]

On Wed, Aug 1, 2012 at 12:03 AM, brent timothy saner
<bre...@gm...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/31/12 16:25, Robert Munteanu wrote:
>>
>> Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR:
>> Parsing WSDL: Couldn't load from 'http://...' Fatal error: Uncaught
>> SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load
>> from 'http://....
>>
>> I checked and there isn't a BOM in my PHP script nor in
>> mantisconnect.php ...
>>
>>> Um, sorry, the entry point was correct.
>>
>>> Can you check the server error log? If that does not help try
>>> tracking the conversation with SOAP UI as decribed at
>>> https://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=User_Guide#Verifying_the_Mantis_SOAP_API_using_SOAP_UI
>
> WELP,
>>>
> this is embarrassing. the error log was being written to a
> totally different file. was wondering why i wasn't getting anything
> useful from where i was looking...
>
> it was giving me this:
>
> [Tue Jul 31 16:35:41 2012] [error] [client XX] PHP Fatal error:
> require_once(): Failed opening required 'adodb/adodb.inc.php'
> (include_path='/path/to/mantis/core/:/path/to/mantis/library:../../library')
> in /path/to/mantis/core/database_api.php on line 35
> [Tue Jul 31 16:35:41 2012] [error] [client XX] PHP Fatal error:
> Uncaught SoapFault exception: [Client] looks like we got no XML
> document in /path/to/mantis/site-anon_report.php:13\nStack trace:\n#0
> /path/to/mantis/site-anon_report.php(13):
> SoapClient->__call('mc_issue_add', Array)\n#1
> /path/to/mantis/site-anon_report.php(13):
> SoapClient->mc_issue_add('anonymous', 'XXXXXXX', Array)\n#2 {main}\n
> thrown in /path/to/mantis/site-anon_report.php on line 13, referer:
> http://..../feedback.html
>
>
> somewhere along the way mantis is stripping my include_path. it looks
> like it's mantisconnect itself, based upon this:
>
> www:/path/to/mantis# grep -iHnR "include_path" *
> ...
> api/soap/mantisconnect.php:15:set_include_path( '../../library' );
> ...
>
> This is how that small section looks now:
>
>   15 $newpath = '../../library';
>   16 set_include_path(get_include_path() . PATH_SEPARATOR . $newpath);
>   17 require_once( 'nusoap/nusoap.php' );

Not sure why you need to do this, it has always worked out of the box...

>
> which DOES give me a new error- and THIS one _seems_ to be an actual
> error from SOAP.
>
> Fatal error: Uncaught SoapFault exception: [Server] Error Type: SYSTEM
> NOTICE, Error Description: Undefined index: project, Stack Trace:
> UnknownFile L? mc_issue_add('anonymous', 'XXXXX', { ['summary'] =>
> 'this is a test bug', ['description'] => 'bug submitted from the live
> site', ['additional_information'] => '(submitted via feedback.html)'
> }) nusoap.php L4000 call_user_func_array('mc_issue_add', { [0] =>
> 'anonymous', [1] => 'XXXXXX', [2] => { ['summary'] => 'this is a test
> bug', ['description'] => 'bug submitted from the live site',
> ['additional_information'] => '(submitted via feedback.html)' } })
> nusoap.php L3689 invoke_method() mantisconnect.php L1540 service('
>
> looks like i'm just missing the "project" key, right?


Right, the project is mandatory.

Robert

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAYSCgACgkQ8u2Zh4MtlQr8HQCeOCyIM42/JTcTGc6Z8G4eSmFq
> /gMAnieOTPrus8myUdeASv4q2Mmy9Hk1
> =+Ik0
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev



-- 
Sent from my (old) computer

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[brent t. s. <bre...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/31/12 16:25, Robert Munteanu wrote:
> 
> Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR:
> Parsing WSDL: Couldn't load from 'http://...' Fatal error: Uncaught
> SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load
> from 'http://....
> 
> I checked and there isn't a BOM in my PHP script nor in 
> mantisconnect.php ...
> 
>> Um, sorry, the entry point was correct.
> 
>> Can you check the server error log? If that does not help try
>> tracking the conversation with SOAP UI as decribed at 
>> https://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=User_Guide#Verifying_the_Mantis_SOAP_API_using_SOAP_UI

WELP,
>> 
this is embarrassing. the error log was being written to a
totally different file. was wondering why i wasn't getting anything
useful from where i was looking...

it was giving me this:

[Tue Jul 31 16:35:41 2012] [error] [client XX] PHP Fatal error:
require_once(): Failed opening required 'adodb/adodb.inc.php'
(include_path='/path/to/mantis/core/:/path/to/mantis/library:../../library')
in /path/to/mantis/core/database_api.php on line 35
[Tue Jul 31 16:35:41 2012] [error] [client XX] PHP Fatal error:
Uncaught SoapFault exception: [Client] looks like we got no XML
document in /path/to/mantis/site-anon_report.php:13\nStack trace:\n#0
/path/to/mantis/site-anon_report.php(13):
SoapClient->__call('mc_issue_add', Array)\n#1
/path/to/mantis/site-anon_report.php(13):
SoapClient->mc_issue_add('anonymous', 'XXXXXXX', Array)\n#2 {main}\n
thrown in /path/to/mantis/site-anon_report.php on line 13, referer:
http://..../feedback.html


somewhere along the way mantis is stripping my include_path. it looks
like it's mantisconnect itself, based upon this:

www:/path/to/mantis# grep -iHnR "include_path" *
...
api/soap/mantisconnect.php:15:set_include_path( '../../library' );
...

This is how that small section looks now:

  15 $newpath = '../../library';
  16 set_include_path(get_include_path() . PATH_SEPARATOR . $newpath);
  17 require_once( 'nusoap/nusoap.php' );

which DOES give me a new error- and THIS one _seems_ to be an actual
error from SOAP.

Fatal error: Uncaught SoapFault exception: [Server] Error Type: SYSTEM
NOTICE, Error Description: Undefined index: project, Stack Trace:
UnknownFile L? mc_issue_add('anonymous', 'XXXXX', { ['summary'] =>
'this is a test bug', ['description'] => 'bug submitted from the live
site', ['additional_information'] => '(submitted via feedback.html)'
}) nusoap.php L4000 call_user_func_array('mc_issue_add', { [0] =>
'anonymous', [1] => 'XXXXXX', [2] => { ['summary'] => 'this is a test
bug', ['description'] => 'bug submitted from the live site',
['additional_information'] => '(submitted via feedback.html)' } })
nusoap.php L3689 invoke_method() mantisconnect.php L1540 service('

looks like i'm just missing the "project" key, right?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAYSCgACgkQ8u2Zh4MtlQr8HQCeOCyIM42/JTcTGc6Z8G4eSmFq
/gMAnieOTPrus8myUdeASv4q2Mmy9Hk1
=+Ik0
-----END PGP SIGNATURE-----

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[Robert M. <rob...@gm...>]

On Tue, Jul 31, 2012 at 11:18 PM, brent timothy saner
<bre...@gm...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 07/31/12 15:41, Robert Munteanu wrote:
>> Hi,
>>
>> On Tue, Jul 31, 2012 at 10:33 PM, brent timothy saner
>> <bre...@gm...> wrote: Yep, that one.
>>
>> I've got some confusion. I can pull the mantisconnect.php?wsdl via
>> wget, a browser, etc. directly just fine and I get XML output, but
>> whenever I try from a PHP script it gives me:
>>
>>> The soap entry point is mantisconnect.php ( no ?wsdl appended )
>>
>
> When I do that, I get
>
> Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
> WSDL: Couldn't load from 'http://...' Fatal error: Uncaught SoapFault
> exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from
> 'http://....
>
> I checked and there isn't a BOM in my PHP script nor in
> mantisconnect.php ...

Um, sorry, the entry point was correct.

Can you check the server error log? If that does not help try tracking
the conversation with SOAP UI as decribed at
https://sourceforge.net/apps/mediawiki/mylyn-mantis/index.php?title=User_Guide#Verifying_the_Mantis_SOAP_API_using_SOAP_UI

Robert

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAYPZ0ACgkQ8u2Zh4MtlQoieACfcVSaYkuCCelSKQLyy2BI4QHd
> uosAoLOB9PkJyuPuQ4ZAA+51m+Hfvh6J
> =VLMU
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev



-- 
Sent from my (old) computer

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[brent t. s. <bre...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/31/12 15:41, Robert Munteanu wrote:
> Hi,
> 
> On Tue, Jul 31, 2012 at 10:33 PM, brent timothy saner 
> <bre...@gm...> wrote: Yep, that one.
> 
> I've got some confusion. I can pull the mantisconnect.php?wsdl via 
> wget, a browser, etc. directly just fine and I get XML output, but 
> whenever I try from a PHP script it gives me:
> 
>> The soap entry point is mantisconnect.php ( no ?wsdl appended )
> 

When I do that, I get

Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing
WSDL: Couldn't load from 'http://...' Fatal error: Uncaught SoapFault
exception: [WSDL] SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://....

I checked and there isn't a BOM in my PHP script nor in
mantisconnect.php ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAYPZ0ACgkQ8u2Zh4MtlQoieACfcVSaYkuCCelSKQLyy2BI4QHd
uosAoLOB9PkJyuPuQ4ZAA+51m+Hfvh6J
=VLMU
-----END PGP SIGNATURE-----

Re: [Mantisbt-soap-dev] "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in"...

[Robert M. <rob...@gm...>]

Hi,

On Tue, Jul 31, 2012 at 10:33 PM, brent timothy saner
<bre...@gm...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yep, that one.
>
> I've got some confusion. I can pull the mantisconnect.php?wsdl via
> wget, a browser, etc. directly just fine and I get XML output, but
> whenever I try from a PHP script it gives me:

The soap entry point is mantisconnect.php ( no ?wsdl appended )

Robert

>
> ______________
> Fatal error: Uncaught SoapFault exception: [Client] looks like we got
> no XML document in
> /home/circle/public_html/mantis/site-anon_report.php:13 Stack trace:
> #0 /home/circle/public_html/mantis/site-anon_report.php(13):
> SoapClient->__call('mc_issue_add', Array) #1
> /home/circle/public_html/mantis/site-anon_report.php(13):
> SoapClient->mc_issue_add('anonymous', 'XXXXXXXX', Array) #2 {main}
> thrown in /home/circle/public_html/mantis/site-anon_report.php on line 13
> ______________
>
>
> I'm almost convinced it's something to do with the custom fields.
>
> Here's the PHP script:
>
> ______________
> <?php
> $reporter = $_REQUEST['fullname'] ;
> $reporter_addy = $_REQUEST['email'] ;
> $desc = $_REQUEST['summary'] ;
> $bigtext = $_REQUEST['description'] ;
> $browser = $_REQUEST['ua'] ;
> $problem_page = $_REQUEST['url'] ;
>
> $username = 'anonymous';
> $password = 'XXXXXXXXX';
> $issue = array ('category_id' => '2', 'project_id' => '1', 'summary'
> => $desc , 'description' => $bigtext, 'custom_URL' => "$problem_page",
> 'custom_User-Agent String' => "$browser", 'custom_Reporter Email' =>
> "$reporter_addy", 'custom_Reporter Name' => "$reporter",
> 'additional_information' => '(submitted via feedback.html)');
> $c = new
> SoapClient('http://path/to/site/scrubbed/mantisconnect.php?wsdl');
> $c->mc_issue_add($username, $password, $issue);
> // print_r($issue);
> ?>
> ________________
>
> Using PHP 5.3.3, MantisBT 1.2.8 (I know, I know).
>
> I've confirmed that the server has both the SOAP client *and* server
> enabled in phpinfo.
>
>
> In fact, the Array *does* get created; If I comment out the
> "$c->mc_issue_add()" line and uncomment the print_r(), I get this:
>
> ________________
> Array ( [category_id] => 2 [project_id] => 1 [summary] => this is a
> test bug [description] => lolnope. [custom_URL] =>
> http://scrubbed/testing.html [custom_Use />
>   <i>Please provide detailed information (i.e. what you<br>
>   were doing when the issue occurred, how we can<br>
>   recreate this issue, any logins we might need,<br>
>   etc.)</i><b>:</b><br />
>   <textarea name="description" rows="8" cols="53"></textarea><br />
>     <b>OS/Browser Version</b>
>   <br />
>   <i>(this should be automatically detected)</i><b>:</b>
>     <br /><script type="text/javascript">
> var ua = navigator.userAgent;
> // document.write('<i>+ua+</i>');
> document.write('<input type="text" readonly="readonly" size="55"
> name="ua" value="'+ua+'">');
> </script><br />
>   <br>
>   <b>Reporting URL</b>
>   <br />
>   <i>(this should be automatically detected)</i><b>: </b>
>     <br /><script type="text/javascript">
> var url = document.referrer;
> // document.write('<i>+url+</i>');
> document.write('<input type="url" readonly="readonly" size="55"
> name="url" value="'+url+'">');
> </script><br />
>   <br>
>   <center><input type="submit" value="Submit"/>     <input
> type="reset" value="Clear"></input></center>
> </form>
> </body>
> </html>
> _________________
>
>
>
>
> SO! Any ideas? How badly am I messing this up?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAlAYMuwACgkQ8u2Zh4MtlQpOjQCgjiUdRQE6qP6qmfBDdFhCq5ii
> ePkAnjlvfJ0HEN4ZMySh6MpPpYNaYaYh
> =gLL7
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Mantisbt-soap-dev mailing list
> Man...@li...
> https://lists.sourceforge.net/lists/listinfo/mantisbt-soap-dev
>



-- 
Sent from my (old) computer