| Author |
Message |
 Topic: EG become hang state |
Sovesky
Replies: 7
Views: 11337
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu Dec 26, 2013 2:09 am Subject: EG become hang state |
| Curiously, all of a sudden I'm having the same issue on a DEV installation. It happened with a simple broker stop-start. |
| Topic: Graphical Mapping - Filter unexistant elements |
Sovesky
Replies: 2
Views: 2085
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Nov 29, 2013 9:57 am Subject: Graphical Mapping - Filter unexistant elements |
Hello all,
I'm using MB 8.0.0.2 and I'm having a problem using graphical mapping and xpath.
Imagine I want to map a text element to the leaf of the following tree (Level3):
Level1.Level2.Leve ... |
| Topic: MB Toolkit Test - Invalid XML character 0xffffffff |
Sovesky
Replies: 11
Views: 6994
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 18, 2013 5:32 am Subject: MB Toolkit Test - Invalid XML character 0xffffffff |
I was copy-pasting my input XML on the the Text Editor, and getting that error.
I tried saving an .xml file encoded with UTF-8 and sending it to the Message Broker Test Client instead of just copyi ... |
| Topic: MB Toolkit Test - Invalid XML character 0xffffffff |
Sovesky
Replies: 11
Views: 6994
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 18, 2013 3:56 am Subject: MB Toolkit Test - Invalid XML character 0xffffffff |
Are you sure it's complaining about the description element?
100% sure. If I replace "Não" with "Nao" I can easily run my flow without a problem.
Are you sure the XML docume ... |
| Topic: MB Toolkit Test - Invalid XML character 0xffffffff |
Sovesky
Replies: 11
Views: 6994
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 18, 2013 3:27 am Subject: MB Toolkit Test - Invalid XML character 0xffffffff |
Your XML does not pass validation : </int0:tipo> vs </int0:type>
It was a typo. My message is bigger than that, and in this post I decided to translate it from portuguese to english. An ... |
| Topic: MB Toolkit Test - Invalid XML character 0xffffffff |
Sovesky
Replies: 11
Views: 6994
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 18, 2013 3:16 am Subject: MB Toolkit Test - Invalid XML character 0xffffffff |
I want to test a web service I'm developing, using the "Test..." feature of WMB Toolkit 8.0.0.2.
The input to my web service:
<?xml version="1.0" encoding="UTF-8&qu ... |
| Topic: User Defined Properties - must specify an initial value... |
Sovesky
Replies: 16
Views: 10373
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 11, 2013 8:24 am Subject: User Defined Properties - must specify an initial value... |
{Rhetorical} What is to be gained by placing all ESQL code in a single file? Not much.
Now I get it. I'm not putting all ESQL code into a single file, but at the same time I'm not modulating it i ... |
| Topic: User Defined Properties - must specify an initial value... |
Sovesky
Replies: 16
Views: 10373
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 11, 2013 6:08 am Subject: User Defined Properties - must specify an initial value... |
mqjeff,
No it's not, I'm just trying to understand the problem.
lancelotlinc,
1. I understand that using the default schema is not advised because everything will be included with every node ... |
| Topic: User Defined Properties - must specify an initial value... |
Sovesky
Replies: 16
Views: 10373
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 11, 2013 3:45 am Subject: User Defined Properties - must specify an initial value... |
| But should this be a problem since I'm declaring it a Module level? |
| Topic: User Defined Properties - must specify an initial value... |
Sovesky
Replies: 16
Views: 10373
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Sep 11, 2013 3:36 am Subject: User Defined Properties - must specify an initial value... |
Hi all,
Using MB 8.0.0.2 I’m experiencing a strange behavior with User Defined Properties. In my main flow, I’m using a single UDP that is mandatory and type string, named deployEnvironment.
... |
| Topic: SOAP Request - Namespaces declaration |
Sovesky
Replies: 15
Views: 10118
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Sep 01, 2013 7:11 am Subject: SOAP Request - Namespaces declaration |
| Problem solved. It was indeed a namespace declaration problem. Using the OutputRoot.SOAP.Context.Namespace approach I was able to send my message to the webservice. Now I feel stupid for this, but as ... |
| Topic: SOAP Request - Namespaces declaration |
Sovesky
Replies: 15
Views: 10118
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 30, 2013 7:50 am Subject: SOAP Request - Namespaces declaration |
'gen.FileNetWS.Throw' node is not in my service, but in the destination service that I'm calling. The error I receive when I do a SOAP Request to that service, comes from that Throw node. 
I'm so ... |
| Topic: SOAP Request - Namespaces declaration |
Sovesky
Replies: 15
Views: 10118
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 30, 2013 7:39 am Subject: SOAP Request - Namespaces declaration |
| Yes, that's what I did. But the Throw node resides in the destination service. After the SOAP Request fails, I've put a trace after it with the Exception Tree and Root, giving me what I have in block ... |
| Topic: SOAP Request - Namespaces declaration |
Sovesky
Replies: 15
Views: 10118
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 30, 2013 7:16 am Subject: SOAP Request - Namespaces declaration |
Unfortunately I don't have access to my destination service. I only have access to the start and rollback monitors of the soap input node.
The throw node is basically the SOAP Input catch handler. ... |
| Topic: SOAP Request - Namespaces declaration |
Sovesky
Replies: 15
Views: 10118
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 30, 2013 6:28 am Subject: SOAP Request - Namespaces declaration |
The exception I'm getting is:
Fault
faultcode:CHARACTER:soapenv:Server
faultstring
detail
Text:CHARACTER:BIP3001I: Exception thrown by throw node 'gen.FileNetWS.Th ... |
