Apache, virtual host and Tomcat
Hi, I would like to run the following configurations with only one machine: 3 domains. Let's name them, www.domain1.com and sthg.domain2.com and www.domain2.com. www.domain1.com runs on 80 using apache and php www.domain2.com runs on 8080 using tomcat, mysql... sthg.domain2.com runs on 443 using apache and php Using the virtual hosts, I managed to set-up successfully www.domain1.com and sthg.domain2.com. I am now trying to include mod_jk, but when doing that, I am loosing the virtual hosts features and all my requests (for all sites) are sent to the tomcat instance (including the https one). Is that possible should probably my first question? Has anyone some experience with a similar set-up? One way (I think) of fixing the problem would be to have to instance of Apache on my machine listening on 80 and 81 for instance. All requests are arriving at 80, but www.domain2.com is pushed to 81 which then implements mod_jk. Thanks for your help. David. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [site] Working under 1.5 Was: Problems under 1.5
Just a follow-up: The hard-coded paths have been turned into parameters, which in turn are now passed in from the Ant script. The properties passed in as parameters were already defined using location, rather than value, so they become absolute paths - i.e. there is no more need to move the 1.4 files after generation. So the 1.4 hacks have been removed. 1.4 and 1.5 still generate different output, but I think I've got a work-round for that (see separate e-mail) S. On Feb 24, 2005 4:41 AM, Henri Yandell [EMAIL PROTECTED] wrote: And now works under 1.4, at least my OS X. Still with the proviso that switching between 1.4 and 1.5 will lead to large svn diffs, so I've got a big warning at the top of the ant output that recommends 1.5. The hacks for 1.4 are clearly defined, but there is a bit of hard-coding of path into the xsl files to get it working under 1.5 that wouldn't be there if I had a clue how to make that work nicely. Hen On Wed, 23 Feb 2005, Henri Yandell wrote: Following the lead of every great salesman, I'll begin by informing one and all that the site now generates under 1.5 quite happily. I'm using 1.5.0-rc under Debian Linux. If pine could do smallprint, I'd point out that 1.4 doesn't work now. I think it's going to be easier to fix 1.4 issues than to fix 1.5 issues. There's still the great big stinking pain of their different indentation/attribute-order, which we could possibly solve by shipping xsltc and forcing use of that. JDK 1.5 doesn't require the bootclasspath pain to get a different version of xsltc than the one in the jdk to work (as sun don't use the apache namespace for their variant). A driving reason for making 1.5 the working one and not 1.4 is that it's quite simply better. 10 seconds vs 2 minutes is hard to argue with. The biggest negative I know is that it cuts Mac users out (and I'm one of those). In a few months we'll be upgrading to 1.5 (Steve willing). I'll work on ant-hackery to make the 1.4 one at least be correct, and then hopefully we can echo a suggestion that using 1.5 is much preferable to 1.4 to avoid the evil svn diffs. If needed, we can then look at shipping xsltc with the build. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[site] Aligning 1.4 and 1.5 output ; other generic changes
I think I've found a way to deal with the different ordering of tag attributes between 1.4 and 1.5. Instead of using table class=x border=0 one can use table xsl:attribute name=classxsl:value-of select='x'//xsl:attribute xsl:attribute name=borderxsl:value-of select='0//xsl:attribute and thus force the attributes to be output in the same order by 1.5 and 1.4. It's harder to read, but it only has to be done for tags with more than one attribute, and hopefully only needs to be done in the stylesheets. The other main difference between 1.4 and 1.5 is that 1.4 adds a space before self-terminated tags, i.e br / as against br/. This can easily be fixed with a replace task. I'm happy to apply these changes, but this would involve updating all the output files. I assume the best would be to emulate 1.5 output in 1.4, rather than fixing the 1.5 output by adding the extra spaces. It's a bit easier too, as the first attribute can be left in the initial tag. Emulating 1.4 order in 1.5 means reordering them all. As all the files would need to be updated, it seems a good time to consider what other global changes are desirable. For example: Copyright symbol should be provided as copy;, not nnn; - this would remove the need for the xml declaration (none of the other ASF sites I checked use this). Maybe use UTF-8 rather than iso-8859-1? [Not sure this would make much difference at present, but might be better long-term?] Any other suggestions? Seb. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r160118 - jakarta/site/docs/site/downloads/downloads_jmeter.html
Thought I'd try just a single page using the new XSL stylesheets ... the page has been updated on minotaur, so should be testable soon. I'll do the rest of the pages later. S. On Apr 5, 2005 12:50 AM, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: sebb Date: Mon Apr 4 16:50:07 2005 New Revision: 160118 URL: http://svn.apache.org/viewcvs?view=revrev=160118 Log: Rebuild using common 1.4/1.5 styles Modified: jakarta/site/docs/site/downloads/downloads_jmeter.html Modified: jakarta/site/docs/site/downloads/downloads_jmeter.html URL: http://svn.apache.org/viewcvs/jakarta/site/docs/site/downloads/downloads_jmeter.html?view=diffr1=160117r2=160118 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
