> The vendor-neutrality aspect of EJB is a sham--you cannot produce a
> well-performant system in EJB without resorting to vendor value-adds, and
> once you do, your portability wafts away on the winds.
>
> Ted Neward
> {.NET || Java} Course Author & Instructor, DevelopMentor
> (http://www.develop.com)
> http://www.javageeks.com/tnewardTed, you really think that? I imagine you have a whole heap more experience that I do, so would like to hear your feedback on my thoughts. <imho> there are always going to be things that the vendors do beyond the spec, but using them doesn't neccessarily remove all chances of portability. I would think there are a number of extensions to any spec, that most vendors implement, and so whilst some work would be involved in porting an application, provided you knew that the new target server supported the functionality you were using, and you know how to use it on the target server, you should be able to port the application. also, if, as you say, the portability promise is a sham, then why dont you always put your logic in the database. as I understand it, one of the goals of middlewear is to remove the use of things like PL-SQL, and have everything following specs. obviously there are other costs involved with putting everything in the database, but if you're not going to get portability of middlewear, then you may as well just be tied to one product (oracle) rather than two (oracle + weblogic)... yes? </imho> anyway, just interested to hear some more on portability... cheesr dim =========================================================================== 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".
