Sanka, AFAIK, In Woden and WSDL 1.1 is still a loooooonnnnggggg way off. So we may as well declare that for Axis2 1.0 we will *NOT* target wsdl2. and stick to wsdl1.1 using wsdl4j.
-- dims On 1/10/06, Sanka Samaranayake <[EMAIL PROTECTED]> wrote: > Hello everyone, > > Pardon me if I am wrong, but aren't we suppose to get rid of WOM and > use wooden as it becomes available? Therefore is it worth to put a lot > of effort to make WOM to hold any information as the central > representation of AxisService? > > Sanka. > > On 1/10/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > Ajith, > > > > it's not just serialization....I think of it as one central > > representation of an axis service. whether it is on disk or in memory. > > Annotations in code will affect it, entries in services.xml may affect > > it, runtime reflection may affect it. But at any given point after > > taking into account the original wsdl, annotations, runtime > > reflection, services.xml etc....the final product is the wom which is > > the Axis Service that the developer wants to expose to the world. > > Whether it is on disk or in memory...it should not matter. Basically > > we should be able to generate xsd's or wsdl11's or wsdl12 or SSDL or > > any other acronym thrown at us > > (http://hinchcliffe.org/archive/2005/05/16/231.aspx) > > > > thanks, > > dims > > > > On 1/9/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Dims has a point, in the sense that WOM represents both the WSDL versions > > > and a serialization of one version may not be a complete representation of > > > the other. However I feel that it'll be an over engineering as far as WOM > > > is > > > considered. I mean if you want to serialize it go do it as either a > > > WSDL1.1 > > > or WSDL2.0 document. > > > > > > > > > > > > On 1/9/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > > > > Eran, > > > > > > > > If that's what you prefer, then sure...but remember we can't read it > > > > then. On a related note, AxisServiceBuilder should *NOT* be working > > > > with WSDL4J classes. getAxisService should operate on a wom. > > > > > > > > -- dims > > > > > > > > On 1/9/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > > Hash: SHA1 > > > > > > > > > > Isn't it the WSDL2Writer you are talking about ? I think WOM model is > > > > > completely WSDL2 and saving WOM means its saving a WSDL 2.0 document. > > > > > > > > > > Davanum Srinivas wrote: > > > > > > > > > > > How about we have an xml format for wom itself? that is neither > > > > > > wsdl11 or wsdl12? Am bringing this up to figure how how we should > > > > > > fix AXIS2-365. Specifically the comment from Sanjiva here: > > > > > > > > > http://marc.theaimsgroup.com/?l=axis-dev&m=113679084111960&w=2 > > > > > > > > > > > > The idea is to store it a neutral format (neither wsdl11 or wsdl12) > > > > > > and at runtime generate whichever version of wsdl is needed. > > > > > > > > > > > > What do you think? > > > > > > > > > > > > thanks, dims > > > > > > > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/ > > > > > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > > Version: GnuPG v1.4.2 (MingW32) > > > > > > > > > > > > > iD8DBQFDwoIxjON2uBzUhh8RAldXAJ9L8aAZBA/wsx797SHBp3n0C2SxUgCggHBC > > > > > jGfuyE5Y9cvgT0edq+UuLu0= > > > > > =nCnr > > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > > > > > > > > > > > > -- > > > > Davanum Srinivas : http://wso2.com/blogs/ > > > > > > > > > > > > > > > > -- > > > Ajith Ranabahu > > > > > > -- > > Davanum Srinivas : http://wso2.com/blogs/ > > > -- Davanum Srinivas : http://wso2.com/blogs/
