Re: JasperException: Unable to compile class for JSP

Put it in a package ... http://jakarta.apache.org/tomcat/faq/classnotfound.html -Tim Goo GGooo wrote: On 10/4/05, Wendy Smoak wrote: From: Goo GGooo [EMAIL PROTECTED] An error occurred at line: 1 in the jsp file: /name.jsp Generated servlet error: UserData cannot be resolved or is not a

JasperException: Unable to compile class for JSP

: === org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: 1 in the jsp file: /name.jsp Generated servlet error: UserData cannot be resolved or is not a type === Files webapps/tut/name.jsp and webapps/tut/WEB-INF/classes/UserData.java are attached. Of course I've got

Re: JasperException: Unable to compile class for JSP

On 10/4/05, Wendy Smoak wrote: From: Goo GGooo [EMAIL PROTECTED] An error occurred at line: 1 in the jsp file: /name.jsp Generated servlet error: UserData cannot be resolved or is not a type === Files webapps/tut/name.jsp and webapps/tut/WEB-INF/classes/UserData.java are attached.

compile precompile jsps at runtime

Hi all, Is there a way to compile precompiled jsp at runtime? i.e., I want to precompiled my jsp before deployment, but after they are deployed I still want to make changes to the jsps that will take effect immediately. I want to be able to change jsp and see the changes immediately although

Re: compile precompile jsps at runtime

Can't with tomcat out of the box. -Tim Zachi Hazan wrote: Hi all, Is there a way to compile precompiled jsp at runtime? i.e., I want to precompiled my jsp before deployment, but after they are deployed I still want to make changes to the jsps that will take effect immediately. I want

Re: compile precompile jsps at runtime

So, how can I do it with tomcat not out of the box? Tim Funk wrote: Can't with tomcat out of the box. -Tim Zachi Hazan wrote: Hi all, Is there a way to compile precompiled jsp at runtime? i.e., I want to precompiled my jsp before deployment, but after they are deployed I still want

Re: compile precompile jsps at runtime

? Tim Funk wrote: Can't with tomcat out of the box. -Tim Zachi Hazan wrote: Hi all, Is there a way to compile precompiled jsp at runtime? i.e., I want to precompiled my jsp before deployment, but after they are deployed I still want to make changes to the jsps that will take effect

RE: compile precompile jsps at runtime

From: Zachi Hazan [mailto:[EMAIL PROTECTED] Subject: Re: compile precompile jsps at runtime So, how can I do it with tomcat not out of the box? One approach would be to cheat! Tomcat compiles the page when the page is first invoked. So, you could for example define a special parameter

AW: JspC compile exception in tomcat-deployer 5.5.10

}${webappname}/WEB-INF/lib include name=*.jar/ /fileset /classpath /taskdef -Ursprüngliche Nachricht- Von: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Gesendet: Montag, 15. August 2005 23:58 An: tomcat-user@jakarta.apache.org Betreff: JspC compile

Re: JspC compile exception in tomcat-deployer 5.5.10

On 8/16/05, Bernhard Slominski [EMAIL PROTECTED] wrote: Hi Richard, the problem is that your classpath for the jasper path is not correct. So this Null Pointer exception actually means that some class was not found. Note that you need all the tomcat libraries in your jaser classpath, as well

JspC compile exception in tomcat-deployer 5.5.10

Hello, I am using the jakarta-tomcat-5.5.10-deployer to deploy my customized war file to tomcat. When I have it do the "compile" target so it pre-compiles the JSP's I get theexception below (its sort of long). I've got the source and can see that it is happening as it processe

Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

Hi all, I am having difficulties to figure out the solution for this issue. Jsp pages with log4j logging statements that worked perfect on Tomcat 4.1.30 could not compile on Tomcat 5.5.9. I commented out the log4j statements for these problematic pages, then, tomcat 5.5.9 could compile them

RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

Users List Subject: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 Hi all, I am having difficulties to figure out the solution for this issue. Jsp pages with log4j logging statements that worked perfect on Tomcat 4.1.30 could not compile on Tomcat 5.5.9. I

RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

:[EMAIL PROTECTED] Sent: August 12, 2005 11:20 AM To: Tomcat Users List Subject: RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 Can you post the JSP directives, and the scriplet that calls log4j? Also, you have been given a line number 39 .. can you work out which line

