| |
 |
Saturday, February 2, 2002 |
Weblogging discussion linking?
I've been sitting on this for a couple weeks because it just didn't seem quite relevant, but now it does.
Mike Cohen expressed the thought a couple weeks back that Radio should be capable of doing exactly what Manila (another UserLand product) is capable of by having a reply section in the weblog. I would like to disagree, and hopefully do so in a way which helps move this all forward.
First, there is the price point and service guarantee to back that up. Radio is essentially a static rendering engine with a decent hosting platform behind it, while Manila is a similar engine, with more sophisticated dynamic hosting services on the backend. I think many people would like to see Manila on a Radio budget, although I don't think this is a UserLand goal. I was initially surprised that UserLand allowed everyone to use their cloud and assume their plan is to show us easy ways to move elsewhere if we become popular, which is probably the right idea for them.
The various discussion areas on (pick your favorite weblog) are both useful and problematic. It's very useful from the standpoint of building a local community. On the other hand, I can't post into someone elses weblog from my own, I have to go there (I can, but they have to be getting my feed, there doesn't seem to be an active blogLink api). Which brings up the point that I think the various weblogs (everyone: developers, users, readers?) all need to consider. If you have a weblog, you already have a public persona of some sort. As an ideal goal, I should be able to post a reply to a weblog (any kind) in my own weblog, sending a reply message to the originator. If it's open, my reply is automatically aggregated (and rendered inline with all other replies), else it awaits owner approval, but it links back to where I started it.
Jon Udell comments here on a recent spat of blog pong played by he and Sam Ruby. He's not sure it's good, but he thinks it is. I think it's great, if a little hard to follow if not caught up in the moment. It gets harder to follow when several people get into it, as happened in the last couple days on several SOAP related threads.
Things are certainly moving in the right direction and it's a lot of fun to watch and play.
2:17:28 AM 
|
|
Cool beans!
After reading this thread, and all the un-attached spin offs (they are all over the place), and thinking about what was said, I've finally got Radio connected via SOAP to an EJB running under JBoss / Tomcat. The name space issue was where I was getting lost, but I knew more or less what I was trying to do. It was just a matter of getting system.verbs.builtins.soap.rpc.client to play along.
I created a basic EJB, with one useful method called status:
public String status()
{
return "Some status text";
}
Deployed the EJB and made sure it was running (also made sure I had the api lib over where Tomcat could see it). Deployed the soap wrapper via the SOAP 2.2 rpcrouter using a basic deployment descriptor (urn:TestStatus, Application, org.apache.soap.providers.StatelessEJBProvider, status method, etc.). Wrote a small java client to make sure it worked. OK, next step, back to Radio.
First I fired up org.apache.soap.util.net.TcpTunnelGui, so I could see what was going on. Dink, dink, dink, success! Here's what the Radio code looks like:
on testService() {
local ( statusStr ="", params = {} );
local ( timeOut = 600 ); // 10 seconds or so
statusStr = soap.rpc.client( actionURI:"/soap/servlet/rpcrouter",
methodName:"status",
adrparams:@params, rpcPort:"8080",
ticksToTimeOut:timeOut,
methodNamespace:"ignored",
methodNamespaceURI:"urn:TestStatus" );
dialog.notify( statusStr )
}
The posted XML looks like this:
POST /soap/servlet/rpcrouter HTTP/1.0
User-Agent: Radio UserLand/8.0.2 (MacOS)
Host: localhost:8090
Content-Type: text/xml; charset="us-ascii"
Content-length: 468
SOAPAction: "/soap/servlet/rpcrouter"
<?xml version="1.0"?>
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance">
<SOAP-ENV:Body>
<ignored:status xmlns:ignored="urn:TestStatus">
</ignored:status>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Note, the way I have things setup, the methodNamespace is ignored. I don't know if this is something about the way the SOAP 2.2 works under Tomcat 3.2.x, something I have some mis-configured or just the way it's supposed to be. I remember getting very confused about this from the client side, because I saw all kinds of weird values in there that made no sense. I used "ignored" here for now, because it seems to be ignored.
I'll see about cleaning up the code and putting it online this weekend. I am now thinking about how a Radio rendered page can be created on demand to check the status of the server. It might also made a useful testing tool. Like I said, 'Cool beans!'
1:40:46 AM
|
|
© Copyright 2002 Dave Ely.
|
|
|
|
|
