On 8/22/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > ant elder wrote: > > So not much consensus on what to do with this yet. The binary distro is > > currently coming in at 107MB. Of that the following 5 samples and demo's > > account for about 50MB: > > > > demo-allert-aggregator.war > > demo-mortgage-creditcheck.war > > sample-helloworld-ws-sdo-webapp.war > > sample-helloworld-ws-service-webapp.war > > sample-calculator-webapp-ws.war > > > > Should we delete these, keep these, delete some of these, keep but don't > > > distribute pre-built artifacts? The three samples are quite similar so i > > think at least one maybe two of them could be removed for this release > and > > then look at just having simple SCA contribution jar's for the samples > and > > demo's for 1.0. (at least one of these was contributed by a user so we > > should try to keep that one) > > > > ...ant > > > > > > This is obviously an issue that we need to fix now. I have two questions: > > - Why are they so big? isn't that a problem in the samples themselves? > > - If all WARs hosting Tuscany apps are going to be so big, isn't that > going to be a problem for a our users as soon as they create two or > three of this WARs? > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > The previous posts to this thread have established that there are concerns with
1 - what is in the war that is build from these samples - currently all of the tuscany jars required 2 - the mechanism in which web apps are built using tuscany - currently using host-webapp 2 first. Sebastien has suggested that we follow the approach outlined in the link he provided [1] Its not clear to me that this implies that the war file goes but certainly the mechansim by which servlets, jsps are connected to tuscany change. The war file might have to go to make the mvn build work but that's a slightly different issue I believe. If I understand correctly running a sample in this mode would be a two phase process. a) install tuscany support into you favourite app server host-geronimo, host-tomcat b) deploy ear, war, jars to the tuscany runtime(s) provided as part of this integration, e.g ant's hot update runtime is an example of how this could be done 1 in this case all of the runtime jars will be moved out of the sample war/jar and into the hosting adapater. That leaves just the sample files and web resources. Doing 1 is a relatively straightforward exercise of refactoring the current war into a slimmed down version. I'm still not convinced that it's a good idea to remove the webapp samples and compress everything into a small number of samples Doing 2 properly is a little more time consuming. Anyone given any thought to host-tomcat (I realize the geronimo integration is in the pipeline) or to <implementation.web>. Can we use the implementation.resource as a basis? As the document at [1] is subject to change maybe we can still use the host-webapp approach but just take ant's webapp distribution approach and separate the samples from packaging all the jars. At least that way we start to move toward the right model .I could spend a little time on this but if someone is a way down the path I don't want to repeat effort. Simon [1] http://www.osoa.org/pages/viewpage.action?pageId=3980
