Re: [Soaplab-users] undeployment

[Sebastien M. <Seb...@un...>]

Hi Mahmut,

it is exactly what I need.
It works perfectly and split Soaplab default services from our home made 
services.

Thanks
See you at Uppsala for EMBRACE meeting

P.S.: 	In http://soaplab.sourceforge.net/soaplab2/EmbossNotes.html
	it seems that build/run/run-batch-test should be replaced by
	build/run/run-batch-client

> Hi Sebastien,
> 
> You can move your ACD files to a new folder, for example
> src/etc/acd/project1/ folder under your soaplab2 home directory.
> 
> Then you can call ant similar to the following example to translate your
> ACD files into the XML form Soaplab requires.
> 
>   > ant _gen -Dacd.dir=src/etc/acd/project1/ -Dsl=Project1.xml
> 
> You should remember to disable default sowa applications
> (OtherApplications.xml) in your soaplab.properties file and instead
> should add the Project1.xml file to the applist property.
> 
>   applist = ${metadata.dir}/EBIApplications.xml
> 
> 
> As a side note.
> Instead of modifying the soaplab.properties.template file you may 
> use a customised soaplab.properties file that can be used directly in
> your Soaplab web applications. If in your build.properties file you set
> the my.soaplab.properties property to your customised soaplab.properties
> file, Soaplab will not generate the runtime soaplab.properties file from
> the template but will instead use your customised soaplab.properties
> file.
> 
>   my.soaplab.properties = my.customised.soaplab.properties.file
> 
> However, Soaplab still applies the following transformations when
> copying your customised soaplab.properties file to the class
> directories.
> 
>         <filter token="PROJECT_HOME" value="${basedir.unix}"/>
>         <filter token="METADATA_DIR"
> value="$${base.dir}/metadata/generated"/>
>         <filter token="RUNTIME_DIR"  value="$${base.dir}/_R_"/>
>         <filter token="SCRIPTS_DIR"  value="$${base.dir}/run"/>
>         <filter token="TOMCAT_HOST"  value="${tomcat.host}"/>
>         <filter token="TOMCAT_PORT"  value="${tomcat.port}"/>
> 
> Regards,
> Mahmut
> 
> 
>> I would like to undeploy testing services from my soaplab2 installation.
>>
>> It is quite easy for Gowlab Applications because there is only to 
>> comment the right line in soaplab.properties.template
>>
>>
>> It is more difficult for other testing and examples services (in sowa 
>> and testing directories) because our own applications are located in the 
>> sowa directory.
>> I cannot comment the Other Applications line in 
>> soaplab.properties.template because this will disable our applications.
>>
>> If I remove ACD files for these applications, a CVS update will 
>> re-create them.
>>
>> I have tried to use gen.disabled.apps in build.properties but this 
>> activates disabled applications defined in xmls/emboss.xml
>>
>>
>> We use a script to update soaplab2 source, then to build metadata, then 
>> to deploy soaplab war and to restart tomcat.
>>
>>
>> So, is there a way to disable testing and examples services without 
>> manually editing application list files after every update or restart ?
>> Thanks

-- 
Sébastien Moretti
SIB EMBnet, Quartier Sorge - Genopode
CH-1015 Lausanne, Switzerland
Tel.: +41 (21) 692 4056/4221
http://ch.embnet.org/  http://myhits.vital-it.ch/