A bug seems to have been introduced in XIncludes in going from 2.1.7 to 2.1.8.
They seem fine when used in this form:
http://www.w3.org/2001/XInclude"; parse="xml"
href="{$common-content-folder}/banner.xml"/>
But there is a problem when used in this form:
http://www.w3.org/2
This looks very similar to
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=COCOON-1489 which
was supposedly checked in for 2.1.8. Perhaps that patch fixed one
situation but broke another?
> A bug seems to have been introduced in XIncludes in going from 2.1.7 to
> 2.1.8.
>
> They seem fine
On Wednesday 04 January 2006 11:48, Jason Johnston wrote:
>
> This looks very similar to
> http://issues.apache.org/jira/secure/ViewIssue.jspa?key=COCOON-1489 which
> was supposedly checked in for 2.1.8. Perhaps that patch fixed one
> situation but broke another?
This is the same issue as in the
On 04.01.2006 20:30, Pasha Minallah wrote:
This looks very similar to
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=COCOON-1489 which
was supposedly checked in for 2.1.8. Perhaps that patch fixed one
situation but broke another?
This is the same issue as in the link. The website se
> On Wednesday 04 January 2006 11:48, Jason Johnston wrote:
>>
>> This looks very similar to
>> http://issues.apache.org/jira/secure/ViewIssue.jspa?key=COCOON-1489
>> which
>> was supposedly checked in for 2.1.8. Perhaps that patch fixed one
>> situation but broke another?
>
> This is the same iss
Jason Johnston wrote:
On Wednesday 04 January 2006 11:48, Jason Johnston wrote:
This looks very similar to
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=COCOON-1489
which
was supposedly checked in for 2.1.8. Perhaps that patch fixed one
situation but broke another?
This
