| Author |
Message |
 Topic: Wildcard element processing fails in MRM |
cjr8020
Replies: 7
Views: 3944
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 24, 2009 3:47 pm Subject: Wildcard element processing fails in MRM |
Kimbert, appreciate your recommendations. Evaluating which route to go.
Just tested switching off validation in the output node, unfortunately, that did not prevent the parse exception - so same o ... |
| Topic: Wildcard element processing fails in MRM |
cjr8020
Replies: 7
Views: 3944
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jun 24, 2009 10:34 am Subject: Wildcard element processing fails in MRM |
| Let me try to describe the problem a little better. The idea was to use an element wildcard as a child of "Body" to allow any element in any namespace to be used in its place. Actually, a ... |
| Topic: Wildcard element processing fails in MRM |
cjr8020
Replies: 7
Views: 3944
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 23, 2009 3:10 pm Subject: Wildcard element processing fails in MRM |
MQSI 6.0.0.8
I have a message envelope defined in an XSD. It has a body element defined in a manner that is nearly identical to soap-envelop 1.2:
Body->sequence->any wildcard ##any
When I ... |
| Topic: Problem with attributes |
cjr8020
Replies: 9
Views: 5840
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jan 21, 2009 6:05 pm Subject: Problem with attributes |
| User trace showed that every element and attribute in the input message was self-defining. I then rebuilt the message set from scratch; and, of course, everything is good - nothing is self-defining a ... |
| Topic: Problem with attributes |
cjr8020
Replies: 9
Views: 5840
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jan 20, 2009 6:33 pm Subject: Problem with attributes |
Having a similar issue.
runtime 6.0.0.8
toolkit 6.0.2
Working in MRM domain. I had trouble accessing XML attributes with ESQL code. Debuging showed that these attributes appeared with the '@' s ... |
| Topic: noNamespaceSchemaLocation using MRM domain |
cjr8020
Replies: 10
Views: 8141
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 25, 2008 5:18 pm Subject: noNamespaceSchemaLocation using MRM domain |
Indeed. This code is simpler and works just as well.
Thanks, kimbert. |
| Topic: noNamespaceSchemaLocation using MRM domain |
cjr8020
Replies: 10
Views: 8141
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Nov 25, 2008 10:09 am Subject: noNamespaceSchemaLocation using MRM domain |
In ESQL, here's the only way I've found so far to specify noNamespaceSchemaLocation attribute:
DECLARE xsi NAMESPACE 'http://www.w3.org/2001/XMLSchema-instance';
SET OutputRoot.MRM.(XMLN ... |
| Topic: noNamespaceSchemaLocation using MRM domain |
cjr8020
Replies: 10
Views: 8141
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 24, 2008 5:53 pm Subject: noNamespaceSchemaLocation using MRM domain |
Toolkit 6.0.2 IFix 016
MQSI runtime 6.0.0.8
This matches the exact issue I'm facing. By default, I'm getting
<SomeElement xmlns:xsd=".." xmlns:xsi="..">
... |
