You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@ws.apache.org by sean <se...@celsoft.com> on 2002/10/28 22:59:25 UTC
Activity
Hi everyone,
I was thinking of using the Apache XML-RPC project as an application
framework for some projects I have coming up. The site at
http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's a
terrible lack of "how-to" documentation there and I couldn't find much
news or other signs of activity.
Is there another site where all the activity is? Is this project alive
and well?
Sean O'Dell
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> Sometime soon I will boil this thread down to a bug report for the dev
> list and the user community at large will benefit from it. Thanks to
> all of you for speaking up and to Martin for posting his code.
Thanks Ryan!
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> Sometime soon I will boil this thread down to a bug report for the dev
> list and the user community at large will benefit from it. Thanks to
> all of you for speaking up and to Martin for posting his code.
Thanks Ryan!
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Douglas Reames <do...@rmsfinance.com>.
Thanks for your good work Ryan.
There is one problem however; I get the Security Exception mentioned in
several threads on this list in March:
http://www.mail-archive.com/rpc-user@xml.apache.org/msg00104.html
I am currently exploring the workaround mentioned.
Regards,
Douglas Reames
At 12:39 AM 10/29/2002 -0500, you wrote:
>Hi, I got curious about using XML-RPC from an applet after reading your
>post, so I put together an example applet to go with the echo examples.
>Here is the code, a jar, and the html file to see the applet. Please
>excuse the clumsy swing work in the applet as I don't pretend to be a GUI
>designer :)
>
>Sometime soon I will boil this thread down to a bug report for the dev
>list and the user community at large will benefit from it. Thanks to all
>of you for speaking up and to Martin for posting his code.
>
>--
>Ryan Hoegg
>ISIS Networks
>http://www.isisnetworks.net
>
>Ryan Hoegg wrote:
>
>>The example in /examples/echo does not include anything for Applets.
>>As far as I can tell, this is completely missing from the examples.
>>
>>I will see if I can get some code working with the applet jar and put
>>together an example.
>>
>>--
>>Ryan Hoegg
>>ISIS Networks
>>
>>Douglas Reames wrote:
>>
>>>Ryan,
>>>
>>>I am a newbie with both java and this java package. I have been able to
>>>get an stand-alone xml-rpc client operational, and I have had
>>>success with applet-based clients when using the 'xml-rpc-1.1.jar'.
>>>However, when I use the 'xml-rpc-1.1-applet.jar' to construct applets, I
>>>have problems.
>>>
>>>I'd like a 'Getting Started' paragraph or 3 that provides an example to
>>>Illustrate a no-frills functional skeleton using the class - XmlRpcApplet:
>>>[ ] setDebug
>>>[a] createArgumentVector
>>>[b] InitClient
>>>[c] Assert that client is a valid SimpleXmlRpcClient that can be used in
>>>'request'
>>>[d] Issue a request
>>>[e] handle exceptions
>>>[f] report results
>>>
>>>It would be nice to have an example that I could go back to compare
>>>against my own applets when issues arise - a good bare bones starting
>>>point. If someone could point me in the right direction, I would be
>>>very appreciative.
>>>
>>>Best regards,
>>>Douglas Reames
>>>RMS Finance
>
>
Re: Activity
Posted by Douglas Reames <do...@rmsfinance.com>.
Thanks for your good work Ryan.
There is one problem however; I get the Security Exception mentioned in
several threads on this list in March:
http://www.mail-archive.com/rpc-user@xml.apache.org/msg00104.html
I am currently exploring the workaround mentioned.
Regards,
Douglas Reames
At 12:39 AM 10/29/2002 -0500, you wrote:
>Hi, I got curious about using XML-RPC from an applet after reading your
>post, so I put together an example applet to go with the echo examples.
>Here is the code, a jar, and the html file to see the applet. Please
>excuse the clumsy swing work in the applet as I don't pretend to be a GUI
>designer :)
>
>Sometime soon I will boil this thread down to a bug report for the dev
>list and the user community at large will benefit from it. Thanks to all
>of you for speaking up and to Martin for posting his code.
>
>--
>Ryan Hoegg
>ISIS Networks
>http://www.isisnetworks.net
>
>Ryan Hoegg wrote:
>
>>The example in /examples/echo does not include anything for Applets.
>>As far as I can tell, this is completely missing from the examples.
>>
>>I will see if I can get some code working with the applet jar and put
>>together an example.
>>
>>--
>>Ryan Hoegg
>>ISIS Networks
>>
>>Douglas Reames wrote:
>>
>>>Ryan,
>>>
>>>I am a newbie with both java and this java package. I have been able to
>>>get an stand-alone xml-rpc client operational, and I have had
>>>success with applet-based clients when using the 'xml-rpc-1.1.jar'.
>>>However, when I use the 'xml-rpc-1.1-applet.jar' to construct applets, I
>>>have problems.
>>>
>>>I'd like a 'Getting Started' paragraph or 3 that provides an example to
>>>Illustrate a no-frills functional skeleton using the class - XmlRpcApplet:
>>>[ ] setDebug
>>>[a] createArgumentVector
>>>[b] InitClient
>>>[c] Assert that client is a valid SimpleXmlRpcClient that can be used in
>>>'request'
>>>[d] Issue a request
>>>[e] handle exceptions
>>>[f] report results
>>>
>>>It would be nice to have an example that I could go back to compare
>>>against my own applets when issues arise - a good bare bones starting
>>>point. If someone could point me in the right direction, I would be
>>>very appreciative.
>>>
>>>Best regards,
>>>Douglas Reames
>>>RMS Finance
>
>
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hi, I got curious about using XML-RPC from an applet after reading your
post, so I put together an example applet to go with the echo examples.
Here is the code, a jar, and the html file to see the applet. Please
excuse the clumsy swing work in the applet as I don't pretend to be a
GUI designer :)
Sometime soon I will boil this thread down to a bug report for the dev
list and the user community at large will benefit from it. Thanks to
all of you for speaking up and to Martin for posting his code.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Ryan Hoegg wrote:
> The example in /examples/echo does not include anything for Applets.
> As far as I can tell, this is completely missing from the examples.
>
> I will see if I can get some code working with the applet jar and put
> together an example.
>
> --
> Ryan Hoegg
> ISIS Networks
>
> Douglas Reames wrote:
>
>> Ryan,
>>
>> I am a newbie with both java and this java package. I have been able
>> to get an stand-alone xml-rpc client operational, and I have had
>> success with applet-based clients when using the 'xml-rpc-1.1.jar'.
>> However, when I use the 'xml-rpc-1.1-applet.jar' to construct
>> applets, I have problems.
>>
>> I'd like a 'Getting Started' paragraph or 3 that provides an example
>> to Illustrate a no-frills functional skeleton using the class -
>> XmlRpcApplet:
>> [ ] setDebug
>> [a] createArgumentVector
>> [b] InitClient
>> [c] Assert that client is a valid SimpleXmlRpcClient that can be used
>> in 'request'
>> [d] Issue a request
>> [e] handle exceptions
>> [f] report results
>>
>> It would be nice to have an example that I could go back to compare
>> against my own applets when issues arise - a good bare bones starting
>> point. If someone could point me in the right direction, I would be
>> very appreciative.
>>
>> Best regards,
>> Douglas Reames
>> RMS Finance
>
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hi, I got curious about using XML-RPC from an applet after reading your
post, so I put together an example applet to go with the echo examples.
Here is the code, a jar, and the html file to see the applet. Please
excuse the clumsy swing work in the applet as I don't pretend to be a
GUI designer :)
Sometime soon I will boil this thread down to a bug report for the dev
list and the user community at large will benefit from it. Thanks to
all of you for speaking up and to Martin for posting his code.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Ryan Hoegg wrote:
> The example in /examples/echo does not include anything for Applets.
> As far as I can tell, this is completely missing from the examples.
>
> I will see if I can get some code working with the applet jar and put
> together an example.
>
> --
> Ryan Hoegg
> ISIS Networks
>
> Douglas Reames wrote:
>
>> Ryan,
>>
>> I am a newbie with both java and this java package. I have been able
>> to get an stand-alone xml-rpc client operational, and I have had
>> success with applet-based clients when using the 'xml-rpc-1.1.jar'.
>> However, when I use the 'xml-rpc-1.1-applet.jar' to construct
>> applets, I have problems.
>>
>> I'd like a 'Getting Started' paragraph or 3 that provides an example
>> to Illustrate a no-frills functional skeleton using the class -
>> XmlRpcApplet:
>> [ ] setDebug
>> [a] createArgumentVector
>> [b] InitClient
>> [c] Assert that client is a valid SimpleXmlRpcClient that can be used
>> in 'request'
>> [d] Issue a request
>> [e] handle exceptions
>> [f] report results
>>
>> It would be nice to have an example that I could go back to compare
>> against my own applets when issues arise - a good bare bones starting
>> point. If someone could point me in the right direction, I would be
>> very appreciative.
>>
>> Best regards,
>> Douglas Reames
>> RMS Finance
>
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
The example in /examples/echo does not include anything for Applets. As
far as I can tell, this is completely missing from the examples.
I will see if I can get some code working with the applet jar and put
together an example.
--
Ryan Hoegg
ISIS Networks
Douglas Reames wrote:
> Ryan,
>
> I am a newbie with both java and this java package. I have been able
> to get an stand-alone xml-rpc client operational, and I have had
> success with applet-based clients when using the 'xml-rpc-1.1.jar'.
> However, when I use the 'xml-rpc-1.1-applet.jar' to construct applets,
> I have problems.
>
> I'd like a 'Getting Started' paragraph or 3 that provides an example
> to Illustrate a no-frills functional skeleton using the class -
> XmlRpcApplet:
> [ ] setDebug
> [a] createArgumentVector
> [b] InitClient
> [c] Assert that client is a valid SimpleXmlRpcClient that can be used
> in 'request'
> [d] Issue a request
> [e] handle exceptions
> [f] report results
>
> It would be nice to have an example that I could go back to compare
> against my own applets when issues arise - a good bare bones starting
> point. If someone could point me in the right direction, I would be
> very appreciative.
>
> Best regards,
> Douglas Reames
> RMS Finance
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
The example in /examples/echo does not include anything for Applets. As
far as I can tell, this is completely missing from the examples.
I will see if I can get some code working with the applet jar and put
together an example.
--
Ryan Hoegg
ISIS Networks
Douglas Reames wrote:
> Ryan,
>
> I am a newbie with both java and this java package. I have been able
> to get an stand-alone xml-rpc client operational, and I have had
> success with applet-based clients when using the 'xml-rpc-1.1.jar'.
> However, when I use the 'xml-rpc-1.1-applet.jar' to construct applets,
> I have problems.
>
> I'd like a 'Getting Started' paragraph or 3 that provides an example
> to Illustrate a no-frills functional skeleton using the class -
> XmlRpcApplet:
> [ ] setDebug
> [a] createArgumentVector
> [b] InitClient
> [c] Assert that client is a valid SimpleXmlRpcClient that can be used
> in 'request'
> [d] Issue a request
> [e] handle exceptions
> [f] report results
>
> It would be nice to have an example that I could go back to compare
> against my own applets when issues arise - a good bare bones starting
> point. If someone could point me in the right direction, I would be
> very appreciative.
>
> Best regards,
> Douglas Reames
> RMS Finance
Re: Activity
Posted by Douglas Reames <do...@rmsfinance.com>.
Ryan,
I am a newbie with both java and this java package. I have been able to
get an stand-alone xml-rpc client operational, and I have had success with
applet-based clients when using the 'xml-rpc-1.1.jar'. However, when I use
the 'xml-rpc-1.1-applet.jar' to construct applets, I have problems.
I'd like a 'Getting Started' paragraph or 3 that provides an example to
Illustrate a no-frills functional skeleton using the class - XmlRpcApplet:
[ ] setDebug
[a] createArgumentVector
[b] InitClient
[c] Assert that client is a valid SimpleXmlRpcClient that can be used in
'request'
[d] Issue a request
[e] handle exceptions
[f] report results
It would be nice to have an example that I could go back to compare against
my own applets when issues arise - a good bare bones starting point. If
someone could point me in the right direction, I would be very appreciative.
Best regards,
Douglas Reames
RMS Finance
At 05:20 PM 10/28/2002 -0500, you wrote:
>sean wrote:
>
>>I was thinking of using the Apache XML-RPC project as an application
>>framework for some projects I have coming up. The site at
>>http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's a
>>terrible lack of "how-to" documentation there and I couldn't find much
>>news or other signs of activity.
>
>What kind of how-to documentation are you looking for? We are aware that
>the documentation is scanty, but as a potential user your ideas of what a
>"Getting started" document would contain would be very helpful.
>
>The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html) on
>the web page gives some information on using the XML-RPC client classes,
>and the "Server Side XML-RPC" link
>(http://xml.apache.org/xmlrpc/server.html) gives some information on using
>the library to provide an XML-RPC interface to your software.
>
>>Is this project alive and well?
>
>Alive and kicking! We are ramping up for a 2.0 release PSN ;)
>
>--ryan
>
Re: Activity
Posted by Douglas Reames <do...@rmsfinance.com>.
Ryan,
I am a newbie with both java and this java package. I have been able to
get an stand-alone xml-rpc client operational, and I have had success with
applet-based clients when using the 'xml-rpc-1.1.jar'. However, when I use
the 'xml-rpc-1.1-applet.jar' to construct applets, I have problems.
I'd like a 'Getting Started' paragraph or 3 that provides an example to
Illustrate a no-frills functional skeleton using the class - XmlRpcApplet:
[ ] setDebug
[a] createArgumentVector
[b] InitClient
[c] Assert that client is a valid SimpleXmlRpcClient that can be used in
'request'
[d] Issue a request
[e] handle exceptions
[f] report results
It would be nice to have an example that I could go back to compare against
my own applets when issues arise - a good bare bones starting point. If
someone could point me in the right direction, I would be very appreciative.
Best regards,
Douglas Reames
RMS Finance
At 05:20 PM 10/28/2002 -0500, you wrote:
>sean wrote:
>
>>I was thinking of using the Apache XML-RPC project as an application
>>framework for some projects I have coming up. The site at
>>http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's a
>>terrible lack of "how-to" documentation there and I couldn't find much
>>news or other signs of activity.
>
>What kind of how-to documentation are you looking for? We are aware that
>the documentation is scanty, but as a potential user your ideas of what a
>"Getting started" document would contain would be very helpful.
>
>The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html) on
>the web page gives some information on using the XML-RPC client classes,
>and the "Server Side XML-RPC" link
>(http://xml.apache.org/xmlrpc/server.html) gives some information on using
>the library to provide an XML-RPC interface to your software.
>
>>Is this project alive and well?
>
>Alive and kicking! We are ramping up for a 2.0 release PSN ;)
>
>--ryan
>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
On Tuesday, October 29, 2002, at 09:33 PM, Daniel Rall wrote:
> java.sun.com's JavaDoc for the javax.security doesn't say anything?
>
> Try our source code:
>
> http://cvs.apache.org/viewcvs/xml-rpc/src/java/org/apache/xmlrpc/
> secure/SecurityConstants.java?rev=1&content-type=text/vnd.viewcvs-
> markup
I've read Sun's documentation (e.g.
http://java.sun.com/products/jsse/doc/guide/API_users_guide.html) and
various other tutorials on Java security
(http://www.javaworld.com/javaworld/jw-05-2001/jw-0525-security-
p3.html).
I understand most of the basic concepts (certificates, keys, CA's,
providers, etc).
I've looked through the xml-rpc source code. Most of the entries seem
to be along the following lines:
* Default security protocol. You probably don't need to
* override this default.
*/
public final static String DEFAULT_SECURITY_PROTOCOL = "TLS";
I'm not usually this thick, but I still don't quite get what the
minimum set of steps is that I need to take to get the simple example I
sent working ...
Surely it should not be this hard :-)
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
On Tuesday, October 29, 2002, at 09:33 PM, Daniel Rall wrote:
> java.sun.com's JavaDoc for the javax.security doesn't say anything?
>
> Try our source code:
>
> http://cvs.apache.org/viewcvs/xml-rpc/src/java/org/apache/xmlrpc/
> secure/SecurityConstants.java?rev=1&content-type=text/vnd.viewcvs-
> markup
I've read Sun's documentation (e.g.
http://java.sun.com/products/jsse/doc/guide/API_users_guide.html) and
various other tutorials on Java security
(http://www.javaworld.com/javaworld/jw-05-2001/jw-0525-security-
p3.html).
I understand most of the basic concepts (certificates, keys, CA's,
providers, etc).
I've looked through the xml-rpc source code. Most of the entries seem
to be along the following lines:
* Default security protocol. You probably don't need to
* override this default.
*/
public final static String DEFAULT_SECURITY_PROTOCOL = "TLS";
I'm not usually this thick, but I still don't quite get what the
minimum set of steps is that I need to take to get the simple example I
sent working ...
Surely it should not be this hard :-)
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Martin Redington <m....@ucl.ac.uk> writes:
> yup, but sadly, there is nothing in the unit tests for the Secure
> client and server.
>
>
> The source to SecureWebServer does contain this tantalising snippet:
>
> 80 * Standard security properties must be set before the
> SecureWebserver
>
> 81 * can be used. The SecurityTool takes care of retrieving these
> 82 * values, but the parent application must set the necessary
> 83 * values before anything will work.
>
> I know they're standard(ish), but I still can't find any good docs on
> them :-(
java.sun.com's JavaDoc for the javax.security doesn't say anything?
Try our source code:
http://cvs.apache.org/viewcvs/xml-rpc/src/java/org/apache/xmlrpc/secure/SecurityConstants.java?rev=1&content-type=text/vnd.viewcvs-markup
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Martin Redington <m....@ucl.ac.uk> writes:
> yup, but sadly, there is nothing in the unit tests for the Secure
> client and server.
>
>
> The source to SecureWebServer does contain this tantalising snippet:
>
> 80 * Standard security properties must be set before the
> SecureWebserver
>
> 81 * can be used. The SecurityTool takes care of retrieving these
> 82 * values, but the parent application must set the necessary
> 83 * values before anything will work.
>
> I know they're standard(ish), but I still can't find any good docs on
> them :-(
java.sun.com's JavaDoc for the javax.security doesn't say anything?
Try our source code:
http://cvs.apache.org/viewcvs/xml-rpc/src/java/org/apache/xmlrpc/secure/SecurityConstants.java?rev=1&content-type=text/vnd.viewcvs-markup
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
yup, but sadly, there is nothing in the unit tests for the Secure
client and server.
The source to SecureWebServer does contain this tantalising snippet:
80 * Standard security properties must be set before the
SecureWebserver
81 * can be used. The SecurityTool takes care of retrieving these
82 * values, but the parent application must set the necessary
83 * values before anything will work.
I know they're standard(ish), but I still can't find any good docs on
them :-(
On Tuesday, October 29, 2002, at 07:59 PM, Daniel Rall wrote:
> Ryan Hoegg <rh...@isisnetworks.net> writes:
>
>> I just went poking around my sources and found a good example of both
>> client and server under the examples/echo directory. Unfortunately it
>> is not included in the xmlrpc-1.1-src.zip on the site :(
>>
>> I will look around some more and see what I can find, but you can get
>> it from anonymous CVS.
>
> Unit tests are almost always the Right Place to Look for this sort of
> thing. A simple echo server is used to unit test XML-RPC.
> --
>
> Daniel Rall <dl...@finemaltcoding.com>
>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
yup, but sadly, there is nothing in the unit tests for the Secure
client and server.
The source to SecureWebServer does contain this tantalising snippet:
80 * Standard security properties must be set before the
SecureWebserver
81 * can be used. The SecurityTool takes care of retrieving these
82 * values, but the parent application must set the necessary
83 * values before anything will work.
I know they're standard(ish), but I still can't find any good docs on
them :-(
On Tuesday, October 29, 2002, at 07:59 PM, Daniel Rall wrote:
> Ryan Hoegg <rh...@isisnetworks.net> writes:
>
>> I just went poking around my sources and found a good example of both
>> client and server under the examples/echo directory. Unfortunately it
>> is not included in the xmlrpc-1.1-src.zip on the site :(
>>
>> I will look around some more and see what I can find, but you can get
>> it from anonymous CVS.
>
> Unit tests are almost always the Right Place to Look for this sort of
> thing. A simple echo server is used to unit test XML-RPC.
> --
>
> Daniel Rall <dl...@finemaltcoding.com>
>
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> I just went poking around my sources and found a good example of both
> client and server under the examples/echo directory. Unfortunately it
> is not included in the xmlrpc-1.1-src.zip on the site :(
>
> I will look around some more and see what I can find, but you can get
> it from anonymous CVS.
Unit tests are almost always the Right Place to Look for this sort of
thing. A simple echo server is used to unit test XML-RPC.
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> I just went poking around my sources and found a good example of both
> client and server under the examples/echo directory. Unfortunately it
> is not included in the xmlrpc-1.1-src.zip on the site :(
>
> I will look around some more and see what I can find, but you can get
> it from anonymous CVS.
Unit tests are almost always the Right Place to Look for this sort of
thing. A simple echo server is used to unit test XML-RPC.
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
sean wrote:
> For a complete newbie to this project (take it from me), these code
> examples are utter perfection. If you guys go with something else,
> don't stray too far from the straight-forwardness of what Martin just
> presented. I'm completely up and running...it's perfect.
Thats great!
> The only thing I might add is usage of an example argument (parameter)
> to the XML-RPC call.
/examples/echo/Client.java in CVS
> This looks to be a really great project; I'm going to use it for at
> least one real project. I hope yours survives all the SOAP propaganda
> (not a big fan of SOAP here).
They are really different tools for different jobs. I foresee myself
using both in some applications.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
sean wrote:
> For a complete newbie to this project (take it from me), these code
> examples are utter perfection. If you guys go with something else,
> don't stray too far from the straight-forwardness of what Martin just
> presented. I'm completely up and running...it's perfect.
Thats great!
> The only thing I might add is usage of an example argument (parameter)
> to the XML-RPC call.
/examples/echo/Client.java in CVS
> This looks to be a really great project; I'm going to use it for at
> least one real project. I hope yours survives all the SOAP propaganda
> (not a big fan of SOAP here).
They are really different tools for different jobs. I foresee myself
using both in some applications.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Re: Activity
Posted by sean <se...@celsoft.com>.
Martin Redington wrote:
>
> Hi Ryan,
>
> here are my examples. They're mostly ripped straight out of the
> main methods of existing stuff.
>
> Sorry not to tidy them up more, but its 1am, and I'm supposed to be
> doing something else.
>
> Feel free to use them, modify them, or throw them away. I'm going to
> do a secure version, maybe tomorrow, in the hope that someone will
> give me some pointers on how to get it working :-)
For a complete newbie to this project (take it from me), these code
examples are utter perfection. If you guys go with something else,
don't stray too far from the straight-forwardness of what Martin just
presented. I'm completely up and running...it's perfect.
The only thing I might add is usage of an example argument (parameter)
to the XML-RPC call.
This looks to be a really great project; I'm going to use it for at
least one real project. I hope yours survives all the SOAP propaganda
(not a big fan of SOAP here).
Sean O'Dell
Re: Activity
Posted by sean <se...@celsoft.com>.
Martin Redington wrote:
>
> Hi Ryan,
>
> here are my examples. They're mostly ripped straight out of the
> main methods of existing stuff.
>
> Sorry not to tidy them up more, but its 1am, and I'm supposed to be
> doing something else.
>
> Feel free to use them, modify them, or throw them away. I'm going to
> do a secure version, maybe tomorrow, in the hope that someone will
> give me some pointers on how to get it working :-)
For a complete newbie to this project (take it from me), these code
examples are utter perfection. If you guys go with something else,
don't stray too far from the straight-forwardness of what Martin just
presented. I'm completely up and running...it's perfect.
The only thing I might add is usage of an example argument (parameter)
to the XML-RPC call.
This looks to be a really great project; I'm going to use it for at
least one real project. I hope yours survives all the SOAP propaganda
(not a big fan of SOAP here).
Sean O'Dell
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> Hi Martin,
>
> Thanks for sending these along. I looked through your examples, and
> they seem very straightforward and ideal for Sean's needs. However,
> as a result of this they are very similar to the stuff in
> /examples/echo in CVS. I am going to use those for now unless someone
> points out something I am missing.
Using (and improving) the existing code Makes Sense (tm).
> In reference to your secure server needs, I realized that there are
> really several tutorials on setting up a server that should be
> explored. Ideally, we would end up with the following:
>
> - One for the built in WebServer
> - One for the built in WebServer using SSL
> - One for serving through a Servlet
>
> If there are others that would be useful, please forward them along as well.
Entering an issue for each of these tasks would be useful.
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Activity
Posted by Daniel Rall <dl...@finemaltcoding.com>.
Ryan Hoegg <rh...@isisnetworks.net> writes:
> Hi Martin,
>
> Thanks for sending these along. I looked through your examples, and
> they seem very straightforward and ideal for Sean's needs. However,
> as a result of this they are very similar to the stuff in
> /examples/echo in CVS. I am going to use those for now unless someone
> points out something I am missing.
Using (and improving) the existing code Makes Sense (tm).
> In reference to your secure server needs, I realized that there are
> really several tutorials on setting up a server that should be
> explored. Ideally, we would end up with the following:
>
> - One for the built in WebServer
> - One for the built in WebServer using SSL
> - One for serving through a Servlet
>
> If there are others that would be useful, please forward them along as well.
Entering an issue for each of these tasks would be useful.
--
Daniel Rall <dl...@finemaltcoding.com>
Re: Handler Trouble
Posted by sean <se...@celsoft.com>.
Hmm...argument mismatch? I wasn't passing any arguments at all, but
I'll try adding some and see what that gets me.
I guess I can go back to the Execute method and perform my own method
lookups if this doesn't work out...it just seemed so eloquent having the
invoker look methods up.
Thanks Martin,
Sean O'Dell
Martin Redington wrote:
> The only thing I can think of offhand, looking at the server
> documentation, is that you've somehow fallen afoul of some kind of
> argument mismatch. May be you could try playing around with arguments:
>
> 1. If you pass the XmlRpcServer any Java object, the server will try
> to resolve incoming calls via object introspection, i.e. by looking
> for public methods in the handler object corresponding to the method
> name and the parameter types of incoming requests. The input
> parameters of incoming XML-RPC requests must match the argument types
> of the Java method (see conversion table), or otherwise the method
> won't be found. The return value of the Java method must be supported
> by XML-RPC.
>
> (from http://xml.apache.org/xmlrpc/server.html)
>
>
> On Tuesday, October 29, 2002, at 04:21 PM, sean wrote:
>
>> Actually, maybe I didn't emphasize this one point enough. If I
>> change the name of the method I'm trying to call to a method that
>> doesn't exist, I do get a "method not found" error. It's only when I
>> specify the correct method name that I get this error. That says to
>> me "the invoker has found the method, but it's complaining."
>>
>> Just trying to figure out why it's complaining. The invoker has
>> clearly found the method, and it's definitely a public method...but
>> it complains about the method being public.
>>
>> Sean O'Dell
>>
>> Martin Redington wrote:
>>
>>>
>>> I haven't tried playing with your code, but I think this may be the
>>> expected behaviour (with a poorly written error message).
>>>
>>> When you invoke test.testmethod, the WebServer (or some component of
>>> it) looks for the handler registered under the name "test", and then
>>> uses introspection to find the "testmethod" method.
>>>
>>> If you try and call something else, e.g. test.someothermethod, then
>>> the WebServer looks for a "someothermethod" method on the registered
>>> handler.
>>>
>>> As there isn't a method called "someothermethod", it throws an
>>> exception with the message:
>>>
>>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>>> TestHandler with modifiers "public"
>>>
>>>
>>>
>>> This presumably actually means: "I couldn't find a public method in
>>> the TestHandler class called "someothermethod", so I'm stuffed".
>>>
>>> Hope this helps,
>>>
>>> cheers,
>>> Martin
>>>
>>> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>>>
>>>> I got Martin's "TestServer" example working, and then I went on to
>>>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>>>> the object introspection as explained in the server how-to. My
>>>> test client keeps giving me this odd error I can't seem to get rid of:
>>>>
>>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>>> TestHandler with modifiers "public"
>>>>
>>>> This error is actually thrown by the XML-RPC web server. Here's
>>>> the code for TestHandler:
>>>>
>>>> class TestHandler
>>>> {
>>>> public String testerror() throws Exception
>>>> {
>>>> System.err.println("TestServer: executing " + "testerror");
>>>> throw new XmlRpcException(20, "this is an error");
>>>> }
>>>> }
>>>>
>>>> I set up the handler in "public static void main" like this:
>>>>
>>>> TestHandler testHandler = new TestHandler();
>>>> webServer.addHandler("test", testHandler);
>>>>
>>>> Clearly, the method is being found because when I call
>>>> "test.testerror" from the client, I get that error, but if I change
>>>> the call to use any other name, it throws a "method not found" sort
>>>> of error.
>>>>
>>>> Why is the Invoker (I think that's who is throwing the error)
>>>> throwing an error and complaining about the testerror method being
>>>> public? Isn't is supposed to be public?
>>>>
>>>> Sean O'Dell
>>>>
>>>>
>>
>>
>>
>>
Re: Handler Trouble
Posted by sean <se...@celsoft.com>.
Hmm...argument mismatch? I wasn't passing any arguments at all, but
I'll try adding some and see what that gets me.
I guess I can go back to the Execute method and perform my own method
lookups if this doesn't work out...it just seemed so eloquent having the
invoker look methods up.
Thanks Martin,
Sean O'Dell
Martin Redington wrote:
> The only thing I can think of offhand, looking at the server
> documentation, is that you've somehow fallen afoul of some kind of
> argument mismatch. May be you could try playing around with arguments:
>
> 1. If you pass the XmlRpcServer any Java object, the server will try
> to resolve incoming calls via object introspection, i.e. by looking
> for public methods in the handler object corresponding to the method
> name and the parameter types of incoming requests. The input
> parameters of incoming XML-RPC requests must match the argument types
> of the Java method (see conversion table), or otherwise the method
> won't be found. The return value of the Java method must be supported
> by XML-RPC.
>
> (from http://xml.apache.org/xmlrpc/server.html)
>
>
> On Tuesday, October 29, 2002, at 04:21 PM, sean wrote:
>
>> Actually, maybe I didn't emphasize this one point enough. If I
>> change the name of the method I'm trying to call to a method that
>> doesn't exist, I do get a "method not found" error. It's only when I
>> specify the correct method name that I get this error. That says to
>> me "the invoker has found the method, but it's complaining."
>>
>> Just trying to figure out why it's complaining. The invoker has
>> clearly found the method, and it's definitely a public method...but
>> it complains about the method being public.
>>
>> Sean O'Dell
>>
>> Martin Redington wrote:
>>
>>>
>>> I haven't tried playing with your code, but I think this may be the
>>> expected behaviour (with a poorly written error message).
>>>
>>> When you invoke test.testmethod, the WebServer (or some component of
>>> it) looks for the handler registered under the name "test", and then
>>> uses introspection to find the "testmethod" method.
>>>
>>> If you try and call something else, e.g. test.someothermethod, then
>>> the WebServer looks for a "someothermethod" method on the registered
>>> handler.
>>>
>>> As there isn't a method called "someothermethod", it throws an
>>> exception with the message:
>>>
>>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>>> TestHandler with modifiers "public"
>>>
>>>
>>>
>>> This presumably actually means: "I couldn't find a public method in
>>> the TestHandler class called "someothermethod", so I'm stuffed".
>>>
>>> Hope this helps,
>>>
>>> cheers,
>>> Martin
>>>
>>> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>>>
>>>> I got Martin's "TestServer" example working, and then I went on to
>>>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>>>> the object introspection as explained in the server how-to. My
>>>> test client keeps giving me this odd error I can't seem to get rid of:
>>>>
>>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>>> TestHandler with modifiers "public"
>>>>
>>>> This error is actually thrown by the XML-RPC web server. Here's
>>>> the code for TestHandler:
>>>>
>>>> class TestHandler
>>>> {
>>>> public String testerror() throws Exception
>>>> {
>>>> System.err.println("TestServer: executing " + "testerror");
>>>> throw new XmlRpcException(20, "this is an error");
>>>> }
>>>> }
>>>>
>>>> I set up the handler in "public static void main" like this:
>>>>
>>>> TestHandler testHandler = new TestHandler();
>>>> webServer.addHandler("test", testHandler);
>>>>
>>>> Clearly, the method is being found because when I call
>>>> "test.testerror" from the client, I get that error, but if I change
>>>> the call to use any other name, it throws a "method not found" sort
>>>> of error.
>>>>
>>>> Why is the Invoker (I think that's who is throwing the error)
>>>> throwing an error and complaining about the testerror method being
>>>> public? Isn't is supposed to be public?
>>>>
>>>> Sean O'Dell
>>>>
>>>>
>>
>>
>>
>>
Re: Handler Trouble
Posted by Martin Redington <m....@ucl.ac.uk>.
The only thing I can think of offhand, looking at the server
documentation, is that you've somehow fallen afoul of some kind of
argument mismatch. May be you could try playing around with arguments:
1. If you pass the XmlRpcServer any Java object, the server will try
to resolve incoming calls via object introspection, i.e. by looking for
public methods in the handler object corresponding to the method name
and the parameter types of incoming requests. The input parameters of
incoming XML-RPC requests must match the argument types of the Java
method (see conversion table), or otherwise the method won't be found.
The return value of the Java method must be supported by XML-RPC.
(from http://xml.apache.org/xmlrpc/server.html)
On Tuesday, October 29, 2002, at 04:21 PM, sean wrote:
> Actually, maybe I didn't emphasize this one point enough. If I change
> the name of the method I'm trying to call to a method that doesn't
> exist, I do get a "method not found" error. It's only when I specify
> the correct method name that I get this error. That says to me "the
> invoker has found the method, but it's complaining."
>
> Just trying to figure out why it's complaining. The invoker has
> clearly found the method, and it's definitely a public method...but it
> complains about the method being public.
>
> Sean O'Dell
>
> Martin Redington wrote:
>
>>
>> I haven't tried playing with your code, but I think this may be the
>> expected behaviour (with a poorly written error message).
>>
>> When you invoke test.testmethod, the WebServer (or some component of
>> it) looks for the handler registered under the name "test", and then
>> uses introspection to find the "testmethod" method.
>>
>> If you try and call something else, e.g. test.someothermethod, then
>> the WebServer looks for a "someothermethod" method on the registered
>> handler.
>>
>> As there isn't a method called "someothermethod", it throws an
>> exception with the message:
>>
>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>> TestHandler with modifiers "public"
>>
>>
>> This presumably actually means: "I couldn't find a public method in
>> the TestHandler class called "someothermethod", so I'm stuffed".
>>
>> Hope this helps,
>>
>> cheers,
>> Martin
>>
>> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>>
>>> I got Martin's "TestServer" example working, and then I went on to
>>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>>> the object introspection as explained in the server how-to. My test
>>> client keeps giving me this odd error I can't seem to get rid of:
>>>
>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>> TestHandler with modifiers "public"
>>>
>>> This error is actually thrown by the XML-RPC web server. Here's the
>>> code for TestHandler:
>>>
>>> class TestHandler
>>> {
>>> public String testerror() throws Exception
>>> {
>>> System.err.println("TestServer: executing " +
>>> "testerror");
>>> throw new XmlRpcException(20, "this is an error");
>>> }
>>> }
>>>
>>> I set up the handler in "public static void main" like this:
>>>
>>> TestHandler testHandler = new TestHandler();
>>> webServer.addHandler("test", testHandler);
>>>
>>> Clearly, the method is being found because when I call
>>> "test.testerror" from the client, I get that error, but if I change
>>> the call to use any other name, it throws a "method not found" sort
>>> of error.
>>>
>>> Why is the Invoker (I think that's who is throwing the error)
>>> throwing an error and complaining about the testerror method being
>>> public? Isn't is supposed to be public?
>>>
>>> Sean O'Dell
>>>
>>>
>
>
>
>
Re: Handler Trouble
Posted by Martin Redington <m....@ucl.ac.uk>.
The only thing I can think of offhand, looking at the server
documentation, is that you've somehow fallen afoul of some kind of
argument mismatch. May be you could try playing around with arguments:
1. If you pass the XmlRpcServer any Java object, the server will try
to resolve incoming calls via object introspection, i.e. by looking for
public methods in the handler object corresponding to the method name
and the parameter types of incoming requests. The input parameters of
incoming XML-RPC requests must match the argument types of the Java
method (see conversion table), or otherwise the method won't be found.
The return value of the Java method must be supported by XML-RPC.
(from http://xml.apache.org/xmlrpc/server.html)
On Tuesday, October 29, 2002, at 04:21 PM, sean wrote:
> Actually, maybe I didn't emphasize this one point enough. If I change
> the name of the method I'm trying to call to a method that doesn't
> exist, I do get a "method not found" error. It's only when I specify
> the correct method name that I get this error. That says to me "the
> invoker has found the method, but it's complaining."
>
> Just trying to figure out why it's complaining. The invoker has
> clearly found the method, and it's definitely a public method...but it
> complains about the method being public.
>
> Sean O'Dell
>
> Martin Redington wrote:
>
>>
>> I haven't tried playing with your code, but I think this may be the
>> expected behaviour (with a poorly written error message).
>>
>> When you invoke test.testmethod, the WebServer (or some component of
>> it) looks for the handler registered under the name "test", and then
>> uses introspection to find the "testmethod" method.
>>
>> If you try and call something else, e.g. test.someothermethod, then
>> the WebServer looks for a "someothermethod" method on the registered
>> handler.
>>
>> As there isn't a method called "someothermethod", it throws an
>> exception with the message:
>>
>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>> TestHandler with modifiers "public"
>>
>>
>> This presumably actually means: "I couldn't find a public method in
>> the TestHandler class called "someothermethod", so I'm stuffed".
>>
>> Hope this helps,
>>
>> cheers,
>> Martin
>>
>> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>>
>>> I got Martin's "TestServer" example working, and then I went on to
>>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>>> the object introspection as explained in the server how-to. My test
>>> client keeps giving me this odd error I can't seem to get rid of:
>>>
>>> Class org.apache.xmlrpc.Invoker can not access a member of class
>>> TestHandler with modifiers "public"
>>>
>>> This error is actually thrown by the XML-RPC web server. Here's the
>>> code for TestHandler:
>>>
>>> class TestHandler
>>> {
>>> public String testerror() throws Exception
>>> {
>>> System.err.println("TestServer: executing " +
>>> "testerror");
>>> throw new XmlRpcException(20, "this is an error");
>>> }
>>> }
>>>
>>> I set up the handler in "public static void main" like this:
>>>
>>> TestHandler testHandler = new TestHandler();
>>> webServer.addHandler("test", testHandler);
>>>
>>> Clearly, the method is being found because when I call
>>> "test.testerror" from the client, I get that error, but if I change
>>> the call to use any other name, it throws a "method not found" sort
>>> of error.
>>>
>>> Why is the Invoker (I think that's who is throwing the error)
>>> throwing an error and complaining about the testerror method being
>>> public? Isn't is supposed to be public?
>>>
>>> Sean O'Dell
>>>
>>>
>
>
>
>
Re: Handler Trouble
Posted by sean <se...@celsoft.com>.
Actually, maybe I didn't emphasize this one point enough. If I change
the name of the method I'm trying to call to a method that doesn't
exist, I do get a "method not found" error. It's only when I specify
the correct method name that I get this error. That says to me "the
invoker has found the method, but it's complaining."
Just trying to figure out why it's complaining. The invoker has clearly
found the method, and it's definitely a public method...but it complains
about the method being public.
Sean O'Dell
Martin Redington wrote:
>
> I haven't tried playing with your code, but I think this may be the
> expected behaviour (with a poorly written error message).
>
> When you invoke test.testmethod, the WebServer (or some component of
> it) looks for the handler registered under the name "test", and then
> uses introspection to find the "testmethod" method.
>
> If you try and call something else, e.g. test.someothermethod, then
> the WebServer looks for a "someothermethod" method on the registered
> handler.
>
> As there isn't a method called "someothermethod", it throws an
> exception with the message:
>
>> Class org.apache.xmlrpc.Invoker can not access a member of class
>> TestHandler with modifiers "public"
>
>
> This presumably actually means: "I couldn't find a public method in
> the TestHandler class called "someothermethod", so I'm stuffed".
>
> Hope this helps,
>
> cheers,
> Martin
>
> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>
>> I got Martin's "TestServer" example working, and then I went on to
>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>> the object introspection as explained in the server how-to. My test
>> client keeps giving me this odd error I can't seem to get rid of:
>>
>> Class org.apache.xmlrpc.Invoker can not access a member of class
>> TestHandler with modifiers "public"
>>
>> This error is actually thrown by the XML-RPC web server. Here's the
>> code for TestHandler:
>>
>> class TestHandler
>> {
>> public String testerror() throws Exception
>> {
>> System.err.println("TestServer: executing " + "testerror");
>> throw new XmlRpcException(20, "this is an error");
>> }
>> }
>>
>> I set up the handler in "public static void main" like this:
>>
>> TestHandler testHandler = new TestHandler();
>> webServer.addHandler("test", testHandler);
>>
>> Clearly, the method is being found because when I call
>> "test.testerror" from the client, I get that error, but if I change
>> the call to use any other name, it throws a "method not found" sort
>> of error.
>>
>> Why is the Invoker (I think that's who is throwing the error)
>> throwing an error and complaining about the testerror method being
>> public? Isn't is supposed to be public?
>>
>> Sean O'Dell
>>
>>
Re: Handler Trouble
Posted by sean <se...@celsoft.com>.
Actually, maybe I didn't emphasize this one point enough. If I change
the name of the method I'm trying to call to a method that doesn't
exist, I do get a "method not found" error. It's only when I specify
the correct method name that I get this error. That says to me "the
invoker has found the method, but it's complaining."
Just trying to figure out why it's complaining. The invoker has clearly
found the method, and it's definitely a public method...but it complains
about the method being public.
Sean O'Dell
Martin Redington wrote:
>
> I haven't tried playing with your code, but I think this may be the
> expected behaviour (with a poorly written error message).
>
> When you invoke test.testmethod, the WebServer (or some component of
> it) looks for the handler registered under the name "test", and then
> uses introspection to find the "testmethod" method.
>
> If you try and call something else, e.g. test.someothermethod, then
> the WebServer looks for a "someothermethod" method on the registered
> handler.
>
> As there isn't a method called "someothermethod", it throws an
> exception with the message:
>
>> Class org.apache.xmlrpc.Invoker can not access a member of class
>> TestHandler with modifiers "public"
>
>
> This presumably actually means: "I couldn't find a public method in
> the TestHandler class called "someothermethod", so I'm stuffed".
>
> Hope this helps,
>
> cheers,
> Martin
>
> On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
>
>> I got Martin's "TestServer" example working, and then I went on to
>> try and make a "non-XmlRpcHandler" handler, hoping it would perform
>> the object introspection as explained in the server how-to. My test
>> client keeps giving me this odd error I can't seem to get rid of:
>>
>> Class org.apache.xmlrpc.Invoker can not access a member of class
>> TestHandler with modifiers "public"
>>
>> This error is actually thrown by the XML-RPC web server. Here's the
>> code for TestHandler:
>>
>> class TestHandler
>> {
>> public String testerror() throws Exception
>> {
>> System.err.println("TestServer: executing " + "testerror");
>> throw new XmlRpcException(20, "this is an error");
>> }
>> }
>>
>> I set up the handler in "public static void main" like this:
>>
>> TestHandler testHandler = new TestHandler();
>> webServer.addHandler("test", testHandler);
>>
>> Clearly, the method is being found because when I call
>> "test.testerror" from the client, I get that error, but if I change
>> the call to use any other name, it throws a "method not found" sort
>> of error.
>>
>> Why is the Invoker (I think that's who is throwing the error)
>> throwing an error and complaining about the testerror method being
>> public? Isn't is supposed to be public?
>>
>> Sean O'Dell
>>
>>
Re: List archive
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Danny Angus" <da...@apache.org> writes:
> Mornin,
>
> Is there an archive for this list anywhere? I looked in all the
> usual places, and only found xml.apache.org/mail/, which is
> something, but not very friendly.
http://archives.apache.org/eyebrowse/SummarizeList?listName=rpc-dev@xml.apache.org
http://archives.apache.org/eyebrowse/SummarizeList?listName=rpc-user@xml.apache.org
--
Daniel Rall <dl...@finemaltcoding.com>
Re: List archive
Posted by Daniel Rall <dl...@finemaltcoding.com>.
"Danny Angus" <da...@apache.org> writes:
> Mornin,
>
> Is there an archive for this list anywhere? I looked in all the
> usual places, and only found xml.apache.org/mail/, which is
> something, but not very friendly.
http://archives.apache.org/eyebrowse/SummarizeList?listName=rpc-dev@xml.apache.org
http://archives.apache.org/eyebrowse/SummarizeList?listName=rpc-user@xml.apache.org
--
Daniel Rall <dl...@finemaltcoding.com>
List archive
Posted by Danny Angus <da...@apache.org>.
Mornin,
Is there an archive for this list anywhere?
I looked in all the usual places, and only found xml.apache.org/mail/, which is something, but not very friendly.
d.
List archive
Posted by Danny Angus <da...@apache.org>.
Mornin,
Is there an archive for this list anywhere?
I looked in all the usual places, and only found xml.apache.org/mail/, which is something, but not very friendly.
d.
Re: Handler Trouble
Posted by Martin Redington <m....@ucl.ac.uk>.
I haven't tried playing with your code, but I think this may be the
expected behaviour (with a poorly written error message).
When you invoke test.testmethod, the WebServer (or some component of
it) looks for the handler registered under the name "test", and then
uses introspection to find the "testmethod" method.
If you try and call something else, e.g. test.someothermethod, then the
WebServer looks for a "someothermethod" method on the registered
handler.
As there isn't a method called "someothermethod", it throws an
exception with the message:
> Class org.apache.xmlrpc.Invoker can not access a member of class
> TestHandler with modifiers "public"
This presumably actually means: "I couldn't find a public method in the
TestHandler class called "someothermethod", so I'm stuffed".
Hope this helps,
cheers,
Martin
On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
> I got Martin's "TestServer" example working, and then I went on to try
> and make a "non-XmlRpcHandler" handler, hoping it would perform the
> object introspection as explained in the server how-to. My test
> client keeps giving me this odd error I can't seem to get rid of:
>
> Class org.apache.xmlrpc.Invoker can not access a member of class
> TestHandler with modifiers "public"
>
> This error is actually thrown by the XML-RPC web server. Here's the
> code for TestHandler:
>
> class TestHandler
> {
> public String testerror() throws Exception
> {
> System.err.println("TestServer: executing " + "testerror");
> throw new XmlRpcException(20, "this is an error");
> }
> }
>
> I set up the handler in "public static void main" like this:
>
> TestHandler testHandler = new TestHandler();
> webServer.addHandler("test", testHandler);
>
> Clearly, the method is being found because when I call
> "test.testerror" from the client, I get that error, but if I change
> the call to use any other name, it throws a "method not found" sort of
> error.
>
> Why is the Invoker (I think that's who is throwing the error) throwing
> an error and complaining about the testerror method being public?
> Isn't is supposed to be public?
>
> Sean O'Dell
>
>
Re: Handler Trouble
Posted by Martin Redington <m....@ucl.ac.uk>.
I haven't tried playing with your code, but I think this may be the
expected behaviour (with a poorly written error message).
When you invoke test.testmethod, the WebServer (or some component of
it) looks for the handler registered under the name "test", and then
uses introspection to find the "testmethod" method.
If you try and call something else, e.g. test.someothermethod, then the
WebServer looks for a "someothermethod" method on the registered
handler.
As there isn't a method called "someothermethod", it throws an
exception with the message:
> Class org.apache.xmlrpc.Invoker can not access a member of class
> TestHandler with modifiers "public"
This presumably actually means: "I couldn't find a public method in the
TestHandler class called "someothermethod", so I'm stuffed".
Hope this helps,
cheers,
Martin
On Tuesday, October 29, 2002, at 07:09 AM, sean wrote:
> I got Martin's "TestServer" example working, and then I went on to try
> and make a "non-XmlRpcHandler" handler, hoping it would perform the
> object introspection as explained in the server how-to. My test
> client keeps giving me this odd error I can't seem to get rid of:
>
> Class org.apache.xmlrpc.Invoker can not access a member of class
> TestHandler with modifiers "public"
>
> This error is actually thrown by the XML-RPC web server. Here's the
> code for TestHandler:
>
> class TestHandler
> {
> public String testerror() throws Exception
> {
> System.err.println("TestServer: executing " + "testerror");
> throw new XmlRpcException(20, "this is an error");
> }
> }
>
> I set up the handler in "public static void main" like this:
>
> TestHandler testHandler = new TestHandler();
> webServer.addHandler("test", testHandler);
>
> Clearly, the method is being found because when I call
> "test.testerror" from the client, I get that error, but if I change
> the call to use any other name, it throws a "method not found" sort of
> error.
>
> Why is the Invoker (I think that's who is throwing the error) throwing
> an error and complaining about the testerror method being public?
> Isn't is supposed to be public?
>
> Sean O'Dell
>
>
Handler Trouble
Posted by sean <se...@celsoft.com>.
I got Martin's "TestServer" example working, and then I went on to try
and make a "non-XmlRpcHandler" handler, hoping it would perform the
object introspection as explained in the server how-to. My test client
keeps giving me this odd error I can't seem to get rid of:
Class org.apache.xmlrpc.Invoker can not access a member of class
TestHandler with modifiers "public"
This error is actually thrown by the XML-RPC web server. Here's the
code for TestHandler:
class TestHandler
{
public String testerror() throws Exception
{
System.err.println("TestServer: executing " + "testerror");
throw new XmlRpcException(20, "this is an error");
}
}
I set up the handler in "public static void main" like this:
TestHandler testHandler = new TestHandler();
webServer.addHandler("test", testHandler);
Clearly, the method is being found because when I call "test.testerror"
from the client, I get that error, but if I change the call to use any
other name, it throws a "method not found" sort of error.
Why is the Invoker (I think that's who is throwing the error) throwing
an error and complaining about the testerror method being public? Isn't
is supposed to be public?
Sean O'Dell
Handler Trouble
Posted by sean <se...@celsoft.com>.
I got Martin's "TestServer" example working, and then I went on to try
and make a "non-XmlRpcHandler" handler, hoping it would perform the
object introspection as explained in the server how-to. My test client
keeps giving me this odd error I can't seem to get rid of:
Class org.apache.xmlrpc.Invoker can not access a member of class
TestHandler with modifiers "public"
This error is actually thrown by the XML-RPC web server. Here's the
code for TestHandler:
class TestHandler
{
public String testerror() throws Exception
{
System.err.println("TestServer: executing " + "testerror");
throw new XmlRpcException(20, "this is an error");
}
}
I set up the handler in "public static void main" like this:
TestHandler testHandler = new TestHandler();
webServer.addHandler("test", testHandler);
Clearly, the method is being found because when I call "test.testerror"
from the client, I get that error, but if I change the call to use any
other name, it throws a "method not found" sort of error.
Why is the Invoker (I think that's who is throwing the error) throwing
an error and complaining about the testerror method being public? Isn't
is supposed to be public?
Sean O'Dell
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
On Tuesday, October 29, 2002, at 01:18 AM, Ryan Hoegg wrote:
> Hi Martin,
>
> Thanks for sending these along. I looked through your examples, and
> they seem very straightforward and ideal for Sean's needs. However,
> as a result of this they are very similar to the stuff in
> /examples/echo in CVS. I am going to use those for now unless someone
> points out something I am missing.
That's fine with me. As I said, they're essentially just ripped main
methods.
> In reference to your secure server needs, I realized that there are
> really several tutorials on setting up a server that should be
> explored. Ideally, we would end up with the following:
> - One for the built in WebServer
> - One for the built in WebServer using SSL
> - One for serving through a Servlet
>
> If there are others that would be useful, please forward them along as
> well.
Well, I'm going to try and fix up my secure Hello World tomorrow. I'd
like to get everything working properly (e.g, TLS and SSL), and to
understand how it all works. I'm most of the way there, but I'm
obviously missing a few tricks, most of which are pretty standard I
think.
I suspect my problems and their solutions would be a good basis for a
secure XML-RPC how-to.
More tomorrow ...
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
On Tuesday, October 29, 2002, at 01:18 AM, Ryan Hoegg wrote:
> Hi Martin,
>
> Thanks for sending these along. I looked through your examples, and
> they seem very straightforward and ideal for Sean's needs. However,
> as a result of this they are very similar to the stuff in
> /examples/echo in CVS. I am going to use those for now unless someone
> points out something I am missing.
That's fine with me. As I said, they're essentially just ripped main
methods.
> In reference to your secure server needs, I realized that there are
> really several tutorials on setting up a server that should be
> explored. Ideally, we would end up with the following:
> - One for the built in WebServer
> - One for the built in WebServer using SSL
> - One for serving through a Servlet
>
> If there are others that would be useful, please forward them along as
> well.
Well, I'm going to try and fix up my secure Hello World tomorrow. I'd
like to get everything working properly (e.g, TLS and SSL), and to
understand how it all works. I'm most of the way there, but I'm
obviously missing a few tricks, most of which are pretty standard I
think.
I suspect my problems and their solutions would be a good basis for a
secure XML-RPC how-to.
More tomorrow ...
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hi Martin,
Thanks for sending these along. I looked through your examples, and
they seem very straightforward and ideal for Sean's needs. However, as
a result of this they are very similar to the stuff in /examples/echo in
CVS. I am going to use those for now unless someone points out
something I am missing.
In reference to your secure server needs, I realized that there are
really several tutorials on setting up a server that should be explored.
Ideally, we would end up with the following:
- One for the built in WebServer
- One for the built in WebServer using SSL
- One for serving through a Servlet
If there are others that would be useful, please forward them along as well.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Martin Redington wrote:
>
> Hi Ryan,
>
> here are my examples. They're mostly ripped straight out of the
> main methods of existing stuff.
>
> Sorry not to tidy them up more, but its 1am, and I'm supposed to be
> doing something else.
>
> Feel free to use them, modify them, or throw them away. I'm going to
> do a secure version, maybe tomorrow, in the hope that someone will
> give me some pointers on how to get it working :-)
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hi Martin,
Thanks for sending these along. I looked through your examples, and
they seem very straightforward and ideal for Sean's needs. However, as
a result of this they are very similar to the stuff in /examples/echo in
CVS. I am going to use those for now unless someone points out
something I am missing.
In reference to your secure server needs, I realized that there are
really several tutorials on setting up a server that should be explored.
Ideally, we would end up with the following:
- One for the built in WebServer
- One for the built in WebServer using SSL
- One for serving through a Servlet
If there are others that would be useful, please forward them along as well.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Martin Redington wrote:
>
> Hi Ryan,
>
> here are my examples. They're mostly ripped straight out of the
> main methods of existing stuff.
>
> Sorry not to tidy them up more, but its 1am, and I'm supposed to be
> doing something else.
>
> Feel free to use them, modify them, or throw them away. I'm going to
> do a secure version, maybe tomorrow, in the hope that someone will
> give me some pointers on how to get it working :-)
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
Hi Ryan,
here are my examples. They're mostly ripped straight out of the main
methods of existing stuff.
Sorry not to tidy them up more, but its 1am, and I'm supposed to be
doing something else.
Feel free to use them, modify them, or throw them away. I'm going to do
a secure version, maybe tomorrow, in the hope that someone will give me
some pointers on how to get it working :-)
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
Hi Ryan,
here are my examples. They're mostly ripped straight out of the main
methods of existing stuff.
Sorry not to tidy them up more, but its 1am, and I'm supposed to be
doing something else.
Feel free to use them, modify them, or throw them away. I'm going to do
a secure version, maybe tomorrow, in the hope that someone will give me
some pointers on how to get it working :-)
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
I just went poking around my sources and found a good example of both
client and server under the examples/echo directory. Unfortunately it
is not included in the xmlrpc-1.1-src.zip on the site :(
I will look around some more and see what I can find, but you can get it
from anonymous CVS.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
sean wrote:
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
I just went poking around my sources and found a good example of both
client and server under the examples/echo directory. Unfortunately it
is not included in the xmlrpc-1.1-src.zip on the site :(
I will look around some more and see what I can find, but you can get it
from anonymous CVS.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
sean wrote:
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
Re: Activity
Posted by Nicolas RAOUL <ni...@makina-corpus.com>.
One week ago I learnt about XML-RPC and I did a little example with the
Apache librairies.
My humble example consists in:
- a server
- an applet
The appet contains a textbox, a button and a label. You can type a message
in the text box, then hit the button, the applet sends the message to the
server, the server gives a reply, this reply is displayed in the applet.
It's really basic, easy to understand, and I think anyone can modify it.
All the code and librairies are available in:
www.chez.com/rastabot/xmlrpc/nr-xmlrpc-example.tar.gz
No other files are needed, an explanation is provided as README.TXT
Hope this helps.
Nicolas RAOUL.
By the way:
I have been looking for sort of XML-RPC which wouldn't be tied to HTTP
Any link for this ?
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
>
> The snippets that are there now are tedious to assemble into a working
> server. The example isn't complete in terms of "here's you get you an
> XML-RPC server going" so I'm left with no way to figure out how to fill
> in the blanks except by poking around, guessing...testing. It's very
> stressful on this newcomer.
>
> Once I see a "Hello, world" example application running, then I will
> know I have all the necessary components installed, and I can then
> extend the example to start handling the tasks I need the application to
> perform.
>
> Sean O'Dell
>
Re: Activity
Posted by Nicolas RAOUL <ni...@makina-corpus.com>.
One week ago I learnt about XML-RPC and I did a little example with the
Apache librairies.
My humble example consists in:
- a server
- an applet
The appet contains a textbox, a button and a label. You can type a message
in the text box, then hit the button, the applet sends the message to the
server, the server gives a reply, this reply is displayed in the applet.
It's really basic, easy to understand, and I think anyone can modify it.
All the code and librairies are available in:
www.chez.com/rastabot/xmlrpc/nr-xmlrpc-example.tar.gz
No other files are needed, an explanation is provided as README.TXT
Hope this helps.
Nicolas RAOUL.
By the way:
I have been looking for sort of XML-RPC which wouldn't be tied to HTTP
Any link for this ?
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
>
> The snippets that are there now are tedious to assemble into a working
> server. The example isn't complete in terms of "here's you get you an
> XML-RPC server going" so I'm left with no way to figure out how to fill
> in the blanks except by poking around, guessing...testing. It's very
> stressful on this newcomer.
>
> Once I see a "Hello, world" example application running, then I will
> know I have all the necessary components installed, and I can then
> extend the example to start handling the tasks I need the application to
> perform.
>
> Sean O'Dell
>
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
The best way to contribute that would be by:
1. Creating a bug report in Bugzilla
2. Formatting your example with documentation as an xdoc
3. Attaching the xdoc to your bug report with an explanation of what it is.
I will be happy to fill in the blanks for the parts you don't want to
do. I would appreciate it if you formatted it like the current server
side XML-RPC document and included explanations of the steps involved as
my involvement in this project is mostly client side.
If nothing else, though, just ship me what you have and I will shop
around on the dev list for someone to clean it up for the site.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Martin Redington wrote:
> Funnily enough, I've got almost exactly that ("hello world") sitting
> right here.
>
> I'll tidy it up a bit, if someone else will write some intro text,
> with instructions for windows users if required (unix only here, I'm
> afraid).
>
> On Monday, October 28, 2002, at 10:55 PM, sean wrote:
>
>> What would be nice is if you did away with the server example that's
>> there now entirely and put up a "Hello, world" application (complete
>> source, nothing fancy) with full instructions on getting the example
>> working so anyone new who comes along can follow the instructions,
>> get the server working, then contact the server with a browser (like
>> Netscape) and see the results.
>>
>> The snippets that are there now are tedious to assemble into a
>> working server. The example isn't complete in terms of "here's you
>> get you an XML-RPC server going" so I'm left with no way to figure
>> out how to fill in the blanks except by poking around,
>> guessing...testing. It's very stressful on this newcomer.
>>
>> Once I see a "Hello, world" example application running, then I will
>> know I have all the necessary components installed, and I can then
>> extend the example to start handling the tasks I need the application
>> to perform.
>>
>> Sean O'Dell
>
Re: Activity
Posted by sean <se...@celsoft.com>.
Martin Redington wrote:
>
> Funnily enough, I've got almost exactly that ("hello world") sitting
> right here.
>
> I'll tidy it up a bit, if someone else will write some intro text,
> with instructions for windows users if required (unix only here, I'm
> afraid).
That would be great. The compiling and running part can be left
out...it's just the basic code that matters to me. A few snippets of
code and skeletal class documentation isn't enough for me...I'm not
smart enough to figure it all out I guess. It will be nice to have the
class reference once I understand "how it works" but right now, "how it
works" is really unclear to me.
Sean O'Dell
Re: Activity
Posted by sean <se...@celsoft.com>.
Martin Redington wrote:
>
> Funnily enough, I've got almost exactly that ("hello world") sitting
> right here.
>
> I'll tidy it up a bit, if someone else will write some intro text,
> with instructions for windows users if required (unix only here, I'm
> afraid).
That would be great. The compiling and running part can be left
out...it's just the basic code that matters to me. A few snippets of
code and skeletal class documentation isn't enough for me...I'm not
smart enough to figure it all out I guess. It will be nice to have the
class reference once I understand "how it works" but right now, "how it
works" is really unclear to me.
Sean O'Dell
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
The best way to contribute that would be by:
1. Creating a bug report in Bugzilla
2. Formatting your example with documentation as an xdoc
3. Attaching the xdoc to your bug report with an explanation of what it is.
I will be happy to fill in the blanks for the parts you don't want to
do. I would appreciate it if you formatted it like the current server
side XML-RPC document and included explanations of the steps involved as
my involvement in this project is mostly client side.
If nothing else, though, just ship me what you have and I will shop
around on the dev list for someone to clean it up for the site.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Martin Redington wrote:
> Funnily enough, I've got almost exactly that ("hello world") sitting
> right here.
>
> I'll tidy it up a bit, if someone else will write some intro text,
> with instructions for windows users if required (unix only here, I'm
> afraid).
>
> On Monday, October 28, 2002, at 10:55 PM, sean wrote:
>
>> What would be nice is if you did away with the server example that's
>> there now entirely and put up a "Hello, world" application (complete
>> source, nothing fancy) with full instructions on getting the example
>> working so anyone new who comes along can follow the instructions,
>> get the server working, then contact the server with a browser (like
>> Netscape) and see the results.
>>
>> The snippets that are there now are tedious to assemble into a
>> working server. The example isn't complete in terms of "here's you
>> get you an XML-RPC server going" so I'm left with no way to figure
>> out how to fill in the blanks except by poking around,
>> guessing...testing. It's very stressful on this newcomer.
>>
>> Once I see a "Hello, world" example application running, then I will
>> know I have all the necessary components installed, and I can then
>> extend the example to start handling the tasks I need the application
>> to perform.
>>
>> Sean O'Dell
>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
Funnily enough, I've got almost exactly that ("hello world") sitting
right here.
I'll tidy it up a bit, if someone else will write some intro text, with
instructions for windows users if required (unix only here, I'm afraid).
On Monday, October 28, 2002, at 10:55 PM, sean wrote:
> Ryan Hoegg wrote:
>
>> sean wrote:
>>
>>> I was thinking of using the Apache XML-RPC project as an application
>>> framework for some projects I have coming up. The site at
>>> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but
>>> there's a terrible lack of "how-to" documentation there and I
>>> couldn't find much news or other signs of activity.
>>
>>
>> What kind of how-to documentation are you looking for? We are aware
>> that the documentation is scanty, but as a potential user your ideas
>> of what a "Getting started" document would contain would be very
>> helpful.
>>
>> The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html)
>> on the web page gives some information on using the XML-RPC client
>> classes, and the "Server Side XML-RPC" link
>> (http://xml.apache.org/xmlrpc/server.html) gives some information on
>> using the library to provide an XML-RPC interface to your software.
>
>
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
>
> The snippets that are there now are tedious to assemble into a working
> server. The example isn't complete in terms of "here's you get you an
> XML-RPC server going" so I'm left with no way to figure out how to
> fill in the blanks except by poking around, guessing...testing. It's
> very stressful on this newcomer.
>
> Once I see a "Hello, world" example application running, then I will
> know I have all the necessary components installed, and I can then
> extend the example to start handling the tasks I need the application
> to perform.
>
> Sean O'Dell
>
>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
Funnily enough, I've got almost exactly that ("hello world") sitting
right here.
I'll tidy it up a bit, if someone else will write some intro text, with
instructions for windows users if required (unix only here, I'm afraid).
On Monday, October 28, 2002, at 10:55 PM, sean wrote:
> Ryan Hoegg wrote:
>
>> sean wrote:
>>
>>> I was thinking of using the Apache XML-RPC project as an application
>>> framework for some projects I have coming up. The site at
>>> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but
>>> there's a terrible lack of "how-to" documentation there and I
>>> couldn't find much news or other signs of activity.
>>
>>
>> What kind of how-to documentation are you looking for? We are aware
>> that the documentation is scanty, but as a potential user your ideas
>> of what a "Getting started" document would contain would be very
>> helpful.
>>
>> The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html)
>> on the web page gives some information on using the XML-RPC client
>> classes, and the "Server Side XML-RPC" link
>> (http://xml.apache.org/xmlrpc/server.html) gives some information on
>> using the library to provide an XML-RPC interface to your software.
>
>
> What would be nice is if you did away with the server example that's
> there now entirely and put up a "Hello, world" application (complete
> source, nothing fancy) with full instructions on getting the example
> working so anyone new who comes along can follow the instructions, get
> the server working, then contact the server with a browser (like
> Netscape) and see the results.
>
> The snippets that are there now are tedious to assemble into a working
> server. The example isn't complete in terms of "here's you get you an
> XML-RPC server going" so I'm left with no way to figure out how to
> fill in the blanks except by poking around, guessing...testing. It's
> very stressful on this newcomer.
>
> Once I see a "Hello, world" example application running, then I will
> know I have all the necessary components installed, and I can then
> extend the example to start handling the tasks I need the application
> to perform.
>
> Sean O'Dell
>
>
Re: Activity
Posted by sean <se...@celsoft.com>.
Ryan Hoegg wrote:
> sean wrote:
>
>> I was thinking of using the Apache XML-RPC project as an application
>> framework for some projects I have coming up. The site at
>> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
>> a terrible lack of "how-to" documentation there and I couldn't find
>> much news or other signs of activity.
>
>
> What kind of how-to documentation are you looking for? We are aware
> that the documentation is scanty, but as a potential user your ideas
> of what a "Getting started" document would contain would be very helpful.
>
> The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html)
> on the web page gives some information on using the XML-RPC client
> classes, and the "Server Side XML-RPC" link
> (http://xml.apache.org/xmlrpc/server.html) gives some information on
> using the library to provide an XML-RPC interface to your software.
What would be nice is if you did away with the server example that's
there now entirely and put up a "Hello, world" application (complete
source, nothing fancy) with full instructions on getting the example
working so anyone new who comes along can follow the instructions, get
the server working, then contact the server with a browser (like
Netscape) and see the results.
The snippets that are there now are tedious to assemble into a working
server. The example isn't complete in terms of "here's you get you an
XML-RPC server going" so I'm left with no way to figure out how to fill
in the blanks except by poking around, guessing...testing. It's very
stressful on this newcomer.
Once I see a "Hello, world" example application running, then I will
know I have all the necessary components installed, and I can then
extend the example to start handling the tasks I need the application to
perform.
Sean O'Dell
Re: Activity
Posted by sean <se...@celsoft.com>.
Ryan Hoegg wrote:
> sean wrote:
>
>> I was thinking of using the Apache XML-RPC project as an application
>> framework for some projects I have coming up. The site at
>> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
>> a terrible lack of "how-to" documentation there and I couldn't find
>> much news or other signs of activity.
>
>
> What kind of how-to documentation are you looking for? We are aware
> that the documentation is scanty, but as a potential user your ideas
> of what a "Getting started" document would contain would be very helpful.
>
> The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html)
> on the web page gives some information on using the XML-RPC client
> classes, and the "Server Side XML-RPC" link
> (http://xml.apache.org/xmlrpc/server.html) gives some information on
> using the library to provide an XML-RPC interface to your software.
What would be nice is if you did away with the server example that's
there now entirely and put up a "Hello, world" application (complete
source, nothing fancy) with full instructions on getting the example
working so anyone new who comes along can follow the instructions, get
the server working, then contact the server with a browser (like
Netscape) and see the results.
The snippets that are there now are tedious to assemble into a working
server. The example isn't complete in terms of "here's you get you an
XML-RPC server going" so I'm left with no way to figure out how to fill
in the blanks except by poking around, guessing...testing. It's very
stressful on this newcomer.
Once I see a "Hello, world" example application running, then I will
know I have all the necessary components installed, and I can then
extend the example to start handling the tasks I need the application to
perform.
Sean O'Dell
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
sean wrote:
> I was thinking of using the Apache XML-RPC project as an application
> framework for some projects I have coming up. The site at
> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
> a terrible lack of "how-to" documentation there and I couldn't find
> much news or other signs of activity.
What kind of how-to documentation are you looking for? We are aware
that the documentation is scanty, but as a potential user your ideas of
what a "Getting started" document would contain would be very helpful.
The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html) on
the web page gives some information on using the XML-RPC client classes,
and the "Server Side XML-RPC" link
(http://xml.apache.org/xmlrpc/server.html) gives some information on
using the library to provide an XML-RPC interface to your software.
> Is this project alive and well?
Alive and kicking! We are ramping up for a 2.0 release PSN ;)
--ryan
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
sean wrote:
> I was thinking of using the Apache XML-RPC project as an application
> framework for some projects I have coming up. The site at
> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
> a terrible lack of "how-to" documentation there and I couldn't find
> much news or other signs of activity.
What kind of how-to documentation are you looking for? We are aware
that the documentation is scanty, but as a potential user your ideas of
what a "Getting started" document would contain would be very helpful.
The "Client Classes" link (http://xml.apache.org/xmlrpc/client.html) on
the web page gives some information on using the XML-RPC client classes,
and the "Server Side XML-RPC" link
(http://xml.apache.org/xmlrpc/server.html) gives some information on
using the library to provide an XML-RPC interface to your software.
> Is this project alive and well?
Alive and kicking! We are ramping up for a 2.0 release PSN ;)
--ryan
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Martin Redington wrote:
>
> I'm in the same boat, and I second that question. There doesn't seem
> to be much activity, newbie questions go unanswered on the lists
> (where are the archives, BTW?), and I've heard dark mutterings from
> some quarters about a lack of progress on patch acceptance etc.
We are trying to pay more attention to newbie questions, but we all have
day jobs :) Patch acceptance is moving along, just new contributors
don't really know what to expect when contributing code to the project.
We have partially addressed this with a new doc that still needs to be
linked into the site.
> Judging by the CVS Changelog, not much has happened since June. Has
> everyone moved onto SOAP or something?
I think we have been slightly decadent when it comes to Changelog
entries, as a lot of the bigger library changes are being kept out of
CVS until they reach a certain level of appropriateness. You can get a
better picture of the current activity of the project on Bugzilla at
http://nagoya.apache.org/bugzilla/query.cgi?product=XML-RPC .
The slow process of migrating to maven is complicating things too, as
new changes are to be documented in changes.xml.
--ryan
Re: Activity
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Martin Redington wrote:
>
> I'm in the same boat, and I second that question. There doesn't seem
> to be much activity, newbie questions go unanswered on the lists
> (where are the archives, BTW?), and I've heard dark mutterings from
> some quarters about a lack of progress on patch acceptance etc.
We are trying to pay more attention to newbie questions, but we all have
day jobs :) Patch acceptance is moving along, just new contributors
don't really know what to expect when contributing code to the project.
We have partially addressed this with a new doc that still needs to be
linked into the site.
> Judging by the CVS Changelog, not much has happened since June. Has
> everyone moved onto SOAP or something?
I think we have been slightly decadent when it comes to Changelog
entries, as a lot of the bigger library changes are being kept out of
CVS until they reach a certain level of appropriateness. You can get a
better picture of the current activity of the project on Bugzilla at
http://nagoya.apache.org/bugzilla/query.cgi?product=XML-RPC .
The slow process of migrating to maven is complicating things too, as
new changes are to be documented in changes.xml.
--ryan
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
I'm in the same boat, and I second that question. There doesn't seem to
be much activity, newbie questions go unanswered on the lists (where
are the archives, BTW?), and I've heard dark mutterings from some
quarters about a lack of progress on patch acceptance etc.
Judging by the CVS Changelog, not much has happened since June. Has
everyone moved onto SOAP or something?
On Monday, October 28, 2002, at 09:59 PM, sean wrote:
> Hi everyone,
>
> I was thinking of using the Apache XML-RPC project as an application
> framework for some projects I have coming up. The site at
> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
> a terrible lack of "how-to" documentation there and I couldn't find
> much news or other signs of activity.
>
> Is there another site where all the activity is? Is this project
> alive and well?
>
> Sean O'Dell
>
>
Re: Activity
Posted by Martin Redington <m....@ucl.ac.uk>.
I'm in the same boat, and I second that question. There doesn't seem to
be much activity, newbie questions go unanswered on the lists (where
are the archives, BTW?), and I've heard dark mutterings from some
quarters about a lack of progress on patch acceptance etc.
Judging by the CVS Changelog, not much has happened since June. Has
everyone moved onto SOAP or something?
On Monday, October 28, 2002, at 09:59 PM, sean wrote:
> Hi everyone,
>
> I was thinking of using the Apache XML-RPC project as an application
> framework for some projects I have coming up. The site at
> http://xml.apache.org/xmlrpc/ seemed somewhat filled out, but there's
> a terrible lack of "how-to" documentation there and I couldn't find
> much news or other signs of activity.
>
> Is there another site where all the activity is? Is this project
> alive and well?
>
> Sean O'Dell
>
>