I could be wrong but i think Mat and i run very similar setups. by 100% self contained means each CFML application has all the CFML files it needs to work correctly. Which means each project has all the frameworks packaged up in the project then uses application specific mappings. If you have concern about the frameworks being access by the web you can do what we do which is put all the frameworks into a frameworks directory and add an Application.cfm in that directory with <cfabort /> that will prevent any of those files from being web accessible, just make sure if you want something in those sub directories to be web accessible to have an application.cfm(cfc) in that folder...
I also take the approach of deploying each of my projects to my JEE container, instead of altering servelt container mappings etc (that just seems dirty to me). I've made a template eclipse project available for anyone to use http://svn.cfinnovate.com/trunk/eclipsetemplate/ Feel free to check it out and use it. The build is simple alter the build.properties to the proper deployment root then drop in all the different instances you want into _build/deploy to deploy to the different instances you have deployed on your app server/servlet container. I add an openbd, railo and coldfusion8 properties file as those are what I use locally. Adam On Fri, May 22, 2009 at 11:42 AM, Matthew Woodward <[email protected]>wrote: > Robert Capps wrote: > >> So I guess my question is using this architecture with the J2EE >> container will not work because when I access localhost I really have >> to call localhost/web/ and then localhost/frameworks is also available >> in the browser. How do you set up access to your frameworks? >> > > I treat everything as a 100% self-contained project, meaning each project > has its own copy of all the files it needs, including frameworks. I've found > that the benefits of doing things this way far outweigh any concerns about > duplicate files, versions of frameworks, etc. because then I know my apps > are entirely self-contained and I'm not going to run into any issues with > someone changing a mapping, upgrading a framework, etc. and breaking my > apps. > > The other thing I like about this approach is that it's much cleaner and > simpler in my opinion, because you don't even have to worry about mappings > and aliases to resources outside your application. > > Happy to clarify further if this isn't making sense. > > -- > Matt Woodward > [email protected] > http://www.mattwoodward.com/blog > > Please do not send me proprietary file formats such as Word, PowerPoint, > etc. as attachments. > http://www.gnu.org/philosophy/no-word-attachments.html > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
