subject:"XInclude"

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  wrote:
> 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: "/element1/elemen...@id=somenumber]".
>>
>> Theorem: any XPath expression can be evaluated with a SAX filter.
>> Proof?
>> Do you know some exceptions?
>>
>
> What about this one : //foo[bar[position() = 3]//baz], find all elements
> "foo" whose 3rd "bar" child has a "baz" descendent element.
>
> This requires to buffer the contents of every "foo" element to inspect their
> chidren sub-tree.
>
> Sylvain
>
> --
> Sylvain Wallez - http://bluxte.net
>
>



-- 
http://www.google.com/profiles/simone.tripodi

Re: XInclude optimization

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, the exception comes when an
expression contains siblings/parent references...
What do you think about it?
Best regards and thanks for your hint!
Simone

On Mon, Nov 23, 2009 at 7:12 AM, 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: "/element1/elemen...@id=somenumber]".
>
> Theorem: any XPath expression can be evaluated with a SAX filter.
> Proof?
> Do you know some exceptions?
>
> Jos
>
>

-- 
http://www.google.com/profiles/simone.tripodi

Re: XInclude optimization

2009-11-22 Thread Sylvain Wallez


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: "/element1/elemen...@id=somenumber]".

Theorem: any XPath expression can be evaluated with a SAX filter.
Proof?
Do you know some exceptions?
  


What about this one : //foo[bar[position() = 3]//baz], find all elements 
"foo" whose 3rd "bar" child has a "baz" descendent element.


This requires to buffer the contents of every "foo" element to inspect 
their chidren sub-tree.


Sylvain

--
Sylvain Wallez - http://bluxte.net

Re: XInclude optimization

2009-11-22 Thread Sylvain Wallez


Simone Tripodi wrote:

Hi Sylvain,
thanks for your kind reply! I suspected the XPath limitations you
explained very well, but deeply in my heart I was hoping to a solution
I didn't know yet, for this reason I asked it :P :P

I'll take a look at both the solutions, eve if the first sounds to me
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 was suggesting to choose the actual xpath implementation according to 
the given XPath expression, since the Tika approach is really pure 
streaming. But this adds some complexity.



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 juniors involved in Joost :P
  


That's right! I did not made the connection! This is a small world ;-)

Sylvain

--
Sylvain Wallez - http://bluxte.net

Re: XInclude optimization

2009-11-22 Thread Jos Snellings

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 expression can be evaluated with a SAX filter.
Proof?
Do you know some exceptions?

Jos

Re: XInclude optimization

Hi Sylvain,
thanks for your kind reply! I suspected the XPath limitations you
explained very well, but deeply in my heart I was hoping to a solution
I didn't know yet, for this reason I asked it :P :P

I'll take a look at both the solutions, eve if the first sounds to me
more compliant 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 juniors involved in Joost :P

