J. Wolfgang Kaltz wrote:
Andreas Hartmann schrieb:
(...)
- the resource type matching does not yet use the new meta-data
I don't quite understand, what do you mean here?
At the start of the meta-data discussion (a while back, true enough :) )
we talked about removing the need for calculating the resource type upon
each request for a document, and instead keeping the resource type in
the metadata and using that value.
OK, I'm on the track again :)
I guess that would mean removing the DocumentTypeResolver, and replacing
it with calls to Document.getResourceType().
For example, PageEnvelopeModule.getDocumentType() would now just be a
one-liner, envelope.getDocument().getResourceType()
Big +1
That would mean that we could get rid of the URIParameterizer which
would simplify and speed up the processing.
The document type could be added to the PageEnvelope, which would
remove the inconsistency between PE and PEModule.
I don't know if there are also more complicated cases, as the
DocumentTypeResolver is used in several places and also involves an
instance of the DocumentType class.
The DocumentTypeResolver could be removed, but I'd change
String Document.getResourceType() throws DocumentException;
to
DocumentType getResourceType() throws DocumentException;
or better
ResourceType getResourceType() throws DocumentException;
which would use the DocumentTypeBuilder (ResourceTypeBuilder) for
lazy loading the ResourceType object.
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
