Hi, after dealing with the legal issues (I have sent in the contributors agreement today) I started to get our code to get our code to run with = the new code base. Since the code generation was originally based on Apache = WSRF there are (of course) some problems to port it to the new code base.
Andrew, since you would like to work on the code generation too, I think = we should start to discuss whether we want to port the code from Apache = WSRF to muse or we just re-develope the parts from WSRF (I would tend to the = first, so we have to identify the needed parts and perhaps put it into a new module). What is your opinion to this? Do you think it makes sense to = put our Apache WSRF extensions to the jira? Furthermore we have to think = about a concept to deal with different SOAP-Engines (at least Axis 1/2 - and = what about OSGi?). Another point is that we have to decide how we want to = deal with different xml schema compilers (if we want to support more than one :o). In my opinion we should at least support XmlBeans, since they are = quite good in compiling complex schemas. Dan, I saw that you are also dealing with the (de-)serialization in the = core module. I don't know whether this is good or not, I had a lot of = problems with Axis using their own (default) de-/serializiation and code = generation mechanisms when dealing with wsdl-files that include complex = xml-schemas. I think there will be some dependencies to the code generation parts that = we have to clarify.=20 Regards, Oliver -- Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
