Return-Path: 
 <users-return-63368-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 39638 invoked from network); 21 Feb 2004 11:55:03 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 21 Feb 2004 11:55:03 -0000
Received: (qmail 48542 invoked by uid 500); 21 Feb 2004 11:54:53 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 48526 invoked by uid 500); 21 Feb 2004 11:54:53 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
list-post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 48510 invoked from network); 21 Feb 2004 11:54:52 -0000
Received: from unknown (HELO mail.gmx.net) (213.165.64.20)
  by daedalus.apache.org with SMTP; 21 Feb 2004 11:54:52 -0000
Received: (qmail 6184 invoked by uid 65534); 21 Feb 2004 11:54:49 -0000
Received: from host-65-199-134-17.link.com.eg (EHLO Acer) (65.199.134.17)
  by mail.gmx.net (mp008) with SMTP; 21 Feb 2004 12:54:49 +0100
X-Authenticated: #1193893
From: "Christian Kreutz" <schreibchris@gmx.de>
To: <users@cocoon.apache.org>
Subject: AW: Xinclude/Xpointer problem with XHTML Namespace
Date: Sat, 21 Feb 2004 13:53:17 +0100
Message-ID: <000001c3f879$af6eeec0$9fedfea9@EGYPT>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
Importance: Normal
In-Reply-To: <000a01c3f7e6$e50fe9f0$9fedfea9@EGYPT>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Can't believe I solved it!!

In my case it has to have a xhtml extension.

<article1>
  <xi:include
href=3D"article1/index.xml#xmlns(xhtml=3Dhttp://www.w3.org/1999/xhtml)xpo=
int
er(//xhtml:title)" />=20
</article1>

Regards

Christian=20


> -----Urspr=FCngliche Nachricht-----
> Von: Christian Kreutz [mailto:schreibchris@gmx.de]
> Gesendet: Freitag, 20. Februar 2004 20:23
> An: users@cocoon.apache.org
> Betreff: AW: Xinclude/Xpointer problem with XHTML Namespace
>=20
>=20
>=20
>=20
> > -----Urspr=FCngliche Nachricht-----
> > Von: Bruno Dumon [mailto:bruno@outerthought.org]
> > Gesendet: Dienstag, 17. Februar 2004 00:51
> > An: users@cocoon.apache.
> > Betreff: Re: AW: Xinclude/Xpointer problem with XHTML Namespace
> >=20
> >=20
> > On Mon, 2004-02-16 at 19:17, Christian Kreutz wrote:
> > > First of all thanks very trying to help me with this.
> > > It is good to know there seems more behind
> > > this problem then just a small error - played to long with this=20
> > > problem to be just easy to solve. :-)
> > >=20
> > > It seems it has to do something with the html
> > > tag combined with the XHTML namespace. I tried your things and had
> > > the same results.
> > > =20
> > > I found this point what might has do somehting
> > > with it:
> > >=20
> > http://archives.real->
> time.com/pipermail/cocoon-devel/2003-May/013622.h
> > > tm
> > > l
> >=20
> > That issue has been fixed for a while:
> > http://nagoya.apache.org/bugzilla/show_bug.cgi> ?id=3D19423
> >=20
> > It
> > refered to the fact that you couldn't use the
> > xmlns() stuff in xpointer expressions.
> >=20
> > >=20
> > > I am using Xalan 2.5.0. Is this maybe a reason?
> >=20
> > Xalan does however indeed have something to do with it. To build a
> > DOM from SAX events, we use the trax API whose implementation is=20
> > provided by Xalan.
> >=20
> > And I know Xalan does different stuff for HTML then XML, and does
> > this by checking the root element. The only thing I still have to=20
> > find out is what it does exactly do different here. It must be=20
> > something with the DOM it builds (since two completely independent=20
> > XPath implementations can't handle it).
> >=20
> > I can't promise when I'll be able to look into this further. Maybe
> > some evening this week. If you want to have a look at it yourself,=20
> > the DOM-tree is made in
> > XPointerContent.getDocument() and the XPath is evaluated on
> > this in XPointerPart.process().
>=20
> I tried it the last days with Xalan 2.5.2 but it didn't work. I also=20
> tried it with Xlink but the same error ocurs. With java I am=20
> unfortunately not experienced enough to go to deep in the above=20
> mentioned functions. I am going to investigate the next days further=20
> but honestly I am quite hopeless solving this problem myself and think
> about changing to something other then xhtml files.
>=20
> Cheers and thanks very much for your help so far
>=20
> Christian
>=20
>=20
> =20
> > --=20
> > Bruno Dumon                             http://outerthought.org/
> > Outerthought - Open Source, Java & XML Competence Support Center
> > bruno@outerthought.org                          bruno@apache.org
> >=20
> >=20
> >=20
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >=20
> >=20
>=20
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>=20
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org