t;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 19, 2001 5:34 AM
Subject: Re: borrowing a "request"
> Sachin--Thanks for the reply. Having burned another 10 hours or so on
this, I can
> report it goes way beyond the request object. As far as I can tell, I
>> With regards,
>> Sachin S. Khanna
>> http://www.emailanorder.com
>> - Original Message -
>> From: Martin Smith <[EMAIL PROTECTED]>
>> To: <[EMAIL PROTECTED]>
>> Sent: Sunday, June 17, 2001 9:20 AM
>> Subject: Re: borrowing a "reque
To: [EMAIL PROTECTED]
> Subject: Re: borrowing a "request"
>
>
> Brad--
>
> Thanks for the advice. Actually it's not a bean with getters &
> setters, just a
> plain old class. So I'm not doing usebean, for example. I'm
> pretty sure I'm not
&
s,
> Sachin S. Khanna
> http://www.emailanorder.com
> - Original Message -
> From: Martin Smith <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, June 17, 2001 9:20 AM
> Subject: Re: borrowing a "request"
>
> > Get/set and a null con
artin Smith <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, June 17, 2001 9:20 AM
Subject: Re: borrowing a "request"
> Get/set and a null constructor, I thought. Anyhow. Fact is, I can't seem
to
> directly reference my class from a jsp without getting tha
Get/set and a null constructor, I thought. Anyhow. Fact is, I can't seem to
directly reference my class from a jsp without getting that "response already
committed" error. I even trimmed down the class to be trivial (does nothing) and
still get a error creating an instance of it or referring to
As far as I'm concerned, bean is just Sun's marketing name for objects. JSP'
s usebean just requires the object to have get/set methods, which is
another bad idea that JSP perpetrates with usebean.
On Saturday, June 16, 2001, at 08:38 PM, Martin Smith wrote:
> So I'm not doing usebean, for exampl
Brad--
Thanks for the advice. Actually it's not a bean with getters & setters, just a
plain old class. So I'm not doing usebean, for example. I'm pretty sure I'm not
generating any response before this error. Anyhow...next stop hashmap ...
I do want to look at frameworks: was thinking of St
The exception is telling you that the JSP and bean are doing something out
of the proper sequence. Setting the response type after sending some output
is the most likely cause.
What you're doing can be made to work. I used to do JSP work exactly this
way. But since getting all this sorted out is
This is probably dumb, but . . .
I am trying to re-do a "model 1" JSP app to do at least minimal
separation between presentation and scriptlets.
So, I extracted all the java from my JSP and put it into a java class.
Since the work I want to do in the class (doing a parameterized
retrieval into
10 matches
Mail list logo
