For all dummys like me, here is the correct way to solve the problem
above:
call _serializer.setPrefix(, NAMESPACE);
where NAMESPACE := the default namespace of your xml
then call
_serializer.startTag(NAMESPACE, test);
...
_serializer.endTag(NAMESPACE, test);
null is not needed anymore and yet
Hi,
to come back to a way of solution. Does anyone know how to solve the
described problem?
Is the only way to write a new XMLWriter without XML Serializer?
Thanks!
On 15 Feb., 23:06, Sky skysoftwaredes...@googlemail.com wrote:
Hi,
I do not want to write my XML Serialization new. its
Thanks for the clarification Bob!
I will try to change my code. Nevertheless like Streets of Boston
said, I would say that this is a bug and should be changed, at least
in the docs.
On 13 Feb., 06:09, Streets Of Boston flyingdutc...@gmail.com wrote:
The documentation of the *startTag* method
I testet the java.xml.XMLConstants.NULL_NS_URi:
private static final String NAMESPACE = XMLConstants.NULL_NS_URI;
_serializer.setPrefix(, NAMESPACE);
_serializer.startTag(NAMESPACE, gpx);
Now there is the following error. How would you handle tha? (For
clarification I want to write a xml with no
Yes, this is exactly what I want to do. Write old plain XML without
Namespace.
The question is how I get it to work on Andorid 2.3?
On 13 Feb., 21:04, Streets Of Boston flyingdutc...@gmail.com wrote:
I think it was mainly meant for XML documents that don't use namespaces at
all, since there
Could you write the XML file yourself, just with print type statements?
Not as convenient as using a serializer, and probably not as pretty
(indents, attributes and stuff), but if it's meant as input for another
program, it probably doesn't have to be perfect, right?
-- Kostya
13.02.2011
Hi,
I do not want to write my XML Serialization new. its complex, and time
is expensive. And currently it works perfectly on all Android Versions
2.3. I think things should not be downgraded from one to another
release, except something gets deprecated. Its like Street of Boston
said its a
I believe the documentation is confused -- and possibly the spec on which it
is based.
Having a namespace value (null) which causes the the XML to take on some
value which cannot be determined except by examining the past program
execution trace possibly back all the way to when the document
I think it was mainly meant for XML documents that don't use namespaces at
all, since there is no startTag(String elementName) method.
And i think you can leave it null if it implicitly takes on the namespace of
its parent-element.
Whether the acceptance of null for this parameter is OK or
While you are not crazy to think *null* might mean something useful, let me
point out the line of reasoning you need to follow:
Exactly what namespace did you expect *null* to give you? Why do you hold
the opinion that *null* should give you this namespace?
And exactly what namespace are you
The documentation of the *startTag* method mentions this:
... If namespace is null no namespace prefix is printed but just name...
Regardless of the XML starndard, this means that null is a valid and
documented input for this method. If this has suddenly become broken in 2.3
(i haven't seen
11 matches
Mail list logo
