ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Martin <>
Subject Read / write files inside jar
Date Wed, 08 Oct 2003 09:21:51 GMT

EJB and other J2EE components (usually jared) use xml file as configuration
standards (pool size, cache size, ...).

We would like to be able to retrieve (store) and modify these configuration
files, J2EE server being offline. In other terms, it would be an offline
configuration, with a storage possibility (reuse the same configurations for
an other server).

This idea becomes harder when one think that jar (EJB), war (Web Apps) and
rar (Connectors) can themselves be packaged inside an ear (Enterprise
Archive) file.

The solution I have for now is to extract those xml files and correponding
templates, reconfigure them using a property file and <copy> and reinsert
them into the *ar files. I am not sure it is that easy...

Does anyone have an idea on how to do this simply with ant?

Thank you,


Confidentiality Notice: The information contained in this e-mail message is
intended only for the personal and confidential use of the recipient(s)
named above. If the reader of this message is not the intended recipient or
an agent responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is strictly
prohibited. If you have received this communication in error, please notify
us immediately by e-mail, and delete the original message. 

Message confidentiel : Les informations contenues dans ce message sont
destinees a un usage personnel et confidentiel du destinataire indique
ci-dessus. Si le lecteur de ce message n'est pas le destinataire prevu, ou
n'est pas une personne en charge de le delivrer au destinataire voulu, vous
etes par la presente informe que vous avez recu ce document par erreur, et
que tout examen, transmission, distribution ou copie de ce message est
totalement interdit. Si vous avez recu cette communication par erreur, nous
vous remercions de bien vouloir nous avertir immediatement par e-mail et de
detruire le message d'origine.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message