Hi Berney,

I will try and answer your query. Xbean configurations look ok to me. 

Can you share the wsdl for

http://localhost:88/WebServiceESBunivis/WebServiceESBunivis/WebServiceES
Bunivis.asmx 


Is this a document style. From the code it does not look to me like a
document style WS.

"String r = webServiceESBunivis.findLectureXML("Architecture");"

Also the can you provide the error stack trace with the log level set to
DEBUG.

Regards,
Rabi Mishra, 
http://rabisblog.blogspot.com/
c++; /* this makes c bigger but returns the old value */ 

-----Original Message-----
From: Bombjack [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, July 04, 2007 8:15 AM
To: [email protected]
Subject: Issues with simple proxy scenario


Hi,

I'm new to the ServiceMix world and have been trying to get the
following scenario to work, but it keeps giving me trouble:

-A web service called TestXmlFile in a jsr181 SU serves as a consumer.
-This web service calls some function provided by an external web
service named WebServiceESBunivis.

I started by creating the WSDLs for the TestXmlFile and
WebServiceESBunivis, and generated all the corresponding classes through
the "mvn generate-sources" command. The only class I then edited was
TestXmlFileImpl.java.

So far, I am able to contact and get a response from TestXmlFile.
However, as soon as TestXmlFile tries to call some function provided by
the external WebServiceESBunivis, I'm getting the error messages "Could
not invoke service" and "Error sending JBI exchange" by xfire.

Web service TestXmlFile is defined as:
-------------------------------------
@WebService(serviceName = "TestXmlFile", targetNamespace =
"http://meinBeispiel.org/testxmlfile";, endpointInterface =
"org.meinbeispiel.testxmlfile.LecturePortType")
public class TestXmlFileImpl
    implements LecturePortType
{
        
    private WebServiceESBunivisSoap webServiceESBunivis;
        
    public void setWebServiceESBunivis(WebServiceESBunivisSoap
webServiceESBunivis) {
        this.webServiceESBunivis = webServiceESBunivis;
    }
    
    
    public FindLectureResponse
getSomeLecture(org.meinbeispiel.testxmlfile.FindLectureRequest
FindLectureRequest) {
        
----> String r = webServiceESBunivis.findLectureXML("Architecture");

        FindLectureResponse rep = new FindLectureResponse();
        rep.setReturnString("test");
        return rep;
-------------------------------------

The above arrow points out the line that keeps causing the error
messages.
I registered both services in the http xbean.xml and jsr181 xbean.xml
files as follows:

<!--HTTP SU-->
<beans xmlns:http="http://servicemix.apache.org/http/1.0";
       xmlns:testfile="http://meinBeispiel.org/testxmlfile";
       xmlns:univis="http://univis.com";>
       
  <http:endpoint service="testfile:TestXmlFile"
                 endpoint="TestXmlFilePort"
                 role="consumer"
                 locationURI="http://localhost:8192/MeinBeispiel/";
                 soap="true" />             
    
  <http:endpoint service="univis:WebServiceESBunivis"
                 endpoint="WebServiceESBunivisSoap"
                 role="provider"
                
locationURI="http://localhost:88/WebServiceESBunivis/WebServiceESBunivis
/WebServiceESBunivis.asmx"
                 soap="true" />
</beans>


and


<!--JSR181 SU-->
<beans xmlns:jsr181="http://servicemix.apache.org/jsr181/1.0";
       xmlns:univis="http://univis.com";>

    <jsr181:endpoint pojo="#testxmlfile"
                     wsdlResource="classpath:service.wsdl" 
                     typeMapping="jaxb2"
                     annotations="jsr181"
                     style="document" />
                     
  <bean id="testxmlfile"
class="org.meinbeispiel.testxmlfile.TestXmlFileImpl">
    <property name="webServiceESBunivis">
      <jsr181:proxy context="#context" 
                    type="com.univis.WebServiceESBunivisSoap"
                    service="univis:WebServiceESBunivis" />
    </property>
  </bean>
  
</beans>


I probably made a relatively simple mistake somewhere, but for the life
of it I can't figure out exactly where.
Thanks in advance for your help,
Berny

--
View this message in context:
http://www.nabble.com/Issues-with-simple-proxy-scenario-tf4022130s12049.
html#a11424065
Sent from the ServiceMix - User mailing list archive at Nabble.com.



The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com

Reply via email to