Re: [digester] XML rules, set-properties-rule, and ignoring missing properties
Hi Paul, thanks a lot for reporting, very appreciated. Can you fill a JIRA issue for that? As a Digester best practice, I suggest you to not go through the XML rules definition but, if you need a more compact way to express rules, refer to rules binder, which is pretty faster than mapping the XML document to rules. HTH, best, -Simo [1] http://commons.apache.org/proper/commons-digester/guide/binder.html http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Fri, Feb 28, 2014 at 5:57 PM, paul anderson wrote: > The javadoc on SetPropertiesRule: > >>isIgnoreMissingProperty()>>Are attributes found in the xml > without matching properties to be ignored? > > > implies that one should be able to write a rule such as > > ** > > or > ** > > > but obviously these don't work. > > Surely it's a common use-case to want to digest arbitrarily complex XML > without needing to specify one by one every attribute you don't care about? > > Requiring a user to catalog an exhaustive set of attributes all over their > digester rules creates an extraordinary burden and would also clutter the > rules as to make them near unreadable. > > Unless memory fails me, Digester used to silently ignore missing > properties, so it seems we've lost something since then. Seems that either > of the options marked *** would be a better solution than having scores of > ignore-elements all over the place: > > > > > > > > > > > > What is more, when the XML schema is extended to add attributes (common > occurrence) this pattern of "fail unless explicitly ignored" causes a > maintenance nightmare.
[digester] XML rules, set-properties-rule, and ignoring missing properties
The javadoc on SetPropertiesRule: >>isIgnoreMissingProperty()>> Are attributes found in the xml >>without matching properties to be ignored? implies that one should be able to write a rule such as ** or ** but obviously these don't work. Surely it's a common use-case to want to digest arbitrarily complex XML without needing to specify one by one every attribute you don't care about? Requiring a user to catalog an exhaustive set of attributes all over their digester rules creates an extraordinary burden and would also clutter the rules as to make them near unreadable. Unless memory fails me, Digester used to silently ignore missing properties, so it seems we've lost something since then. Seems that either of the options marked *** would be a better solution than having scores of ignore-elements all over the place: What is more, when the XML schema is extended to add attributes (common occurrence) this pattern of "fail unless explicitly ignored" causes a maintenance nightmare.
Re: [pipeline] Is it active
On 2014-02-28, Vatsyayan, Abhijat wrote: > I could not locate maven repository or downloads for commons > pipeline. pipeline is a Sandbox component, as such it hasn't seen enough developer interest to become a "proper" component and cannot make releases. AFAICT it hasn't seen any code change in more than two years. Realistically the component is not active. But that doesn't mean it has to stay that way. It might just take somebody with energy to revive it. Stefan - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
[pipeline] Is it active
I could not locate maven repository or downloads for commons pipeline. I can go to subversion, download and compile but before that I would like to know if this project has been abandoned. I do not mind contributing, this is an important capability for me but I would like to better understand the activity and interest level of this project. Abhijat This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.
[pipeline] Is it active
I could not locate maven repository or downloads for commons pipeline. I can go to subversion, download and compile but before that I would like to know if this project has been abandoned. I do not mind contributing, this is an important capability for me but I would like to better understand the activity and interest level of this project. Abhijat This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.
[ANNOUNCE] Commons Attributes has been moved to dormant
Hi, since no development has happened for a long while, the Apache Commons Attributes component has been moved to dormant. No further development is expected. The SVN location has changed from: https://svn.apache.org/repos/asf/commons/proper/attributes to: https://svn.apache.org/repos/asf/commons/dormant/attributes Synchronization of the git mirror (git:// git.apache.org/commons-attributes.git) has been deactivated. The website has moved from: http://commons.apache.org/proper/commons-attributes/ to: http://commons.apache.org/dormant/commons-attributes/ Regards, Benedikt Ritter, on behalf of the Apache Commons community -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
