You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Eric Schneider <er...@centralparksoftware.com> on 2005/01/31 03:01:05 UTC
Re: Tapestry JSP Tags expect JSP 2.0?
Hi,
I just dug this up in the archives. Howard does this condition still
exist? I have a client that is interested in upgrading some Tapestry
2.3 applications to 3.0.1. They don't use any of the Tapestry JSP tag
library stuff, so maybe this isn't a concern for me.
They're running on the SunOne application server, which is aligned JSP
1.2/Servlet 2.3. Just wondering what's required to get it done.
Thanks in advance.
Cheers,
eric
On Aug 9, 2004, at 7:28 PM, Howard Lewis Ship wrote:
> It seems like Tapestry is stuck in between the two JSP versions. Fix
> it for one set of users, break it for the others. I decided to create
> something that would work with Jetty and Tomcat 5. This is another
> reason to hate JSPs. Ideally, Tapestry would ship with *two*
> different JSP taglibs, one for JSP 1.x and one for JSP 2.x.
>
>
>
> On Mon, 9 Aug 2004 13:40:55 -0700, Nicholas Lesiecki
> <nl...@vmsinfo.com> wrote:
>> Thanks, that's exactly what we did. We had hoped to avoid doing it.
>>
>> Would it make sense for the tapestry team to consider building
>> Tapestry
>> against the earlier version of the spec?
>>
>> Cheers,
>> Nick
>>
>>
>>
>> -----Original Message-----
>> From: John McTeague [mailto:john@shortslant.com]
>> Sent: Monday, August 09, 2004 1:14 PM
>> To: 'Tapestry users'
>> Subject: RE: Tapestry JSP Tags expect JSP 2.0?
>>
>> Ive had the same problem. To get round it, you need to build tapestry
>> yourslef using servlet 2.3 api jar files (i.e. from tomcat 4) not the
>> serlvet jar files the tapestry 3.0 build file uses. JspContext is a
>> new
>> class in the 2.4 servlet api's and therefore there is a good chance
>> your
>> container wont have it.
>>
>> -----Original Message-----
>> From: Nicholas Lesiecki [mailto:nlesiecki@vmsinfo.com]
>> Sent: 09 August 2004 18:44
>> To: tapestry-user@jakarta.apache.org
>> Subject: Tapestry JSP Tags expect JSP 2.0?
>>
>> Hiya Folks- We're wondering if anyone has had a similar experience:
>>
>> - We're trying to link from a JSP page to a page in a
>>
>> Tapestry 3.0 Application.
>>
>> - We're using the "external" tag from the Tapestry JSP
>>
>> tag library to achieve this goal.
>>
>> - We're getting a "ClassNotFoundException" because the
>>
>> container fails to find the class 'JSPContext' when calling
>> PageContext.getOut
>>
>> in ExternalTag
>>
>> So, realizing that the Tapestry-3.0 jars had been compiled against
>> JSP 2.0,
>> we realized that this was the problem: Our Weblogic application is
>> running
>> under JSP 1.2.
>>
>> So, we re-compiled the Tapestry src against JSP 1.2. Now our errors
>> are
>> gone, but as we were about to check-in the new Tapestry jars, we
>> wondered if
>> anyone else out there had already created a JSP 1.2 compatible jar,
>> or had a
>> more elegant solution.
>>
>> We're using Tapestry 3.0 under Weblogic 8.1 SP2.
>>
>> Thanks!
>>
>> _-Nick Lesiecki and Ben Greenberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>>
>
>
> --
> Howard M. Lewis Ship
> Independent J2EE / Open-Source Java Consultant
> Creator, Jakarta Tapestry
> Creator, Jakarta HiveMind
> http://howardlewisship.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry JSP Tags expect JSP 2.0?
Posted by Eric Schneider <er...@centralparksoftware.com>.
Excellent. Thanks Erik!
Cheers,
e.
On Jan 31, 2005, at 6:46 AM, Erik Hatcher wrote:
> If you're not using taglibs/JSP, then this isn't a concern at all -
> simply do not put the taglib registrations in web.xml.
>
> Erik
>
> On Jan 30, 2005, at 9:01 PM, Eric Schneider wrote:
>
>> Hi,
>>
>> I just dug this up in the archives. Howard does this condition
>> still exist? I have a client that is interested in upgrading some
>> Tapestry 2.3 applications to 3.0.1. They don't use any of the
>> Tapestry JSP tag library stuff, so maybe this isn't a concern for me.
>>
>> They're running on the SunOne application server, which is aligned
>> JSP 1.2/Servlet 2.3. Just wondering what's required to get it done.
>>
>> Thanks in advance.
>>
>> Cheers,
>> eric
>>
>>
>> On Aug 9, 2004, at 7:28 PM, Howard Lewis Ship wrote:
>>
>>> It seems like Tapestry is stuck in between the two JSP versions. Fix
>>> it for one set of users, break it for the others. I decided to create
>>> something that would work with Jetty and Tomcat 5. This is another
>>> reason to hate JSPs. Ideally, Tapestry would ship with *two*
>>> different JSP taglibs, one for JSP 1.x and one for JSP 2.x.
>>>
>>>
>>>
>>> On Mon, 9 Aug 2004 13:40:55 -0700, Nicholas Lesiecki
>>> <nl...@vmsinfo.com> wrote:
>>>> Thanks, that's exactly what we did. We had hoped to avoid doing it.
>>>>
>>>> Would it make sense for the tapestry team to consider building
>>>> Tapestry
>>>> against the earlier version of the spec?
>>>>
>>>> Cheers,
>>>> Nick
>>>>
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: John McTeague [mailto:john@shortslant.com]
>>>> Sent: Monday, August 09, 2004 1:14 PM
>>>> To: 'Tapestry users'
>>>> Subject: RE: Tapestry JSP Tags expect JSP 2.0?
>>>>
>>>> Ive had the same problem. To get round it, you need to build
>>>> tapestry
>>>> yourslef using servlet 2.3 api jar files (i.e. from tomcat 4) not
>>>> the
>>>> serlvet jar files the tapestry 3.0 build file uses. JspContext is a
>>>> new
>>>> class in the 2.4 servlet api's and therefore there is a good chance
>>>> your
>>>> container wont have it.
>>>>
>>>> -----Original Message-----
>>>> From: Nicholas Lesiecki [mailto:nlesiecki@vmsinfo.com]
>>>> Sent: 09 August 2004 18:44
>>>> To: tapestry-user@jakarta.apache.org
>>>> Subject: Tapestry JSP Tags expect JSP 2.0?
>>>>
>>>> Hiya Folks- We're wondering if anyone has had a similar experience:
>>>>
>>>> - We're trying to link from a JSP page to a page in a
>>>>
>>>> Tapestry 3.0 Application.
>>>>
>>>> - We're using the "external" tag from the Tapestry JSP
>>>>
>>>> tag library to achieve this goal.
>>>>
>>>> - We're getting a "ClassNotFoundException" because the
>>>>
>>>> container fails to find the class 'JSPContext' when calling
>>>> PageContext.getOut
>>>>
>>>> in ExternalTag
>>>>
>>>> So, realizing that the Tapestry-3.0 jars had been compiled against
>>>> JSP 2.0,
>>>> we realized that this was the problem: Our Weblogic application is
>>>> running
>>>> under JSP 1.2.
>>>>
>>>> So, we re-compiled the Tapestry src against JSP 1.2. Now our
>>>> errors are
>>>> gone, but as we were about to check-in the new Tapestry jars, we
>>>> wondered if
>>>> anyone else out there had already created a JSP 1.2 compatible jar,
>>>> or had a
>>>> more elegant solution.
>>>>
>>>> We're using Tapestry 3.0 under Weblogic 8.1 SP2.
>>>>
>>>> Thanks!
>>>>
>>>> _-Nick Lesiecki and Ben Greenberg
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> tapestry-user-help@jakarta.apache.org
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>>> For additional commands, e-mail:
>>>> tapestry-user-help@jakarta.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>> Independent J2EE / Open-Source Java Consultant
>>> Creator, Jakarta Tapestry
>>> Creator, Jakarta HiveMind
>>> http://howardlewisship.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Tapestry JSP Tags expect JSP 2.0?
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
If you're not using taglibs/JSP, then this isn't a concern at all -
simply do not put the taglib registrations in web.xml.
Erik
On Jan 30, 2005, at 9:01 PM, Eric Schneider wrote:
> Hi,
>
> I just dug this up in the archives. Howard does this condition still
> exist? I have a client that is interested in upgrading some Tapestry
> 2.3 applications to 3.0.1. They don't use any of the Tapestry JSP tag
> library stuff, so maybe this isn't a concern for me.
>
> They're running on the SunOne application server, which is aligned JSP
> 1.2/Servlet 2.3. Just wondering what's required to get it done.
>
> Thanks in advance.
>
> Cheers,
> eric
>
>
> On Aug 9, 2004, at 7:28 PM, Howard Lewis Ship wrote:
>
>> It seems like Tapestry is stuck in between the two JSP versions. Fix
>> it for one set of users, break it for the others. I decided to create
>> something that would work with Jetty and Tomcat 5. This is another
>> reason to hate JSPs. Ideally, Tapestry would ship with *two*
>> different JSP taglibs, one for JSP 1.x and one for JSP 2.x.
>>
>>
>>
>> On Mon, 9 Aug 2004 13:40:55 -0700, Nicholas Lesiecki
>> <nl...@vmsinfo.com> wrote:
>>> Thanks, that's exactly what we did. We had hoped to avoid doing it.
>>>
>>> Would it make sense for the tapestry team to consider building
>>> Tapestry
>>> against the earlier version of the spec?
>>>
>>> Cheers,
>>> Nick
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: John McTeague [mailto:john@shortslant.com]
>>> Sent: Monday, August 09, 2004 1:14 PM
>>> To: 'Tapestry users'
>>> Subject: RE: Tapestry JSP Tags expect JSP 2.0?
>>>
>>> Ive had the same problem. To get round it, you need to build tapestry
>>> yourslef using servlet 2.3 api jar files (i.e. from tomcat 4) not the
>>> serlvet jar files the tapestry 3.0 build file uses. JspContext is a
>>> new
>>> class in the 2.4 servlet api's and therefore there is a good chance
>>> your
>>> container wont have it.
>>>
>>> -----Original Message-----
>>> From: Nicholas Lesiecki [mailto:nlesiecki@vmsinfo.com]
>>> Sent: 09 August 2004 18:44
>>> To: tapestry-user@jakarta.apache.org
>>> Subject: Tapestry JSP Tags expect JSP 2.0?
>>>
>>> Hiya Folks- We're wondering if anyone has had a similar experience:
>>>
>>> - We're trying to link from a JSP page to a page in a
>>>
>>> Tapestry 3.0 Application.
>>>
>>> - We're using the "external" tag from the Tapestry JSP
>>>
>>> tag library to achieve this goal.
>>>
>>> - We're getting a "ClassNotFoundException" because the
>>>
>>> container fails to find the class 'JSPContext' when calling
>>> PageContext.getOut
>>>
>>> in ExternalTag
>>>
>>> So, realizing that the Tapestry-3.0 jars had been compiled against
>>> JSP 2.0,
>>> we realized that this was the problem: Our Weblogic application is
>>> running
>>> under JSP 1.2.
>>>
>>> So, we re-compiled the Tapestry src against JSP 1.2. Now our errors
>>> are
>>> gone, but as we were about to check-in the new Tapestry jars, we
>>> wondered if
>>> anyone else out there had already created a JSP 1.2 compatible jar,
>>> or had a
>>> more elegant solution.
>>>
>>> We're using Tapestry 3.0 under Weblogic 8.1 SP2.
>>>
>>> Thanks!
>>>
>>> _-Nick Lesiecki and Ben Greenberg
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>>> For additional commands, e-mail:
>>> tapestry-user-help@jakarta.apache.org
>>>
>>>
>>
>>
>> --
>> Howard M. Lewis Ship
>> Independent J2EE / Open-Source Java Consultant
>> Creator, Jakarta Tapestry
>> Creator, Jakarta HiveMind
>> http://howardlewisship.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org