| Author |
Message |
 Topic: Call a java function from esql code in WMB v8.0 |
rock33
Replies: 5
Views: 6623
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Mon Oct 07, 2013 6:54 am Subject: Call a java function from esql code in WMB v8.0 |
Thanks mqjeff.
I have placed .jar file into shared-classes only. |
| Topic: Call a java function from esql code in WMB v8.0 |
rock33
Replies: 5
Views: 6623
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Oct 07, 2013 6:25 am Subject: Call a java function from esql code in WMB v8.0 |
Thanks a lot lancelotlinc for spotting the minor bug.
Its is working fine. |
| Topic: Call a java function from esql code in WMB v8.0 |
rock33
Replies: 5
Views: 6623
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Oct 07, 2013 5:50 am Subject: Call a java function from esql code in WMB v8.0 |
Hi All,
I am trying to call user defined java function from esql.
I have created an Message broker application and added the java project (Myutil)as an project reference.
Once the bar file ha ... |
| Topic: Java call from XSLT v1.0 |
rock33
Replies: 6
Views: 5189
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Oct 06, 2013 9:02 am Subject: Java call from XSLT v1.0 |
I did apply the latest fix pack (i.e,)v8.0.0.2 for both toolkit and WMB runtime but no use getting the same exception.
Have have one tryied user defined java call from xsl in WMB v8? |
| Topic: Java call from XSLT v1.0 |
rock33
Replies: 6
Views: 5189
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Oct 06, 2013 4:39 am Subject: Java call from XSLT v1.0 |
Hi Iam getting the below exception while tryig to call user defined java funtion from xslt in Websphere message broker v8.0.0.1.
Exception:
(Location of error unknown)javax.xml.transform.Transform ... |
| Topic: No compatible processor is found for XSLT version 2.0 |
rock33
Replies: 6
Views: 6184
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Oct 03, 2013 2:22 am Subject: No compatible processor is found for XSLT version 2.0 |
| Thanks for the updates so far. |
| Topic: No compatible processor is found for XSLT version 2.0 |
rock33
Replies: 6
Views: 6184
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 02, 2013 6:50 am Subject: No compatible processor is found for XSLT version 2.0 |
Thanks a lot lancelotlinc.
If XSLT 2.0 is not yet ready to use in WMB v8.0.0.2 why they put into the supported releases in Version 8.0.
Any comment from IBM folks would be appreciated. |
| Topic: No compatible processor is found for XSLT version 2.0 |
rock33
Replies: 6
Views: 6184
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Oct 02, 2013 5:44 am Subject: No compatible processor is found for XSLT version 2.0 |
Hi All,
I am using WMB Toolkit v8.0.0.2 and WMB runtime v8.0.0.2
I have tried to run .xsl file from WMB toolkit. Under the processor tab its says this error message ' No compatible processor is ... |
| Topic: Parsing '&' in Esql code |
rock33
Replies: 9
Views: 12325
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Sep 26, 2013 6:05 am Subject: Parsing '&' in Esql code |
| Thanks jsware for the Explanation. |
| Topic: Parsing '&' in Esql code |
rock33
Replies: 9
Views: 12325
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Sep 23, 2013 4:53 am Subject: Parsing '&' in Esql code |
Use the following line instead:
SET OutputRoot.XMLNSC.name.(XMLNSC.Attribute)ID = '&en';
Have you tested jsware the above line of code? |
| Topic: Parsing '&' in Esql code |
rock33
Replies: 9
Views: 12325
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Sep 22, 2013 11:48 am Subject: Parsing '&' in Esql code |
Thanks for the reply fjb_saper.
My target is fileOutput node.
Below is the line in the compute node.
SET OutputRoot.XMLNSC.name.(XMLNSC.Attribute)ID = '&en';
Outcome :
<name I ... |
| Topic: Parsing '&' in Esql code |
rock33
Replies: 9
Views: 12325
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Sep 22, 2013 11:18 am Subject: Parsing '&' in Esql code |
Hi
Is anyone knows how to parse '&' to the target xml. It is an hardcoded value at the compute node and the incoming parser is XMLNSC.
Ex:
Source attribute: <name id='&en' />
... |
