I don't think I'm completely clear on the issue, so I'll try to
summarize how I understand this.

When an existing Tx* store is moved to a different scope the name of the
"root" def.xml file changes to match the name of the new scope. When the
filesystem of the existing store is read-only (as on a CD) this can't
happen and the store is not loaded. The suggestion is to add a parameter
to the <scope> element in the namespace to specify where the Tx* store
should put the "root" descriptor file.

Assuming that my summary is correct (and I really feel like I'm missing
something) I think the parameter would be more appropriate in the
configuration of the TxXMLFileDescriptorsStore. I can't see how
different store implementations would be able to use the parameter, and
putting it with the <scope> implies it is some sort of
generally-applicable value.

Other than that it seems like a good idea to me :). I haven't worked on
the Tx* stores at all, though, so there could be implications here that
I'm unaware of.

-James

On Tue, 2004-10-12 at 07:31, Oliver Zeigermann wrote:
> What do others think about this?
> 
> Oliver
> 
> Darren Hartford schrieb:
> 
> > Obviously, +1 here ;-)
> >  
> > Looking over the other tags, using a <parameter> subtag would work as well and be 
> > more consistent.
> > 
> >     -----Original Message----- 
> >     From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] 
> >     Sent: Mon 10/11/2004 3:32 PM 
> >     To: Slide Users Mailing List 
> >     Cc: 
> >     Subject: Re: read-only support (CD/DVD)
> >     
> >     
> > 
> >     > p.s. I recommend adding in another attribute to the <scope> tag to configure 
> > where it should store that file, but that is only if <scope> is the only file 
> > created/changed in a read-only store during integration.
> >     
> >     Sounds like a good solution to your problem. Should be doable with
> >     reasonable effort as well.
> >     
> >     Comments?
> >     
> >     Oliver
> >     
> >     
> >     ---------------------------------------------------------------------
> >     To unsubscribe, e-mail: [EMAIL PROTECTED]
> >     For additional commands, e-mail: [EMAIL PROTECTED]
> >     
> >     
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to