++1 for dropping the DTD's....  All of them. :)

On Thu, Sep 29, 2016 at 2:41 PM, Dan Smith <dsm...@pivotal.io> wrote:

> +1 for dropping the dtd up to 6.6. -1 for dropping 7.0/8.0, 8.1 xsd. I
> think we should keep those for another release or two to make it easier for
> people upgrading.
>
> Is anyone actually using createTypesFromXml? If not, I would suggest
> deprecating it.
>
> -Dan
>
> On Thu, Sep 29, 2016 at 2:33 PM, Jacob Barrett <jbarr...@pivotal.io>
> wrote:
>
> > The files MUST remain in the source otherwise the validating parser will
> > have to download them from the website. This is VERY slow and only works
> if
> > you have Internet access. The schema resolver first looks in the class
> path
> > then to the web.
> >
> > -Jake
> >
> >
> > On Thu, Sep 29, 2016 at 2:24 PM Anthony Baker <aba...@pivotal.io> wrote:
> >
> > > Any active dtd's or schema’s should be hosted near to
> > > http://geode.apache.org/schema/cache/.  If you follow the directions
> [1]
> > > to update the website it’s not too hard.
> > >
> > > Can we remove the pivotal.io schema from source?
> > >
> > >         ./geode-core/src/main/resources/META-INF/schemas/
> > > schema.pivotal.io/gemfire/cache/cache-8.1.xsd
> > >
> > > We should upload the lucene scheme to the website also:
> > >         ./geode-lucene/src/main/resources/META-INF/schemas/
> > > geode.apache.org/lucene/lucene-1.0.xsd
> > >
> > >
> > > Anthony
> > >
> > > [1]
> > > https://github.com/apache/incubator-geode/blob/develop/geode
> > -site/website/README.md
> > >
> > >
> > > > On Sep 29, 2016, at 2:15 PM, Darrel Schneider <dschnei...@pivotal.io
> >
> > > wrote:
> > > >
> > > > statisticsType.dtd is used
> > > > by org.apache.geode.StatisticsTypeFactory.createTypesFromXml(Reader)
> > > > See the javadocs on StatisticsTypeFactory for an example of how to
> use
> > > it.
> > > >
> > > > On Thu, Sep 29, 2016 at 1:50 PM, Kirk Lund <kl...@apache.org> wrote:
> > > >
> > > >> I'm actually unfamiliar with statisticsType.dtd:
> > > >>
> > > >> geode-core/src/main/resources/org/apache/geode/statisticsType.dtd
> > > >>
> > > >> I notice it still references GemStone and gemstone.com. Do we have
> > > copies
> > > >> of the dtds on geode.apache.org? Where should these dtds live
> online?
> > > >>
> > > >> Thanks,
> > > >> Kirk
> > > >>
> > > >>
> > > >> On Thu, Sep 29, 2016 at 9:37 AM, Hitesh Khamesra <
> > > >> hitesh...@yahoo.com.invalid> wrote:
> > > >>
> > > >>> We have following dtds in geode source code. We were thinking to
> > remove
> > > >>> previous versions(1.0 to 6.6) of dtds.Please let us know if there
> is
> > > any
> > > >>> concern on  this.
> > > >>>
> > > >>> ./main/resources/org/apache/geode/admin/doc-files/ds4_0.dtd
> > > >>> ./main/resources/org/apache/geode/admin/doc-files/ds5_0.dtd
> > > >>> ./main/resources/org/apache/geode/admin/jmx/internal/doc-
> > > >>> files/mbeans-descriptors.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache3_0.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache4_0.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache4_1.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache5_0.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache5_1.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache5_5.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache5_7.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache5_8.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache6_0.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache6_1.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache6_5.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache6_6.dtd
> > > >>>
> > > >>>
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache7_0.dtd
> > > >>> ./main/resources/org/apache/geode/cache/doc-files/cache8_0.dtd
> > > >>> ./main/resources/org/apache/geode/statisticsType.dtd
> > > >>>
> > > >>> Thanks.HItesh
> > > >>>
> > > >>>
> > > >>
> > >
> > >
> >
>



-- 

~/William

Reply via email to