[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-commons-dev
Subject:    Re: [jira] Commented: (JELLY-207) http:get causes a null pointer
From:       Frank Cornelis <cornelis () octalis ! com>
Date:       2005-03-31 12:51:59
Message-ID: 424BF26F.8010803 () octalis ! com
[Download RAW message or body]

Exactly, nesting sessions should be pointless. There should be only one 
global httpclient when you use http:session.

dion gillard (JIRA) wrote:

> [ http://issues.apache.org/jira/browse/JELLY-207?page=comments#action_61880 ]
> 
> dion gillard commented on JELLY-207:
> ------------------------------------
> 
> I'm not sure this is the right solution. All the get tags would then share the same \
> session regardless of their nesting. 
> 
> 
> > http:get causes a null pointer exception
> > ----------------------------------------
> > 
> > Key: JELLY-207
> > URL: http://issues.apache.org/jira/browse/JELLY-207
> > Project: jelly
> > Type: Bug
> > Components: taglib.http
> > Environment: define:taglib
> > Reporter: Frank Cornelis
> > Attachments: SessionTag-static-httpclient.patch
> > 
> > http:get causes a null pointer exception when used within define:tag with a \
> > surrounding http:session When a http:get that lives inside define:tag find a \
> > parent http:session, which was defined inside define:taglib, then http:get \
> > creates a new SessionTag object, which an unset httpclient, and tries to use it. \
> > This cause a null pointer exception. Making the _httpClient static inside the \
> > SessionTag solves to problem. 
> > 
> 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]