Issue Details (XML | Word | Printable)

Key: WODEN-142
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dan Harvey
Reporter: John Kaputin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Woden

<documentation> element should not be wrapped as java.lang.Object

Created: 07/Feb/07 02:42 AM   Updated: 14/Aug/07 09:38 AM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: M8

Time Tracking:
Not Specified

File Attachments:
  Size
Text File Licensed for inclusion in ASF works BaseWSDLReader.java.patch 2007-08-01 09:18 AM Dan Harvey 0.7 kB
Text File Licensed for inclusion in ASF works DocumentationElement.java.patch 2007-08-08 10:28 AM Dan Harvey 2 kB
Text File Licensed for inclusion in ASF works DocumentationElementTest.java.patch 2007-08-01 09:18 AM Dan Harvey 3 kB
Text File Licensed for inclusion in ASF works DocumentationImpl.java.patch 2007-08-01 09:18 AM Dan Harvey 1 kB
Text File Licensed for inclusion in ASF works WSDL20ToAxisBuilderl.java.patch 2007-08-08 01:38 PM Dan Harvey 1 kB

Resolution Date: 14/Aug/07 09:38 AM


 Description  « Hide
DocumentationElement has the methods set/getContent which wrap the <wsdl:documentation> element as a java.lang.Object. The convention in the Woden API for wrapping WSDL elements is to use XMLElement as the wrapper. At the very least this interface should use XMLElement. A better approach might be to represent mixed content in this interface.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
John Kaputin added a comment - 19/Jul/07 10:15 AM
I think it will be sufficient just to change DocumentElement API to represent the <document> element as an org.apache.woden.XMLElement, rather than java.lang.Object. However, I have posted to the woden-dev list to see if there are any particular requirements for handling mixed content directly from the DocumentElement API.

Dan Harvey added a comment - 01/Aug/07 09:07 AM
As there where no requests for any particular requirements to handle the content directly from the DocumentElement API I have changed the set/GetContent methods to use the XMLElement.

John Kaputin added a comment - 02/Aug/07 09:56 AM
Dan has contributed the fix, so assigning JIRA to him.

John Kaputin added a comment - 08/Aug/07 10:23 AM
Dan is going to check if the Axis2 codegen uses the documentation element and if so, what affect this JIRA has so that we can sync up any Axis2 code changes required.

Dan Harvey added a comment - 08/Aug/07 01:30 PM
There is only one place in the Axis2 code that they use the DocumentationElement which is in the file

/axis2/modules/kernel/src/org/apache/axis2/description/WSDL20ToAxisServiceBuilder.java

this uses getContent() to get an Object then cast it to a org.w3c.dom.Element object. This just needs one line adding to get the Element out of our XMLElement holder.

I've attached a patch to this Jira which would do this for them.

John Kaputin added a comment - 12/Aug/07 10:54 PM
I have confirmed with Keith Chapman that this fix is OK. Will apply the Woden patches, then notify him to apply the patch for the Axis2 codegen (WSDL20ToAxisServiceBuilder).

John Kaputin added a comment - 12/Aug/07 11:58 PM
r565209
DocumetationElement
DocumentationElementTest
DocumentationImpl
BaseWSDLReader

(WSDL20ToAxisServiceBuilder patch to be applied next)

Keith Godwin Chapman added a comment - 13/Aug/07 05:27 AM
Fixed Axis2 Build. Thanks for the patch Dan.