My first guess would be a namespace issue...

Since my last Mail I've tried to solve the problem and discovered,
that it must be a issue with
the prefix (in my case: 'sec'). Because if I remove all special
prefixes ('sec') from my source xml and the xpointer-call, it works.


I declared the namespace in the xml-file (and not especially for the xpointer).
That was not enough. You gave me the hint with the xmlns() xpointer.

Now it works. The solution is:

<xsl:attribute 
name="href">prefs.xml#xmlns(sec=http://myserver.com/specs/cocoon/sec)xpointer(/sec:title/sec:subtitle)</xsl:attribute>

Conclusion: There is a version issue, because v2.0 doesn't need the
correct namespace declaration for the xpointer.


Thanks a lot for your help, Jason.

--
Regards,

Stefan


2007/2/21, Jason Johnston <[EMAIL PROTECTED]>:
Stefan Shoeman wrote:
> Hello *,
>
> i have an old application, which works fine with Cocoon 2.0. It uses
> xpointers (in combination
> with xinclude) to define special parts in a xml-document. For example:
>
>
> <xsl:attribute
> name="href">prefs.xml#xpointer(/sec:title/sec:subtitle)</xsl:attribute>
>
>
> In Cocoon 2.1.9 / 2.1.10 this doesn't work. XInclude runs fine, but
> not the xpointers.
>
> I've only seen a major change, concerning xpointer, in the changelog of
> 2.1.10.
> But with 2.1.9 it's the same problem...

Yes there was a change to xpointer handling in the XIncludeTransformer
for 2.1.10 to bring it into compliance with the spec, but the old
non-conformant behavior was left in (and deprecated) for compatibility
so it should still work for the time being.

My first guess would be a namespace issue... how is the 'sec' namespace
prefix declared?  Does declaring it with a xmlns() xpointer part help?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to