Re: PROPOSAL (round 3): Extensions to MDR XMI API

Hi,
the problem with going with only the standard interfaces and provide all 
the config in the factory method is that XmiWrite does not have any 
method that allows to specify target document URI, which makes 
XMIReferenceProvider useless. Specifying such a parameter in the factory 
is IMO also not a good solution. So I guess that at least for the 
XmiWriter we will have to extend the standard interface anyway.
Martin

Petr Kuzel wrote:
> On Monday 05 August 2002 08:08, Holger Krug wrote:
> 
>>* to provide a nice and clean standard implementation which gives
>>  exactly what the standard requires and nothing more (already exists)
> 
> 
> I looked over your discussion and I think that above is the point.
> The standard interface already exists. So I would introduce a factory
> class instantiating readers/writers using additional hints i.e.:
> 
> class XmiReaderFactory {  
>   XmiReader create(ContentHandler, XMIReferenceResolver);
>   XmiReader create(XMIReferenceResolver);
>   // ...
> }
> 
> class XmiWriterFactory {
>   XmiWriter create(ContentHandler, XMIReferenceProvider);
>   XmiWriter create(XMIRefernceProvider);
>   // ...
> }
> 
> Unfortunately methods taking ContentHandler may produce
> JMI interface implementations with modified semantics 
> (I not sure if it is allowed). If it is not allowed then
> you can drop it (pipelining nor pretty printing is not 
> hard requirement AFAIK).
> 
> Anyway next round will be probably necessary :-)
> 
>   Cc.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]