Context/DefaultContext Question

2003-12-02 Thread Dhruva B. Reddy
Thanks to all who responded to my OutOfMemoryError post.  Among other
things, it was suggested that I look at the reloadable attribute for
the context definition.

We define a DefaultContext in server.xml, with the reloadable
attribute explicitly set to false.  We also have, for each application,
a separate context definition file, for which the reloadable
attribute is explicitly set to true.

I'm a little confused about these two work together.  We have a JNDI
resource set up in the DefaultContext for e-mail (see the
mail/Session example in the JNDI Resources HOWTO) that is actually
called mail/Session, with the mail.smtp.host parameter set to
localhost.  In the application-specific context, this same resource
is defined by the same name, but with mail.smtp.host set to a
different value.  The application always uses the value defined in the
DefaultContext.  Is this because the same name is being used, and once
something is defined in the DefaultContext, it cannot be overridden by
an app-specific Context?

Going back to the reloadable attribute, is each context that sets
this  overriding the value in DefaultContext?

Thanks,
Dhruva

__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Context/DefaultContext Question

2003-12-02 Thread Shapira, Yoav

Howdy,
For JNDI resources, such as your mail session, first bound stays bound.
In fact I'm surprised you don't get an error in the logs when you try to
define another JNDI resource with the same name.

For most other properties, including reloadable, last set stays set.  So
the context-specific one overrides DefaultContext.

Your setup is confusing and superfluous.  Only specify a property in one
place.

Yoav Shapira
Millennium ChemInformatics


-Original Message-
From: Dhruva B. Reddy [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 02, 2003 7:57 AM
To: tomcat
Subject: Context/DefaultContext Question

Thanks to all who responded to my OutOfMemoryError post.  Among other
things, it was suggested that I look at the reloadable attribute for
the context definition.

We define a DefaultContext in server.xml, with the reloadable
attribute explicitly set to false.  We also have, for each application,
a separate context definition file, for which the reloadable
attribute is explicitly set to true.

I'm a little confused about these two work together.  We have a JNDI
resource set up in the DefaultContext for e-mail (see the
mail/Session example in the JNDI Resources HOWTO) that is actually
called mail/Session, with the mail.smtp.host parameter set to
localhost.  In the application-specific context, this same resource
is defined by the same name, but with mail.smtp.host set to a
different value.  The application always uses the value defined in the
DefaultContext.  Is this because the same name is being used, and once
something is defined in the DefaultContext, it cannot be overridden by
an app-specific Context?

Going back to the reloadable attribute, is each context that sets
this  overriding the value in DefaultContext?

Thanks,
Dhruva

__
Do you Yahoo!?
Free Pop-Up Blocker - Get it now
http://companion.yahoo.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]