|
Home > Archive > EAserver > April 2005 > DispayTag taglib
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Mark Maslow 2005-04-13, 1:24 pm |
| DisplayTag is a very useful open source tag library for displaying
tables with built-in sort, pagination and export facilities.
http://displaytag.sourceforge.net/
Works like a charm under Tomcat, but I can't get JSPs that use it to
even compile under EAServer.
Has anyone gotten this to work under EAServer?? Or is it time to move
on to a *real* servlet engine for production ;-)
| |
| Peter Abbott 2005-04-13, 8:24 pm |
| I have used it heaps within easerver. Made life some much easier than
having to right my own code. I just followed the samples and bobs your
uncle. Even if you deploy the sample war it should all work fine without
having to even move any libraries around like you have to with other 3rd
party products.
Also, the servlet engine that easerver uses is really the tomcat servlet
engine. The difference that causes the most headaches is the way
easerver implements classloading.
Pete
Mark Maslow wrote:
> DisplayTag is a very useful open source tag library for displaying
> tables with built-in sort, pagination and export facilities.
>
> http://displaytag.sourceforge.net/
>
> Works like a charm under Tomcat, but I can't get JSPs that use it to
> even compile under EAServer.
>
> Has anyone gotten this to work under EAServer?? Or is it time to move
> on to a *real* servlet engine for production ;-)
| |
| Mark Maslow 2005-04-13, 8:24 pm |
| Hmm ...
What version of EAServer are you running? The examples in the sample
war won't work for me either.
Tomcat generates code like:
_jspx_th_display_tab
le_0.setName(new String("test"));
while EAServer generates:
_jspx_th_display_tab
le_0.setName(new String(test));
and the compiler complains that "test is an undefined variable"
I wish what you said was true - that the servlet engine that easerver
uses is the tomcat servlet engine. Unfortunately, I know from
experience that this is not true - it's proprietary, and generally seems
to be buggier. I have run into problems compile JSPs before, but have
usually been able to come up with a workaround, but this time I'm stuck.
Maybe this is fixed in a later version? Again, what version do you use?
In article <425d838e$1@forums-2-dub>, abmannz@yahoo.co.nz says...
> I have used it heaps within easerver. Made life some much easier than
> having to right my own code. I just followed the samples and bobs your
> uncle. Even if you deploy the sample war it should all work fine without
> having to even move any libraries around like you have to with other 3rd
> party products.
>
> Also, the servlet engine that easerver uses is really the tomcat servlet
> engine. The difference that causes the most headaches is the way
> easerver implements classloading.
>
> Pete
>
>
> Mark Maslow wrote:
>
>
| |
| Peter Abbott 2005-04-13, 8:24 pm |
| We are on 4.2.3 for the production version. We are also using version
1.0-b2 of display tag and it works perfectly. I just deployed the
displaytag-examples.war to 4.2.3, 4.2.5 and 5.2 and they all worked.
I downloaded version 1.0 and tried to deploy it and get the same error
you are seeing and I tried all the same eas versions as before, so it
seems that displaytag is the problem and not eas. I guess this is a good
reason for us not to upgrade to version 1.0 of displaytag :0)
Pete
Mark Maslow wrote:[color=darkred
]
> Hmm ...
>
> What version of EAServer are you running? The examples in the sample
> war won't work for me either.
>
> Tomcat generates code like:
>
> _jspx_th_display_tab
le_0.setName(new String("test"));
>
> while EAServer generates:
>
> _jspx_th_display_tab
le_0.setName(new String(test));
>
> and the compiler complains that "test is an undefined variable"
>
> I wish what you said was true - that the servlet engine that easerver
> uses is the tomcat servlet engine. Unfortunately, I know from
> experience that this is not true - it's proprietary, and generally seems
> to be buggier. I have run into problems compile JSPs before, but have
> usually been able to come up with a workaround, but this time I'm stuck.
>
> Maybe this is fixed in a later version? Again, what version do you use?
>
>
> In article <425d838e$1@forums-2-dub>, abmannz@yahoo.co.nz says...
>
| |
| Peter Abbott 2005-04-13, 8:24 pm |
| Looking at the source code the setName(...) function was changed in
version 1.0 to take an object instead of a String. Myabe behind the
scene when the jasper compiler generates the servlet file it thinks it
is being smart but isnt.
Mark Maslow wrote:[color=darkred
]
> Hmm ...
>
> What version of EAServer are you running? The examples in the sample
> war won't work for me either.
>
> Tomcat generates code like:
>
> _jspx_th_display_tab
le_0.setName(new String("test"));
>
> while EAServer generates:
>
> _jspx_th_display_tab
le_0.setName(new String(test));
>
> and the compiler complains that "test is an undefined variable"
>
> I wish what you said was true - that the servlet engine that easerver
> uses is the tomcat servlet engine. Unfortunately, I know from
> experience that this is not true - it's proprietary, and generally seems
> to be buggier. I have run into problems compile JSPs before, but have
> usually been able to come up with a workaround, but this time I'm stuck.
>
> Maybe this is fixed in a later version? Again, what version do you use?
>
>
> In article <425d838e$1@forums-2-dub>, abmannz@yahoo.co.nz says...
>
| |
| Mark Maslow 2005-04-13, 8:24 pm |
| Thanks *very* much for the helpful information.
Replaced displaytag-1.0.jar with displaytag-1.0-b2.jar, and all is well.
1.0 works just fine with Tomcat 5, but not EAServer. Don't know just
where the fault lies, but it's great to have a way to get it working -
thanks again.
In article <425d9235@forums-1-dub>, abmannz@yahoo.co.nz says...
> We are on 4.2.3 for the production version. We are also using version
> 1.0-b2 of display tag and it works perfectly. I just deployed the
> displaytag-examples.war to 4.2.3, 4.2.5 and 5.2 and they all worked.
>
> I downloaded version 1.0 and tried to deploy it and get the same error
> you are seeing and I tried all the same eas versions as before, so it
> seems that displaytag is the problem and not eas. I guess this is a good
> reason for us not to upgrade to version 1.0 of displaytag :0)
>
> Pete
>
>
| |
| Mark Maslow 2005-04-13, 8:24 pm |
| I opened a case. The TS engineer did repro the problem (pretty simple
to do, after all), and will research further.
In article <425d98d4$2@forums-2-dub>, abmannz@yahoo.co.nz says...
> Looking at the source code the setName(...) function was changed in
> version 1.0 to take an object instead of a String. Myabe behind the
> scene when the jasper compiler generates the servlet file it thinks it
> is being smart but isnt.
>
| |
| Peter Abbott 2005-04-13, 8:24 pm |
| Better you then me. Sybase support are probably getting sick of me with
all the bugs I have been finding lately.
Mark Maslow wrote:[color=darkred
]
> I opened a case. The TS engineer did repro the problem (pretty simple
> to do, after all), and will research further.
>
> In article <425d98d4$2@forums-2-dub>, abmannz@yahoo.co.nz says...
>
|
|
|
|
|