| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Websphere ESB custom java transform - how? |
« View previous topic :: View next topic » |
| Author |
Message
|
| seingbe |
 Posted: Tue Feb 28, 2012 1:44 am Post subject: Websphere ESB custom java transform - how? |
 |
|
Newbie
Joined: 23 Feb 2012
Posts: 2
|
Hi guys,
I'm having trouble using custom java transforms in my mediation. I've probably missed something, but have not found any hints googling/browsing ESB documentation.
My scenario:
I'm creating a mediation between two xml formats, and need to use some Custom transforms.
(For example, to add days to a date)
To achieve this I'm using a Java class in a separate Java project.
I create a Custom Java transform in my mediation, and point this to my Java class, and the appropriate method.
So far so good.
However, when publishing and running the mediation on the test environment, I get this error:
CWSXM0202E: An unexpected exception occurred when processing mediation flow for component "MyMediation"
in module "MyModule": CWSXM1025E: An unexpected exception occurred when the flow was called:
IXJXE0920E: [ERR API0136] Execution terminated because of the following error:
'IXJXE0394E: [ERR 0343] The processor is unable to resolve a reference to the Java method 'GetDueDateDefault'.;
SystemID: xsltcl:/xslt/input_map_req_1.xsl; Line#: 111; Column# 85
The mediation project has a dependency on the Java project, and is set to deploy it with the module.
The Java project is also a ticked as a project reference in the mediation project.
Exporting the project to an .EAR-file and installing it through the server console gives the same result.
Target environment is Websphere ESB Server 7.5
What am I missing? All help appreciated!  |
|
| Back to top |
|
 |
| seingbe |
| Posted: Tue Apr 10, 2012 3:09 am Post subject: Problem solved |
|
|
Newbie
Joined: 23 Feb 2012
Posts: 2
|
Finally managed to get a proper response for my PMR on this matter.
I find the error message misleading, since I assumed the deployed application was unable to call the java method at all.
Instead, it is because the java method was defined using the wrong parameter data type.
All data from the message is extracted to String, regardless of datatype in the xml schema. After changing my method to use String parameter instead of Date I was able to call it.
Hope this helps someone else. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
