| Author |
Message |
 Topic: [Solved] Invalid Regular expression when importing xsd. |
juddg
Replies: 2
Views: 2087
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jul 19, 2006 1:42 am Subject: Problem with the dash (-) character |
Hi,
The problem appears to be with the dash characters at the end of the character class expressions. If the dash is intended to be interpretted literally it must be escaped because on its own it ... |
| Topic: MRM XML Validation Error Using Validate Node in WMB 6.0 |
juddg
Replies: 20
Views: 15209
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Jun 19, 2006 5:08 am Subject: Please log a service call |
Hi,
Please can you raise a service call with IBM for this problem quoting this post. The problem is specific to an empty element that is parsed as self-defining on input but is then subsequently m ... |
| Topic: MRM XML Validation Error Using Validate Node in WMB 6.0 |
juddg
Replies: 20
Views: 15209
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Jun 16, 2006 9:34 am Subject: Reproducible |
Hi,
I can reproduce te problem using either a java compute node or an ESQL compute node. However if I don't copy across the empty element from the input to the output but create it in the output w ... |
| Topic: MRM XML Validation Error Using Validate Node in WMB 6.0 |
juddg
Replies: 20
Views: 15209
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Jun 16, 2006 6:01 am Subject: Further clarification |
Hi,
When you say that you manipulate the incoming message do you create a new output message based on the values in the input message? It appears that the element in the tree has an unrecognised t ... |
| Topic: MRM XML Validation Error Using Validate Node in WMB 6.0 |
juddg
Replies: 20
Views: 15209
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Jun 16, 2006 1:56 am Subject: Clarification |
Hi,
This error is returned when attempting to serialize the message tree to the output rather than parsing an input message. Please can you clarify the nodes in your flow and ESQL and mappings tha ... |
| Topic: Namespaces in esql |
juddg
Replies: 4
Views: 4151
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 15, 2006 9:23 am Subject: Use XMLNSC.Attribute instead of XML.Attribute |
Hi,
As this is the XMLNSC domain also replace XML.Attribute with XMLNSC.Attribute.
Regards,
juddg. |
| Topic: Namespaces in esql |
juddg
Replies: 4
Views: 4151
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 15, 2006 9:02 am Subject: Do not put the namespace prefixes in quotes |
Hi,
Please try the following :
Set case1 = Coalesce(InputRoot.XMLNSC.sp:"Envelope".sp:"Body".n1:"CaseGetReply".n1:"CaseRequest".(XML.Attribute)caseNumberKey, 'Unknown');
Regards,
juddg |
| Topic: Problem with TDS Message Set |
juddg
Replies: 1
Views: 2731
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 13, 2006 7:10 am Subject: Try the following |
Hi,
Please try the following model (untested) :
MSG_TYPE
Composition: Ordered Set
Content Validation: Closed
Data Element Separation : Tagged Delimited
Delimiter & ... |
| Topic: Problem with parsing tagged delimited messages |
juddg
Replies: 18
Views: 14438
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 26, 2006 4:31 am Subject: Another thing to check |
Hi,
One thing I didn't make clear is that the F1 element should be removed as children of the messages in the model because all of the F1 element will be consumed by the tags of the messages.
... |
| Topic: Problem with parsing tagged delimited messages |
juddg
Replies: 18
Views: 14438
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu May 25, 2006 12:37 am Subject: Problem with parsing tagged delimited messages |
Hi,
There is no way of restricting a physical format to just part of a message set defintion. When you say:
This however creates a problem as it seems to be conflicting with the Physical Proper ... |
| Topic: Problem with parsing tagged delimited messages |
juddg
Replies: 18
Views: 14438
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed May 24, 2006 4:07 am Subject: Clarification |
Hi cloucas,
I think what jefflowrey means is to make the whole of the F1 field the tag for the messages. That is the tag and the value. From your description this value should be unique ... |
| Topic: Problem with parsing tagged delimited messages |
juddg
Replies: 18
Views: 14438
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue May 23, 2006 3:45 am Subject: Clarification |
Hi cloucas,
Please can you clarify the format of the data that your are parsing. Does each message have a tag or does the data look like?
[F1][F2][F3][F4][F1][F8][F9][F10][F1][F7][ ... |
| Topic: Repeating fields in an output CWF missing |
juddg
Replies: 8
Views: 5047
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue May 16, 2006 4:42 am Subject: Repeat Count |
Vitor,
If you look at the CWF properties for the reference to the Stockline element you whould see a Repeat Count field which should be set to 4 in your scenario. On write of the CWF format re ... |
| Topic: ASBITSTREAM returns 'oa' for empty MRM |
juddg
Replies: 2
Views: 2563
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Apr 27, 2006 1:58 am Subject: More information please |
Hi,
When you say the character 'oa' do you mean the line feed character hex '0a'. When you say you are running CSD 7 do you mean V5.0 CSD7 ? Is the message format you are using TDS? If you are usi ... |
| Topic: [URGENT] TDS message model |
juddg
Replies: 19
Views: 17183
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 18, 2006 2:40 am Subject: Combined message |
Hi,
Assuming that you want the data modelled in the following structure:
<a1>A1</a1>
<char>AAAA</char>
<char>BBBB</char>
.
.
The following model, ... |
