No, there should be a reason for that, well of course, there is the CMP problem in EJB 1.1, that is, there are some portability problems if you develop CM entity beans due to ambiguities/lags in the specification, but that�s not the problem here. I am very sorry if my last post confused somebody, I haven�t personally used WebSphere (I developed for a while in VAJ, though) and I have not done cross-VM testing, but the point is that IBM does force you to use their JVM and JDK, so maybe �technically speaking� cross-VM portability exist, but they won�t even let you find out� in JBuilder (this is just an example, I�m not Borland biased) you can change both of then, in others you can change the compiler but have to reinstall if you want to use another JDK, but the point is you *can* do it. I would really like to hear an explanation of why this occurs in the IBM case, are there technical incompatibilities or is just company policy? Again, my apologies for talking without a sound technical base.
J. -----Original Message----- From: syed huda [mailto:[EMAIL PROTECTED]] Sent: Monday, December 03, 2001 11:39 AM To: Javier Glez Subject: Re: J2EE/EJB VM I am new to EJB and I am getting confused. Does it mean that if I develop J2EE application using VAJ and WebSphere, it won't be deployable to other application servers? ==========================================================================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".
