If I were to want to deliver a complete application, involving EJBs, JSPs and various other bits and pieces (HTML, XSLT) as a package, what would you recommend? To give a bit of context: I already have a protoype application based on the jboss-2.0-FINAL and tomcat-3.2-b7 download. I bundle the EJBs, JSPs etc into an EAR, and that works more-or-less fine. I would be very keen on open-ended disussion around this topic, but specific issues that have occurred to me so far are: Using an EAR to deploy puts extra steps into trivial customisations, e.g. editing the HTML in the JSPs and XSLTs. Stopping JBoss (apparently necessary on Win2K), bundling into an EAR, copying the EAR, and restarting JBoss. Not much for a techie perhaps but it will get in the way of the more creative types who may well be doing these customisations. I have seen "directory deployment" mentioned a few times on this list, which may help the customisation issue, but I haven't found any definitive mention of which versions this works in, and where you need to put the directories and files. Another way of getting around this would of course to deploy the JSPs and XSLT on a separate Servlet engine (under Apache for example). But then that is another thing for the user to administer. I would like this to be as straightforward as possible. Finally, talking about Apache, what is all this about JBoss-Tomcat-Apache integration? I have seen a lot about problems, and how to do it, but what does it achieve? Would it help me? How would the average webmaster react to the idea that to run my application in a supported way he would need to integrate his Apache with JBoss-Tomcat? Many thanks for your attention, and looking forward to your replies. Steve Slatcher _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