On Sun, Nov 22, 2009 at 3:27 PM, Sylvain Wallez  wrote:
> Simone Tripodi wrote:
>>
>> 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.
>>
>
> Don't be sorry. We all have our own jobs/interest/duties 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 APIs; the problem comes when
>> processing a document referenced by xinclude+xpointer, that forces the
>> processor to extract a sub-document of the included.
>>
>> To perform this, I implemented a DOM parsing, then through XPath I
>> extract the sub-document the processor has to be included, then
>> navigating the elements will be converted to SAX events. As you
>> noticed, this takes time, too much IMO, but I didn't find/don't know
>> any better solution :(
>> Since you experienced the stax, maybe you're able to suggest me a fast
>> way to parse a document with xpath and invoke SAX events, so I'm able
>> to provide you a much better - and faster, above all - solution.
>>
>> Any hint? Every suggestion will be very appreciated.
>>
>
> The problem with XPath and XML streaming (be it SAX or StAX) is that XPath
> is a language that allows exploring the document tree in all directions and
> thus inherently expects having the whole document tree available, which is
> clearly not compatible with streaming.
>
> There are different approaches to solving this :
> - use a deferred loading DOM implementation, which buffers events only when
> it needs them to traverse the tree. Axiom [1] provides this IIRC, along with
> an XPath implementation.
> - restrain the XPointer expression to a subset of XPath that can easily be
> implemented on top of a stream. This means restricting selection only on the
> current element, its attribute and its ancestors. There's an implementation
> of this approach in Tika.
>
> The XInclude transformer can be smart enough to use the most efficient
> implementation for the given XPath expression, i.e. try to parse it with
> Tika's restricted subset, and fallback to something more costly, either
> Axiom or plain DOM.
>
> Sylvain
>
> [1] http://ws.apache.org/commons/axiom/
> [2]
> https://svn.apache.org/repos/asf/lucene/tika/trunk/tika-core/src/main/java/org/apache/tika/sax/xpath/
>
> --
> Sylvain Wallez - http://bluxte.net
>
>



-- 
http://www.google.com/profiles/simone.tripodi

Re: XInclude optimization

2009-11-22 Thread Sylvain Wallez

Simone Tripodi wrote:

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.

Don't be sorry. We all have our own jobs/interest/duties 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 APIs; the problem comes when
processing a document referenced by xinclude+xpointer, that forces the
processor to extract a sub-document of the included.

To perform this, I implemented a DOM parsing, then through XPath I
extract the sub-document the processor has to be included, then
navigating the elements will be converted to SAX events. As you
noticed, this takes time, too much IMO, but I didn't find/don't know
any better solution :(
Since you experienced the stax, maybe you're able to suggest me a fast
way to parse a document with xpath and invoke SAX events, so I'm able
to provide you a much better - and faster, above all - solution.

Any hint? Every suggestion will be very appreciated.

The problem with XPath and XML streaming (be it SAX or StAX) is that
XPath is a language that allows exploring the document tree in all
directions and thus inherently expects having the whole document tree
available, which is clearly not compatible with streaming.

There are different approaches to solving this :
- use a deferred loading DOM implementation, which buffers events only
when it needs them to traverse the tree. Axiom [1] provides this IIRC,
along with an XPath implementation.
- restrain the XPointer expression to a subset of XPath that can easily
be implemented on top of a stream. This means restricting selection only
on the current element, its attribute and its ancestors. There's an
implementation of this approach in Tika.

The XInclude transformer can be smart enough to use the most efficient
implementation for the given XPath expression, i.e. try to parse it with
Tika's restricted subset, and fallback to something more costly, either
Axiom or plain DOM.

Sylvain

[1] http://ws.apache.org/commons/axiom/
[2]
https://svn.apache.org/repos/asf/lucene/tika/trunk/tika-core/src/main/java/org/apache/tika/sax/xpath/

--
Sylvain Wallez - http://bluxte.net

XInclude optimization

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, 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 APIs; the problem comes when
processing a document referenced by xinclude+xpointer, that forces the
processor to extract a sub-document of the included.

To perform this, I implemented a DOM parsing, then through XPath I
extract the sub-document the processor has to be included, then
navigating the elements will be converted to SAX events. As you
noticed, this takes time, too much IMO, but I didn't find/don't know
any better solution :(
Since you experienced the stax, maybe you're able to suggest me a fast
way to parse a document with xpath and invoke SAX events, so I'm able
to provide you a much better - and faster, above all - solution.

Any hint? Every suggestion will be very appreciated.
Thanks in adavance, best regards!!!
Simone

-- 
http://www.google.com/profiles/simone.tripodi

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2009-11-21 Thread Reinhard Poetz (JIRA)


 [ 
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: (was: 3.0.0-alpha-2)
   3.0.0-alpha-3
Affects 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
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-sax
>Affects Versions: 3.0.0-alpha-1
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-3
>
> Attachments: XInclude.patch, 
> XIncludeTransformerFixedAndApacheHeaders.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2009-02-07 Thread Reinhard Poetz (JIRA)


 [ 
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 transformer as a PipelineComponent
> --
>
> Key: COCOON3-3
> URL: https://issues.apache.org/jira/browse/COCOON3-3
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-sax
>Affects Versions: 3.0.0-alpha-2
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
> Attachments: XInclude.patch, 
> XIncludeTransformerFixedAndApacheHeaders.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-17 Thread Simone Tripodi (JIRA)


 [ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simone Tripodi updated COCOON3-3:
-

Attachment: XIncludeTransformerFixedAndApacheHeaders.patch

Hi
I'm really sorry to have 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 to apply it.

I also modified a little the previous XIncludeTransformer in way to be ready to 
be reused in the sitemap.

The XPointerFrameworkParser is generated using javacc; this justify the pom's 
modifications: the javacc plugin compiles the grammar in java sources, hat are 
managed through the build-helper plugin. So, only the .jj file should be 
committed, not also generated files.

I really hope this helps, don't hesitate if some help is needed.

> 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: cocoon-pipeline
>Affects Versions: 3.0.0-alpha-2
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
> Attachments: XInclude.patch, 
> XIncludeTransformerFixedAndApacheHeaders.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-17 Thread Reinhard Poetz (JIRA)


[ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640564#action_12640564
 ] 

Reinhard Poetz commented on COCOON3-3:
--

I forgot this to mention in my previous comment: 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://issues.apache.org/jira/browse/COCOON3-3
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-pipeline
>Affects Versions: 3.0.0-alpha-2
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
> Attachments: XInclude.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-17 Thread Reinhard Poetz (JIRA)


[ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640562#action_12640562
 ] 

Reinhard Poetz commented on COCOON3-3:
--

I tried to apply your patch 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
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-pipeline
>Affects Versions: 3.0.0-alpha-2
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
> Attachments: XInclude.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-06 Thread Reinhard Poetz (JIRA)


 [ 
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 transformer as a PipelineComponent
> --
>
> Key: COCOON3-3
> URL: https://issues.apache.org/jira/browse/COCOON3-3
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-pipeline
>Affects Versions: 3.0.0-alpha-2
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Fix For: 3.0.0-alpha-2
>
> Attachments: XInclude.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-06 Thread Simone Tripodi (JIRA)


 [ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simone Tripodi updated COCOON3-3:
-

Attachment: XInclude.patch

As mentioned on http://cocoon.apache.org/3.0/roadmap.html, 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 managed the 'accept' and 
'accept-language' attributes that weren't previously implemented;
- I maintained the deprecated xpointer support;
- The dependencies from old Excalibur's org.apache.excalibur.xml.xpath.* have 
been replaced with Java5 provided javax.xml.xpath.* - they are very similar;
- The XPointer grammar has been adapted to be managed by the 
maven-javacc-plugin (generation + report);
- The original DOMStreamer has been simplified;
- I only adapted the existing code to the new structure and used Java5 
generics, iterators where possible.

I really hope this helps! :)

> 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: cocoon-pipeline
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
> Attachments: XInclude.patch
>
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-02 Thread Simone Tripodi (JIRA)


[ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636548#action_12636548
 ] 

Simone Tripodi commented on COCOON3-3:
--

I started working on it but it's not so easy (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
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-pipeline
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-10-02 Thread Reinhard Poetz (JIRA)


[ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12636543#action_12636543
 ] 

Reinhard Poetz commented on COCOON3-3:
--

Usually the job of porting Cocoon 2.x 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
> Project: Cocoon 3
>  Issue Type: Improvement
>  Components: cocoon-pipeline
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-09-29 Thread Simone Tripodi (JIRA)


[ 
https://issues.apache.org/jira/browse/COCOON3-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12635407#action_12635407
 ] 

Simone Tripodi commented on COCOON3-3:
--

It seems that Xerces' implementation 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 fragments.  Thus, only whole documents can be included using 
this component in the pipeline."

The oldest cocoon's version porting should be the best solution.

> 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: cocoon-pipeline
>Reporter: Simone Tripodi
>Assignee: Cocoon Developers Team
>Priority: Minor
>
> Oldest versions of cocoon already contain an XInclude transformer, it could 
> be a good starting point:
> http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java
> XPointer package's dependencies should be reduced to be imported in the new 
> pipeline:
> http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer
> An alternative solution could be using xerces2 APIs:
> http://xerces.apache.org/xerces2-j/faq-xinclude.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (COCOON3-3) Provide an XInclude transformer as a PipelineComponent

2008-09-29 Thread Simone Tripodi (JIRA)

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: cocoon-pipeline
Reporter: Simone Tripodi
Assignee: Cocoon Developers Team
Priority: Minor


Oldest versions of cocoon already contain an XInclude transformer, it could be 
a good starting point:

http://svn.eu.apache.org/repos/asf/cocoon/trunk/core/cocoon-pipeline/cocoon-pipeline-components/src/main/java/org/apache/cocoon/transformation/XIncludeTransformer.java

XPointer package's dependencies should be reduced to be imported in the new 
pipeline:

http://svn.eu.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/src/java/org/apache/cocoon/components/xpointer

An alternative solution could be using xerces2 APIs:

http://xerces.apache.org/xerces2-j/faq-xinclude.html


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: ZipFileSerializer After XInclude Throws NullPointerException

2007-05-31 Thread Adrien Guillon

   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

Re: ZipFileSerializer After XInclude Throws NullPointerException

2007-05-31 Thread Adrien Guillon

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.: +31 (0) 10 850 1200
> Fax: +31 (0) 10 850 1199
> www.daidalos.nl
> KvK 27164984
>
>
> De informatie - verzonden in of met dit emailbericht - is afkomstig van
> Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit
> bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan
> dit bericht kunnen geen rechten worden ontleend.

Re: ZipFileSerializer After XInclude Throws NullPointerException

2007-05-31 Thread Adrien Guillon

Hi Joerg,

1) This resulted in the same error when I configured the pipeline like so:











2)  I changed the XInclude to this:



http://apache.org/cocoon/zip-archive/1.0"; 
xmlns:xi="http://www.w3.org/2001/XInclude"; >
 
  
 


and removed simple.xml from the pipeline... I get the same result.

Thanks.

AJ




> Hello Adrien,
>
> can you try 1. to use a reader for simple.xml pipeline instead of
> generator + serializer, 2. to include simple.xml directly instead of via
> cocoon pipeline?
>
> Joerg

RE: ZipFileSerializer After XInclude Throws NullPointerException

2007-05-30 Thread Geert Josten

> > Now I have two other files:
> > 
> > simple.xml: Hello
> > 
> > simple_xi.xml: 
> > 
> >   > xmlns:zip="http://apache.org/cocoon/zip-archive/1.0";
> > xmlns:xi="http://www.w3.org/2001/XInclude"; >   > name="content.xml" serializer="xml">
> >  
> 
> 
> Hello Adrien,
> 
> can you try 1. to use a reader for simple.xml pipeline 
> instead of generator + serializer, 2. to include simple.xml 
> directly instead of via cocoon pipeline?
> 
> Joerg

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.: +31 (0) 10 850 1200
Fax: +31 (0) 10 850 1199
www.daidalos.nl
KvK 27164984


De informatie - verzonden in of met dit emailbericht - is afkomstig van 
Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit 
bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit 
bericht kunnen geen rechten worden ontleend.

Re: ZipFileSerializer After XInclude Throws NullPointerException

2007-05-30 Thread Joerg Heinicke


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 constructed a very simple sitemap and XML files, and have 
been able to reproduce the problem.  I'm using Cocoon 2.1.10 with JDK 1.5.  
The problem was also reproduced on Cocoon 2.1.9 with JDK 1.4.


   What's funny is that if I take the resultant XML file after the xinclude 
transformation, and serialize with xml, and then run the zip file serializer 
on that file... everything is fine.  It doesn't look like an XML document 
issue...


Please find relevant info below let me know if anything else is needed.

AJ

   Here's a simple sitemap snippet to show the problem:





















Now I have two other files:

simple.xml: Hello

simple_xi.xml: 



http://apache.org/cocoon/zip-archive/1.0"; 
xmlns:xi="http://www.w3.org/2001/XInclude"; >

 
  
 



Hello Adrien,

can you try 1. to use a reader for simple.xml pipeline instead of 
generator + serializer, 2. to include simple.xml directly instead of via 
cocoon pipeline?


Joerg

ZipFileSerializer After XInclude Throws NullPointerException

2007-05-30 Thread Adrien Guillon

   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 and XML files, and have 
been able to reproduce the problem.  I'm using Cocoon 2.1.10 with JDK 1.5.  
The problem was also reproduced on Cocoon 2.1.9 with JDK 1.4.

   What's funny is that if I take the resultant XML file after the xinclude 
transformation, and serialize with xml, and then run the zip file serializer 
on that file... everything is fine.  It doesn't look like an XML document 
issue...

Please find relevant info below let me know if anything else is needed.

AJ

   Here's a simple sitemap snippet to show the problem:





















Now I have two other files:

simple.xml: Hello

simple_xi.xml: 


http://apache.org/cocoon/zip-archive/1.0"; 
xmlns:xi="http://www.w3.org/2001/XInclude"; >
 
  
 


After executing the XInclude Transformer directly and saving the output, you 
get this file (and running zip serializer just on this file works okay):
no_pipeline.xml:

http://apache.org/cocoon/zip-archive/1.0"; 
xmlns:xi="http://www.w3.org/2001/XInclude";>
 
  Hello
 



= Stack Trace =

java.lang.NullPointerException:

Cocoon stacktrace[hide]
Failed to process pipeline
context://utils/oasis/sitemap.xmap - 55:40  
context://utils/oasis/sitemap.xmap - 54:45  
context://utils/oasis/sitemap.xmap - 53:48  
context://utils/sitemap.xmap - 10:62
context://sitemap.xmap - 879:66 

Java stacktrace[hide]

java.lang.NullPointerException
at 
org.apache.cocoon.xml.AbstractXMLPipe.setDocumentLocator(AbstractXMLPipe.java:40)
at 
org.apache.cocoon.components.sax.XMLTeePipe.setDocumentLocator(XMLTeePipe.java:113)
at 
org.apache.cocoon.transformation.XIncludeTransformer$XIncludePipe.processXIncludeElement(XIncludeTransformer.java:476)
at 
org.apache.cocoon.transformation.XIncludeTransformer$XIncludePipe.startElement(XIncludeTransformer.java:241)
at 
org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:95)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown 
Source)
at 
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown 
Source)
at 
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown 
Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
 
Source)
at 
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown 
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown 
Source)
at org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
at org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:334)
at 
org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:326)
at 
org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:116)
at 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:367)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:481)
at 
org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:121)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:47)
at 
org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:108)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
at 
org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:69)
at 
org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:93)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:235)
at 
org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:177)
at

