Hi, In the meantime I have found that Soap 2.0.1 can export the WSDL and the XSD it imports as a set of local files, re-writing the XSD imports in the proceess, which does me , for now.
Thanks Wayne On Tue, Apr 29, 2008 at 1:59 PM, Wayne Keenan <[EMAIL PROTECTED]> wrote: > I got around to installing the Repository today, cool, but I think pulling > down and caching the XSD isnt there yet, is it on the plan soon? and would > the option of being able to export the cached XSD's to the filesystem for > other non -repo enabled projects (e.g. Apache ODE) to slurp in? > > Regards > Wayne > > > On Fri, Apr 11, 2008 at 3:52 PM, Asankha C. Perera <[EMAIL PROTECTED]> > wrote: > > > Wayne > > > > I think the more elegant solution is for a central registry/repository > > to import this WSDL - and suck in the dependencies properly. Then the ESB > > can work off the Registry.. I think the WSO2 Registry < > > http://wso2.org/projects/registry> already does support this, or plans > > to support this soon. And Synapse can then integrate with the WSO2 Registry > > anytime.. > > > > asankha > > > > > > Wayne Keenan wrote: > > > > > Hi > > > > > > Thanks for the suggestion. I was hoping for a more transparent > > > solution. > > > The XSD that are directly included by the WSDL include furhter XSD's. > > > I will > > > be working with umpteen unknown WSDL's as the system grows and so > > > would like > > > to avoid the maintenance by introducing some kind of transparent and > > > persisted cache without altering the original WSDL. > > > > > > This is potentially not directly a Synapse problem, but a XML parser > > > issue, > > > but I would like to understand how to get the XML parser using a > > > Synapse > > > compatible repository, if that's one way to solve it. > > > > > > Regards > > > Wayne > > > > > > On Fri, Apr 11, 2008 at 6:13 AM, Ruwan Linton <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > > > > > Hi Wayne, > > > > > > > > Yes. It is already possible with the Synapse registry. In-order to > > > > get > > > > this > > > > functionality you need to enable the registry in the synapse.xml and > > > > change > > > > the wsdl in such a way that the include URIs refer to the XSDs > > > > uploaded to > > > > the registry rather than the once available over the internet. > > > > > > > > You can enable the registry by putting the following configuration > > > > fragment > > > > to the top of the synapse.xml under the definitions tag; > > > > > > > > <registry > > > > provider="org.apache.synapse.registry.url.SimpleURLRegistry"> > > > > <parameter name="root">file:./registry/</parameter> > > > > <parameter name="cachableDuration">15000</parameter> > > > > </registry> > > > > > > > > Thanks, > > > > Ruwan > > > > > > > > On Thu, Apr 10, 2008 at 7:28 PM, Wayne Keenan < > > > > [EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > I have an 'industry standard' WSDL published thru a Synapse proxy > > > > > which > > > > > pulls in about 30 external XSD's off the internet. > > > > > I was wondering if anyone had manage to create an xinclude URI > > > > > resolver > > > > > that > > > > > would use a local registry as opposed to pulling > > > > > the XSD's off the net. > > > > > I guess a secondary solution would be to introduce something a the > > > > > > > > > > > > > > network > > > > > > > > > > > > > level but I was hoping anyone could point me in the direction of > > > > > some > > > > > > > > > > > > > > sort > > > > > > > > > > > > > of repository integration for the XML parser. > > > > > > > > > > If this isn't directly possible at the moment, would anyone care > > > > > to > > > > > outline > > > > > thoughts on the feasibility, possible leverage of existing > > > > > solutions and > > > > > perhaps touch points in various code modules I might need analyse > > > > > to > > > > > support > > > > > such functionality in the: XML Parser, Synapse Proxy and Synapse > > > > > Repository. > > > > > > > > > > > > > > > Regards > > > > > Wayne > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Ruwan Linton > > > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > > > > > > > > > > > > > > > > > > > > >
