Help coderanch get a
new server
by contributing to the fundraiser
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

Parse doesn't happen with xmlns in xml file

Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm working with FileMaker and Xtags currently, and all seems to be going well except I have a problem.
FileMaker exports the xml starting with :
<?xml version="1.0" encoding="UTF-8" ?>
But if I don't remove :
Nothing happens for output, but if it is removed everything works fine. I was using the crimson parser but I changed to xerces to see if that would work but no change.
Any ideas?
Dany Hovinga
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Here's something which matches my problem, but this is a XLST conversion, but might jog someones mind.
I think this behaviour is caused by two things.
You're seeing the contents of the ERRORCODE, DATABASE and LAYOUT nodes
because the apply-templates in your FMPDSORESULT template results in these
nodes being matched by the default rule. You need a rule to override the
default rule which does nothing, like
<xsl:template match="node()" />
Then, the namespace problem is a FAQ. What you're seeing is that both the
FMPDSORESULT node and the ROW nodes are being matched *not* by your template
but by the default rule and their content therefore being 'dumped' (the
default behaviour).
Why is your FMPDSORESULT template not being used? It's because XPath
expressions match the null namespace not the default namespace. Try adding a
namespace declaration to your stylesheet
(xmlns:fmpro="" and then changing your
template so that you have
You'll probably also want to include "fmpro" in your stylesheet's
exclude-result-prefixes attribute.
[ July 22, 2003: Message edited by: Dany Hovinga ]
Do the next thing next. That’s a pretty good rule. Read the tiny ad, that’s a pretty good rule, too.
We need your help - Coderanch server fundraiser
    Bookmark Topic Watch Topic
  • New Topic