| XsdValidation [message #42223] |
Tue, 27 April 2004 16:03  |
Eclipse User |
|
|
|
Ed,
In the process of doing some other work, we doing a lot of modifications
to an XsdResourceImpl. We seem to be running into performance problems
where everytime a value is changed or new items are added or removed, the
entire schema tries to validate. Is there any way to turn off the auto
validation and then turn it on when the entire effort is complete so as to
only perform the validation once at the end of the major operation?
thanks,
lp
|
|
|
|
|
| Re: XsdValidation [message #42292 is a reply to message #42261] |
Tue, 27 April 2004 16:52  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Lance,
Nothing should set it back to true on its own. When it's false, QNames aren't
resolved and no type analysis is done. Each schema instance has a separate
setting for this, so maybe you have a multiple schema scenario? Setting it to
true doesn't change the syntactic structure so doing that before save isn't
necessary.
Lance Phillips wrote:
> I had just found it! What kind of things would trigger that value getting
> set back to true on it's own? My test seemed to FLY right along after I set
> this to false. But somewhere in the middle it started bogging down. Not
> sure if it is XSD related or not yet.
>
> What are the implications of leaving it to false and only setting it to true
> when you save and then setting it right back to false after saving?
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:408EBF41.4ACB9E0F@ca.ibm.com...
> > Lance,
> >
> > There's XSDSchema.setIncrementalUpdate. You can turn it back on when
> you're
> > done your edits...
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > In the process of doing some other work, we doing a lot of
> modifications
> > > to an XsdResourceImpl. We seem to be running into performance problems
> > > where everytime a value is changed or new items are added or removed,
> the
> > > entire schema tries to validate. Is there any way to turn off the auto
> > > validation and then turn it on when the entire effort is complete so as
> to
> > > only perform the validation once at the end of the major operation?
> > >
> > > thanks,
> > >
> > > lp
> >
|
|
|
| Re: XsdValidation [message #586035 is a reply to message #42223] |
Tue, 27 April 2004 16:14 |
| Eclipse User |
|
|
|
Lance,
There's XSDSchema.setIncrementalUpdate. You can turn it back on when you're
done your edits...
Lance Phillips wrote:
> Ed,
> In the process of doing some other work, we doing a lot of modifications
> to an XsdResourceImpl. We seem to be running into performance problems
> where everytime a value is changed or new items are added or removed, the
> entire schema tries to validate. Is there any way to turn off the auto
> validation and then turn it on when the entire effort is complete so as to
> only perform the validation once at the end of the major operation?
>
> thanks,
>
> lp
|
|
|
| Re: XsdValidation [message #586052 is a reply to message #42252] |
Tue, 27 April 2004 16:35 |
| Eclipse User |
|
|
|
I had just found it! What kind of things would trigger that value getting
set back to true on it's own? My test seemed to FLY right along after I set
this to false. But somewhere in the middle it started bogging down. Not
sure if it is XSD related or not yet.
What are the implications of leaving it to false and only setting it to true
when you save and then setting it right back to false after saving?
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:408EBF41.4ACB9E0F@ca.ibm.com...
> Lance,
>
> There's XSDSchema.setIncrementalUpdate. You can turn it back on when
you're
> done your edits...
>
> Lance Phillips wrote:
>
> > Ed,
> > In the process of doing some other work, we doing a lot of
modifications
> > to an XsdResourceImpl. We seem to be running into performance problems
> > where everytime a value is changed or new items are added or removed,
the
> > entire schema tries to validate. Is there any way to turn off the auto
> > validation and then turn it on when the entire effort is complete so as
to
> > only perform the validation once at the end of the major operation?
> >
> > thanks,
> >
> > lp
>
|
|
|
| Re: XsdValidation [message #586065 is a reply to message #42261] |
Tue, 27 April 2004 16:52 |
| Eclipse User |
|
|
|
Lance,
Nothing should set it back to true on its own. When it's false, QNames aren't
resolved and no type analysis is done. Each schema instance has a separate
setting for this, so maybe you have a multiple schema scenario? Setting it to
true doesn't change the syntactic structure so doing that before save isn't
necessary.
Lance Phillips wrote:
> I had just found it! What kind of things would trigger that value getting
> set back to true on it's own? My test seemed to FLY right along after I set
> this to false. But somewhere in the middle it started bogging down. Not
> sure if it is XSD related or not yet.
>
> What are the implications of leaving it to false and only setting it to true
> when you save and then setting it right back to false after saving?
>
> thanks,
>
> lp
>
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:408EBF41.4ACB9E0F@ca.ibm.com...
> > Lance,
> >
> > There's XSDSchema.setIncrementalUpdate. You can turn it back on when
> you're
> > done your edits...
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > In the process of doing some other work, we doing a lot of
> modifications
> > > to an XsdResourceImpl. We seem to be running into performance problems
> > > where everytime a value is changed or new items are added or removed,
> the
> > > entire schema tries to validate. Is there any way to turn off the auto
> > > validation and then turn it on when the entire effort is complete so as
> to
> > > only perform the validation once at the end of the major operation?
> > >
> > > thanks,
> > >
> > > lp
> >
|
|
|
Powered by
FUDForum. Page generated in 0.07508 seconds
Home