RE: Newbie: Suggestions for development environment
> >What is the best practice for this that allows the most hassle-free > deployment with the > >least opportunity for breaking the webapp in moving it from local > >machine > to host machine? I use the main Cocoon sitemap as a kind of 'switchboard', without having any of my site code within it. I then have a sub-sitemap for a site which contains all of the code specific to that site. That sitemap does not need to be within the tomcat/webapps/cocoon folder, it can be anywhere. I then keep all of my XML, XSL, etc in the same folder (or in xml, xsl, etc subfolders of..) as the sub-sitemap. That means, when I want to deploy a site, all I have to do is copy that folder with its sitemap and sub-folders, and update the root sitemap to mount the sub- sitemap. Works well for me. As to minimal build, there has been a lot of work going into this recently, but all of this work has gone into the latest (not-yet-released) Cocoon 2.1. You can edit a file excluding the bits you don't want, and then run the build process which can prepare you a war file ready for deployment with just the features you want. For 2.0.4 you need to use the methods described on the wiki. Regards, Upayavira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Newbie: Suggestions for development environment
I am also a Newbie but, having the same outlook as yourself I think I understand what you want... >I have created multiple Cocoon instances, but am not sure this is the best way to do it. The >reason I say this, is that when I access localhost/cocoon I see the directory page; but when I >access localhost/cocoon_dev (the second instance, set up with intentions of creating a Cocoon >instance with minimal overhead for my webapp) I get a 404 error. This tells me that something is >amiss (I think). I think you are looking for a so called "minimal" install. This includes the requirements of Cocoon but does not include all the other stuff. See the http://wiki.cocoondev.org/ (thanks to Geoff Howard) site for more info. I found the page rather hidden away being a link under "Main, For Beginners, Set up cocoon in 15 minutes, [scroll down] MinimalCocoonConfiguration" so here's a direct link: http://wiki.cocoondev.org/Wiki.jsp?page=MinimalCocoonConfiguration. However, as an ignorant novice I noted that this tutorial didn't go quite far enough: having deleted all the pipelines you have to put at least one back and a corresponding file (of course) to test whether it works or you'll just get an error! >Another method I have read says that the way to do it is to create a webapp directory within >the cocoon/mount directory and use a subsitemap. >What is the best practice for this that allows the most hassle-free deployment with the >least opportunity for breaking the webapp in moving it from local machine to host machine? Don't know myself yet sorry! With my limited experience it seems that sub apps are nice and portable but may have app specific (rather than cocoon specific) requirements (e.g. db connection pools, logicsheets) that are set in the main app so it kinda depends what you are doing I guess. HTH(!) Phil Coultard --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.465 / Virus Database: 263 - Release Date: 25/03/03 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Newbie: Suggestions for development environment
I'm not sure I understand what you want to achieve. To have two cocoons on tomcat, you can simply put two war files with different names. For example, put cocoon.war and its copy under name cocoon-dev.war in webapps directory. So, you'll have two cocoons: http://localhost:8080/cocoon/ and http://localhost:8080/cocoon-dev/. When I play with settings, sometimes, I simply copy extracted cocoon directory in Tomcat's webapps folder into a different name, like /webapps/cocoon1. There was also a thread on "minimal" cocoon deployment, maybe that's what you need to search for in this mailing list. -Original Message-From: Joe Williams [mailto:[EMAIL PROTECTED]Sent: Saturday, April 05, 2003 11:02 AMTo: [EMAIL PROTECTED]Subject: Newbie: Suggestions for development environment I have created multiple Cocoon instances, but am not sure this is the best way to do it. The reason I say this, is that when I access localhost/cocoon I see the directory page; but when I access localhost/cocoon_dev (the second instance, set up with intentions of creating a Cocoon instance with minimal overhead for my webapp) I get a 404 error. This tells me that something is amiss (I think).
Newbie: Suggestions for development environment
I am a technical writer learning to use Cocoon. I have read the FAQs and done Google searches for an answer to this question (which doesn't mean that it is not out there somewhere, of course). I have installed Cocoon and experimented with it somewhat successfully and would like to begin building and deploying a webapp that will create dynamic documentation. I am creating my project on a Linux box on a home network, and will deploy to a Web server on the Internet. I would like to keep the full Cocoon installation (2.0.3 on Tomcat 4.1.18) on my home box, but don't particularly want to burden my hosting provider with all of the samples, documentation, and other overhead of the full install. I am confused after reading about setting up a development environment and deploying webapps. I have created multiple Cocoon instances, but am not sure this is the best way to do it. The reason I say this, is that when I access localhost/cocoon I see the directory page; but when I access localhost/cocoon_dev (the second instance, set up with intentions of creating a Cocoon instance with minimal overhead for my webapp) I get a 404 error. This tells me that something is amiss (I think). Another method I have read says that the way to do it is to create a webapp directory within the cocoon/mount directory and use a subsitemap. OK. But when I deploy from my local (home network) machine to my provider's machine (on the Internet) I will have to create a new sitemap that references whatever components the webapp requires. Maybe this is no big deal to experienced Cocoon developers/users but it seems like an opportunity for a lot of confusion and extra work. What is the best practice for this that allows the most hassle-free deployment with the least opportunity for breaking the webapp in moving it from local machine to host machine? You may reply off-list if you like and I will post whatever works for other newbies. As always, let me know if I have left out information that would be helpful in understanding the question, and I will provide it. Or, if there is a link that explains this, that would be fine, as well. Thanks. Joe
