Re: [castor-dev] question on strictelements

2005-02-17 Thread Keith Visco
Hi Peter, Yikes, I guess I need to supply a LocalConfiguration#setProperties() method that can be called to indicate property changes. Unfortunately once the LocalConfiguration is created the properties are currently written in stone. I wasn't aware of that limitation. The good news is that you

Re: [castor-dev] question on strictelements

2005-02-16 Thread Peter Lin
Hi keith, I tried your suggestion, but it doesn't appear to work. I'm using 0.9.5. I generated classes using the following sample schema from JWSDP. http://www.w3.org/2001/XMLSchema";> The sample XML

Re: [castor-dev] question on strictelements

2005-02-04 Thread Peter Lin
thanks for the suggestion, i'll give it a try. should be a workable solution. peter On Fri, 04 Feb 2005 18:12:50 -0600, Keith Visco <[EMAIL PROTECTED]> wrote: > > > Hi Peter, > > Have you tried the following: > > import org.exolab.castor.util.Configuration; > import org.exolab.castor.util.L

Re: [castor-dev] question on strictelements

2005-02-04 Thread Keith Visco
Hi Peter, Have you tried the following: import org.exolab.castor.util.Configuration; import org.exolab.castor.util.LocalConfiguration; Properties props = LocalConfiguration.getInstance().getProperties(); props.setProperty(Configuration.Property.StrictElements, "true"); Just be careful when setting

Re: [castor-dev] question on strictelements

2005-02-04 Thread Peter Lin
What are the chances of my patch getting into the next release? http://bugzilla.exolab.org/show_bug.cgi?id=1868 I totally understand the static unmarshal() methods are there for convenience, which is probably why the third party client I'm using is using them :) I imagine other people are also

Re: [castor-dev] question on strictelements

2005-02-02 Thread Peter Lin
hi kieth, the challenge here is I am using a third party client which uses castor. The objectfactory uses the static unmarshal() method. Although I could rewrite the objectfactory I don't want to take the responsibility for the third party client. I submitted a patch, which should have minimal im

Re: [castor-dev] question on strictelements

2005-02-02 Thread Keith Visco
Peter, The static unmarshal() methods are simply for convenience. You can easily construct an Unmarshaller, configure it, and invoke it as such: Unmarshaller unm = new Umarshaller(MyClass.class); unm.setIgnoreExtraElements(true); unm.unmarshal(myReader); --Keith Peter Lin wrote: has anyone given

[castor-dev] question on strictelements

2005-02-02 Thread Peter Lin
has anyone given thought to making strictelement configurable through system properties? The reason I ask is, for production I would like the ability to turn off strictelements so that in the event a third party changes the schema, the server doesn't just get errors. I was looking over UnmarshalH