| Author |
Message |
 Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Aug 04, 2014 1:23 pm Subject: Special Char causing evaluateXPath to fail |
Thanks fjb_saper & kimbert..after posting a reply I realized what was being told  this is superb, code is working now - so basically root cause was two things
1) String to bytes - that needs a ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Aug 04, 2014 11:44 am Subject: Special Char causing evaluateXPath to fail |
Sry Kimbert.. didnt get what u said, what is issue with msgAsText.getBytes() ?
//Now create outBody again
outBody = outRoot.createElementAsLastChildFromBitstream(msgAsText.getBytes(), ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 01, 2014 7:37 am Subject: Special Char causing evaluateXPath to fail |
Interesting thing is when i change the code to
msgAsText = String.format((new StringBuilder("%-")).append(rec.getMaxPadLength()-1).append("s&qu ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jul 31, 2014 8:48 pm Subject: Special Char causing evaluateXPath to fail |
Yes changing model will need a complete rewrite of code at different places. Btw I didnt code that
Back to the problem - Kimbert that's a very good point on String constructor, I changed code to ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jul 30, 2014 1:47 pm Subject: Special Char causing evaluateXPath to fail |
Jeff I cant change the model as of now 
Without a special char this works like a charm... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jul 30, 2014 12:26 pm Subject: Special Char causing evaluateXPath to fail |
Vitor - yes the requirment is that clients can send the last element in the message set of variable length, so the size of input message may vary but the max will be always 1697.
While converting t ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Jul 30, 2014 11:25 am Subject: Special Char causing evaluateXPath to fail |
Hi Kimbert - below are more details
Incoming fixed length message is of size 1209, so we need to first convert that to size 1697 to match msg set size
//Convert incoming message to bytes
byte[ ... |
| Topic: Special Char causing evaluateXPath to fail |
deepeshk79
Replies: 18
Views: 11618
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jul 29, 2014 2:02 pm Subject: Special Char causing evaluateXPath to fail |
Hi - below is an issue that we are getting while doing an xpath on a parsed FLM message with message set.
Code is
List<MbElement> mbElements = (List<MbElement>) rootElmt.getLa ... |
| Topic: Very strange issue with CURRENT_TIMESTAMP |
deepeshk79
Replies: 18
Views: 15743
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Aug 28, 2011 6:24 am Subject: Current_TimeStamp issue in ESQL |
I'm posting this in response to an old thread, so apologies for that, but we too are facing the same problem with TimeStamp
The details are as below
--Compute Node 1 - display Time Stamp (using en ... |
| Topic: Extracting CDATA in a Java Compute Node |
deepeshk79
Replies: 3
Views: 3626
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 22, 2010 1:55 pm Subject: Extracting CDATA in a Java Compute Node |
Hi All,
I have an input message as below
Sample Response Message:
<?xml version="1.0" encoding="UTF-8"?>
<?ABHeader version="1.0"?>
<?ABEnve ... |
| Topic: Attaching an element to existing xml in Java Compute node |
deepeshk79
Replies: 2
Views: 2784
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Jan 08, 2010 6:02 pm Subject: Attaching an element to existing xml in Java Compute node |
| Thanks for the help. The code worked..... |
| Topic: Move statement issue |
deepeshk79
Replies: 22
Views: 17228
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 07, 2010 9:34 am Subject: Move statement issue |
| Thanks rekarm01 and fjb_saper. The links that you provided has the details, the earlier link didnt talk about the MOVE statement failing with TYPE XMLNSC.Element. I think Vitor has a habit of reading ... |
| Topic: Attaching an element to existing xml in Java Compute node |
deepeshk79
Replies: 2
Views: 2784
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jan 07, 2010 9:30 am Subject: Attaching an element to existing xml in Java Compute node |
I am facing an issue in adding a string as an MbElement. That string will be having tags.
String docString = "<check>asdfsdafdfdf</check>";
Input XML is as below:
< ... |
| Topic: Move statement issue |
deepeshk79
Replies: 22
Views: 17228
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Dec 28, 2009 6:32 pm Subject: Move statement issue |
| Vitor I did read all the above posts in this thread and as per the link that you gave, it says we can use XMLNSC.Element to point to elements within a Parent tag. Only XMLNSC.Field has a limitation as ... |
| Topic: Move statement issue |
deepeshk79
Replies: 22
Views: 17228
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Dec 28, 2009 6:21 pm Subject: Move statement issue |
Jeff,
As per fjb_saper,
As for the syntax I thought you had to include it in () like "Type (XMLNSC.Element) "
Even if we have (), the error is still there.
Also in the link p ... |
