My experience is that with jndi.properties you've got to figure out where to
put it which has been different for every servlet container I've used.  The
good news is that it beats hard coding the machine name/port # into some
java code (which I am foolishly doing right now with a helper class).

The quality of the CMP implementation vary's greatly between containers,
though you can always buy Cocobase to even the score a bit if money is no
object.

Cheers
Jay Walters

-----Original Message-----
From: Dan Christopherson [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 16, 2001 11:23 AM
To: [EMAIL PROTECTED]
Subject: Re: Vendor specific issues


On Fri, 16 Feb 2001, Krishnan Subramanian wrote:

> 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).
For the properties, you should just use a jndi.properties file for the
client. Within beans, doing 'new InitialContext()' should always work.

> (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 ...
Another thing that has bit me with CMP entities is that some containers
seem to be rather touchy about what Java type maps to what SQL type.


>
> 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".
>

--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)

Opinions expressed are mine and do not neccessarily reflect any
position or opinion of nVISIA.

---------------------------------------------------------------------------
If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
-Eben Moglen

===========================================================================
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".

Reply via email to