On Mon, Apr 14, 2008 at 3:15 PM, Vidar Ramdal <vidar@idium.no> wrote:
> On Mon, Apr 14, 2008 at 2:41 PM, Conoly, Brett
> <Brett.Conoly@digitalinsight.com> wrote:
> > This is only a guess but the jcr:content node has a mimetype property,
> > are you setting that correctly when you first put the new nodes into the
> > repository? There are actually a few ways to automate this using
> > already written code. There's JMimeMagic which reads the bytes but
> > can't really tell the difference in different text files, i.e. text/html
> > -> text/plain. There's also sun's MimeTable which seems to be based on
> > the extension and will be able to interpret different types of text
> > based files. Again this is just a guess but it may work.
>
>
> Thanks for your suggestion, but the MIME type is correct in the
> exporting repository, and is also set correctly in the importing
> repository.
>
> I see the problem now: The jcr:data property is a Binary in the
> exporting repository, but a String in the importing. How could this
> have happened?
And, BTW, the value of the jcr:data property is garbled (that is, a
Base64-encoded String).
--
Vidar S. Ramdal <vidar@idium.no> - http://www.idium.no
Akersgata 16, N-0158 Oslo, Norway
|