Hi,
This post is for all of those that are struggling with the Web Service Data Control and especially the xsd:attribute tag.
I just came across with a problem where a Web Service Data Control was fetching empty data in the ADF 11g page. The scenario was pretty simple actually. There was a web Service deployed on a Web Logic Server and there was a sample ADF application where a Web Service Data Control was created based on the wsdl. The creation of the Web Service Data Control was pretty straightforward, no policies or detailed configurations.
I examined the schema of the wsdl in detail and one element had a complexType with xsd:attribute.
The actual element that had the problem.
I could not see any issue either in the wsdl or the Data Control and the page.
So I decided to experiment a bit and changed the xsd:attribute to xsd:element. Then I mocked the service with soapui and created a different sample application.
The problem was resolved. I could see my data properly.
So I started digging a bit more and I found out that there is a bug logged for the Human Task Data Control.
The case mentioned above is identical with the case of Web Service Data Control. So we wait for the fix.
The purpose of this post is to help people that came across with this issue and are actually stuck for days not knowing the problem.
Given that, we should try to find workarounds..... you spin me right round
Of course, the work around will be based on the project's needs.. so it is up to you..
Cheers!
This post is for all of those that are struggling with the Web Service Data Control and especially the xsd:attribute tag.
I just came across with a problem where a Web Service Data Control was fetching empty data in the ADF 11g page. The scenario was pretty simple actually. There was a web Service deployed on a Web Logic Server and there was a sample ADF application where a Web Service Data Control was created based on the wsdl. The creation of the Web Service Data Control was pretty straightforward, no policies or detailed configurations.
I examined the schema of the wsdl in detail and one element had a complexType with xsd:attribute.
The actual element that had the problem.
I could not see any issue either in the wsdl or the Data Control and the page.
So I decided to experiment a bit and changed the xsd:attribute to xsd:element. Then I mocked the service with soapui and created a different sample application.
The problem was resolved. I could see my data properly.
So I started digging a bit more and I found out that there is a bug logged for the Human Task Data Control.
Bug 14063990 : ATTRIBUTES
IN XML DOCUMENT ARE NOT WELL SUPPORTED IN ADF HUMAN TASK DATA CONTROL
The case mentioned above is identical with the case of Web Service Data Control. So we wait for the fix.
The purpose of this post is to help people that came across with this issue and are actually stuck for days not knowing the problem.
Given that, we should try to find workarounds..... you spin me right round
Of course, the work around will be based on the project's needs.. so it is up to you..
Cheers!
