Well yes it seems u will be in for some pain. Tomcat5 and Apache2 is a
nightmare and I am surprised there isn't a 'how to get it working nice'
paper online- all the docs seem to gloss over the topic... I have it sort of
working but the /magnoliaPublic/ is still in the URL so I guess its really
doesn't work and I have no idea if it's an Apache thing or a Tomcat/Magnolia
thing... it's a strange one because it becomes useable if you can set it up
for deployment. Mind you there's loads of JSP websites, so it must be
doable? I also have a new book on the topic, its now in the bin!
Maybe its because im using:
String contentPath = request.getContextPath();
contentPath+page.getHandle();
and the contentPath is the full path to the page that includes the
/magnoliaPublic/? If I take it out and code it so it's a relative path to
say 'index/home.html' the page wont load- seems load if I point to
'index/home' (without the .html), but cant be correct surely? So I seem to
be stuck with the /magnoliaPublic/ in the path... I made it ROOT in Tomcat
but when I click a link on the page- that link then just links off to
/magnoliaPublic/ anyways...
gave up last night messing with it (brain burn) and played a bit of World of
Warcraft with the wife. Funny how u think u have it all sorted and you just
don't at all really- I should stick to video and 3d programming :) LOL
if anyone wants to help us noobs and has some time to spill the blackarts to
this area I would be the first to appreciate it..
aNt
ps: https is also something I was thinking of adding- I can see that being a
bitch also dude :(
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> Sent: 28 September 2005 19:21
> To: [email protected]
> Subject: Re: [magnolia-user] deployed URL's '/magnoliaAuthor/' or
> '/magnoliaPublic/'?
>
> I see my thread from 2 months ago has reappeared.
>
> I've been spending a lot of time figuring out how to deal with a clean
> server config where webapps are setup with context config files, and
> Resource and Realm elements require different treatment, how to deal
> with JSTL 1.1 as opposed to 1.0, how to deal with JSP 2.0 as opposed to
> 1.2 (no, make that JSPX), how to deal with the i18n support, installing
> RC2 & setting up definitions, & then exporting & importing the
> denifitions to RC3, then to RC4, then to 2.1 Final.
>
> I'm finally to where I can start rebuilding my site on 2.1. I've never
> had much success with the clustering functionality, or configuring
> subscribers other than the default public, so won't even try to activate
> from 2.0.3 to 2.1. I understand that with the differences in the
> repository standards, that's not a good idea anyway.
>
>
> Soon, I will need to again turn my attention to this 'Connect Tomcat to
> Apache', but I'm afraid this is the most obsure topic of all. I had a
> Magnolia-based site ready last November, but our networks guys didn't
> get the mod_jk connector working until February. This didn't look very
> good to the execs who think that Magnolia was the problem.
>
> My guys could not connect Apache 1.3 to Tomcat 5, and didn't want to go
> down some of the other optional roads because the technologies are
> depricated. They did an upgrade to Apache 2.0, and with some help from
> me, finally got the connection to work. I believe I hit the Magnolia
> demo site once, and Tomcat had fallen over or something, and I saw some
> Apache error screen with 'Apache 1.3' at the bottom, so I know someone
> knows how to connect Apache 1.3 to Tomcat 5.0. I sure wish they would've
> shared that, but Apache issues aren't Magnolia issues, so the topic is
> somewhat out of bounds.
>
> I'm not sure, but it seems that any Tomcat URI can be connected to
> Apache in various ways. My organization is a co-operative of 1600
> independent pharmacies, and we have more resources and focus on our
> secure (HTTPS) members site, than our public site (HTTP). So while its
> nice that we were able to get a public Magnolia-based site running AND
> connected to Apache, to me the biggest issue is, and has always been,
> are we going to be able to take a 'Website' config tree (say 'udhome')
> and connect that to Apache port 80 (HTTP), while also taking another
> 'Website' tree, (say 'udmembers') and connect that to Apache port 443
> (HTTPS), while also taking another 'Website' tree (say 'udsales') and
> connecting that also to Apache port 443 (HTTPS)?
>
> The two sites on HTTPS would not be at webroot, but would have their own
> URI's or contexts (https://www.ud.com/members/ , https://ud.com/sales/).
> Right now, our members site is still PHP-based, and is constrained by
> PHPlib. I added a little redirect script at webroot that takes you to
> '/members/' if you browse to webroot.
>
>
> From the administrative wizardry I've seen exhibited by some of the
> Magnolia users and developers, I think many would say "Oh yes,
> connecting those Tomcat URI's to those Apache virtual URI's is easy",
> but for me, I think I'm in for a major headache.
>
> As far as my original question regarding linking to resources relative
> to webroot being a problem with the single Tomcat setup, I haven't been
> able to wrap my mind around how I'm going to deal with that. I see
> discussions around 'simpleNavigation' come up a lot, and this appears to
> be what you use if you want your navigation to dynamically come from the
> the 'website' repository, but we use a DHTML cascading menu where I have
> to hard code the links. I've fooled with server & client side scripting
> enough that I could probably pull the nav data from the repository and
> dynamically write the javascript arrays needed by the DHTML menu, and
> this would probably take care of the '/magnoliaPublic/' and
> '/magnoliaAuthor/', but I don't know. I'm in a "the more I learn, the
> less I know" situation.
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 28, 2005 8:28 AM
> To: [email protected]
> Subject: Re: [magnolia-user] deployed URL's '/magnoliaAuthor/' or
> '/magnoliaPublic/'?
>
> Seems to have worked- but I still get my magnoliaPublic within the link.
> Without it nothing links up... not sure what else I can do...
>
> aNt
>
>
>
> ----------------------------------------------------------------
> for list details see
> http://www.magnolia.info/en/magnolia/developer.html
> ----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
