Couple newbie questions

Hi,
I am using FMPP w/ Ant to create a installer for our application.  
Working pretty good so far but have a couple issues:

1) We've using the ant XMLProperty to create Ant properties based on XML 
config files.  This is great for us, as we have lots of config items and 
grouping them hierarchically is convienient.  The problem, of course, is 
that ant properties of the form 'parent.property' are a problem for 
FMPP/Freemarker since ${parent.property} tries to resolve 'parent' then 
'property' as a child.  I read the FM docs regarding the 
${.vars["parent.property"]} syntax to get around the problem.  That 
works but is syntactically clunky.  Is there a cleaner way to do this?

2) Some of the files that we are configuring are Unix shell scripts.  In 
some cases the ${SHELL_VAR} form for shell variables is used, and the 
FMPP processing throws an error when it hits one of these as they are 
not defined.  This becomes a tricky problem as it's nice to know from an 
FMPP perspective that I've hit an undefined variable reference, but in 
this case I'd like to maybe log, the undefined var and keep processing.  
Or is there some way to define an alternate variable resolution syntax 
for FMPP/Freemarker?  This is a Java web application were building so we 
are going to run into the same problem with Java Expression Language 
variables that use the ${} form as well.



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl