jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicolas Belisle <Nicolas.Beli...@bibl.ulaval.ca>
Subject Re: XML schema to node types
Date Wed, 25 Jan 2006 18:20:52 GMT
Hi Peeter,

(Sorry for the late response)

Many thanks for the contribution.
This is a great addition to Jackrabbit. This will ease the integration of 
existing formats.

I haven't had time to test it yet, but will have a deep look at it in a few 
weeks.

Regards,

Nicolas


Le 21:54 2006-01-09, vous avez écrit:
>Hi Mike,
>
>You are right about that bug.
>
>I have intermittent access to a useful computer right now (travelling)
>and can't commit stuff (for some mysterious reason) but I have
>arranged to have a patch applied by another committer which should fix
>tthe specific problem. As for the more general issue of dealing with
>the default namespace I will take a look at that when I get a chance.
>
>Of course your are free to fix stuff yourself and send patches to me
>or another commiter.
>
>Actually could you clarify exactly what the default namespace issue is
>again? I am not quite sure I see what you mean (though I am sure you
>are right :-)
>
>Sorry I can't be of more help at the moment,
>
>Cheers,
>Peet
>
>
>On 1/10/06, Michael Daglian <michael.daglian@gmail.com> wrote:
> > Hello Peeter,
> >
> > Apologies if I am misusing the schema converter code you committed but I
> > am a bit confused as to how to make use of the NamespaceExtractor class.
> > As demonstrated in your test-case for the SchemaConverter I am
> > attempting to use an extractor to get the additional namespaces out a
> > schema file. However, this does not appear possible due to the use of
> > getURI for the mapping property:
> >
> > <<<
> >
> > if (mapping.getURI(prefix) != null){...
> >
> > >>>
> >
> > The NamespaceMapping class throws an exception if the prefix is unmapped
> > and thus the empty NamespaceMapping created using the default structure
> > always generates this exception, which only gets caught and logged.
> >
> > On another note, it seems unclear how to best handle the default
> > namespace using the NamespaceMapping class. When using the reader and
> > explicitly mapping the namespace to be "" (i.e
> > NamespaceMapping.setMapping("", "");), this works fine. But when
> > outputting it writes the default namespace in a manner that the reader
> > cannot read. Is there a recommended way of handling this case? Thanks!
> >
> > Best Regards,
> >
> > -- Mike
> >
> >
> > On 12/20/05, Peeter Piegaze <peeter.piegaze@day.com> wrote:
> > >
> > > Hi Nicolas,
> > >
> > > Regarding your interest in XML schema to JCR node type conversion: I
> > > have committed the XSD to JCR node type converter into
> > > contribs/nt-ns-util
> > >
> > > Cheers
> > > Peeter
> > >
> > >
> > > On 10/31/05, Nicolas Belisle <Nicolas.Belisle@bibl.ulaval.ca> wrote:
> > > > Great news !
> > > >
> > > > I'm looking forward to this.
> > > >
> > > >
> > > > Many thanks,
> > > >
> > > > Nick
> > > >
> > > >
> > > > >Hi Nicholas, Actually, I wrote something that does this. I haven't
> > > gotten
> > > > >around to completely finishing it yet, but I will take your mail as
a
> > > > >motivator to do just that. Then I will commit to contribs. Cheers,
> > > Peeter
> > > > >On 10/31/05, Nicolas Belisle <Nicolas.Belisle@bibl.ulaval.ca>
wrote: >
> > > > >Hi, > > I'm currently investigating ways to convert XML schemas
to
> > > > >Jackrabbit node > types declaration. This way, most metadata formats
> > > > >(Dublin Core, MARC21, > etc.) could be integrated easily in a
> > > Jackrabbit
> > > > >repository. > > Anyone has done something in that direction
and would
> > > like
> > > > >to its share > ideas ? Any other comments on this ? > > I
would
> > > certainly
> > > > >contribute the result back to Jackrabbit. > > > Regards,
> > Nick > >
> > > >
> > > >
> > >
> >
> >


Mime
View raw message