Hi Jordan,

Ok, so my install looks like

c:\openbd\tomcat\webapps

and I see 3 app folders in the webapps directory

host-manager
manager
ROOT

With jetty, I had both the WEB-INF folder and Bluedragon folder in my
webapp's folder

c:\openbd\tomcat\webapps\myapp\WEB-INF
c:\openbd\tomcat\webapps\myapp\Bluedragon

The WEB-INF folder of the jetty install has contents

myapp\web-inf\bin
myapp\web-inf\bluedragon
myapp\web-inf\classes
myapp\web-inf\customtags
myapp\web-inf\lib
myapp\web-inf\webresources
myapp\web-inf\web.xml


Now.. looking at the webapps\root folder

it appears that the web-inf folder in the root folder only has the web.xml
file, and not the other folders. I assume this is because in this install,
OpenBD is a common class, and the adminapi, administrator, jars and scripts
folders are not needed for each webapp, and are found in the main c:\openbd
folder. So for my new context, I don't need anything but the web.xml file,
correct? And I only need that if I'm going to have web.xml settings that are
custom to that context.

Correct?

Now, looking at the jetty install again, in my context, The BlueDragon
Folder has contents

myapp\bluedragon\adminapi
myapp\bluedragon\administrator
myapp\bluedragon\jars
myapp\bluedragon\scripts

Which is the same as the Root folder found on the tomcat install.

The admin console is specific for each context, correct?

Meaning, if I have two tomcat context's.. website1.com and website2.com,
each would have, or could have, it's own bluedragon webadmin. That's true,
right? So if I configure a new context, and another one already has a bunch
of datasources setup, etc. those won't carry over to the new context.

Just trying to understand how everything connects together.

-- 
Open BlueDragon Public Mailing List
 http://www.openbluedragon.org/   http://twitter.com/OpenBlueDragon
 online manual: http://www.openbluedragon.org/manual/

 mailing list - http://groups.google.com/group/openbd?hl=en

Reply via email to