Hi Florent
Are you familiar with xmlbeans? its like JAXB but better.. it has
support for reflecting schema types.. I was hoping it would allow me
to reflect a schema and construct beans on the fly at runtime.. but
it seems you need to compile the schema first.. (into tightly bound
javabeans)
All objects in xmlbeans implement XMLObject and so it should be
possible to reflect the xmlbean getters and setters using most of the
info you have in the current data model.
This would require as part of a component extension a schema
compilation.. but the benefits are huge.
I will try and spike code something.. but before I waste too much
time i'd like to know whether there are reasons why JAXB, castor or
xmlbeans are not used.
One of the other benefits of xmlbeans is validation on the fly..
also xmlbeans are used by axis2 so you would be half way to shifting
data to and fro remote WS calls
http://xmlbeans.apache.org/
I am going to spend some time following data as it moves through the
layers.. and see where I might fit an xmlbeans structure.. I think it
should replace or augment the hashmaps in the datamodel.. but suspect
this will have massive impact to the core.
Only one way to find out.
Yours
Phil
On 28 Feb 2007, at 11:15, Florent Guillaume wrote:
On 27 Feb 2007, at 18:03, Philip Cornelius wrote:
I have a couple of questions:
1. What does this facet do?
<facet name="Downloadable"/>
It's a "marker" on the type so that the user interface can directly
provide a link to the file stored in the document.
I'm not sure if the current UI still has it.
2. When I copy a document to 'My Worklist' there is a zip export
option.. what is that for.. it says 'the selected documents hold
no exportable data' when I click on it.
I don't know about this.
3. I have followed through the code to see where DocumentModel and
DataModels get created..
Can you tell me wether I have understood the things below correctly?
As I understand it there is a DataModel for each of the schemas
defined for the document type
Once these schemas are read in, the data is stored in HashMaps and
the schema info is discarded
the schema namespace information is lost in the DocumentModel
nowhere in Nuxeo is the document stored or retrievable as an XML DOM
The schema info is not discarded. A document is always associated
to its type's schema, you can use the type service to retrieve this.
Florent
Yours
Phil
On 27 Feb 2007, at 09:56, Philip Cornelius wrote:
Yes.. I am thinking of documents already defined by their
schema.. rather than say pdf to xml etc, like in the NXSample.
We already have a very extensive XML format for our documents.. I
am thinking of using Nuxeo to do our workflow and business
processes etc..
I'll try and get my head around some of the technologies you are
using and of course I will contribute if I can.. we are still
j2ee 1.4 and struts but we have extensive experience in XML and
web services especially around character encoding issues..
Yours
Phil
On 26 Feb 2007, at 23:47, Florent Guillaume wrote:
No, I should have been clearer: there is no code either. We
haven't standardized on a format to export a document as XML,
even though one could be devised based on its XSD schema.
We'd love contributions for this :)
Florent
On 26 Feb 2007, at 21:30, Philip Cornelius wrote:
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
--
Florent Guillaume, Director of R&D, Nuxeo
Open Source Enterprise Content Management (ECM)
http://www.nuxeo.com http://www.nuxeo.org +33 1 40 33 79 87
!DSPAM:5,45e564f343021661821359!
--
Dr. Phil Cornelius <[EMAIL PROTECTED]>
Head of Engineering
PolicyMatter Ltd. 01189 301834
_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm
