[betwixt] How can I ignore certain instances?

Hi, while writing XML from a large object tree, I'd like to ignore some instances that don't need to get written out. I found that the method ignoreElement(ElementDescriptor, Context) of AbstractBeanWriter simply checks for emptyElements. Is there any other way to keep individual instances

writing to xml

Hi guys, another newbie question... when I want to just write xml files, do I always need to create an object with AbstractFactory or is there a simpler way of doing things? thanks -- -- Anton Stoyanov

Re: [VFS] ranged downloads?

Mario Ivankovits wrote: Jeffrey D. Brekke wrote: Very interesting. Some ftp servers do not support the REST command, would it seek from the beginning in those cases? No. I just brew with wather too ;-) The current solution requires a REST-capable ftp server. Hmmm ... but maybe such a

[DBCP] Connection leak in PoolableConnection.close()

Hi DBCP, PoolableConnection.close() does logic equivalent to : if ( isClosed()){ throw new SQLException(.); } else { _pool.returnObject(this); } The isClosed() method is that of ancestor DelegatingConnection, and it does: if(_closed || _conn.isClosed()) { return true;

Re: [DBCP] Connection leak in PoolableConnection.close()

Hi Hugh, You have a good point there. Your suggestion is using _closed is correct but we also need to invalidate the pooled connection if the underlying connection is closed. I have put some code into this bugzilla issue: http://issues.apache.org/bugzilla/show_bug.cgi?id=33591 Can you verify

RE: [digester] Portion of configuration handled by a different pr ocessor.

Sorry about that I have now added digester in the subject. I think a custom rule class similar to the nodecreaterule will work in my scenario. The plugin still seems to assume that digester would be handling the rules for the plugin classes (even though we get the flexibility of adding these

[BeanUtiils] recursion of describe

I'm trying to take a DTO, convert it to a hashmap of String/String pairs which can then be read back into a hashmap and use BeanUtils.populate(dto, map) to reconstruct the object. Are there any BeanUtils or PropertyUtils methods that will automatically handle arrayed, mapped and nested properties

[Lang] ReflectionToStringBuilder bug

I have added this bug to bugzilla http://issues.apache.org/bugzilla/show_bug.cgi?id=33574 It states the following: I think it should be important for calls to ToStringStyle.appendFieldStart() be balanced with calls to ToStringStyle.appendFieldEnd(). The method

Re: [betwixt] How can I ignore certain instances?

On Tue, 2005-02-15 at 14:50, Christian Aust wrote: Hi, while writing XML from a large object tree, I'd like to ignore some instances that don't need to get written out. I found that the method ignoreElement(ElementDescriptor, Context) of AbstractBeanWriter simply checks for

Re: [JXPATH] Prefix on jxpath sentence when read DOM

ijorge, I have been getting a bunch of requests for a change in this area. The problem is that I currently don't know what change to make without breaking the conformance to the XPath specification. See http://issues.apache.org/bugzilla/show_bug.cgi?id=32360 Please advise, - Dmitri

Re: writing to xml

you'll probably get a quicker and better answer if you followed the list conventions and added a prefix naming the component you're interested in. - robert On Tue, 2005-02-15 at 15:26, Anton Stoyanov wrote: Hi guys, another newbie question... when I want to just write xml files, do I

RE: [digester] Portion of configuration handled by a different pr ocessor.

On Tue, 2005-02-15 at 10:12 -0800, Gogineni, Pratima wrote: I think a custom rule class similar to the nodecreaterule will work in my scenario. The plugin still seems to assume that digester would be handling the rules for the plugin classes (even though we get the flexibility of adding these

RE: [digester] Portion of configuration handled by a different pr ocessor.

Thanks again for the input Simon, My scenario is that Im trying to embed the configuration necessary for a 3rd party component in my configuration file (which means i dont want to maintain the logic for parsing and creating the objects in my code since the logic could change with upgraded