Have a look at your sitemap and try to comprehend the processings. For example start with only the generator and an XML serializer in the pipeline. See on which stage the namespace declaration is added.

Joerg

Derek Hohls wrote:
Yes, that's what I would like to know too - how to remove
all the attribute data "attached' (not sure by which process
or component) to the <page> tag....
Thanks
Derek

>>> [EMAIL PROTECTED] 04/11/2002 10:03:32 >>>
What you read is the complaint of MSXML about the namespace declaration
xmlns:xml="...". This declaration should not be in the output, it's
implicit. Can you remove it in any way?

Regards,

Joerg

Derek Hohls wrote:
> Does anyone know of a reason why an XSL stylesheet would exhibit
> different behaviour under Windows (test machine) and Unix (server).
> > Could it be related to the fact that when I try and generate the XML
> input
> to the stylesheet on the server, the brower returns an error:
> > The XML page cannot be displayed Cannot view XML input using XSL style
> sheet.
> Please correct the error and then click the Refresh button, or try
> again later.
> The namespace prefix is not allowed to start with the reserved string
> "xml". Line 2, Position 7
>
> <page xmlns:xml="http://www.w3.org/XML/1998/namespace"; <http://www.w3.org/XML/1998/namespace>
> xmlns:xsp="http://apache.org/xsp"; <http://apache.org/xsp>
> xmlns:xspdoc="http://apache.org/cocoon/XSPDoc/v1"; <http://apache.org/cocoon/XSPDoc/v1>
> xmlns:esql="http://apache.org/cocoon/SQL/v2"; <http://apache.org/cocoon/SQL/v2>>
>
>
> I have also tried running a "static" file through the same stylesheet
> and it seems to work OK - of course, as I cannot see the generated
> XML there may be problems with it.
>
> Does anyone know how to overcome either (ot both!) of these
> problems.
>
> Thanks
> Derek

---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

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

Reply via email to