Mailing-List: contact user-help@xmlbeans.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@xmlbeans.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <45824935.5070702@compassplus.ru>
Date: Fri, 15 Dec 2006 12:05:25 +0500
From: Den Grigorenko <d.grigorenko@compassplus.ru>
Reply-To: d.grigorenko@compassplus.ru
Organization: Compass Plus
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: user@xmlbeans.apache.org
Subject: Classes simplifying
References: <7867963.post@talk.nabble.com> <7871978.post@talk.nabble.com>
In-Reply-To: <7871978.post@talk.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Good day.
We try to use XmlBeans in the project executed by Java-machine inside  
Oracle 10 database.
That is why all  the classes we have created should be loaded to the  
database. Our Xml-schemes are large (more than 100 Kbyte) and they are 
multiple.

Thus, their compilation through the use of scomp utility results in the  
rather large *.jar files (several mb) whose loading to the database
is a time consuming process (deploy and resolve are executed for 
thousands classes and resources correspondingly).
At that, the resulting classes contain the most methods we don't apply.
We have a question (wish):
Are there any appropriate settings "simplifying" the classes being
generated ?
E.g, DO NOT include methods xgetXXX(), xsetXXX() in the interfaces,
reduce the number of parse(...) methods in the inner Factory class,
give up all the possible variants and leave the ones which are really
needed.


-- 
Den Grigorenko
Compass Plus


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org