How to generate a site.xml at run time?

[Angeshwar Deepak <an...@yahoo.com>]

Hi,

I would like to know if a site.xml file can be
generated at run time. i.e. I will be nowing the label
name only after the entire build process. So I cannot
type before hand as

<about label="Juna">
<level2 label="Component">
....
....
</level2>

but rather I will know the directory name 'Component'
only after the build process. So can this name 
'Component' be passed as a property name from the
build file to the site.xml file. Something like
${component}, whose value will be known after the
build process.

I had asked the same question number of times, but
could not get any solution. Any suggestion reg this
will be great.

bye,
with regards,
Deepak.


		
_______________________________
Do you Yahoo!?
Win 1 of 4,000 free domain names from Yahoo! Enter now.
http://promotions.yahoo.com/goldrush

Re: How to generate a site.xml at run time?

[Angeshwar Deepak <an...@yahoo.com>]

Hi,

I did find a solution.
All I had to do was put a for loop and echo inside the
build file. like

<for param="sitecomponent"
list="${report.componentlist}">
<sequential>
<echo file="${site}" append="true"><![CDATA[
<level2 label="@{sitecomponent}">
...
...
</level2>
]]></echo>
</sequential>
</for>
<echo file="${site}" append="true"><![CDATA[
	</about>
.....
.....
</site>]]>
</echo>

where ${site} is the default location where i want to
create my site.xml.
and ${sitecomponent} holds the label values for which
directories will be generated. the loop runs until all
the directory names listed in the list are created in
the site.xml
this way a site.xml will be generated during run time.
and it solves my problem.

thanks anyway.
with regards,
Deepak.


--- Dave Brondsema <da...@brondsema.net> wrote:

> On Wed, 25 Aug 2004, Angeshwar Deepak wrote:
> 
> > Hi,
> >
> > I would like to know if a site.xml file can be
> > generated at run time. i.e. I will be nowing the
> label
> > name only after the entire build process. So I
> cannot
> > type before hand as
> >
> > <about label="Juna">
> > <level2 label="Component">
> > ....
> > ....
> > </level2>
> >
> > but rather I will know the directory name
> 'Component'
> > only after the build process. So can this name
> > 'Component' be passed as a property name from the
> > build file to the site.xml file. Something like
> > ${component}, whose value will be known after the
> > build process.
> >
> > I had asked the same question number of times, but
> > could not get any solution. Any suggestion reg
> this
> > will be great.
> >
> 
> Angeshwar,
> 
> We've read your question several times.  Posting it
> over and over is not
> going to get any more response than you've already
> recieved.  Have you
> tried my previous suggestions
>
(http://issues.apache.org/eyebrowse/ReadMsg?listName=user@forrest.apache.org&msgNo=455)?
> 
> I suggest taking a step back and looking at the
> bigger problem you are
> trying to solve.  Is this the only way to achieve
> what you want?
> 
> 
> -- 
> Dave Brondsema : dave@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
> http://csx.calvin.edu : student org
> 



		
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Re: How to generate a site.xml at run time?

[Dave Brondsema <da...@brondsema.net>]

On Wed, 25 Aug 2004, Angeshwar Deepak wrote:

> Hi,
>
> I would like to know if a site.xml file can be
> generated at run time. i.e. I will be nowing the label
> name only after the entire build process. So I cannot
> type before hand as
>
> <about label="Juna">
> <level2 label="Component">
> ....
> ....
> </level2>
>
> but rather I will know the directory name 'Component'
> only after the build process. So can this name
> 'Component' be passed as a property name from the
> build file to the site.xml file. Something like
> ${component}, whose value will be known after the
> build process.
>
> I had asked the same question number of times, but
> could not get any solution. Any suggestion reg this
> will be great.
>

Angeshwar,

We've read your question several times.  Posting it over and over is not
going to get any more response than you've already recieved.  Have you
tried my previous suggestions
(http://issues.apache.org/eyebrowse/ReadMsg?listName=user@forrest.apache.org&msgNo=455)?

I suggest taking a step back and looking at the bigger problem you are
trying to solve.  Is this the only way to achieve what you want?


-- 
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org