Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: local policy)
From: "Jan Ole Brenna" <jobrenna@solarsoft.no>
To: <commons-dev@jakarta.apache.org>
Subject: betwixt 0.7RC2 suppress elements
Date: Tue, 12 Jul 2005 11:58:44 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: AcWGyEeCwErkJuX7T8mSlbwdygF3Hw==
Message-Id: <20050712095853.9F39710FB2A6@asf.osuosl.org>

I'm using betwixt to transfer my object graph to xml. The objekt graph are
persistent pojo beans managed by hibernate.
My problem is that betwixt traverses the complete objekt graph, triggering
hibernate to load all lazy collections. And I'm ending up with almost
loading the whole database.
I don't wont that, I would like to prevent betwixt from traversing the lazy
parts of my graph.
Hibernate has a method to check if a lazy collection is loaded, in order to
use this method I have to have the value for a given property(element).
 
PropertySuppressionStrategy.suppressProperty can't be used since values of
properties are not known at that time (of course).
 
The method for suppressing attributes:
ValueSuppressionStrategy.suppressAttribute(AttributeDescriptor
attributeDescriptor, String value) can't be used since it is called for
simple properties only. (And I don't want the output
beanWriter.getXMLIntrospector().getConfiguration().setAttributesForPrimitive
s(true) gives)
 
If I had a method for suppressing elements eg:
boolean suppressElement(xxxx, Object value){
 
and this metod was checked before writing every element this would be simple
to achive.
 
regards
Jan Ole


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org