Is it a strong use? After all, you said XML-RPC was faster and lighter -
okay, granted. Then you pointed out that XML-RPC wasn't a MS solution,
either - with emphasis. SOAP is also an IBM solution, yet you didn't say
"NOT an IBM solution" - you centered on MS. Typically, that's bigotry. If
I'm incorrect in my analysis, well... that's okay, it just seemed to be
the connotation you were offering.

On Fri, 25 May 2001, elephantwalker wrote:

> Joe,
> 
> Using a word like 'bigot' is a little strong, there are several technical
> experts that have evaluated the soap standard and xml-rpc (often, you can
> use xml-rpc with soap), and concluded that soap is a "heavy" standard,
> versus the relatively light implementations of xml-rpc out there. So this is
> a considered opinion.
> 
> In the end, isv's will use whatever gets us to the end of the project in the
> cheapest, most reliable way.
> 
> Regards,
> 
> the elephantwalker
> 
> 
> 
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph B.
> Ottinger
> Sent: Friday, May 25, 2001 4:08 AM
> To: Orion-Interest
> Subject: RE: HELP! 1.4.5 and JMS
> 
> 
> Well, that's useful. Actually, I'm investigating the use of SOAP now (not
> being an anti-MS idiot^Wbigot and all) and it's pretty nice; with a decent
> toolkit like GLUE (http://www.themindelectric.com/) it's easy to use with
> Orion, fast, and cross-platform and cross-language. All pluses, if you
> need that kind of capability.
> 
> On Thu, 24 May 2001, elephantwalker wrote:
> 
> > Yes...drop SOAP and use XML-RPC. Faster and lighter and NOT a Microsoft
> > solution.
> >
> > www.xml-rpc.org
> >
> > also Brett McGlaughlin's book Java and XML.
> >
> > Regards,
> >
> > the elephantwalker
> >   -----Original Message-----
> >   From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Su, Yi
> >   Sent: Thursday, May 24, 2001 8:01 PM
> >   To: Orion-Interest
> >   Subject: RE: HELP! 1.4.5 and JMS
> >
> >
> >   Hello,
> >
> >   Does anyone knows that what Java tools, libraries are currently
> supporting
> > XML schema and XLL.
> >
> >   Is there resources for me to look up for using SOAP using Java?
> >
> >   Thanks alot.
> >
> >   Regards,
> >
> >   Yeoman
> >
> >     -----Original Message-----
> >     From: Vidur Dhanda [mailto:[EMAIL PROTECTED]]
> >     Sent: Thursday, May 17, 2001 10:16 AM
> >     To: Orion-Interest
> >     Cc: 'Orion-Interest'
> >     Subject: Re: HELP! 1.4.5 and JMS
> >
> >
> >     Hi Kesav,
> >     Thanks for the tip. I tried that with both 1.4.5 and 1.4.8.  After
> > removing the connection factory line, in 1.4.5, the client hangs on
> > TopicConnection.createSubscriber().  If I give the createTopicConnection a
> > username and password, then the server throws a NPE and the client hangs
> at
> > createTopicConnection().
> >
> >     The same problem persists in 1.4.8.
> >
> >     I'm sure I'm doing something really stupid.  However, I have no idea
> how
> > to solve it.  I'm attaching some code in the hope that someone can help me
> > out of this mess.  I've tried it against 1.4.5 and 1.4.8.  And I am really
> > desperate!
> >
> >     Thanks,
> >     Vidur
> >
> >     Kesav Kumar wrote:
> >
> >
> >       Just remove the connectionfactory line from your jms.xml.
> >
> >       Kesav Kumar
> >       Software Engineer
> >       Voquette, Inc.
> >       650 356 3740
> >       mailto:[EMAIL PROTECTED]
> >       http://www.voquette.com
> >       Voquette...Delivering Sound Information
> >
> >       -----Original Message-----
> >       From: Vidur Dhanda [mailto:[EMAIL PROTECTED]]
> >       Sent: Wednesday, May 16, 2001 11:31 AM
> >       To: Orion-Interest
> >       Subject: HELP! 1.4.5 and JMS
> >
> >       Please help!  I broke something in my code and can't figure it out.
> > On
> >       the client, I'm consistently getting:
> >       java.lang.NullPointerException
> >        at java.io.DataOutputStream.writeUTF(DataOutputStream.java:329)
> >        at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
> >        at com.evermind.server.jms.cj.<init>(JAX)
> >        at com.evermind.server.jms.b8.start(JAX)
> >        at
> >
> >
> com.epistemic.km.server.NotificationBase.getConnection(NotificationBase.java
> > :89)
> >
> >        at
> >
> >
> com.epistemic.km.server.NotificationBase.getSession(NotificationBase.java:10
> > 1)
> >
> >        at
> >
> >
> com.epistemic.km.server.NotificationBase.getSubscriber(NotificationBase.java
> > :44)
> >
> >       Auto-started clients can send/receive messages without trouble.
> >
> >       getConnection() calls createTopicConnection() and then start().
> >       If I use, createConnection (usr, pwd), then the system hangs.
> >
> >       In jms.xml, I have:
> >       <jms-server host="192.168.10.2" port="9127">
> >        <topic-connection-factory host="192.168.10.2"
> >             location="jms/notificationFactory" port="9127" />
> >        <topic name="DWItem Notification"
> location="jms/dwItemNotification">
> >        </topic>
> >
> >       Any ideas?  I'm on version 1.4.5.  1.4.8 has a regression on bug 188
> >       that is a show stopper for us.  And in fact, this code worked uptil
> >       yesterday when I made changes to try and get 1.4.8 to work.
> >
> >       TIA,
> >       Vidur
> >
> >       PS.  If possible, please also cc me directly.  I'm really desperate.
> >       --
> >       Vidur Dhanda
> >       Active Solutions
> >       tel: 617/566-1252
> >       cell: 617/821-7115
> >       [EMAIL PROTECTED]
> >       www.active-solutions-inc.com
> >
> >
> >     --
> >     Vidur Dhanda
> >     Active Solutions
> >     tel: 617/566-1252
> >     cell: 617/821-7115
> >     [EMAIL PROTECTED]
> >     www.active-solutions-inc.com
> >
> >
> >
> 
> -----------------------------------------------------------
> Joseph B. Ottinger                       [EMAIL PROTECTED]
> http://adjacency.org/                         IT Consultant
> 
> 
> 

-----------------------------------------------------------
Joseph B. Ottinger                       [EMAIL PROTECTED]
http://adjacency.org/                         IT Consultant


Reply via email to