I opened a JIRA for the catalog.[1]
[1] http://issues.apache.org/jira/browse/WODEN-14
On 7/9/06, John Kaputin <[EMAIL PROTECTED]> wrote:
Per my recent response to Oshani on her requirements, I'll open a JIRA on
ElementSource and do the initial work this coming week in an SVN branch for
review before merging into the trunk.
John Kaputin
"Jeremy Hughes"
<[EMAIL PROTECTED]
rg> To
Sent by: [email protected]
[EMAIL PROTECTED] cc
om
Subject
Re: local resolving of
07/07/2006 06:14 WSDL/XMLSchema URLs
Please respond to
[EMAIL PROTECTED]
he.org
I'm not sure whether John has implemented any of what he proposed in
his ElementSource proposal. He's currently at the W3C interop event in
Toronto so should be online soon.
Cheers,
Jeremy
On 7/7/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> OK, no problem ! but first I must make sure that I'll be able to retrieve
the XML Schema DOM in the next iteration of woden. Should I start working
on this first or are other persons already working on the subject ?
>
> -----Message d'origine-----
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de
> Jeremy Hughes
> Envoyé : vendredi 7 juillet 2006 12:00
> À : [email protected]
> Objet : Re: local resolving of WSDL/XMLSchema URLs
>
>
> On 7/7/06, [EMAIL PROTECTED]
> <[EMAIL PROTECTED]> wrote:
> > Hi,
> > me again :-)
> >
> > Due to the nature of the environment of the component I'm writing, I
need to find a way to resolve default URLs like XML Schema xsd and dtd or
XML xsd file locally. Since Woden requires an Internet connection to work
I've modified my host file and installed an apache http server to host the
needed files. This is good for testing but a local "caching" feature need
to be bundled in Woden itself to be acceptable to my superiors.
> >
> > I've read in the documentation that "Planned functionality that does
not yet exist in Woden and is NOT described in this User Guide
includes:Resolving URLs with an entity or catalog resolver, ..." is it the
same issue I'm mentioning in this email ?
>
> Yes they're the same. The objective of the catalog resolver is to
> retrieve well known xml files from a local cache (or catalog) so
> network traffic is minimised - or in your case removed all together.
> >
> > If so, I'll be willing to help implementing it in woden since I just
can't start an other woden from scratch :-) Where should I start ?
>
> Xerces supports catalogs. A good starting place is here:
> http://xerces.apache.org/xerces2-j/faq-xcatalogs.html
>
> Really appreciate your help on this!
>
> Thanks,
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
