You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by ch...@apache.org on 2004/04/26 16:25:19 UTC
svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Author: cheche
Date: Mon Apr 26 07:25:18 2004
New Revision: 10285
Modified:
xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
Log:
Use the transformed skinconf so avoid the entity resolution for document()
Modified: xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
==============================================================================
--- xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf (original)
+++ xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf Mon Apr 26 07:25:18 2004
@@ -189,7 +189,7 @@
<values>
<skin>@skin@</skin>
<!--FIXME: hard code values -->
- <skinconf>skinconf.xml</skinconf>
+ <skinconf>@project.home@/build/webapp/skinconf.xml</skinconf>
<doc>@project.home@/@project.content-dir@/</doc>
<content>@project.home@/@project.raw-content-dir@/</content>
<content.xdocs>@project.home@/@project.xdocs-dir@/</content.xdocs>
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Juan Jose Pablos <ch...@che-che.com>.
Nicola Ken Barozzi escribió:
>> Juan Jose Pablos wrote:
>>> Nicola Ken Barozzi escribió:
>>> Ah, ok. Question: why do we need to load it as xmlproperty?
>>
>>
>> So we can use them on ant build script.
>
>
> Ok, I wrote the XmlProperty task, so I know this :-PPP
>
> The question is: what do we use it for in the ant build?
>
for the validate-site target and to decide if lucene shoud create a
index or not.
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Juan Jose Pablos wrote:
> Nicola Ken Barozzi escribió:
>
>> Juan Jose Pablos wrote:
>>
>>> This file will be transformer and copied to the context (build/webapp).
>>>
>>> This output has not got any DTD, so I can be loaded by xmlproperty or
>>> by the document() function, or it can extended other values for
>>> non-default features.
>>
>> Ah, ok. Question: why do we need to load it as xmlproperty?
>
> So we can use them on ant build script.
Ok, I wrote the XmlProperty task, so I know this :-PPP
The question is: what do we use it for in the ant build?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Juan Jose Pablos <ch...@che-che.com>.
Nicola Ken Barozzi escribió:
> Juan Jose Pablos wrote:
>> This file will be transformer and copied to the context (build/webapp).
>>
>> This output has not got any DTD, so I can be loaded by xmlproperty or
>> by the document() function, or it can extended other values for
>> non-default features.
>
>
> Ah, ok. Question: why do we need to load it as xmlproperty?
>
So we can use them on ant build script.
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Juan Jose Pablos wrote:
>
> Nicola Ken Barozzi escribió:
>
>>
>> Could you kindly explain this commit? :-)
>>
>
> Sure my Friend....
>
> The idea I have got about skinconf is this one:
>
> on a normal project you have src/documentation/skinconf.xml
>
> This file will be transformer and copied to the context (build/webapp).
>
> This output has not got any DTD, so I can be loaded by xmlproperty or by
> the document() function, or it can extended other values for
> non-default features.
Ah, ok. Question: why do we need to load it as xmlproperty?
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Juan Jose Pablos <ch...@che-che.com>.
Nicola Ken Barozzi escribió:
>
> Could you kindly explain this commit? :-)
>
Sure my Friend....
The idea I have got about skinconf is this one:
on a normal project you have src/documentation/skinconf.xml
This file will be transformer and copied to the context (build/webapp).
This output has not got any DTD, so I can be loaded by xmlproperty or by
the document() function, or it can extended other values for
non-default features.
Before that commit the skinconf element was pointed to the source
(src/documentation/skinconf.xml) so we could not see the transformation.
I changed that to skinconf.xml as it was relative to the cocoon context,
but when that is used by the document () function., the path is relative
to the stylesheet.
I have just updated to use project.webapp
Cheers,
Cheche
> On my branch I put @project.home@/@project.skinconf@ in that value (that
> seems to work), and I don't understand the below path...
>
> TIA
>
> cheche@apache.org wrote:
>
>> Author: cheche
>> Date: Mon Apr 26 07:25:18 2004
>> New Revision: 10285
>>
>> Modified:
>> xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
>> Log:
>> Use the transformed skinconf so avoid the entity resolution for
>> document()
>>
>>
>> Modified: xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
>> ==============================================================================
>>
>> --- xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf (original)
>> +++ xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf Mon Apr
>> 26 07:25:18 2004
>> @@ -189,7 +189,7 @@
>> <values>
>> <skin>@skin@</skin>
>> <!--FIXME: hard code values --> -
>> <skinconf>skinconf.xml</skinconf> +
>> <skinconf>@project.home@/build/webapp/skinconf.xml</skinconf>
>> <doc>@project.home@/@project.content-dir@/</doc>
>> <content>@project.home@/@project.raw-content-dir@/</content>
>>
>> <content.xdocs>@project.home@/@project.xdocs-dir@/</content.xdocs>
>>
>
>
Re: svn commit: rev 10285 - xml/forrest/trunk/src/core/context/WEB-INF
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Could you kindly explain this commit? :-)
On my branch I put @project.home@/@project.skinconf@ in that value (that
seems to work), and I don't understand the below path...
TIA
cheche@apache.org wrote:
> Author: cheche
> Date: Mon Apr 26 07:25:18 2004
> New Revision: 10285
>
> Modified:
> xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
> Log:
> Use the transformed skinconf so avoid the entity resolution for document()
>
>
> Modified: xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf
> ==============================================================================
> --- xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf (original)
> +++ xml/forrest/trunk/src/core/context/WEB-INF/cocoon.xconf Mon Apr 26 07:25:18 2004
> @@ -189,7 +189,7 @@
> <values>
> <skin>@skin@</skin>
> <!--FIXME: hard code values -->
> - <skinconf>skinconf.xml</skinconf>
> + <skinconf>@project.home@/build/webapp/skinconf.xml</skinconf>
> <doc>@project.home@/@project.content-dir@/</doc>
> <content>@project.home@/@project.raw-content-dir@/</content>
> <content.xdocs>@project.home@/@project.xdocs-dir@/</content.xdocs>
>
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------