Regarding what you did not know I meant. I thought I explained it but I will try again, and try to do better. I provide different look and feels to different clients. They choose. Thus, my urls are modified so that I can have a constant url in the struts-conf.xml under, e.g. "input" for the action mapping, and a variable one in the tiles.xml. Thus, I have to have between the struts xml and the tiles xml readings a way of converting. I do this with a Layout object that is spawned from the ServletContext and placed in the session on the index.jsp page. This is the object that is showing null in Opera but is not null in IE or Netscape and I have checked to make sure that it is there. This should not, I know, affect Opera. But, these are the facts and all the facts I know.
The fact is I don't have trouble with IE and Netscape and I do with Opera. Here is the code that Opera seems (in impossible terms) to conflict with and is in my index.jsp page which merely FORWARDS to another page:
session.setAttribute(SiteConstant.LAYOUT,session.getServletContext().getAttribute(SiteConstant.LAYOUT));
The FORWARD is <logic:forward name='<%= indexUrl %>'/> where String indexUrl = layout + "_index"; and where layout is presently hardcoded for these tests. When the session gets to "indexUrl", with Opera sometimes the session does not have the default layout object in the session. I can cure this in Opera by having the index.jsp FORWARD page contain the following code:
At 11:54 AM 5/28/2004, Rick Reumann wrote:
Michael McGrady wrote:
No, this is not correct, Rick. The null pointer is for the reference to the Layout object in the session, which in fact is there. When I have the index page check to see if the object is there, Opera does not have a problem on OTHER pages. Odd? It is as if the placement of that object in the session does not happen with Opera unless you check that it has happened. BUT THAT IS ABSURD. Opera has no knowledge of any of this. RIght?
If you are sure you haven't changed some cookie settings and you aren't spawning a new window, then my guess is there will be a way to duplicate the exact same problem in IE/Netscape/Mozilla. I don't get what you mean by:
"The null pointer is for the reference to the Layout object in the session, which in fact is there."
The above would have nothing to do with a browser and is impossible, unless you think you are refering to the same Session but you are not.
In other words, you are setting something in Session scope and then later on you do some stuff which somehow spawns a new Session.
To say you are getting a null pointer for a reference to an object that really is there in Session is impossible:) In other words if you do
Object obj = session.getAttribute("someOjbect");
and obj is null then there is no way "someObject" is refering to a handle to an object in this session.
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