[jira] Updated: (COCOON-1881) Xinclude transformer has changed behaviour with Saxon 8.7.1

2006-10-12 Thread JIRA

 [ 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
> ---
>
> Key: COCOON-1881
> URL: http://issues.apache.org/jira/browse/COCOON-1881
> Project: Cocoon
>  Issue Type: Bug
>  Components: - Components: Sitemap
>Affects Versions: 2.1.8, 2.1.10-dev (current SVN)
>Reporter: Philip Fennell
> Attachments: xinclude.tar.gz
>
>
> With Windows XP sp2, Cocoon 2.1.8, Tomcat 5.5 and Saxon 8.6.1 or 8.7 
> configured as the default XSLT transformer I was able to embed xi:include 
> instructions within source documents and have Cocoon's Xinclude processor 
> resolve the URL (relative to the source document) correctly.
> e.g.
> 
>   login.xml not included. 
> However, when I moved to Saxon 8.7.1 (and also with 8.7.3) the xinclude fails 
> to locate the referenced file unless I change the href attribute so that the 
> url is relative to the current Cocoon context.
> e.g.
> 
>   login.xml not included. 
> Important Note:
> ===
> It is important to understand that I am 'NOT' using Cocoon to process the 
> requested document but rather to process the request (by using Cocoon's 
> request generator) information itself, which includes a refernece to the 
> original requested document. The request info is transformed into an 
> 'envelope' containing the request parameters, HTTP header info and an 
> interface definition file that may contain xi:include instructions that 
> reference additional static content. It is these xi:include instructions that 
> are at the centre of the problem. The example is in:
> xinclude/interface/config/login.xml
> The Cocoon pipeline match that does all the work can be found starting at 
> line 182 of sitemap.xmap.
> During the processing, the requested content and referenced content merged 
> and transformed into XHTML within the main rendering transform:
> xinclude/interface/transforms/xhtml/screen.xsl
> ===
> To run the test webapp that I have attached you will need to set-up Cocoon as 
> follows:
> 1) Add the following lines to cocoon/WEB-INF/cocoon.xconf:
>  role="org.apache.excalibur.xml.xslt.XSLTProcessor/saxon"
>   class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl">
> 
> 
>  value="net.sf.saxon.TransformerFactoryImpl"/>
>   
> after the Xalan component declaration.
> 2) Get Saxon 8.7 and 8.7.3 from http://www.saxonica.com/ and place the 
> following jars in cocoon/WEB-INF/lib
> saxon8.jar
> saxon8-dom.jar
> saxon8-xpath.jar
> 3) Unpack the attached ZIP file (xinclude.zip) in your cocoon directory
> 4) Use the following link to access the test page:
> http://localhost:8080/cocoon/xinclude/interface/config/login.html
> (Depending on host and port number etc you may need to tweak this url.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (COCOON-1881) Xinclude transformer has changed behaviour with Saxon 8.7.1

2006-07-13 Thread Philip Fennell (JIRA)

 [ 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 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: 2.1.8, 2.1.10-dev (current SVN)
> Reporter: Philip Fennell
>  Attachments: xinclude.tar.gz
>
> With Windows XP sp2, Cocoon 2.1.8, Tomcat 5.5 and Saxon 8.6.1 or 8.7 
> configured as the default XSLT transformer I was able to embed xi:include 
> instructions within source documents and have Cocoon's Xinclude processor 
> resolve the URL (relative to the source document) correctly.
> e.g.
> 
>   login.xml not included. 
> However, when I moved to Saxon 8.7.1 (and also with 8.7.3) the xinclude fails 
> to locate the referenced file unless I change the href attribute so that the 
> url is relative to the current Cocoon context.
> e.g.
> 
>   login.xml not included. 
> Important Note:
> ===
> It is important to understand that I am 'NOT' using Cocoon to process the 
> requested document but rather to process the request (by using Cocoon's 
> request generator) information itself, which includes a refernece to the 
> original requested document. The request info is transformed into an 
> 'envelope' containing the request parameters, HTTP header info and an 
> interface definition file that may contain xi:include instructions that 
> reference additional static content. It is these xi:include instructions that 
> are at the centre of the problem. The example is in:
> xinclude/interface/config/login.xml
> The Cocoon pipeline match that does all the work can be found starting at 
> line 182 of sitemap.xmap.
> During the processing, the requested content and referenced content merged 
> and transformed into XHTML within the main rendering transform:
> xinclude/interface/transforms/xhtml/screen.xsl
> ===
> To run the test webapp that I have attached you will need to set-up Cocoon as 
> follows:
> 1) Add the following lines to cocoon/WEB-INF/cocoon.xconf:
>  role="org.apache.excalibur.xml.xslt.XSLTProcessor/saxon"
>   class="org.apache.excalibur.xml.xslt.XSLTProcessorImpl">
> 
> 
>  value="net.sf.saxon.TransformerFactoryImpl"/>
>   
> after the Xalan component declaration.
> 2) Get Saxon 8.7 and 8.7.3 from http://www.saxonica.com/ and place the 
> following jars in cocoon/WEB-INF/lib
> saxon8.jar
> saxon8-dom.jar
> saxon8-xpath.jar
> 3) Unpack the attached ZIP file (xinclude.zip) in your cocoon directory
> 4) Use the following link to access the test page:
> http://localhost:8080/cocoon/xinclude/interface/config/login.html
> (Depending on host and port number etc you may need to tweak this url.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (COCOON-1881) Xinclude transformer has changed behaviour with Saxon 8.7.1

2006-07-13 Thread Philip Fennell (JIRA)

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: 2.1.8, 2.1.10-dev (current SVN)
Reporter: Philip Fennell


With Windows XP sp2, Cocoon 2.1.8, Tomcat 5.5 and Saxon 8.6.1 or 8.7 configured 
as the default XSLT transformer I was able to embed xi:include instructions 
within source documents and have Cocoon's Xinclude processor resolve the URL 
(relative to the source document) correctly.

e.g.


  login.xml not included. 

However, when I moved to Saxon 8.7.1 (and also with 8.7.3) the xinclude fails 
to locate the referenced file unless I change the href attribute so that the 
url is relative to the current Cocoon context.

e.g.


  login.xml not included. 



Important Note:
===

It is important to understand that I am 'NOT' using Cocoon to process the 
requested document but rather to process the request (by using Cocoon's request 
generator) information itself, which includes a refernece to the original 
requested document. The request info is transformed into an 'envelope' 
containing the request parameters, HTTP header info and an interface definition 
file that may contain xi:include instructions that reference additional static 
content. It is these xi:include instructions that are at the centre of the 
problem. The example is in:

xinclude/interface/config/login.xml

The Cocoon pipeline match that does all the work can be found starting at line 
182 of sitemap.xmap.

During the processing, the requested content and referenced content merged and 
transformed into XHTML within the main rendering transform:

xinclude/interface/transforms/xhtml/screen.xsl

===



To run the test webapp that I have attached you will need to set-up Cocoon as 
follows:

1) Add the following lines to cocoon/WEB-INF/cocoon.xconf:

  



  

