Erlang/OTP Forums

It's disappointing that the xmlrpc components aren't distributed in a single, compiled package...

Having installed the compiled erlang xmlrpc module, I see ejabberd_xmlrpc isn't distributed as a .beam... Any pointers to one? Or can I compile from WinXP command line?

There's a bin (but no ebin) directory in my WinXP ejabberd directory... Same as ebin?


I want ANY XMLRPC client to be able to use ONLY the register command... Is this the config for that:

It's disappointing that the xmlrpc components aren't distributed in a single, compiled package...

Having installed the compiled erlang xmlrpc module, I see ejabberd_xmlrpc isn't distributed as a .beam... Any pointers to one? Or can I compile from WinXP command line?

There's a bin (but no ebin) directory in my WinXP ejabberd directory... Same as ebin?


I want ANY XMLRPC client to be able to use ONLY the register command... Is this the config for that:

Can I do something like this?

Doesn't seem to work...

$ cd ejabberd-2.1.1
$ bin/erlc -I includes lib/xmlrpc/ejabberd_xmlrpc.erl
lib/xmlrpc/ejabberd_xmlrpc.erl:25: can't find include file "ejabberd.hrl"
lib/xmlrpc/ejabberd_xmlrpc.erl:26: can't find include file "mod_roster.hrl"
lib/xmlrpc/ejabberd_xmlrpc.erl:27: can't find include file "jlib.hrl"
lib/xmlrpc/ejabberd_xmlrpc.erl:325: undefined macro ''WARNING_MSG''
lib/xmlrpc/ejabberd_xmlrpc.erl:241: function build_fault_response/3 undefined

Jeez, this has been frustrating...

Could you email me the xmlrpc.beam you just compiled?



On Thu, Jan 7, 2010 at 12:16 PM, Liam <ejabberd@networkimprov.net (ejabberd@networkimprov.net)> wrote:

Spoke too soon! This works:

$ cd ejabberd-2.1.1

$ bin/erlc -I includes/ejabberd/include some_path/ejabberd_xmlrpc.erl

Thank heavens. And thanks for your help!



On Thu, Jan 7, 2010 at 12:44 PM, Liam <ejabberd@networkimprov.net (ejabberd@networkimprov.net)> wrote:

>Also note that the Guide says [1]:
> If at least one restriction is defined, then the frontend expects that
> authentication information is provided when executing a command.
>
>That means you will have to provide auth of some Jabber account inside the XMLRPC calls.

I don't see from the xmlrpc readme how to include authentication in an xmlrpc call.

My xmlrpc text looks like:

<methodcall>

On deeper inspection, I gather an authentication struct comes before a command struct, so my xmlrpc msg is:

<methodcall>
<methodname>register</methodname>
<params><param><value><struct>

<member><name>user</name><value><string>xmlrpc_access</string></value></member>
<member><name>server</name><value><string>localhost</string></value></member>
<member><name>password</name><value><string>pass</string></value></member>
</struct></value></param><param><value><struct>
<member><name>user</name><value><string>newuser</string></value></member>
<member><name>host</name><value><string>localhost</string></value></member>
<member><name>password</name><value><string>newpass</string></value></member>
</struct></value></param></params></methodcall>


However, I'm getting back an empty response with HTTP result 415 (invalid media). The headers:

Server: nginx/0.7.62
Date: Fri, 08 Jan 2010 05:59:38 GMT
Content-Type: text/xml
Connection: keep-alive
Content-Length: 0

(I proxy the request via nginx; I'm sure it's handing it on.)

Ideas?



On Thu, Jan 7, 2010 at 2:47 PM, Liam <ejabberd@networkimprov.net (ejabberd@networkimprov.net)> wrote: