for providing patches ;) I started applying them.
Just 2 minor requests: for future patches, please name them with a more
semantic name (i.e. issue55.patch would start being more useful), and you can
provide your patching code in a single file.
The XInclude Transformer needs to be integrated
!
The XInclude Transformer needs to be integrated in the sitemap
--
Key: COCOON3-55
URL: https://issues.apache.org/jira/browse/COCOON3-55
Project: Cocoon 3
Issue Type: New Feature
issue.patch for the future; about providing more than one
patch, I just thought it was useful to keep samples separated from actual code
just because maybe samples are not intended to be included in the way I
propose. Anyway, I'll follow this advice of yours as well :-)
The XInclude Transformer needs
not actually need to be modified: in the attached patched I've
just configured the XInclude transformer to work in the sitemap and I've
included in the sample.
The XInclude Transformer needs to be integrated in the sitemap
The XInclude Transformer needs to be integrated in the sitemap
--
Key: COCOON3-55
URL: https://issues.apache.org/jira/browse/COCOON3-55
Project: Cocoon 3
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz reassigned COCOON3-3:
Assignee: Reinhard Poetz (was: Cocoon Developers Team)
Provide an XInclude transformer
Patch applied, many thanks Simone!
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
Project: Cocoon 3
Issue
Simone Tripodi wrote:
Hi Guys,
do you have some spare time to review the last patch submitted on [1]?
I know it requires time...
Thanks in advance, best regards,
Unless somebody else is quicker than me, I will have a look at your
patch before I create the release.
--
Reinhard Pötz
Hi Reinhard
Very appreciated, thanks!!! :)
alles gute, auf wiedersehen!
Simo
On Fri, Dec 11, 2009 at 8:44 AM, Reinhard Pötz reinh...@apache.org wrote:
Simone Tripodi wrote:
Hi Guys,
do you have some spare time to review the last patch submitted on [1]?
I know it requires time...
Thanks in
according to our needs, so if you agree I'd add the
XInclude in the cocoon-sax module... what do you think about it? Just
let me know!
See you guys and thanks a *lot* for your help :)
Best regards
Simo
On Tue, Nov 24, 2009 at 12:16 PM, Reinhard Pötz reinh...@apache.org wrote:
Simone Tripodi
) contains a new
implementation of the XInclude processor based strictly only on SAX APIs, no
more DOM to extract elements by ids or by xpath expressions.
Like always, don't hesitate to contact me if some help or extra work is needed
to apply the patch.
Provide an XInclude transformer
Simone Tripodi wrote:
Hi Sylvain and Simone,
thank you a lot, the suggestions you provided are all very very
interesting, so I wonder now if it is possible to realize a processor
able to use at the same time the Tika way when it recognizes some kind
of paths, the XSL-on-the-fly for more complex
Hi Sylvain,
there are no words to say thank you, very very appreciated, I'll
follow your suggestions :)
A bientot
Simone
On Tue, Nov 24, 2009 at 10:21 AM, Sylvain Wallez sylv...@apache.org wrote:
Simone Tripodi wrote:
Hi Sylvain and Simone,
thank you a lot, the suggestions you provided
Hi Sylvain
Sorry but I forgot to ask you a short question in the previous email:
can the Tika code be imported/modified into Cocoon3? AFAIK it should
be allowed, but I don't know the conditions under which it can be
done.
A bientot!!!
Simo
On Tue, Nov 24, 2009 at 10:29 AM, Simone Tripodi
Simone Tripodi wrote:
Hi Sylvain
Sorry but I forgot to ask you a short question in the previous email:
can the Tika code be imported/modified into Cocoon3? AFAIK it should
be allowed, but I don't know the conditions under which it can be
done.
I don't really understand your question. Tika
Simone Tripodi wrote:
Hi Sylvain
Sorry but I forgot to ask you a short question in the previous email:
can the Tika code be imported/modified into Cocoon3?
Do you really have to modify Tika code? If so it would be best to give
back your contributions to the their project.
Since you have to
and
modifying them according to our needs, so if you agree I'd add the
XInclude in the cocoon-sax module... what do you think about it? Just
let me know!
See you guys and thanks a *lot* for your help :)
Best regards
Simo
On Tue, Nov 24, 2009 at 12:16 PM, Reinhard Pötz reinh...@apache.org wrote:
Simone
Hi Simone and Sylvain,
aren't XSLT transformers already SAX/Xpath optimized? I mean, an XSLT
containing an XPath expression and used in a SAX context, isn't already
able to resolve the XPath while keeping buffering at the minimum possible?
I can clearly remember that there has been a lot of
Simone Gianni wrote:
Hi Simone and Sylvain,
aren't XSLT transformers already SAX/Xpath optimized? I mean, an XSLT
containing an XPath expression and used in a SAX context, isn't
already able to resolve the XPath while keeping buffering at the
minimum possible?
I can clearly remember that
Hi Sylvain and Simone,
thank you a lot, the suggestions you provided are all very very
interesting, so I wonder now if it is possible to realize a processor
able to use at the same time the Tika way when it recognizes some kind
of paths, the XSL-on-the-fly for more complex cases. What do you
Hi all guys,
I'm very sorry if I don't appear frequently on the ML but since April
I've been working very hard for a customer client in Paris that don't
let me some spare time to dedicate to OS projects.
I'm writing because I'm sure the XInclude transformer I submitted time
ago could be optimized
that have
driven us away from Cocoon. Glad to see you back!
I'm writing because I'm sure the XInclude transformer I submitted time
ago could be optimized, so I'd like to ask you a little help :)
The state of the art is that, when including an entire document, it is
processed efficiently through SAX
to the xpointer recommendation and at the same time
closer with what I already did - and to older XInclude cocoon
implementations.
Thank you very much for your hints, very well appreciated :)
A bientot!
Simone
P.S. Offtopic: maybe I'm wrong, but I'm sure we met once in Tolouse, I
was one of the Asemantics
Hmmm, I guess the XPath expression is known before the parsing begins?
I remember I have done a similar thing, where a chunk had to be isolated
from a document that came by via a SAX stream, but here the xpath
expression was something like: /element1/elemen...@id=somenumber].
Theorem: any XPath
more compliant to the xpointer recommendation and at the same time
closer with what I already did - and to older XInclude cocoon
implementations.
Axiom is what will give you the better compliance, but it is a
relatively heavyweight solution compared to pure streaming. This is why
I
Jos Snellings wrote:
Hmmm, I guess the XPath expression is known before the parsing begins?
I remember I have done a similar thing, where a chunk had to be isolated
from a document that came by via a SAX stream, but here the xpath
expression was something like:
Hi Jos,
thanks for your reply, the XPath expression is already known before
parsing the document since the XInclude processor catches the xpointer
reference before including the document.
I think your solution works but I've the suspect just for a limited
subset of the XPath expressions
Hi Sylvain,
indeed, that's yet another exception I didn't think, thanks for your
clarification!!!
Bonne journée, a bientot ;)
Simo
On Mon, Nov 23, 2009 at 8:28 AM, Sylvain Wallez sylv...@apache.org wrote:
Jos Snellings wrote:
Hmmm, I guess the XPath expression is known before the parsing
Version/s: (was: 3.0.0-alpha-2)
3.0.0-alpha-1
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
[
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON3-3:
-
Component/s: (was: cocoon-pipeline)
cocoon-sax
Provide an XInclude
but the DOMUtils.stream() method is missing. Can
you please add it to your patch? Thanks!
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
: Please make sure that _all_
files that you add have the Apache License 2.0 header. Thank you very much in
advance!
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https
provided a corrupted patch.
The new patch, named XIncludeTransformerFixedAndApacheHeaders.patch fixes the
missing method, creates an XInclude unit test for JUnit4, and adds the right
header.
Sorry if I've never attached the header, but not being an Apache committer I
thought I didn't have the right
, the XInclude support
is one of the unscheduled feature for cocoon 3.0.0
The attached patch provides the porting to Cocoon3's pipeline of old XInclude
Transformer already present in previous releases; some TestCase are also
provided.
Just few notes:
- As described in http://www.w3.org/TR/xinclude/, I
[
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reinhard Poetz updated COCOON3-3:
-
Fix Version/s: 3.0.0-alpha-2
Affects Version/s: 3.0.0-alpha-2
Provide an XInclude
components to Cocoon 3 is straight
forward and in this case the best option IMO.
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
(for me, at least ;) ).
I should be able to provide an initial patch in a week
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
Provide an XInclude transformer as a PipelineComponent
--
Key: COCOON3-3
URL: https://issues.apache.org/jira/browse/COCOON3-3
Project: Cocoon 3
Issue Type: Improvement
Components
of XPointer is incomplete:
https://svn.apache.org/repos/asf/xerces/java/trunk/src/org/apache/xerces/xinclude/XIncludeHandler.java
Reading from the javadoc: Currently, this implementation has only partial
support for the XInclude specification. Specifically, it is missing support for
XPointer document
Hi Joerg,
1) This resulted in the same error when I configured the pipeline like so:
map:match pattern=simple.zip
map:generate src=simple_xi.xml/
map:transform type=xinclude/
map:serialize type=zip/
/map:match
map:match pattern
Hi Geert!
I tried the CInclude transformer... same result! The problem must be with the
ZipArchiveSerializer...
AJ
Also tried cinclude transformer?
Kind regards,
Geert
Drs. G.P.H. Josten
Consultant
Daidalos BV
Source of Innovation
Hoekeindsehof 1-4
2665 JZ Bleiswijk
Tel.:
Hi All,
I had one more idea... I tried to insert a stylesheet between the xinclude
transformer and the zip serializer, that just copied the xml tree... this
didn't do anything either (same Null Pointer Exception)... I wonder what it
could be ?
AJ
Hello All,
I'm writing some sitemap logic for handling Oasis Document Format (ODF)
files. However, I've found what looks like a bug in Cocoon-2.1.10. I get a
NullPointerException when the ZipFileSerializer is preceded by the XInclude
transformer. I constructed a very simple sitemap
On 30.05.2007 18:56, Adrien Guillon wrote:
I'm writing some sitemap logic for handling Oasis Document Format (ODF)
files. However, I've found what looks like a bug in Cocoon-2.1.10. I get a
NullPointerException when the ZipFileSerializer is preceded by the XInclude
transformer. I
Now I have two other files:
simple.xml: simpleHello/simple
simple_xi.xml:
?xml version=1.0 encoding=ISO-8859-1? zip:archive
xmlns:zip=http://apache.org/cocoon/zip-archive/1.0;
xmlns:xi=http://www.w3.org/2001/XInclude; zip:entry
name=content.xml serializer=xml
[ http://issues.apache.org/jira/browse/COCOON-1881?page=all ]
Jörg Heinicke updated COCOON-1881:
--
Component/s: - Components: Sitemap
(was: Blocks: (Undefined))
Xinclude transformer has changed behaviour with Saxon 8.7.1
Xinclude transformer has changed behaviour with Saxon 8.7.1
---
Key: COCOON-1881
URL: http://issues.apache.org/jira/browse/COCOON-1881
Project: Cocoon
Type: Bug
Components: Blocks: (Undefined)
Versions
[ http://issues.apache.org/jira/browse/COCOON-1881?page=all ]
Philip Fennell updated COCOON-1881:
---
Attachment: xinclude.tar.gz
I have enclosed the test case refered to in the description of this bug.
Xinclude transformer has changed behaviour
to 2.1.10-dev and 2.2-dev. Feel free to
reopen the bug if needed.
XInclude transformer uses href fragment rather than xpointer attribute (spec
conformance)
-
Key: COCOON-1753
URL: http
a typo which is also fixed by this
patch.
In addition, the patch fixes multiple-nested fallbacks, which did not function
before, and a JUnit testcase was added for that.
Junit tests pass successfully, and all xinclude samples function as before.
Patch is against 2.1.x branch, but would need
[ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
Antonio Gallardo reassigned COCOON-1489:
Assign To: Antonio Gallardo
[PATCH] XInclude transformer does not handle fallback correctly
with minor changes to 2.1.10-dev and
2.2-dev. Please feel free to reopen the issue if needed.
[PATCH] XInclude transformer does not handle fallback correctly
---
Key: COCOON-1489
URL: http://issues.apache.org/jira
/viewvc?view=revrevision=409912
[PATCH] XInclude transformer does not handle fallback correctly
---
Key: COCOON-1489
URL: http://issues.apache.org/jira/browse/COCOON-1489
Project: Cocoon
Type: Bug
://svn.apache.org/viewvc?view=revrevision=409920
[PATCH] XInclude transformer does not handle fallback correctly
---
Key: COCOON-1489
URL: http://issues.apache.org/jira/browse/COCOON-1489
Project: Cocoon
Type
.
XInclude transformer uses href fragment rather than xpointer attribute (spec
conformance)
-
Key: COCOON-1753
URL: http://issues.apache.org/jira/browse/COCOON-1753
Project: Cocoon
.
XInclude transformer uses href fragment rather than xpointer attribute (spec
conformance)
-
Key: COCOON-1753
URL: http://issues.apache.org/jira/browse/COCOON-1753
Project: Cocoon
[ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
David Crossley updated COCOON-1489:
---
Bugzilla Id: (was: 34325)
Other Info: [Patch available]
Description:
When using the xi:fallback element, the XInclude transformer returns
-fragments are still interpreted
but produce a WARN log message stating support will be removed in a future
release. Tested against the samples and some ad-hoc tests. Needs review.
XInclude transformer uses href fragment rather than xpointer attribute (spec
conformance
[
http://issues.apache.org/jira/browse/COCOON-1753?page=comments#action_12366586
]
Jason Johnston commented on COCOON-1753:
Also in the diff are updates to the samples changing them from using
url-fragments to xpointer attributes.
XInclude
needs some more non-trivial polishing
[PATCH] XInclude transformer does not handle fallback correctly
---
Key: COCOON-1489
URL: http://issues.apache.org/jira/browse/COCOON-1489
Project: Cocoon
Type
XInclude transformer uses href fragment rather than xpointer attribute (spec
conformance)
-
Key: COCOON-1753
URL: http://issues.apache.org/jira/browse/COCOON-1753
Project: Cocoon
[ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
Jean-Baptiste Quenot reassigned COCOON-1489:
Assign To: Jean-Baptiste Quenot (was: Cocoon Developers Team)
[PATCH] XInclude transformer does not handle fallback correctly
[ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
Antonio Gallardo reopened COCOON-1489:
--
See: http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=113639560121665w=2
This sample will faail: http://www.w3.org/TR/xinclude/#fallback-example
[EMAIL PROTECTED] wrote:
A comment has been created.
http://cocoon.zones.apache.org/daisy/legacydocs/458.html
Document ID: 458
Name: XInclude Transformer
Branch: main
Language: default
Created by: Jean-Baptiste Quenot
Created on: 11/21/05 1:23:09 PM
Visibility: public
Cacheable: yes. What
[ http://issues.apache.org/jira/browse/COCOON-599?page=all ]
Helma van der Linden reopened COCOON-599:
-
reopened just to set the resolution to fixed
XPointer implementation in XInclude Transformer is broken
[ http://issues.apache.org/jira/browse/COCOON-599?page=all ]
Helma van der Linden closed COCOON-599:
---
Resolution: Fixed
XPointer implementation in XInclude Transformer is broken
[ http://issues.apache.org/jira/browse/COCOON-879?page=all ]
Helma van der Linden reopened COCOON-879:
-
reopened just to set the resolution to fixed
Need to be able to use cinclude or xinclude to manage sitemap fragments
[ http://issues.apache.org/jira/browse/COCOON-879?page=all ]
Helma van der Linden closed COCOON-879:
---
Resolution: Fixed
Need to be able to use cinclude or xinclude to manage sitemap fragments
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=24498.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=24498.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26755.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Joachim Breitsprecher wrote:
Hi all,
I think I found a bug in Cocoon's XInclude transformer. Try this
pipeline:
map:match pattern=test
map:generate src=test.xml /
map:transform type=xinclude /
map:serialize type=xml /
/map:match
whith test.xml containing:
?xml version=1.0 encoding=utf-8
/show_bug.cgi?id=34325
Summary: [PATCH] XInclude transformer does not handle fallback
correctly
Product: Cocoon 2
Version: Current SVN 2.2
Platform: All
OS/Version: All
Status: NEW
Severity: normal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34325.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Michael Wechner wrote:
what do you mean by unbalanced output?
?xml version=1.0 encoding=ISO-8859-1?root
xmlns:xi=http://www.w3.org/2001/XInclude;
elementThis should be here if the file was not found
/xi:include
/root
Have you filed this patch yet?
yep I just did :-)
http
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34325.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34325.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hi all,
I think I found a bug in Cocoon's XInclude transformer. Try this pipeline:
map:match pattern=test
map:generate src=test.xml /
map:transform type=xinclude /
map:serialize type=xml /
/map:match
whith test.xml containing:
?xml version=1.0 encoding=utf-8 ?
root xmlns:xi=http://www.w3.org
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|Normal
/show_bug.cgi?id=26750
General XInclude sample does not work
--- Additional Comments From [EMAIL PROTECTED] 2004-02-08 11:32 ---
This fix won't help anyone ;-)
Fixed the XIncludeTransformer, a subtle change had broken it.
/show_bug.cgi?id=26750
General XInclude sample does not work
--- Additional Comments From [EMAIL PROTECTED] 2004-02-08 13:18 ---
Oh, nice, that's of course a much better fix. I didn't thought of a change in
the XIncludeTransformer and only had a possible problem in the new Xerces in mind
/show_bug.cgi?id=26750
General XInclude sample does not work
Summary: General XInclude sample does not work
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Macintosh
URL: http://localhost:/samples/aggregation/test.html
OS/Version
/show_bug.cgi?id=26755
XInclude processing failed for sample due to wrong xpointer expression
Summary: XInclude processing failed for sample due to wrong
xpointer expression
Product: Cocoon 2
Version: Current CVS 2.1
Platform: Other
/show_bug.cgi?id=26755
XInclude processing failed for sample due to wrong xpointer expression
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=26750
General XInclude sample does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PROTECTED
/show_bug.cgi?id=26755
XInclude processing failed for sample due to wrong xpointer expression
--- Additional Comments From [EMAIL PROTECTED] 2004-02-07 14:26 ---
Missed that one ...
/show_bug.cgi?id=26750
General XInclude sample does not work
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution
/show_bug.cgi?id=25016
XInclude fallback does not work, if referenced file does not exist.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED
/show_bug.cgi?id=25016
XInclude fallback does not work, if referenced file does not exist.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|VERIFIED|CLOSED
/show_bug.cgi?id=25016
XInclude fallback does not work, if referenced file does not exist.
Summary: XInclude fallback does not work, if referenced file does
not exist.
Product: Cocoon 2
Version: 2.1.3
Platform: PC
OS/Version: Windows 9x
/show_bug.cgi?id=25016
XInclude fallback does not work, if referenced file does not exist.
--- Additional Comments From [EMAIL PROTECTED] 2003-11-26 14:49 ---
Created an attachment (id=9300)
Test File cocoon-2.1.3\build\webapp\samples\aggregation\content\test.xml
/show_bug.cgi?id=25016
XInclude fallback does not work, if referenced file does not exist.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
--- Additional Comments From [EMAIL PROTECTED] 2003-11-09 20:54 ---
Yes
Say you have a file called resources.xml:
map:resources
!-- A bunch of resources I want to share in several sitemaps
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
--- Additional Comments From [EMAIL PROTECTED] 2003-11-09 23:08 ---
Sounds reasonable, but I guess it won't be implemented. This means using a
Cocoon transformer on the sitemap itself. *ouch
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
--- Additional Comments From [EMAIL PROTECTED] 2003-11-08 15:47 ---
Can you be a bit more explicite, i.e. providing use cases/samples?
/show_bug.cgi?id=24240
Generate/XInclude/CInclude from cocoon:// has wrong context
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
Summary: Need to be able to use cinclude or xinclude to
manage sitemap fragments
Product: Cocoon 2
Version: 2.1.1
Platform: Other
OS/Version
/show_bug.cgi?id=24498
Need to be able to use cinclude or xinclude to manage sitemap fragments
[EMAIL PROTECTED] changed:
What|Removed |Added
BugsThisDependsOn
/show_bug.cgi?id=24240
Generate/XInclude/CInclude from cocoon:// has wrong context
--- Additional Comments From [EMAIL PROTECTED] 2003-11-02 09:07 ---
I think this is a duplicate of bug#22377
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22377
/show_bug.cgi?id=24240
Generate/XInclude/CInclude from cocoon:// has wrong context
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
1 - 100 of 112 matches
Mail list logo
