ObjectWeb Consortium
Search ObjectWeb Mail Archive: 

Advanced Search - Powered by Google


Mail Archive Home | enhydra List | April 2004 Index

<--  Date Index  --> <--  Thread Index  -->

Re: Re: [enhydra] XMLC compilation with ANT


Hello Yves,
 
First: I am sory that I was not able to contact You sooner.
 
Second: Please, use Enhydra mailing list to represent Your problems and comunicate with other members. We have pretty active comunity and it will be shame not to use it :)
 
Now about Your problem:
How to integrate Your enhydra application in Enhydra runtime installation?!
You can try to do it by using Enhydra Administration application (Enhydra Adnmin application - application distributed with runtime version). Or, do it manualy by defining another application in multiserver.conf file, placing configuration file of Your enhydra application in Enhydras application configuration directory (defined as Server.ConfDir parameter in multiserver.conf file) and configuring loger in log4j.xml file.
We produce same structure for Enhydra runtime version as we do for Enhydra developer version (so technique is the same).
 
Best Regards,
        Slobodan Vujasinovic
     Enhydra Development Team
----- Original Message -----
Sent: Sunday, April 18, 2004 20:46
Subject: Fwd: Re: [enhydra] XMLC compilation with ANT

Thank you Slobodan... it works great now ! XMLC just compile the modified html !
A short question : do you know how the run-time version of enhydra works without the complete installation of enhydra 5.1 to simply run an enhydra application ?
 
Best regards from Switzerland
Yves


Slobodan Vujasinovic <slobodan@xxxxxxxxxxxxx> wrote:
De: "Slobodan Vujasinovic"
À:
Objet: Re: [enhydra] XMLC compilation with ANT
Date: Fri, 16 Apr 2004 13:51:09 +0200

Since You didn't gave some more specific informations about concrete problem I will have to sopouse  that Your xmlc task looks, something, like this

 

    <xmlc srcdir="${xmlcresources.dir}"
        sourceout="${dir.xmlc}"
        packagename="${project.package}.presentation"
        options="options.xmlc"
        compile="true"
        includes="**/*.html">
        <arg value="-d" />
        <arg value="${dir.classes}" />
    </xmlc>

 

If attribute "compile" is set on true then "xmlc" generation process will be executed every time. If You set compile attribute value to false target will generate java source files that will not be compiled (except if You include them in Your own compilation process).

 

My suggestion (for quick solution) would be to change "xmlc" target to

 

<xmlc srcdir="${xmlcresources.dir}"
      sourceout="${dir.src}"
      packagename="${project.package}.presentation"
      options="options.xmlc"
      includes="**/*.html">
  </xmlc>

 

Where ${dir.src} is directory where Your source files are stored (source directory of "javac" compilation target).

 

NOTE: Attribute "compile" by default is set to false and these will generate java source files in Your source directory which will remain there until You delete it manually or override them with new ones ("xmlc" target will generate them only for changed "html" files). These java files will be (since they are stored in "source" directory) compiled along with the rest of Your code. 

 

Best Regards,

        Slobodan Vujasinovic

     Enhydra Development Team


Yahoo! Mail : votre e-mail personnel et gratuit qui vous suit partout !
Créez votre Yahoo! Mail

Dialoguez en direct avec vos amis grâce à Yahoo! Messenger !


<--  Date Index  --> <--  Thread Index  -->

Reply via email to:

Powered by MHonArc.

Copyright © 1999-2005, ObjectWeb Consortium | contact | webmaster.