Re: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

[mailto:[EMAIL PROTECTED] Sent: August 12, 2005 11:20 AM To: Tomcat Users List Subject: RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 Can you post the JSP directives, and the scriplet that calls log4j? Also, you have been given a line number 39 .. can you work out which line

RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

Subject: Re: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 It doesn't like the agent_report_all_in_jsp classname. I'm guessing that's supposed to be the name of the servlet class generated from the jsp. Are you sure it's correct? If it is then you may have to use a String

RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

on Tomcat 4.1.30 does not have? Thanks. Gary -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: August 12, 2005 11:46 AM To: Tomcat Users List Subject: RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 I think Jon maybe onto something ... to use

RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

? Allistair. -Original Message- From: Gary Zhu [mailto:[EMAIL PROTECTED] Sent: 12 August 2005 17:08 To: Tomcat Users List Subject: RE: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9 First of all, I am not the one who did this app. Second, it is the case

Re: Cannot compile jsp pages with log4j statements -- Tomcat 5.5.9

is agent_report_all_in.jsp is in a different directory from the one that fails to compile. It works in 4.1 but needs to be imported in 5.x.x. Allistair Crossley wrote: Hi, It doesn't really matter if you did the app or not, it's irrelevant to this conversation and you asked a question. Anyway

Compile error in v5 but not v4

Hello; An application I'm trying to support runs without error on Tomcat 4.1.24 on Windows and Tomcat 4.0.3 on HPUX. When attempting to have it run on Tomcat 5.0.28 on Windows one of the very large JSP pages fails to compile: Jul 27, 2005 3:02:46 PM org.apache.jasper.compiler.Compiler

Re: Compile error in v5 but not v4

Tomcat5 uses jasper 2 which does much better optimizations of handlng custom tags. If you ahve a page with a lot of custom tags - it might not compile in tomcat 4. One alternative (but with a performance penalty) is to split some of the JSP file into a run-time include (jsp:include). -Tim

[Jasper/Orion] compile JSP servlets

I'm trying to write an ant task to pre-compile JSP pages, but I have the following problem. Here is a piece of page : # form:input type=hidden name=idy value=%= itlBean.getIdy() %/ (itlBean.getIdy() returns a Long.) Then I try to transform the JSP page into a servlet with the jasper task

1.2.10 JK compile issue on AIX 5L

After 800 tries at getting APache compiled with the AIX C compiler xlc_r, I now need to compile mod_k. I downloaded the sources for connector 1.2.10. I am trying to compile it on AIX 5L with uname -a AIX hostname 2 5 00C04A2E4C00. I am using AIX's cc_r compiler per instructions from http

Re: JSP pre-compile and Apache

sorts of weird errors occurred. I remember reading somewhere that Apache expected the actual jsp file, not the compiled version. So I reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp

AW: JSP pre-compile and Apache

Well there is one big advantage when using precompiled JSPs: You're sure that all JSPs are compilable, so you don't get any compile errors on your live site. That gives your application more stability. Bernhard -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED

Re: AW: JSP pre-compile and Apache

precompiled JSPs: You're sure that all JSPs are compilable, so you don't get any compile errors on your live site. That gives your application more stability. Bernhard -Ursprngliche Nachricht- Von: Charl Gerber [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 17. Juni 2005 08:07

AW: AW: JSP pre-compile and Apache

It's not that it's not tested. It can happen very easiliy, when you just forgot to check something in the version control: You added a method to a bean, change the JSP, it's working fine in you test environment, you check in the JSP, but forget the bean, do the release and you get the compile

How can I using Jasper 2 JSP Engine back-compile the java file to jsp file?

I deleted all my project files by misoperation. Using the FinalDate+GoogleDesktop makes all java and xml files back. But some jsp ... ;-( Thanks In Advance

JSP pre-compile and Apache

to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone managed to get

Re: JSP pre-compile and Apache

reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone

Re: JSP pre-compile and Apache

and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same? How about the overhead to check if the .jsp file indeed matches the compiled version? Has someone managed to get precompiled JSP's

Re: JSP pre-compile and Apache

remember reading somewhere that Apache expected the actual jsp file, not the compiled version. So I reverted back to *not* precompiling JSP's and everything worked as expected. Question now, obviously there is a first-time-compile penalty per jsp, but once compiled, should performance be the same

JSP too big to compile?

We have a web page that contains many business documents laid out one after the other so a user can just click print and have all of them print together (with a stylesheet that starts each contract on its own printed page). But we seem to be having an error that the generated servlet code is

RE: JSP too big to compile?

@jakarta.apache.org Subject: JSP too big to compile? We have a web page that contains many business documents laid out one after the other so a user can just click print and have all of them print together (with a stylesheet that starts each contract on its own printed page). But we seem to be having

Re: JSP too big to compile?

You are actually limited by Java. I can't recall the actual size off hand, but a method can only be so big. From what I remember, it has something to do with server side includes vs jsp includes. We ended up doing some pretty nasty stuff by conditionally doing a server side include. I can't

Re: JSP too big to compile?

@jakarta.apache.org Subject: JSP too big to compile? We have a web page that contains many business documents laid out one after the other so a user can just click print and have all of them print together (with a stylesheet that starts each contract on its own printed page). But we seem to be having

RE: JSP too big to compile?

working..for me it do. Maarten -Oorspronkelijk bericht- Van: David Wall [mailto:[EMAIL PROTECTED] Verzonden: zaterdag 4 juni 2005 0:18 Aan: Tomcat Users List Onderwerp: Re: JSP too big to compile? The jsp:include is coming very close for us, but we're doing some tricks on these JSP pages

Tomcat optimization... saving internal strings with character encoding at compile time.

in this setup would be dynamic strings from EL. It would also save more memory for English text since strings no longer are stored in 32bit but just UTF8 encoded 8 bit values. It would slow down compile time though because Jasper would now need to call toByteArray() on all your strings

Re: Tomcat optimization... saving internal strings with character encoding at compile time.

it directly. The only thing that would need to be encoded in this setup would be dynamic strings from EL. It would also save more memory for English text since strings no longer are stored in 32bit but just UTF8 encoded 8 bit values. It would slow down compile time though because Jasper would

5.5.9 jasper ant compile options

I want to compile my jsps before depolying my war, so I'm using the standalone deployer build.xml. In the web.xml (for the jsp servlet) I can set some options eg. genStrAsCharArray or trimSpaces. How can I set these compile options in the ant task? Thx Gernot

Unable to pre-compile JSP with jspC ant task

I commented the reference to the library directory. The task is then used by: !-- = -- !-- Compiles the jsp pages-- !-- = -- target name=jspc depends= description=Compile jsp

compile against servlet.jar but must run tomcat with servlet-ap1.jar

Hi All, We our new to Tomcat and have a bit of an odd problem. We are developing a getting started project. We have found that we must compile with servlet.jar in our CLASSPATH, but Tomcat will not run with servlet.jar in the CLASSPATH. Tomcat will run with servlet-api.jar, but the test

Re: compile against servlet.jar but must run tomcat with servlet-ap1.jar

As a generality, a compilation should set up all required environment setting with each build run. Those settings should be transitory, i.e., should not persists beyond that build. So in your case you would add servlet.jar to the classpath temporarily, compile, and revert the classpath

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

era, so I suspect it will take the same time before that IBM compiler supports Java 5 features. Netbeans will comile them in the IDE with Java 5, but Tomcat won't compile them with Java 5. - Original Message - From: Stefan Parnet [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org

Please correct docs - Compile JSPs w/ JDK 1.5

Please correct the documentation to reflect that this does not work. It would save a lot of time and lots of emails here about the same issue. Thanks, Milo -- ___ Get your free email from http://www.dellmail.com

RE: Howto configure tomcat to compile JSPs with Sun JDK 1.5

d'origine- De : Stefan Parnet [mailto:[EMAIL PROTECTED] Envoyé : mercredi 27 avril 2005 16:14 À : Tomcat Users List Objet : Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5 Lutz Zetzsche schrieb: Hi Stefan, Am Mittwoch, 27. April 2005 15:20 schrieb Stefan Parnet: Hello, I

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

to compile JSPs. But it should be possible to change the config, so that Tomcat uses another compiler. At least, the releasenotes say so. But there is no useful howto at the tomcat web site or anywhere else. (at least I didn't find one) The problem is: 1. Tomcat 5.5 (without compatibility packages

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

Hi Stefan, Am Donnerstag, 28. April 2005 09:07 schrieb Stefan Parnet: The problem is: 1. Tomcat 5.5 (without compatibility packages) runs only with Java 1.5 (JRE!) 2. The built in Java compiler to compile JSPs (and only JSPs) is the Eclipse JDT Compiler !!! JAVA 1.4 !!! == So Servlets

RE: Howto configure tomcat to compile JSPs with Sun JDK 1.5

since (I haven't found time to compile Tomcat on my own and try), and I didn't find anything about this in the 5.5.9 changelog. Regards Stephan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

Howto configure tomcat to compile JSPs with Sun JDK 1.5

Hello, I installed Tomcat 5.5.9 and want to use Java 1.5 in my JSPs. Since Tomcat 5.5 uses the Eclipse JDT Compiler (Java 1.4), it cannot compile my JSPs. So I want the tomcat to compile the JSP's with the Sun JDK 1.5 compiler. I searched the web, but I did not find any instructions how

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

Hi Stefan, Am Mittwoch, 27. April 2005 15:20 schrieb Stefan Parnet: Hello, I installed Tomcat 5.5.9 and want to use Java 1.5 in my JSPs. Since Tomcat 5.5 uses the Eclipse JDT Compiler (Java 1.4), it cannot compile my JSPs. So I want the tomcat to compile the JSP's with the Sun JDK 1.5

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

Lutz Zetzsche schrieb: Hi Stefan, Am Mittwoch, 27. April 2005 15:20 schrieb Stefan Parnet: Hello, I installed Tomcat 5.5.9 and want to use Java 1.5 in my JSPs. Since Tomcat 5.5 uses the Eclipse JDT Compiler (Java 1.4), it cannot compile my JSPs. So I want the tomcat to compile the JSP's

Re: Howto configure tomcat to compile JSPs with Sun JDK 1.5

Hi Stefan, Am Mittwoch, 27. April 2005 16:14 schrieb Stefan Parnet: I have the environment variables JAVA_HOME and JRE_HOME already set to the JDK, but Tomcat still compiles JSPs with its built in Eclipse JDT Java compiler. This fact is mentioned in the Release Notes. There is also mentioned

JSPs slow to compile?

I am running Liferay Portal Pro 3.3 under tomcat 5.5.9 on fedora fc3 running on a 1.2ghz p4 w/ 3gb ram. Initial page loads are taking on the order of 30 seconds. After the initial page load, it takes just a second to reload. 30 seconds seems like a long time to initially compile the page

Re: JSPs slow to compile?

running on a 1.2ghz p4 w/ 3gb ram. Initial page loads are taking on the order of 30 seconds. After the initial page load, it takes just a second to reload. 30 seconds seems like a long time to initially compile the page and load it. Do I potentially have something misconfigured? Also, I've tried

Compile JSPs with Java 5 features?

I've followed the directions in the docs to get 5.5.7 to compile JSPs with -source 1.5 features. It stays in -source 1.4 mode. I know the docs say the IBM compiler will be updated to handle Java 5 feature. When inner classes were introduced in jdk 1.1, it took IBM a year to implement inner

JSP compile with jdk 1.5 in 5.5.7

/param-value /init-param I get an error saying that the [java 5 ] features are not supported in source 1.4 Seems like these flags are not being passed to ant. Are these flags still valid? Can JSPs be compile using Java 5 in Tomcat 5.5.x? I know the docs say that the IBM compiler

Cannot compile class in WEB-INF/classes

HttpServletRequest request as an argument. This will be passed when this method is called from the scriplet java code from the JSP page. The Problem is that the utility java file does not compile and gives error- Cannot recognize HttpServletRequest. Shouldn't servlet-api.jar be automatically

RE: Cannot compile class in WEB-INF/classes

Did you import javax.servlet.http.* ? -Original Message- From: Rahul Joshi [mailto:[EMAIL PROTECTED] Sent: Thursday, March 10, 2005 1:19 PM To: tomcat-user@jakarta.apache.org Subject: Cannot compile class in WEB-INF/classes I have a Simple JSP page in my webapps/myappname. I have

RE: Cannot compile class in WEB-INF/classes

: Rahul Joshi [mailto:[EMAIL PROTECTED] Sent: Thursday, March 10, 2005 1:19 PM To: tomcat-user@jakarta.apache.org Subject: Cannot compile class in WEB-INF/classes I have a Simple JSP page in my webapps/myappname. I have a utility class which this page will use. The class file for this should

RE: Cannot compile class in WEB-INF/classes

Have you compiled the class previously? The source for the class does not go in the WEB-INF/classes directory - only the class files go here. You also need to pre-compile your classes - Tomcat doesn't do this for you. -Original Message- From: Rahul Joshi [mailto:[EMAIL PROTECTED] Sent

RE: Cannot compile class in WEB-INF/classes

I did not try compiling it at an external location. I thought I would compile it in classes and then delete the source java file later. I will try your suggestion of compiling it outside of tomcat and then copying the class in the classes directory. But does it mean that a java file cannot

Tomcat 5.x - Is AIX 5.2 a supported O.S.? Unable to compile jsvc-src

I can't find documentation regarding supported Operating Systems or levels for Tomcat 5.x or 5.5.7. The error returned from .configure to indicates AIX 5.2.0 is not a supported operating system. When looking at .configure, I don't see any support for AIX. Is this correct or am I missing

Tomcat 5.x - Is AIX 5.2 a supported O.S.? Unable to compile jsvc-src

Subject:Tomcat 5.x - Is AIX 5.2 a supported O.S.? Unable to compile jsvc-src I can't find documentation regarding supported Operating Systems or levels for Tomcat 5.x or 5.5.7. The error returned from .configure to indicates AIX 5.2.0 is not a supported operating system. When looking

JSP Compile size error.

When trying to run my web app (Tomcat 5.5.6 on RedHat Linux 9) I get the following error:- org.apache.jasper.JasperException: Unable to compile class for JSP Generated servlet error: The code of method _jspService(javax.servlet.http.HttpServletRequest, javax.servlet.http.HttpServletResponse

Re: JSP Compile size error.

@includes to include source - that could be another reason for such a large file. [Personally .. @includes are evil] -Tim Kelly, Steve wrote: When trying to run my web app (Tomcat 5.5.6 on RedHat Linux 9) I get the following error:- org.apache.jasper.JasperException: Unable to compile class for JSP

RE: JSP Compile size error.

Thanks Tim. You're right the jsp is pretty huge. Is this limit configurable anywhere? Steve. -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: 21 January 2005 11:48 To: Tomcat Users List Subject: Re: JSP Compile size error. Its a limit of the java compiler

RE: JSP Compile size error.

From: Tim Funk [mailto:[EMAIL PROTECTED] Subject: Re: JSP Compile size error. Its a limit of the java compiler. Actually it's a limitation of the Virtual Machine Specification. The method size in a class file is a 16-bit field. (I thought it was supposed to get bigger in 5.0 - I'm still

Re: dynamically compile JSPs

and compiles the JSP file to the proper directory under TOMCAT_HOME/work/ Now - I have another problem - there are 2 types of files that I do this with. They both wind up being Struts/Tiles layout files, just in different directories basically. When I upload/compile to one of the directories

Re: Can't compile mod_jk 1.2.8

. The issue was addressed on the list couple of days ago. Take a look at: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error thread from Jan. 5th. The solution is to download and compile the latest Apache 2.0.52 version. Mladen. Thank you ALL for your advice on this matter! I found the mod_proxy

Re: dynamically compile JSPs

I was messing around with the code a little bit, and tried this: JspC antTask = new JspC(); antTask.setArgs(new String[] { -compile, uploadTileFilePath }); antTask.execute(); but this always gave me an error that javax.servlet package could not be found. Replying to myself here - but I got

Unable to compile class for JSP

Hi, This web page displays correctly http://www.dksy.net:8080/examples/jsp/num/numguess.jsp but all of the other examples on this page display the error below: http://www.dksy.net:8080/examples/jsp/index.html org.apache.jasper.JasperException: Unable to compile class for JSP An error

RE: Unable to compile class for JSP

Server Env: Apache Tomcat 4.1.30 JVM 1.4.2_04-b05 Linux - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

RE: Unable to compile class for JSP

@jakarta.apache.org Subject: Unable to compile class for JSP Hi, This web page displays correctly http://www.dksy.net:8080/examples/jsp/num/numguess.jsp but all of the other examples on this page display the error below: http://www.dksy.net:8080/examples/jsp/index.html org.apache.jasper.JasperException

Can't compile mod_jk 1.2.8

/sh /usr/bin/libtool --silent --mode=compile gcc -I/usr/include/httpd -g -O2 -DHAVE_JNI -O2 -g -pipe -march=i386 -mcpu=i686 -DSSL_EXPERIMENTAL_ENGINE -I/usr/kerberos/include -pthread -DHAVE_APR -I/rpmbuild/skvidal/rpm/BUILD/httpd-2.0.46/prefork/srclib/apr/include /rpmbuild/skvidal/rpm/BUILD/httpd

Re: dynamically compile JSPs

this code in my class after the JSP file is uploaded: JspC antTask = new JspC(); antTask.setArgs(new String[] { uploadTileFilePath }); antTask.execute(); And this does not seem to compile the file reliably. It does seem like something is happening, because the upload/compile action takes about 25-30

Re: Can't compile mod_jk 1.2.8

This is just a guess, but try it without the --with-java-home=... setting. ./configure --with-apxs=/usr/sbin/apxs I'm working with the following on Sun Solaris 8: Tomcat 5.0.28 Apache 2.0.52 mod_jk 1.2.8 I was using Tomcat 5.5.4, but was having problems, so I dropped back to the 5.0.x branch.

Re: Can't compile mod_jk 1.2.8

] To: tomcat-user@jakarta.apache.org Sent: Monday, January 10, 2005 5:04 PM Subject: Can't compile mod_jk 1.2.8 Hello All, I know just enough to be dangerous.. not enough to know what is blowing my mod_jk build. I am on a super-fast dual 3.2GHz machine running CentOS (RedHat ES 3.0) with Apache

Re: dynamically compile JSPs

Hey, I remember this thread :) (Mostly because you quoted my comment!) One solution is to shell out to do the compilation. I think I probably gave it to you last time, but here's the two pertinent lines from my compile job that does it: java -classpath %CP% org.apache.jasper.JspC -v3 -die -d

Re: Can't compile mod_jk 1.2.8

Parsons... How would mod_proxy() work? How is it used? I have not used it. Thanks, Troy -- Troy Simpson Applications Analyst/Programmer, OCPDBA, MCSE, SCSA North Carolina State University Libraries Campus Box 7111 | Raleigh | North Carolina ph.919.515.3855 | fax.919.513.3330

Re: Can't compile mod_jk 1.2.8

Basically, the idea is that if you want to serve static content along with dynamic (i.e., Tomcat webapp generated) content, you can server the dynamic through mod_jk/Tomcat and server the static from Apache. Apache tends to be more efficient and finely tunable from the straight http side.

Re: Can't compile mod_jk 1.2.8

http://httpd.apache.org/docs-2.0/mod/mod_proxy.html http://jakarta.apache.org/tomcat/faq/connectors.html#vs - Original Message - From: Ben Ricker [EMAIL PROTECTED] To: Tomcat Users List tomcat-user@jakarta.apache.org Sent: Monday, January 10, 2005 7:06 PM Subject: Re: Can't compile mod_jk

Re: Can't compile mod_jk 1.2.8

couple of days ago. Take a look at: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error thread from Jan. 5th. The solution is to download and compile the latest Apache 2.0.52 version. Mladen. - To unsubscribe, e-mail: [EMAIL

Re: [FIXED] Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Thomas Tinnes wrote: Hello, Just a follow up to let you know how this got resolved. First, thanks to all my respondents. It all helped. I tried using ./buildconf.sh, but got the same result. The Rosetta Stone came from Mladden when it was pointed out that the second value of -DHAVE_APR hadn't a -I

Re: [FIXED] Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Hello, Just a brief epilog. Yes, Mladen, that's exactly what I had to do, in the end. I was trying to stay within the client's framework of crumbling, elderly programs and not take apps forward (in version), but in the end it proved impossible. It took four hours to compile the elderly Apache

Re: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Mladen, No luck, alas. Same error. But thank you for the pointer, all the same. [EMAIL PROTECTED] make Making all in common make[1]: Entering directory `/tmp/jk/jakarta-tomcat-connectors-1.2.8-src/jk/native/common' /bin/sh /usr/bin/libtool --silent --mode=compile gcc -I/usr/include/httpd -g -O2

RE: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

From: Thomas Tinnes [mailto:[EMAIL PROTECTED] Subject: Re: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error -I/usr/src/redhat/BUILD/httpd-2.0.46/prefork/srclib/apr/include /usr/src/redhat/BUILD/httpd-2.0.46/srclib/apr/include -g -O2 I think the problem is directly above: there's

Re: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Thomas Tinnes wrote: Mladen, No luck, alas. Same error. But thank you for the pointer, all the same. Seems that the space is not a problem, but you have a strange entry: -I/usr/src/redhat/BUILD/httpd-2.0.46/prefork/srclib/apr/include /usr/src/redhat/BUILD/httpd-2.0.46/srclib/apr/include ...

RE: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Subject: RE: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error P.S. I believe there should be a space before each -I, but it may be optional. Make that AFTER each -I. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL

Re: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

On Wed, 5 Jan 2005, Thomas Tinnes wrote: Mladen, No luck, alas. Same error. But thank you for the pointer, all the same. [EMAIL PROTECTED] make Making all in common make[1]: Entering directory file or directory make[1]: *** [jk_ajp12_worker.lo] Error 1 make[1]: Leaving directory

[FIXED] Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

was to go to each Makefile (./common, ./apache-1.3, ./apache-2.0) and just vi and add the missing -I. It seems to have compiled and installed fine. Thanks, again, to all. _tom On Jan 4, 2005, at 9:16 PM, Thomas Tinnes wrote: Hello, Getting a compile error I'm having trouble understanding. Here's my

Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Hello, Getting a compile error I'm having trouble understanding. Here's my setup: Installing jakarta-tomcat-connectors-1.2.8-src.tar.gz from the Jakarta site. On a Linux Red Hat Enterprise 3 (Taroon) on an i386 arch i686 cpu. I'm using gcc version 3.4.3 20041212 (Red Hat 3.4.3-10). There's

Re: Mod_JK 1.2.8, gcc 3.4.3 on Linux RH ES3 - compile error

Thomas Tinnes wrote: make[1]: Entering directory `/tmp/jk/jakarta-tomcat-connectors-1.2.8-src/jk/native/common' -D_GNU_SOURCE -I /usr/local/java/include -I /usr/local/java/include/ -c jk_ajp12_worker.c Perhaps the error is caused by space between -I and /usr/local/java Have no idea why this

Re: Compile and Deploy JSPs - Tomcat 4.0

Usually Tomcat JSPC compiler compiles classes to package org.apache.jsp. You can override it by specifiying packagename as an argument to the compile command/Ant task. Perhaps something is wrong with the compile arguments you used or the classfiles are not packed into the war file. rgds Antony

RE: Compile and Deploy JSPs - Tomcat 4.0

in advance, Abhay -Original Message- From: Antony Paul [mailto:[EMAIL PROTECTED] Sent: Tue, 21 Dec 2004 09:34 To: Tomcat Users List Subject: Re: Compile and Deploy JSPs - Tomcat 4.0 The proper way to do this is use the JSPC task to compile JSP files to class files and then create url

dynamically compile JSPs

Hi all - If you have your tomcat servers setup with development=false (compiling every 5 minutes) - is there a way to dynamically compile certain JSP pages from inside your servlet code? (Or at least to trigger a compile to happen off of the schedule?) If so - are there any side effects

Re: dynamically compile JSPs

compile certain JSP pages from inside your servlet code? (Or at least to trigger a compile to happen off of the schedule?) If so - are there any side effects of doing this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

Re: Compile and Deploy JSPs - Tomcat 4.0

:655) Could any one help. Thanks in advance, Abhay -Original Message- From: Antony Paul [mailto:[EMAIL PROTECTED] Sent: Tue, 21 Dec 2004 09:34 To: Tomcat Users List Subject: Re: Compile and Deploy JSPs - Tomcat 4.0 The proper way to do this is use the JSPC task

Re: dynamically compile JSPs

want to compile dynamically is a struts/tiles layout page. There is no way to access the file directly through the browser. I may be able to get away with putting jsp_compile=true in the tile definition path, but I'd like to avoid that because (if my understanding of this parameter is true

RE: dynamically compile JSPs

This might be a long way round but you could call a system ant job to compile them. Or if it is appropriate in your environment you should just precompile them anyway, this way there will be no performance hit at all on your production server when a new deployment is made. Ta Matt

  1   2   3   4   5   6   7   8   9   10   >