a few things come to mind straight away:
(1) some vendors have different ways of getting
the initial context (props). put the code of getting
the context in a separate utility class, that way
you need to change it at one place only (if at all).
(2) use objects and not primitives for your pk as
some vendors do not support primitives.
& of course the usual additions like not using vendor
specific extensions or 'features' as they might like
to call them ...
krish
----- Original Message -----
From: Gounder, Palanisamy <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 16, 2001 2:29 PM
Subject: Vendor specific issues
> I have to deploy a EJB to different types of Application Servers. In this
> case what are issues/things that I should be aware of while developing
the
> EJB. Is there any source where it is listed?
>
>
===========================================================================
> 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".
