If this was all you had to use, you would be safe to invalidate B and A if C
changed.  A certainly depends on C, and B possibly.  X,Y and Z cannot depend
on C if C is not in the pool already.  The tricky part is what to do if Y
changes, since A, B and/or C might depend on it.  I'm not sure there's any
solution for that using this approach.

The dependency tree info would have to be maintained outside the grammar
pool and consulted when a new insertion is made.

Jeff
----- Original Message ----- 
From: "Bob Foster" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, December 06, 2004 2:12 PM
Subject: Re: Problem with grammar pool


> Wish it were that easy. After parsing the instance document, the grammar
> pool holds X,Y,Z,A,B,C. Now C is changed, and the resulting parse
> replaces C in the grammar pool. Which others should be invalidated?
> Multiple namespaces may be involved. It is not certain from this
> information there is any schema interdependency at all.
>
> Bob
>
> Jeff Greif wrote:
> > You would find out, for example, that
> >
> > Before parsing A.xsd, the grammar pool held X,Y,Z
> > After parsing A, it held X,Y,Z,A,B,C.
> >
> > So B,C were imported during the parse of A.  You could save dependency
trees
> > based on this information.
> >
> > Jeff
> > ----- Original Message ----- 
> > From: "Bob Foster" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, December 06, 2004 1:38 PM
> > Subject: Re: Problem with grammar pool
> >
> >
> >
> >>Jeff Greif wrote:
> >>
> >>>Another not-very-appealing possibility is to iterate over the grammar
> >
> > pool
> >
> >>>before and after parsing the document or root schema and look at the
> >
> > change.
> >
> >>I'm not sure what I would find out from this.
> >>
> >>
> >>>This assumes the grammar pool is not used by multiple threads.
> >>
> >>It is, but I have a way to lock it.
> >>
> >>Bob
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>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]
>


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

Reply via email to