tag:blogger.com,1999:blog-6003063374827736283.post2321230578143520802..comments2010-06-03T22:09:34.944-07:00Paul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-6003063374827736283.post-41333871275089868572010-06-03T22:09:34.944-07:002010-06-03T22:09:34.944-07:00You will need to copy the sandesha2.mar into the client repo under the modules directory and then the Axis client will find it once it is engaged.Dizzyhttp://www.blogger.com/profile/06682730637849313537noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-80620705312122607522010-06-01T17:53:41.419-07:002010-06-01T17:53:41.419-07:00Hi,<br /><br />I am using Axis 2.1.4 and Sandesha 2.1.3.<br /><br />I created a dir Client_Repo, placed the axis2.xml and added the ref to sandesha2.<br />I also created modules folder and placed the sandesha mar file in it.<br /><br />When I create the ConfigurationContext instance I always get the below error.<br />org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: sandesha2<br /> at org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:464)<br /> at org.apache.axis2.engine.AxisConfiguration.engageGlobalModules(AxisConfiguration.java:591)<br /> at org.apache.axis2.deployment.DeploymentEngine.engageModules(DeploymentEngine.java:615)<br /> at org.apache.axis2.deployment.FileSystemConfigurator.engageGlobalModules(FileSystemConfigurator.java:142)<br /> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:81)<br /> at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContextFromFileSystem(ConfigurationContextFactory.java:184)Error meassage in CPS :The system is attempting to engage a module that is not available: sandesha2<br /><br />Could anyone pleas help me out?nagraj.http://www.blogger.com/profile/17131421906564253609noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-35885184948783803142007-09-19T14:24:00.000-07:002007-09-19T14:24:00.000-07:00Thanks a lot that´s the answer i needed. I newer in this i was wondering that my problems are because the bindings. So i needed to confirm mi doubts.<BR/><BR/>Regards<BR/>Yuli Noriega.yulihttp://www.blogger.com/profile/05283582419366489019noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-36273037081018564862007-09-19T11:33:00.000-07:002007-09-19T11:33:00.000-07:00I can't run the example, it throws me the following exception when i do the call to the stub:<BR/><BR/>2007-09-19 20:29:11,968 WARN [SenderWorker] <B>Sandesha2 sender thread has not received a valid synchronous response.</B><BR/>java.lang.NullPointerException<BR/> at org.apache.axis2.engine.HTTPLocationBasedDispatcher.findOperation(HTTPLocationBasedDispatcher.java:51)<BR/> <BR/>I'm pretty desperate. I don't know to do.<BR/><BR/>RegardsJosé Miguelhttp://www.blogger.com/profile/00958369793837679822noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-44736862329363812362007-09-19T08:32:00.000-07:002007-09-19T08:32:00.000-07:00Yuli<BR/><BR/>You cannot use RM with the HTTP binding as this is not a SOAP message. WSRM needs SOAP to add the RM headers.<BR/><BR/>Can you trace the messages using TCPMON? That would help figure out the problem.<BR/><BR/>PaulPaulhttp://www.blogger.com/profile/04602015245105431809noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-72742246347566459162007-09-18T17:50:00.000-07:002007-09-18T17:50:00.000-07:00Another thing i forgot to tell you is that i tried your sample with the binding soap11 and soap12 and it goes well, but with HttpportStub it doesn´t run (this is because the Web Service i need is binding with HttpportStub ). So i modified the binding as soap12 and it ran ok, i did the same with my Web Service but it has the same exception.yulihttp://www.blogger.com/profile/05283582419366489019noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-56863390711084177842007-09-18T17:44:00.000-07:002007-09-18T17:44:00.000-07:00Sip, before engage sandesha my Web Service run without any problem but when i engage it, is when the problem appears, everything seems ok until i write "stub._getServiceClient().getOptions().setProperty("Sandesha2LastMessage","true");"<BR/>But when i execute the method in order to get the result is when the client wait a few seconds and then it trhows the exception.yulihttp://www.blogger.com/profile/05283582419366489019noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-76613580514948149572007-09-18T17:43:00.000-07:002007-09-18T17:43:00.000-07:00Sip, before engage sandesha my Web Service run without any problem but when i engage it, is when the problem appears, everything seems ok until i write "stub._getServiceClient().getOptions().setProperty("Sandesha2LastMessage","true");"<BR/>But when i execute the method in order to get the result is when the client wait a few seconds and then it trhows the exception.yulihttp://www.blogger.com/profile/05283582419366489019noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-39001095176886063712007-09-18T15:30:00.000-07:002007-09-18T15:30:00.000-07:00Yuli<BR/><BR/>The complexity of the message should make NO difference to Sandesha and WSRM. The main question I would ask you is "does the service work BEFORE you add WSRM?". <BR/><BR/>If you get the service working without RM then it should also work with it.<BR/><BR/>PaulPaul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-71215210453785559622007-09-18T15:19:00.000-07:002007-09-18T15:19:00.000-07:00Hi Paul<BR/><BR/>Your sample was very interesting. But i need to know how to engage sandesha with a sample more complicated. I ran your sample and in goes well. But when i wanted to engage sandesha in a Web Service that return an object whose atributes are a number and a description i got the error "Time out while waiting for the server to send the response." and in the log server in seems that the problem is with the sincronization of the threads.<BR/>I would like to know if you could provide a sample with more complexity. And of course if something is missing in my sample and you have and idea i appreciate if you can tell me some about it.<BR/><BR/>Regards<BR/>Yuli Noriegayulihttp://www.blogger.com/profile/05283582419366489019noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-33226073555878180162007-05-22T04:36:00.000-07:002007-05-22T04:36:00.000-07:00Hello Paul,<BR/>Yes, You are correct. -uw was not specified when I generated stubs. Thanks for the information :)<BR/>regards<BR/>CharithaCharithahttp://www.blogger.com/profile/00209392844529688942noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-6082307895879842152007-05-22T04:15:00.000-07:002007-05-22T04:15:00.000-07:00Charitha<BR/><BR/>I think you must have left off the option -uw (Unwrap) when you created the Stub. The get_return() is a wrapping of the response type.<BR/><BR/>PaulPaul Fremantlehttp://www.blogger.com/profile/15326219720808613358noreply@blogger.comtag:blogger.com,1999:blog-6003063374827736283.post-71813761136992091492007-05-22T03:45:00.000-07:002007-05-22T03:45:00.000-07:00Hi Paul,<BR/>This is a great sample! I was able to make Sandesha2 running by walking through the steps given in the sample. Even though it is not a big issue, I had to put stub.getVersion().get_return() to print the results of getVerion() method. I think you have missed the get_return() method. <BR/>Anyway, Thank you very much for providing such a simple,working and understandable sample for Sandesha2.<BR/><BR/>Regards<BR/>Charitha KankanamgeCharithahttp://www.blogger.com/profile/00209392844529688942noreply@blogger.com