Tim,
Any chance you could list some of the operations that you wound up keeping
behind these interfaces? Or were they all vendor specific enhancements? It
might prove quite instructional...
Thanks,
tim.
> I want to respond to the issue of portability and vendor specific API's.
>
> You can keep your code portable by implementing vendor specifc code behind
> your own interfaces. I have done this with great success, having ported an
> application across three (THREE!) application servers (and an O/R mapping
> tool). I have had to modify maybe three or four classes (implementations of
> the interfaces) each time and it has been very painless.
>
> Don't be afraid to use vendor specific API's, but use them wisely, and
> design for the inevitable change!
>
> Your mileage may (will) vary...
===========================================================================
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".