after the Xalan component declaration.


2) Get Saxon 8.7 and 8.7.3 from http://www.saxonica.com/ and place the 
following jars in cocoon/WEB-INF/lib

saxon8.jar
saxon8-dom.jar
saxon8-xpath.jar


3) Unpack the attached ZIP file (xinclude.zip) in your cocoon directory


4) Use the following link to access the test page:

http://localhost:8080/cocoon/xinclude/interface/config/login.html

(Depending on host and port number etc you may need to tweak this url.)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-05-29 Thread Antonio Gallardo (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
 
Antonio Gallardo closed COCOON-1489:


Fix Version: 2.2-dev (Current SVN)
 2.1.10-dev (current SVN)
 Resolution: Fixed

Thanks Jason for the patch. It was applied 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/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug

>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
> Assignee: Antonio Gallardo
>  Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
>  Attachments: COCOON-1489.diff, cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-05-29 Thread Antonio Gallardo (JIRA)

 [ 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
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug

>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
> Assignee: Antonio Gallardo
>  Attachments: COCOON-1489.diff, cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-05-29 Thread Jason Johnston (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]

Jason Johnston updated COCOON-1489:
---

Attachment: COCOON-1489.diff

Patch fixes issue with ill-formed result from xi:include within a fallback. The 
JUnit testcase for that functionality had 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 to be applied to trunk as well.

> [PATCH] XInclude transformer does not handle fallback correctly
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug

>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
>  Attachments: COCOON-1489.diff, cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-05-28 Thread Antonio Gallardo (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1753?page=all ]
 
Antonio Gallardo closed COCOON-1753:


Fix Version: 2.2-dev (Current SVN)
 2.1.10-dev (current SVN)
 Resolution: Fixed

Thanks for the patch. It was applied 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://issues.apache.org/jira/browse/COCOON-1753
>  Project: Cocoon
> Type: Bug

>   Components: - Components: Sitemap
> Versions: 2.1.9
> Reporter: Jason Johnston
> Assignee: Antonio Gallardo
>  Fix For: 2.2-dev (Current SVN), 2.1.10-dev (current SVN)
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-05-27 Thread Antonio Gallardo (JIRA)

[ 
http://issues.apache.org/jira/browse/COCOON-1489?page=comments#action_12413615 
] 

Antonio Gallardo commented on COCOON-1489:
--

The problem shows up if we replace the element with a nested  in 
. Testcase added:

http://svn.apache.org/viewvc?view=rev&revision=409920

> [PATCH] XInclude transformer does not handle fallback correctly
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug

>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-05-27 Thread Antonio Gallardo (JIRA)

[ 
http://issues.apache.org/jira/browse/COCOON-1489?page=comments#action_12413612 
] 

Antonio Gallardo commented on COCOON-1489:
--

Added a junit testcase for this bug and it seems to work, please review the 
testcase here:

http://svn.apache.org/viewvc?view=rev&revision=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

>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Kommentiert: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-04-24 Thread JIRA

[ 
http://issues.apache.org/jira/browse/COCOON-1753?page=comments#action_12376067 
] 

Jörg Heinicke commented on COCOON-1753:
---

Providing backward compatibility and adding a warning is our way of deprecating 
stuff, so your patch should be absolutely ok.

> 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
> Type: Bug

>   Components: - Components: Sitemap
> Versions: 2.1.9
> Reporter: Jason Johnston
> Assignee: Antonio Gallardo
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-04-24 Thread Jason Johnston (JIRA)

[ 
http://issues.apache.org/jira/browse/COCOON-1753?page=comments#action_12376031 
] 

Jason Johnston commented on COCOON-1753:


I wrote the patch to be entirely backward compatible, though it does write a 
WARN log message saying support for the old non-standard syntax will be removed 
in a future release. That can (and should) go up for a vote of course. If it's 
decided that the old syntax should remain supported (which would technically be 
a violation of the spec), then you can just remove that WARN message and 
everything should be dandy.

> 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
> Type: Bug

>   Components: - Components: Sitemap
> Versions: 2.1.9
> Reporter: Jason Johnston
> Assignee: Antonio Gallardo
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-04-24 Thread Antonio Gallardo (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1753?page=all ]

Antonio Gallardo reassigned COCOON-1753:


Assign To: Antonio Gallardo

> 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
> Type: Bug

>   Components: - Components: Sitemap
> Versions: 2.1.9
> Reporter: Jason Johnston
> Assignee: Antonio Gallardo
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-04-24 Thread Antonio Gallardo (JIRA)

[ 
http://issues.apache.org/jira/browse/COCOON-1753?page=comments#action_12375976 
] 

Antonio Gallardo commented on COCOON-1753:
--

I like the patch, the only problem I see is backward compatibility. What to do?

> 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
> Type: Bug

>   Components: - Components: Sitemap
> Versions: 2.1.9
> Reporter: Jason Johnston
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-02-28 Thread David Crossley (JIRA)

 [ 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  element, the XInclude transformer returns a
not-well-formed document.

Example:

http://www.w3.org/2001/XInclude";>
  

  This should be here if the file was not found

  


returns this, if the included resource does not exist:

http://www.w3.org/2001/XInclude";>
  
  This should be here if the file was not found
  


  was:
When using the  element, the XInclude transformer returns a
not-well-formed document.

Example:

http://www.w3.org/2001/XInclude";>
  

  This should be here if the file was not found

  


returns this, if the included resource does not exist:

http://www.w3.org/2001/XInclude";>
  
  This should be here if the file was not found
  



> [PATCH] XInclude transformer does not handle fallback correctly
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug
>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Commented: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-02-15 Thread Jason Johnston (JIRA)

[ 
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 transformer uses href fragment rather than xpointer attribute (spec 
> conformance)
> -
>
>  Key: COCOON-1753
>  URL: http://issues.apache.org/jira/browse/COCOON-1753
>  Project: Cocoon
> Type: Bug
>   Components: - Components: Sitemap
> Versions: 2.1.9-dev (current SVN)
> Reporter: Jason Johnston
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Updated: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-02-15 Thread Jason Johnston (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1753?page=all ]

Jason Johnston updated COCOON-1753:
---

Attachment: COCOON-1753.diff

Attached patch.  Implements xpointer="..." attribute as the preferred way for 
specifying xpointer fragments.  The old href-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)
> -
>
>  Key: COCOON-1753
>  URL: http://issues.apache.org/jira/browse/COCOON-1753
>  Project: Cocoon
> Type: Bug
>   Components: - Components: Sitemap
> Versions: 2.1.9-dev (current SVN)
> Reporter: Jason Johnston
>  Attachments: COCOON-1753.diff
>
> The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
> states the following about the href attribute:
> "Fragment identifiers must not be used; their appearance is a fatal error."
> Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
> specified using a fragment identifier in the href attribute.  The correct way 
> to support xpointers is the "xpointer" attribute on xi:include, which the 
> transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-02-03 Thread Jean-Baptiste Quenot (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]

Jean-Baptiste Quenot reassigned COCOON-1489:


Assign To: (was: Jean-Baptiste Quenot)

Unassigning this bug, as there's also another issue COCOON-1753, maybe 
XIncludeTransformer 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: Bug
>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Created: (COCOON-1753) XInclude transformer uses href fragment rather than xpointer attribute (spec conformance)

2006-01-31 Thread Jason Johnston (JIRA)

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
Type: Bug
  Components: - Components: Sitemap  
Versions: 2.1.9-dev (current SVN)
Reporter: Jason Johnston


The XInclude 1.0 spec (see http://www.w3.org/TR/xinclude/#include_element) 
states the following about the href attribute:

"Fragment identifiers must not be used; their appearance is a fatal error."

Cocoon's XIncludeTransformer incorrectly allows xpointer fragments to be 
specified using a fragment identifier in the href attribute.  The correct way 
to support xpointers is the "xpointer" attribute on xi:include, which the 
transformer does not currently recognize.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Assigned: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-01-18 Thread Jean-Baptiste Quenot (JIRA)

 [ 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
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug
>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
> Assignee: Jean-Baptiste Quenot
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Reopened: (COCOON-1489) [PATCH] XInclude transformer does not handle fallback correctly

2006-01-06 Thread Antonio Gallardo (JIRA)

 [ http://issues.apache.org/jira/browse/COCOON-1489?page=all ]
 
Antonio Gallardo reopened COCOON-1489:
--


See: http://marc.theaimsgroup.com/?l=xml-cocoon-users&m=113639560121665&w=2
This sample will faail: http://www.w3.org/TR/xinclude/#fallback-example


> [PATCH] XInclude transformer does not handle fallback correctly
> ---
>
>  Key: COCOON-1489
>  URL: http://issues.apache.org/jira/browse/COCOON-1489
>  Project: Cocoon
> Type: Bug
>   Components: * Cocoon Core
> Versions: 2.2-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Joachim Breitsprecher
> Assignee: Cocoon Developers Team
>  Attachments: cocoon-xinclude-transformer-patch.txt
>
> When using the  element, the XInclude transformer returns a
> not-well-formed document.
> Example:
> http://www.w3.org/2001/XInclude";>
>   
> 
>   This should be here if the file was not found
> 
>   
> 
> returns this, if the included resource does not exist:
>  xmlns:xi="http://www.w3.org/2001/XInclude";>
>   
>   This should be here if the file was not found
>   
> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Re: [DAISY] Comment added to XInclude Transformer

2005-11-22 Thread Antonio Gallardo


[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 does it mean?  AFAICT XIncludeTransformer does not 
implement CacheableProcessingComponent.
 


Please see: http://issues.apache.org/bugzilla/show_bug.cgi?id=31600

Best Regards,

Antonio Gallardo.

[jira] Closed: (COCOON-879) 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
> ---
>
>  Key: COCOON-879
>  URL: http://issues.apache.org/jira/browse/COCOON-879
>  Project: Cocoon
> Type: Improvement
>   Components: - Components: Sitemap
> Versions: 2.1.1
>  Environment: Operating System: other
> Platform: Other
> Reporter: Oleg Dulin
> Assignee: Cocoon Developers Team
> Priority: Minor

>
> Currently, there is no way to reuse sitemap fragments across different files.
> This severely limits refactoring possibilities.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Reopened: (COCOON-879) 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 reopened COCOON-879:
-


reopened just to set the resolution to fixed

> Need to be able to use "cinclude" or "xinclude" to manage sitemap fragments
> ---
>
>  Key: COCOON-879
>  URL: http://issues.apache.org/jira/browse/COCOON-879
>  Project: Cocoon
> Type: Improvement
>   Components: - Components: Sitemap
> Versions: 2.1.1
>  Environment: Operating System: other
> Platform: Other
> Reporter: Oleg Dulin
> Assignee: Cocoon Developers Team
> Priority: Minor

>
> Currently, there is no way to reuse sitemap fragments across different files.
> This severely limits refactoring possibilities.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Closed: (COCOON-599) 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
> -
>
>  Key: COCOON-599
>  URL: http://issues.apache.org/jira/browse/COCOON-599
>  Project: Cocoon
> Type: Bug
>   Components: * Cocoon Core
> Versions: 2.1.8-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Torsten Schlabach
> Assignee: Cocoon Developers Team
> Priority: Critical

>
> Take this XML file as somefile.xml:
> 
>   
> Dummy document
>   
>   
> One paragraph!
>   
> 
>  results in nothing 
> being
> included though this should be correct sntax according to the XPointer spec.
> Using
>  instead seems to be 
> a
> workaround, but *only* as long as the document that is beeing included does 
> not
> use a special namespace.
> If you try to include an XHTML document neither
> 
> nor
> 
> will yield any results. It just silently includes nothing without *any* 
> messages
> in any log file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[jira] Reopened: (COCOON-599) XPointer implementation in XInclude Transformer is broken

 [ 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
> -
>
>  Key: COCOON-599
>  URL: http://issues.apache.org/jira/browse/COCOON-599
>  Project: Cocoon
> Type: Bug
>   Components: * Cocoon Core
> Versions: 2.1.8-dev (Current SVN)
>  Environment: Operating System: All
> Platform: All
> Reporter: Torsten Schlabach
> Assignee: Cocoon Developers Team
> Priority: Critical

>
> Take this XML file as somefile.xml:
> 
>   
> Dummy document
>   
>   
> One paragraph!
>   
> 
>  results in nothing 
> being
> included though this should be correct sntax according to the XPointer spec.
> Using
>  instead seems to be 
> a
> workaround, but *only* as long as the document that is beeing included does 
> not
> use a special namespace.
> If you try to include an XHTML document neither
> 
> nor
> 
> will yield any results. It just silently includes nothing without *any* 
> messages
> in any log file.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

DO NOT REPLY [Bug 24498] - Need to be able to use "cinclude" or "xinclude" to manage sitemap fragments

2005-09-16 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=24498


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 24498] - Need to be able to use "cinclude" or "xinclude" to manage sitemap fragments

2005-09-16 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=24498


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID




--- Additional Comments From [EMAIL PROTECTED]  2005-09-17 08:14 ---
There is much stuff on the way regarding this issue/enhancement: includes in
sitemap, splitted xconfs, VPCs, blocks. So this issue is obsolete.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 26755] - XInclude processing failed for sample due to wrong xpointer expression

2005-08-18 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=26755


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 34325] - [PATCH] XInclude transformer does not handle fallback correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34325


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED




-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 34325] - [PATCH] XInclude transformer does not handle fallback correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34325


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED




--- Additional Comments From [EMAIL PROTECTED]  2005-04-06 12:39 ---
Done. Thanks for reporting. :-)

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

Re: Bug in XInclude transformer?

2005-04-06 Thread Joachim Breitsprecher

Michael Wechner wrote:
what do you mean by unbalanced output?
http://www.w3.org/2001/XInclude";>

  This should be here if the file was not found
  


Have you filed this patch yet?
yep I just did :-)
http://issues.apache.org/bugzilla/show_bug.cgi?id=34325

Greetings,
Joachim

DO NOT REPLY [Bug 34325] - [PATCH] XInclude transformer does not handle fallback correctly

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34325





--- Additional Comments From [EMAIL PROTECTED]  2005-04-06 12:04 ---
Created an attachment (id=14630)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=14630&action=view)
Patch that solves the issue


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

DO NOT REPLY [Bug 34325] New: - [PATCH] XInclude transformer does not handle fallback correctly

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.

http://issues.apache.org/bugzilla/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
  Priority: P2
 Component: core
AssignedTo: dev@cocoon.apache.org
ReportedBy: [EMAIL PROTECTED]


When using the  element, the XInclude transformer returns a
not-well-formed document.

Example:

http://www.w3.org/2001/XInclude";>
  

  This should be here if the file was not found

  


returns this, if the included resource does not exist:

http://www.w3.org/2001/XInclude";>
  
  This should be here if the file was not found
  


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

Re: Bug in XInclude transformer?

2005-04-06 Thread Michael Wechner

Joachim Breitsprecher wrote:
Hi all,
I think I found a bug in Cocoon's XInclude transformer. Try this 
pipeline:


  
  
  

whith test.xml containing:

http://www.w3.org/2001/XInclude";>
  

  This should be here if the file was not found

  

With all cocoon versions I tested (2.1.4, 2.1.5.1, 2.1.6, SVN head) 
this pipeline gives me an unbalanced output if 
this_file_does_not_exist.xml doesn't exist.

what do you mean by unbalanced output?

I have prepared a patch against the current SVN version and am ready 
to file a bug if no-one objects :-)

