Jeremy I agree that is the correct long term plan! But I also thought there was a plan (as evidenced by checking in the 1.4 code) to move WSDL4J over as-is and work on the 1.x and 2.x code both in Apache? It seems like it might be a good idea?
Paul On 3/8/07, Jeremy Hughes <[EMAIL PROTECTED]> wrote:
On 08/03/07, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > Jukka, > > There may be a way out...check the JIRA :) Maybe it hasn't been clear (sorry) ... the code in the JIRA is a snapshot of WSDL4J 1.4. Axis2 uses WSDL4J 1.6.2 which isn't contributed. So, the revisions to WSDL4J since 1.4 haven't been contributed. The way forward on this IMO, is for Axis2 to move to use Woden and not WSDL4J. Woden doesn't yet support WSDL 1.1, but it does have an intention to (although it doesn't have the intention of being a JSR 110 implementation). Regards, Jeremy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
