| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| user exception (mapped from WSDL's wsdl:fault construct) |
« View previous topic :: View next topic » |
| Author |
Message
|
| rekarm01 |
 Posted: Sun Nov 09, 2008 3:46 pm Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
I don't see anything wrong with the mxsd you posted. I have no trouble using it with Content Assist.
Perhaps there's a problem with your workspace or toolkit state. You might try one or more of the following:- clean your message flow and message set projects (Project -> Clean)
- restart your toolkit with "-clean" option
- delete your message flow and message set projects from your workspace, (do not remove files), and reimport them
- create a new workspace and import your projects there
| simon.starkie wrote: |
I have a ResetContentDescriptor wired to the Error terminal of the HTTP Request Node. The ResetContentDescriptor has:
Message domain = to MRM : For binary, text or XML messages (namespace aware, validation, low memory use)
Reset message domain = checked
Message set = MDESimulatorMessageSet (EIR443S002001)
Reset message set = checked
Message type = blank (i.e. not set...I've tried XML but no difference)
Reset message type = checked |
"XML" is not normally one of your choices. Your drop-down list should be populated with message types like "Envelope", "Fault", or "KpSystemException". In this case, "Envelope" is probably the one you want.
| simon.starkie wrote: |
Message format = blank (i.e. not set...I've tried XML1 but no difference)
Reset message format = checked |
For SOAP Envelopes, "XML1" is probably the one you want. |
|
| Back to top |
|
 |
| simon.starkie |
| Posted: Sun Nov 09, 2008 7:59 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
| rekarm01 wrote: |
I don't see anything wrong with the mxsd you posted. I have no trouble using it with Content Assist.
Perhaps there's a problem with your workspace or toolkit state. You might try one or more of the following:- clean your message flow and message set projects (Project -> Clean)
- restart your toolkit with "-clean" option
- delete your message flow and message set projects from your workspace, (do not remove files), and reimport them
- create a new workspace and import your projects there
| simon.starkie wrote: |
I have a ResetContentDescriptor wired to the Error terminal of the HTTP Request Node. The ResetContentDescriptor has:
Message domain = to MRM : For binary, text or XML messages (namespace aware, validation, low memory use)
Reset message domain = checked
Message set = MDESimulatorMessageSet (EIR443S002001)
Reset message set = checked
Message type = blank (i.e. not set...I've tried XML but no difference)
Reset message type = checked |
"XML" is not normally one of your choices. Your drop-down list should be populated with message types like "Envelope", "Fault", or "KpSystemException". In this case, "Envelope" is probably the one you want.
| simon.starkie wrote: |
Message format = blank (i.e. not set...I've tried XML1 but no difference)
Reset message format = checked |
For SOAP Envelopes, "XML1" is probably the one you want. |
That is interesting that it works for you with the same mxsd.
As a matter of fact, I did create a brand new workspace,
just last week when I started this exercise,
before I imported the WSDL to create the Message Set.
But I have not tried -clean so I'll do that next week.
Thanks for the suggestion.
The examples I previously mentioned were related to MRM.
I was using MRM instead of XMLNSC in an attempt to find a workaround.
As Kimbert indicated, message sets should work with all domains.
And we'd prefer to stick with XMLNSC because of it's significant performance improvements over XMLNS and XML parsers.
We have some rather huge HL7V3 WSDL's that inherit from many, many HL7V3 schemata.
So we need all the performance we can get for that...if the wsdl import doesn't run out of memory as it used to do before the fixpack. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Mon Nov 10, 2008 9:20 am Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
Restarted toolkit with "-CLEAN".
But same problem.
Content Assist gets as far as KpSystemException but no further...
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.soapenv:Fault.detail.ns:KpSystemException
What version of fixpacks do you have?
Mine is Message Broker 6.0.2 Interim Fix 010 . |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Mon Nov 10, 2008 9:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| simon.starkie wrote: |
What version of fixpacks do you have?
Mine is Message Broker 6.0.2 Interim Fix 010 . |
I was going to suggest "update your toolkit" as another option, but I thought you might have tried that already.
I'm using Message Broker 6.0.2 Interim Fix 015. |
|
| Back to top |
|
|
| simon.starkie |
| Posted: Mon Nov 10, 2008 2:19 pm Post subject: |
|
|
Disciple
Joined: 24 Mar 2002
Posts: 180
|
The problem is solved after downloading/installing:
WebSphere Message Broker Toolkit Version 6.0.2 Cumulative Interim Fix 016
and creating a brand new workspace
and re-importing the wsdl to create a fresh MessageSet
Content Assist is now able to resolve elements within KpSystemException, including:
-- FIX 016 test
SET OutputRoot.XMLNSC.soapenv:Envelope.soapenv:Body.soapenv:Fault.detail.ns:KpSystemException.hostName
= 'NewHostValue';
Thanks for the help  |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
