FYI: Attached is a note from an IBM researcher who has been using Axis to
create some demos for the IBM Web Services Toolkit. It details from
issues she has had to deal with in regards to the MessageElement class.
After the 1.1 Release, I will work on incorporating her suggested
enhancements
gzilla/show_bug.cgi?id=14134
QName Attributes lose namespace mapping in MessageElement after Serialization.
[EMAIL PROTECTED] changed:
What|Removed |Added
Stat
gzilla/show_bug.cgi?id=14134
QName Attributes lose namespace mapping in MessageElement after Serialization.
--- Additional Comments From [EMAIL PROTECTED] 2002-11-05 18:09 ---
Here is the cvs diff for the fix that I promised. Essentially the QName
Attributes do not get set to null. The
gzilla/show_bug.cgi?id=14130
Type is not used during serialization of MessageElement.
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=14140
getNamespacePrefixes of MessageElement throws a NullPointerException if no namespaces
have been declared.
[EMAIL PROTECTED] changed:
What|Removed
gzilla/show_bug.cgi?id=14139
NamespaceDeclaration's are not used during the serialization of MessageElement.
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=14136
getCompleteAttributes in MessageElement problems
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=14140
getNamespacePrefixes of MessageElement throws a NullPointerException if no namespaces
have been declared.
Summary: getNamespacePrefixes of MessageElement throws a
NullPointerException if no namespaces have been
de
gzilla/show_bug.cgi?id=14139
NamespaceDeclaration's are not used during the serialization of MessageElement.
--- Additional Comments From [EMAIL PROTECTED] 2002-10-31 16:50 ---
Created an attachment (id=3683)
Java test file for this bug.
gzilla/show_bug.cgi?id=14139
NamespaceDeclaration's are not used during the serialization of MessageElement.
Summary: NamespaceDeclaration's are not used during the
serialization of MessageElement.
Product: Axis
Version: 1.0
gzilla/show_bug.cgi?id=14136
getCompleteAttributes in MessageElement problems
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||[EMAIL PRO
gzilla/show_bug.cgi?id=14134
QName Attributes lose namespace mapping in MessageElement after Serialization.
[EMAIL PROTECTED] changed:
What|Removed |Added
gzilla/show_bug.cgi?id=14136
getCompleteAttributes in MessageElement problems
--- Additional Comments From [EMAIL PROTECTED] 2002-10-31 16:25 ---
Created an attachment (id=3682)
Java test file for this bug.
gzilla/show_bug.cgi?id=14136
getCompleteAttributes in MessageElement problems
Summary: getCompleteAttributes in MessageElement problems
Product: Axis
Version: 1.0
Platform: Other
OS/Version: Other
Status: NEW
Severity:
gzilla/show_bug.cgi?id=14134
QName Attributes lose namespace mapping in MessageElement after Serialization.
--- Additional Comments From [EMAIL PROTECTED] 2002-10-31 15:55 ---
Created an attachment (id=3680)
The java file used to show this bug.
gzilla/show_bug.cgi?id=14134
QName Attributes lose namespace mapping in MessageElement after Serialization.
Summary: QName Attributes lose namespace mapping in
MessageElement after Serialization.
Product: Axis
Version: 1.0
Platform:
gzilla/show_bug.cgi?id=14130
Type is not used during serialization of MessageElement.
--- Additional Comments From [EMAIL PROTECTED] 2002-10-31 15:28 ---
Created an attachment (id=3679)
The java file used to demonstrate this bug.
gzilla/show_bug.cgi?id=14130
Type is not used during serialization of MessageElement.
Summary: Type is not used during serialization of MessageElement.
Product: Axis
Version: 1.0
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Se
I think I have found a few bugs in MessageElement. Either that or I need an
explanation on how things work. I am building up a SOAPEnvelope using
MessageElement's. When I build the MessageElement, I set the name,
attributes, value, etc. One specific attribute I set is the xsi:type.
Obvi
12:30 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [PATCH] MessageElement value serialization, etc
>
>
> >In fact to support this nicely, we should provide a MessageElement
> constructor that matches the SOAPHeader one >(namespace, localPart,
> objectValue). [Oh, sorry in the ex
>In fact to support this nicely, we should provide a MessageElement
constructor that matches the SOAPHeader one >(namespace, localPart,
objectValue). [Oh, sorry in the examples above I shouldn't have used the
QNames, since >those constructors don't exist]
>
>I also think
idea is that this API is for
programattic generation of XML from serializable Java stuff, and thus the contents of
the XML are EXACTLY the serialized data of the Java objects.
i.e.
SOAPHeader myHeader = new SOAPHeader(new QName("myNS", "header1"));
MessageElement e1 = new MessageEleme
>>1. I re-introduced SOAPHeader.outputImpl as the build failed without it.
>It looks like you did not add the change to output() and outputImpl() in
>MessageElement. They contained proper code for serializing values, as well
a
>fix for serializing child elements.
The diff of yo
ion of child elements.
I made some changes, which you may like to comment on:
>1. I re-introduced SOAPHeader.outputImpl as the build failed without it.
It looks like you did not add the change to output() and outputImpl() in
MessageElement. They contained proper code for serializing values, as w
Taras,
I have folded the function of your patch into my sandbox, but I wonder if
you could provide the rationale (e.g. what bug did it fix?).
I made some changes, which you may like to comment on:
1. I re-introduced SOAPHeader.outputImpl as the build failed without it.
2. In MessageElement, I
This is the patch we were talking about in chat.
set/getValue changed to set/getObjectValue()
-Taras
SOAPHeader.java
Description: Binary data
MessageElement.java
Description: Binary data
Constants.diff
Description: Binary data
Even though Axis is using SAX internally, it still creates a DOM like
structure from MessageElement object. Also all of the events are recorded.
This leads to cpu/memory utilization similar to that of DOM model. When an
object is deserialized from the Envelope, it is getting all of the events
27 matches
Mail list logo
