> Ok, I have more clues. Here's what I'm trying to do:
>
> <deploymentdescriptor validatexml="true"
> destdir="${build.dir}/${site}">
> <configParam name="web.security.mode" value="basic"/>
> </deploymentdescriptor>
>
> And in web-security.xml I'm using the config parameter to control
which
> authentication mode is enabled. BASIC is nice for Cactus tests, but
> sucks for production sites, so thats one of the reasons for doing
this.
>
> I thought perhaps the dots in my parameter name might be causing the
> problem, and sure enough as soon as I changed it to name="security" it
> worked.
>
> Is there a reason we don't allow dots in configuration parameter
names?
> I'll have to dig into the code to see where this is happening, but
it
> seems unnecessary for us to be stripping the name, right?
Yes there is a reason. Config params have scope. You may have a security
param in webdoclet and another one for its deploymentdescriptor subtask,
or another security config param in another subtask. Now let's say you
want to get the value of the security param in your template file. Which
one should be picked? XDoclet searches for the param in the active
subtask, if not found there then search the webdoclet task. To let it
know exactly which one to use you can prefix it with the subtask name:
deploymentdescriptor.security for example, or even
anothersubtask.security.
But anyway I think first of all ConfigParamHandler should search for the
raw "web.security.mode" param in the active subtask and then try to
search for dots.
Ara
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
