Ok, I think I got the patch to work. I compiled the code you provided and incorporated it to Ode's Axis2 Kernel. I started Ode and it doesn't throw any errors. I tried the .aar service included in the .zip file from JIRA with Eclipse Web Service Explorer and it ran perfectly, but I tried the service with the soap binding how do I try it as a local java call?????
Thanks, Fernando. Sanjiva Weerawarana wrote: > > Hi Fernando, > > We've actually done some work to bring in support for WSIF bindings under > the Axis2 API. The code is currently in JIRA but not committed- the plan > is to get it into trunk ASAP. See > https://issues.apache.org/jira/browse/AXIS2-2137. > > What that patch does is make Axis2 understand how to deal with WSDL > bindings such as the Java binding. We've essentially folded in the > functionality of WSIF into Axis2; that is, once that's in you will not > need to change Ode at all to make it call Java classes as Web services- > it'll "just work" out of the box with Axis2. > > There's been some separate work that has implemented a CORBA binding for > Axis2. See https://issues.apache.org/jira/browse/AXIS2-2996. This CORBA > binding is totally dynamic- it uses the IDL to drive the serialization / > deserialization and is quite powerful. I *think* we may need to do some > refactoring of this code to separate out the MessageFormatter bit but I'm > not certain. > > Once that's done Ode will be able to invoke CORBA services too via the > Axis2 API - i.e., with no changes to Ode you'll be able to invoke Java > classes and CORBA objects too as Web services. > > Bye, > > Sanjiva. > > fLozano wrote: >> Hi, >> >> I'm trying to find where Ode reads the WSDL file, so I can use WSIF to >> read >> it and interpret it instead of the regular Ode-way. >> >> Basically what I'm trying to do is use wsif so I can use java bindings. >> To >> do this, I need to use WSIF to read the wsdl files instead of the regular >> wsdl libraries that Ode uses. This means I need to locate the Ode methods >> that I need to substitute with the WSIF ones. >> >>>From what I've been able to see in the source codes, Ode is *VERY* modular >> and it's hard to understand the process of executing a process. >> >> Any suggestions on how to do this? >> >> Thanks, >> Fernando. > > -- > Sanjiva Weerawarana, Ph.D. > Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ > Member; Apache Software Foundation; http://www.apache.org/ > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ > > -- View this message in context: http://www.nabble.com/Where-does-Ode-read-the-wsdl--tf4281541.html#a12244420 Sent from the Apache Ode Dev mailing list archive at Nabble.com.
