Re: Bad build process for mod_webapp for Apache 2
Jean-Frederic - Attached is my libwebapp.la. I think I tried it with libwebapp.so and it did not produce a usable module. However, I am not too experienced a C/C++ programmer and have never used libtool before, so I was winging it. Here is the result of libtool --version: [root@strider webapp]# /usr/local/apache2/build/libtool --version ltmain.sh (GNU libtool) 1.3.4-freebsd-ports (1.385.2.196 1999/12/07 21:47:57) Thanx for the response! jeff jean-frederic clere wrote: Jeffrey Bonevich wrote: (sorry if this has come through already, but I did not see the post on the mail archive, so I done went and subscribed to the list to resend it) For those of you who do not regularly cruise the tomcat-user postings (you all do that regularly, right? ;-), a number of us in the user community have been struggling with getting Tomcat 4 integrated with Apach 2 using mod_webapp. I and a number of other users found a number of problems in the build process for mod_webapp - biggest of which is that the Makefile does not actually produce a DSO module (i.e. mod_webapp.so) for Apache 2. We figured out that the following will do so (after running configure and make): cd ${LOCATION_OF_CONNECTOR_SRC}/webapp/lib gcc -shared -o libwebapp.so *.lo You build a libwebapp.so cd ../apache-2.0 ${APACHE_HOME}/build/libtool --silent --mode=link \ gcc -shared -o mod_webapp.so -rpath ${APACHE_HOME}/modules \ -module -avoid-version -I../include -L../lib \ -dlopen ../lib/libwebapp.la mod_webapp.lo And you use libwebapp.la ... Are you sure that it does what you except? Could you send me the libwebapp.la and the the result of libtool --version? cp mod_webapp.so ${APACHE_HOME}/modules/ I have included a brief HOWTO that I compiled during the process of figuring this all out. If more information is needed, please let me know directly to my email (I am not presently on the dev mailing list distribution). Thanx! jeff -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Jeffrey Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com Hwæt! Wë Gär-Dena in geär-dagum, peod-cyninga, prym gefrünon, hü ða aepelingas ellen fremedon! # libwebapp.la - a libtool library file # Generated by ltmain.sh - GNU libtool 1.3.4-freebsd-ports (1.385.2.196 1999/12/07 21:47:57) # # Please DO NOT delete this file! # It is necessary for linking the library. # The name that we can dlopen(3). dlname='' # Names of this library. library_names='' # The name of the static archive. old_library='libwebapp.a' # Libraries that this one depends upon. dependency_libs='' # Version information for libwebapp. current=0 age=0 revision=0 # Is this an already installed library? installed=yes # Directory that this library needs to be installed in: libdir='/disk/0/src/java/jakarta-tomcat-connectors-4.0.2-01-src/webapp/lib' -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Bad build process for mod_webapp for Apache 2
(sorry if this has come through already, but I did not see the post on the mail archive, so I done went and subscribed to the list to resend it) For those of you who do not regularly cruise the tomcat-user postings (you all do that regularly, right? ;-), a number of us in the user community have been struggling with getting Tomcat 4 integrated with Apach 2 using mod_webapp. I and a number of other users found a number of problems in the build process for mod_webapp - biggest of which is that the Makefile does not actually produce a DSO module (i.e. mod_webapp.so) for Apache 2. We figured out that the following will do so (after running configure and make): cd ${LOCATION_OF_CONNECTOR_SRC}/webapp/lib gcc -shared -o libwebapp.so *.lo cd ../apache-2.0 ${APACHE_HOME}/build/libtool --silent --mode=link \ gcc -shared -o mod_webapp.so -rpath ${APACHE_HOME}/modules \ -module -avoid-version -I../include -L../lib \ -dlopen ../lib/libwebapp.la mod_webapp.lo cp mod_webapp.so ${APACHE_HOME}/modules/ I have included a brief HOWTO that I compiled during the process of figuring this all out. If more information is needed, please let me know directly to my email (I am not presently on the dev mailing list distribution). Thanx! jeff -- Jeffrey Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com Hwæt! Wë Gär-Dena in geär-dagum, peod-cyninga, prym gefrünon, hü ða aepelingas ellen fremedon! Tomcat4+Apache2+mod_webapp_HOWTO.sh Description: Bourne shell script -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: PATCH: tagdependent tags should not parse content
Another update: I was screwed to begin with - Parser was cutting out even before it got to the relevant section of code because the compiled JSP was sitting in $TOMCAT_HOME/work/localhost8080%2Fmodel2test/! D'oh! Therefore, the patch DOES work. Who do I contact to get this put into production??? Jeffrey Bonevich wrote: BTW I forgot to mention that I tried applying this patch myself to the Parser.java source code, without success - the patch as is does not appear to resolve the issue. Jeffrey Bonevich wrote: I found the following message in the archives for tomcat-dev from Dec 1999. It appears to never have been introduced to the distribution or to CVS or anything. Wondering what the status of a fix might be. * To: [EMAIL PROTECTED] Subject: PATCH: tagdependent tags should not parse content From: "Danno Ferrin" [EMAIL PROTECTED] Date: Wed, 08 Dec 1999 18:19:24 -0700 The bodycontent=tagdependent should provide a literal copy of the tag content. =JSP will handle JSP elements first, but tagdependent shoudlnt. Index: src/share/org/apache/jasper/compiler/Parser.java === RCS file: /home/cvspublic/jakarta-tomcat/src/share/org/apache/jasper/compiler/Parser.java,v retrieving revision 1.6 diff -C3 -r1.6 Parser.java *** Parser.java 1999/11/08 03:14:27 1.6 --- Parser.java 1999/12/09 01:17:40 *** *** 752,758 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); --- 752,764 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! if (bc.equalsIgnoreCase(TagInfo.BODY_CONTENT_TAG_DEPENDENT)) ! // accept no core elements for tag dependent, ! // i.e. literal inclusion of the content ! parser.parse(tagEnd, new Class[] {}); ! else ! // it is JSP body content, so accept all core elements ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PATCH: tagdependent tags should not parse content
I found the following message in the archives for tomcat-dev from Dec 1999. It appears to never have been introduced to the distribution or to CVS or anything. Wondering what the status of a fix might be. * To: [EMAIL PROTECTED] Subject: PATCH: tagdependent tags should not parse content From: "Danno Ferrin" [EMAIL PROTECTED] Date: Wed, 08 Dec 1999 18:19:24 -0700 The bodycontent=tagdependent should provide a literal copy of the tag content. =JSP will handle JSP elements first, but tagdependent shoudlnt. Index: src/share/org/apache/jasper/compiler/Parser.java === RCS file: /home/cvspublic/jakarta-tomcat/src/share/org/apache/jasper/compiler/Parser.java,v retrieving revision 1.6 diff -C3 -r1.6 Parser.java *** Parser.java 1999/11/08 03:14:27 1.6 --- Parser.java 1999/12/09 01:17:40 *** *** 752,758 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); --- 752,764 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! if (bc.equalsIgnoreCase(TagInfo.BODY_CONTENT_TAG_DEPENDENT)) ! // accept no core elements for tag dependent, ! // i.e. literal inclusion of the content ! parser.parse(tagEnd, new Class[] {}); ! else ! // it is JSP body content, so accept all core elements ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: PATCH: tagdependent tags should not parse content
BTW I forgot to mention that I tried applying this patch myself to the Parser.java source code, without success - the patch as is does not appear to resolve the issue. Jeffrey Bonevich wrote: I found the following message in the archives for tomcat-dev from Dec 1999. It appears to never have been introduced to the distribution or to CVS or anything. Wondering what the status of a fix might be. * To: [EMAIL PROTECTED] Subject: PATCH: tagdependent tags should not parse content From: "Danno Ferrin" [EMAIL PROTECTED] Date: Wed, 08 Dec 1999 18:19:24 -0700 The bodycontent=tagdependent should provide a literal copy of the tag content. =JSP will handle JSP elements first, but tagdependent shoudlnt. Index: src/share/org/apache/jasper/compiler/Parser.java === RCS file: /home/cvspublic/jakarta-tomcat/src/share/org/apache/jasper/compiler/Parser.java,v retrieving revision 1.6 diff -C3 -r1.6 Parser.java *** Parser.java 1999/11/08 03:14:27 1.6 --- Parser.java 1999/12/09 01:17:40 *** *** 752,758 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); --- 752,764 String tagEnd = "/"+tag+""; // Parse until the end of the tag body. // Then skip the tag end... ! if (bc.equalsIgnoreCase(TagInfo.BODY_CONTENT_TAG_DEPENDENT)) ! // accept no core elements for tag dependent, ! // i.e. literal inclusion of the content ! parser.parse(tagEnd, new Class[] {}); ! else ! // it is JSP body content, so accept all core elements ! parser.parse(tagEnd); reader.advance(tagEnd.length()); listener.handleTagEnd(bodyStart, reader.mark(), prefix, shortTagName, attrs, tli, ti); -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] -- Jeffrey Nikole Bonevich Maxmillian Bonevich Ann Arbor, Michigan [EMAIL PROTECTED] http://www.bonevich.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]