Access to Message esbMessage = SOAPProcessor.getMessage();

[alcanrom]

Hello,

     I have a problem with a webservice on ESB, we want to integrate two systems and I have created a web service to do transformations with smook in ESB. I used webservice_producer quickstar to do my webservice. I have my webservice on but i have a problem, I don´t know how to pass information to the webservice. I have seen that you can use a xml but message in the webservice logic is not ESB-AWARE, and if I try to modify ESB-AWARE with:

               Message esbMessage = SOAPProcessor.getMessage();

In the webservice is failing, is null the SOAPProcessor and I can not modify ESB-AWARE for the next action use this xml format.

Other question is:

     When you are developing a webservice on ESB, you have to create a folder webservice.war to public the webservice, are there some automatic procces to do this task?.

Thanks...

[mageshbk]

Hi,

Message esbMessage = SOAPProcessor.getMessage();

This feature has been removed. [JBESB-3567] Remove thread local use within SOAPProcessor. You should not rely on this any longer.

When you are developing a webservice on ESB, you have to create a folder webservice.war to public the webservice, are there some automatic procces to do this task?.

Yes. If you use our IDE, JBoss Developer Studio, you can create the webservice war files with easy clicks of button.

[alcanrom]

Hi Magesh, if I want to access to ESB Message from webservice how can I do it?

I need proccess in message in a webservice and I want to build ESB-Message from code of the webservice and in the next action proccess it. I pass data in a variable message more or less webservice_producer quickstart, and if I want to acces to the ESB Message I need use the sentence, Message esbMessage = SOAPProcessor.getMessage();

I don´t understand your response.

About the second, Ho can i do it? , I am using JBOSS DEVELOPER STUDIO and I have to create the folder XXXXX_war in esbcontent and when I compile the class put the class file in the folder.

Thanks for your response.

[hongan]

I'm also having this problem. Would like to know if someone can help?

[mageshbk]

It is a bad design to tightly-couple the Webservice being called with the ESB service that is invoking it. The reason being that the Webservice can be running in an entirely different server. That said, one can serialize the message information to a Database, File or even send it to a JMS Queue which is accessible by both the Webservice and the ESB service. Remember that now the Message is de-coupled from the Webservice point of view, as any changes to that object will not be visible to the ESB service. You can see the helloworld series quickstarts for further help on these sql, jms and file actions.