Have you filed this patch yet?
Michi

Regards,
Joachim


--
Michael Wechner
Wyona Inc.  -   Open Source Content Management   -   Apache Lenya
http://www.wyona.com  http://lenya.apache.org
[EMAIL PROTECTED][EMAIL PROTECTED]

Bug in XInclude transformer?

2005-04-05 Thread Joachim Breitsprecher

Hi all,
I think I found a bug in Cocoon's XInclude transformer. Try this pipeline:

  
  
  

whith test.xml containing:

http://www.w3.org/2001/XInclude";>
  

  This should be here if the file was not found

  

With all cocoon versions I tested (2.1.4, 2.1.5.1, 2.1.6, SVN head) this 
pipeline gives me an unbalanced output if this_file_does_not_exist.xml 
doesn't exist.

I have prepared a patch against the current SVN version and am ready to 
file a bug if no-one objects :-)

Regards,
Joachim

DO NOT REPLY [Bug 24498] - Need to be able to use "cinclude" or "xinclude" to manage sitemap fragments

2004-05-07 Thread bugzilla

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.

http://issues.apache.org/bugzilla/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  |Enhancement

DO NOT REPLY [Bug 26750] - General XInclude sample does not work

2004-02-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/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 :)

Does our XInclude* rely in any way on the Xerces implementation?

