Wrong namespace prefix in generated documents?

Michael Bishop <[email protected]> Mon, 28 Jul 2014 14:27:34 -0400
Newsgroups gmane.text.xml.xmlbeans.user
Message-ID <CAAenQJdNOYukMSBM83MuQ2jHTEr_T1D38kgwd6OR=tVXAfhrgQ@mail.gmail.com>
--001a11339e88a4a3b104ff451329
Content-Type: text/plain; charset=UTF-8

Hello all. I've recently changed the namespace of my schema. Now I'm
getting the wrong prefix name and I'm not sure why.

Old namespace was:

xmlns:*xxx*="http://ccc.bbb.aaa"

New namespace is:

xmlns:*xxx*="*yyy*:aaa:bbb:ccc"

With the old namespace, the prefix for elements was xxx. Now with the new
namespace, the prefix fpr elements is *yyy*. It seems switching from URL
form to URI form has caused the processor to start using the first part of
the URI as the prefix? This happens when I call the static
Factory.newInstance() on generated classes. Older documents with the
correct prefix still parse properly.

It's not a big deal since the namespace is intact and things work as they
should, but I can't figure out why this is happening. I don't declare xmlns:
*yyy* anywhere in the schema or xsdconfig files.

Michael Bishop

--001a11339e88a4a3b104ff451329
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div>Hello all. I&#39;ve recently chan=
ged the namespace of my schema. Now I&#39;m getting the wrong prefix name a=
nd I&#39;m not sure why.<br><br></div>Old namespace was:<br><br>xmlns:<b>xx=
x</b>=3D&quot;<a href=3D"http://ccc.bbb.aaa">http://ccc.bbb.aaa</a>&quot;<b=
r>
<br></div>New namespace is:<br><br>xmlns:<b>xxx</b>=3D&quot;<b>yyy</b>:aaa:=
bbb:ccc&quot;<br><br></div>With the old namespace, the prefix for elements =
was xxx. Now with the new namespace, the prefix fpr elements is <b>yyy</b>.=
 It seems switching from URL form to URI form has caused the processor to s=
tart using the first part of the URI as the prefix? This happens when I cal=
l the static Factory.newInstance() on generated classes. Older documents wi=
th the correct prefix still parse properly.<br>
<br></div>It&#39;s not a big deal since the namespace is intact and things =
work as they should, but I can&#39;t figure out why this is happening. I do=
n&#39;t declare xmlns:<b>yyy</b> anywhere in the schema or xsdconfig files.=
<br>
<br></div>Michael Bishop<br></div>

--001a11339e88a4a3b104ff451329--