Re: Getting OpenBlueDragon and Tomcat to traverse directories

[Jordan Michaels <jo...@viviotech.net>]

Hi Shawn,

My apologies, but I didn't see this message until just now.

Alan did put out a pretty simple instance of OpenBD on Jetty that makes
it pretty dang simple to use Jetty with OpenBD and VirtualHosts.
However, I realize this is not what the majority of the community was
wanting, so I've been doing my own research and time into this issue.
(Hence my revisit to this thread honestly).

So far, I've been able to come up with a method that is fairly simple
but requires a "normal" CFML developer to do some things that they are
probably not familiar with. The process would go something like this:

1) Set up mod_jk connector to apache.
2) Configure Apache VirtualHosts
3) Update tomcat server.xml file with "host" and "context" entries that
match the Apache VirtualHost entries
4) Install an instance of OpenBD for EACH VirtualHost.

This setup would be great for a Shared hosting environment, but not so
great for a single server administrator managing several different
sites. It also differs from how typical CFers are used to doing it with
CF7 and CF8. However, it does get the job done and (IMO) is simpler then
the "proxy" method when using server control panel software.

So... I've been struggling to set up OpenBD in a similar way to that of
"Jasper", the tomcat JSP processor. However, my knowledge in that area
is still pretty weak, so I've been using any extra time I've had to
learn what I can on how that works.

I've also considered just making Jetty the default engine for the
installer, but I like the popularity of Tomcat in that most server
control panels come with a Tomcat management function. So.. if I can get
it to work with Tomcat... then we're golden.

I'll be keeping the OpenBD mailing list updated if I ever figure
something out that's production worthy. (Even if it does make Jetty the
default engine).

HTH

Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
Open BlueDragon Steering Committee
Adobe Solution Provider


Shawn_Usry wrote:
> Hi Jordan - 
> 
> Was just following this thread and I'm wondering if there's an update on the
> Open BD - httpd connector you elude to below?  I'm getting ready to deploy
> several OS images for development servers and wonder if I need to stick with
> CF or if I can make the plunge to OBD!
> 
> Thanks-
> 
> 
> Jordan Michaels wrote:
>> Hi Ross,
>>
>> Alan Williamson, the chair of the OpenBlueDragon Steering Committee has
>> stated that he will blog about how to set up OpenBD in a way that most
>> CFML developers are familiar with very soon. (I've been pestering him
>> about it as well - since I haven't been able to get OpenBD/Tomcat to
>> work how I want it to either.)
>>
>> When he does, I will be releasing a Linux installer that should automate
>> *most* of the installation process. OpenBD users still may have to get
>> their hands dirty and modify some config files when setting up their
>> sites, but the basic install should be covered. I'll automate as much as
>> I can.
>>
>> The installer will support CentOS to start with and branch out to other
>> distros as I have time to adapt the installer to them.
>>
>> FYI
>>
>> Warm regards,
>> Jordan Michaels
>> Vivio Technologies
>> http://www.viviotech.net/
>> Open BlueDragon Steering Committee
>> Adobe Solution Provider
>>
>>
>> rnaheed@nvek.com wrote:
>>>>> From: rnaheed@nvek.com [mailto:rnaheed@nvek.com]
>>>>> Subject: RE: Getting OpenBlueDragon and Tomcat to traverse directories
>>>>> I thought the use of handlers (JKMount and JKUnMount) would
>>>>> direct the requests properly.
>>>> I believe that if you're very, very careful, you can get away with it,
>>>> but
>>>> your risk factor goes way up.
>>>>
>>>>> What if I plan on having only one webapp, OpenBlueDragon?
>>>> The directory (or war file) that contains the webapp should be named
>>>> ROOT
>>>> (case sensitive), and be placed immediately under whatever directory the
>>>> <Host> appBase attribute points to.  In your case, that would be:
>>>>   /var/www/html/mysite/ROOT
>>>> or
>>>>   /var/www/html/mysite/ROOT.war
>>>>
>>> I tried this and it seems to work, kinda.  It forces everything that's
>>> handled by Tomcat to be rooted at /var/www/html/mysite/ROOT, while
>>> everything else that's not (HTML, JPEG, etc.) is rooted under
>>> /var/www/html/mysite.  I wish they could both point to the same
>>> directory,
>>> though.
>>>
>>> Ross
>>>
>>>>  - Chuck
>>>>
>>>>
>>>> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
>>>> MATERIAL and is thus for use only by the intended recipient. If you
>>>> received this in error, please contact the sender and delete the e-mail
>>>> and its attachments from all computers.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To start a new topic, e-mail: users@tomcat.apache.org
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>> --
>>>> This message has been scanned for viruses and
>>>> dangerous content by MailScanner, and is
>>>> believed to be clean.
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
> 

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org