DO NOT REPLY [Bug 26750] - General XInclude sample does not work

2004-02-08 Thread bugzilla

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/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.

DO NOT REPLY [Bug 26750] - General XInclude sample does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750

General XInclude sample does not work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED



--- Additional Comments From [EMAIL PROTECTED]  2004-02-07 15:52 ---
"Fixed" in some way, see commit message for more details:
http://article.gmane.org/gmane.text.xml.cocoon.cvs/10647

DO NOT REPLY [Bug 26755] - XInclude processing failed for sample due to wrong xpointer expression

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26755>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/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 ...

DO NOT REPLY [Bug 26750] - General XInclude sample does not work

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26750

General XInclude sample does not work

[EMAIL PROTECTED] changed:

   What|Removed |Added

 CC||[EMAIL PROTECTED]



--- Additional Comments From [EMAIL PROTECTED]  2004-02-07 14:24 ---
*** Bug 26755 has been marked as a duplicate of this bug. ***

DO NOT REPLY [Bug 26755] - XInclude processing failed for sample due to wrong xpointer expression

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26755>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26755

XInclude processing failed for sample due to wrong xpointer expression

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||DUPLICATE



--- Additional Comments From [EMAIL PROTECTED]  2004-02-07 14:24 ---


*** This bug has been marked as a duplicate of 26750 ***

DO NOT REPLY [Bug 26755] New: - XInclude processing failed for sample due to wrong xpointer expression

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26755>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/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
   URL: http://127.0.0.1:/samples/aggregation/test.html
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Samples
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]

DO NOT REPLY [Bug 26750] New: - General XInclude sample does not work