Hi James, I'm not sure I understand. tools2 will have to depend on the soap & xml modules. Why is this an issue?
Regards, - Dan On 12/20/06, James Mao <[EMAIL PROTECTED]> wrote:
and also need to mention is that the xml-binding.xsd is wsdl11 specific, i don't know how we handle the wsld11 extensibility and wsdl20 extensibility? any plan? Another solution I have is to move the xsd and extensions.xml to tools2 temporarily. > Hi, > > I'm trying to reuse the wsdl extension mechanism used in > rt/core/WSDLManagerImpl for tools, > But i found that it has the dependency problem, to resolve the > dependency problem, > > one solution is to move the extensions.xml and schemas to metacode > module. > For example, to support XMLBinding, we could move the xml-binding.xsd, > xml-binding.xjb and extensions.xml to metacode. > > Later when we support new binding or new transport, we could put xsd > and extensions file into metacode > > I don't know if there is any better solution? > > Thanks, > James. > >
-- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
