| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| soapenc:Array |
View previous topic :: View next topic |
| Author |
Message
|
| shashivarungupta |
 Posted: Tue Nov 11, 2014 5:03 pm Post subject: soapenc:Array |
 |
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Hi,
It's related to a very old versions of WebLogic service (v8.x), which is having a .wsdl and .xsd file, which now needs to be exposed in WMB at SOAPInput Node.
But as soon as I get that .wsdl imported, it throws some warnings and *errors* saying "CTDX1100E : XSD: Attribute reference 'http://schemas.xmlsoap.org/soap/encoding/#arrayType' is unresolved xyz.xsd /xyzLibrary line 19 XSD Schema Validation Problem"
AND
"CTDX1100E : XSD: Type reference 'http://schemas.xmlsoap.org/soap/encoding/#Array' is unresolved xyz.xsd /xyzLibrary line 3 XSD Schema Validation Problem"
The detailed problem that WMB reflects is :
“src-resolve.4.2: Error resolving component 'soapenc:Array'. It was detected that 'soapenc:Array' is in
namespace 'http://schemas.xmlsoap.org/soap/encoding/', but components from this namespace are not
referenceable from schema document 'file:///D:/apps/IBM/wmbt80/workspace2/xyzLibrary/
xyz.xsd'. If this is the incorrect namespace, perhaps the prefix of
'soapenc:Array' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag
should be added to 'file:///D:/apps/IBM/wmbt80/workspace2/xyzLibrary/
xyz.xsd'.”
I hit "http://schemas.xmlsoap.org/soap/encoding/" in explorer, to check if that namespace is correct and exists. Which actually does.
Because this is an older version of WebLogic Service, which might cost thousands of dollars to get it upgraded to latest version of schema model wherever it is in production.
As a concern, if that older Service is exposed by WMB SOAPInput node, is there any wayout which can be used to fix this without changing the existing schema model and wsdl definitions ?
WMB v8.0.0.1 is in use.
Kindly suggest !!
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
 |
| mgk |
| Posted: Wed Nov 12, 2014 12:48 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
You could always use the SOAPInput node in Gateway mode - then you do not need to use a WSDL. Alternatively you could raise a PMR to get the WSDL checked out if you think there is an error with the SOAP Input node...
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed Nov 12, 2014 2:20 pm Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
Or
I might use HTTPInput/Reply and HTTPRequest Node incase of Facade Service, where Validation is not the Criteria.
But needs to deal with Message Transformation before & after the HTTPRequest call, supposing the response received after HTTPRequest is having an Array of elements as per the schema model.
Might be, have to deal with those Array elements in the Response message (from HTTPRequest) before HTTP Reply is sent to Client, using ESQL as per the comments in this link1 or link2
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
|
|
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
