Dion Almaer wrote:
> That wouldn't be good... but you would make it all part of the
> build/deployment process.
> If you had a system with 20,000 client machines, you wouldn't suddenly jump
> from version A to version B.
Well clearly I wouldn't if I was a WebLogic customer :-)
But if I was a Sybase customer, I might well do this if I
want to take advantage of scalability features (such as
eneity bean object caching) in a new server version without
spending tnes of thousands of dollars having client installations
upgraded. Bear in mind these client installations might be outside
my own company and may be very expensive to upgrade. Java applets
might help but what if the clients aren't written in Java? What
if they are written in VB?
Should I have to upgrade my browser just because Amazon puts
in a new web server version? I think not. You may think EJB is
fundamentally different. I would disagree.
Also, have you considered that some of your clients may be
themselves servers? In a large enterprise, who wants to have
to upgrade versions for all of their connected servers just
because one of them is to be upgraded.
We have even had requests from customers wanting app-server
clusters with mixed versions. Do I want to simultaneously
have to upgrade all nodes in my 20-node cluster (taking my
site down for several days) when I can do it piece-meal and
keeping my site up. (Note: Sybase EAServer does not support this
at present, but at least we understand the value of doing so).
True enterprise software vendors understand the importance of
backwards compatibility. Why throw out the 'old' if it can
happily 'co-exist' with the new?
Anyway, I think I've had my say and I'll stop my BEA bashing for
a few weeks :-)
> D
>
>
>>-----Original Message-----
>>From: A mailing list for Enterprise JavaBeans development
>>[mailto:[EMAIL PROTECTED]]On Behalf Of Evan Ireland
>>Sent: Wednesday, September 05, 2001 6:10 PM
>>To: [EMAIL PROTECTED]
>>Subject: Re: differrence in weblogic 5.1 and weblogic 6.0
>>
>>
>>Dion Almaer wrote:
>>
>>
>>>I understand the need for backwards compatibility. However you have to
>>>weigh up having your server be backwards compatible,
>>>to getting rid of that bloat. Depending on what has been changed in the
>>>server side maybe you really can't be backwards compatible. It may be a
>>>pain to run your client using the new weblogic.jar etc... but
>>>
>>is it *that*
>>
>>>much of a pain?
>>>
>>
>>It could be, if you have to install weblogic.jar on 20,000 client
>>machines.
>>
>>
>>
>>>D
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: A mailing list for Enterprise JavaBeans development
>>>>[mailto:[EMAIL PROTECTED]]On Behalf Of Evan Ireland
>>>>Sent: Wednesday, September 05, 2001 4:52 PM
>>>>To: [EMAIL PROTECTED]
>>>>Subject: Re: differrence in weblogic 5.1 and weblogic 6.0
>>>>
>>>>
>>>>Cedric,
>>>>
>>>>Whatever happened to backwards compatibility?
>>>>
>>>>Why shouldn't older clients be able to talk to newer servers?
>>>>
>>>><vendor>
>>>>
>>>>Still, perhaps it's better if you leave it thay way. If you annoy enough
>>>>of your customers, we might win some more business for Sybase EAServer.
>>>>
>>>></vendor>
>>>>
>>>>Cedric Beust wrote:
>>>>
>>>>
>>>>
>>>>>>From: A mailing list for Enterprise JavaBeans development
>>>>>>
>>>>>>
>>>>>>this client code works fine with weblogic 5.1 but it gives following
>>>>>>error in weblogic 6.0
>>>>>>
>>>>>>Exception in main() :javax.naming.CommunicationException
>>>>>>
>>[Root exception
>>
>>>>>>is weblogic.socket.UnrecoverableConnectException: [Login failed:
>>>>>>'Incompatible version:Incompatible versions - this server:6.0.0b2
>>>>>>client:5.1.0]]
>>>>>>
>>>>>>can any one please help me and let me know what should I do
>>>>>>
>>>>>>
>>>>>>
>>>>>You cannot communicate between client and servers with
>>>>>
>>>>>
>>>>different versions.
>>>>
>>>>
>>>>>Make sure you compile and run your client with Weblogic 6.
>>>>>
>>>>>--
>>>>>Cedric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>==================================================================
>>>>=========
>>>>
>>>>
>>>>>To unsubscribe, send email to [EMAIL PROTECTED] and include
>>>>>
>>>>>
>>>>in the body
>>>>
>>>>
>>>>>of the message "signoff EJB-INTEREST". For general help, send email to
>>>>>[EMAIL PROTECTED] and include in the body of the message "help".
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>==================================================================
>>>>=========
>>>>To unsubscribe, send email to [EMAIL PROTECTED] and include
>>>>in the body
>>>>of the message "signoff EJB-INTEREST". For general help, send email to
>>>>[EMAIL PROTECTED] and include in the body of the message "help".
>>>>
>>>>
>>>>
>>>
>>>
>>==================================================================
>>=========
>>To unsubscribe, send email to [EMAIL PROTECTED] and include
>>in the body
>>of the message "signoff EJB-INTEREST". For general help, send email to
>>[EMAIL PROTECTED] and include in the body of the message "help".
>>
>>
>
>
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
