Re: [betwixt] two bugs

From: "robert burrell donkin" <[EMAIL PROTECTED]> > i'd personally say that really betwixt should probably find addModule even > without a matching getModules but jason or james are the ones who should > be able to give a definitely answer. I think I agree. Someone may only want to parse XML and

Re: [CLI] multiple args

On Fri, 14 Jun 2002, bob mcwhirter wrote: > I want to allow multiple -D options, and have them anywhere > in the command-line. > > Right now, that's interp'd as > > maven -D maven.username=werken -D maven:deploy-site > > Which is wrong. > > Workaround is reordering the command-line: > >

Re: Torque OM Betwixt and general use

Hi Christine I'm not totally sure from your example that betwixt was or wasn't using the .betwixt file. You could turn on commons-logging to debug and you'll see what .betwixt files it loads. If you don't have log4j or logkit on your classpath and are not on JDK1.4 then there's a description of h

Re: [Betwixt] Some ideas

Hi Stephen From: "Stephen Colebourne" <[EMAIL PROTECTED]> > Hi, > A while back I looked at using Betwixt for my Bean to XML generation (Joda). > In the end I rolled my own (time pressure was a factor), but I would still > like to refactor Joda to use betwixt if possible in the longer term. > > As

[CLI] multiple args

Howdy folks-- We allow multiple values for an argument now, so that -D foo bar baz results in 'D' having 3 args. Now, I'd like to have multiple instances of single-arg options. To get the above, you'd have to do -D foo -D bar -D baz Why? maven -D maven.username=wer

cvs commit: jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/werkz JellyBuildListener.java ProjectTag.java

werken 2002/06/13 21:04:12 Modified:jelly/src/java/org/apache/commons/jelly/tags/werkz JellyBuildListener.java ProjectTag.java Added: jelly/src/java/org/apache/commons/jelly/tags/jeez JeezTagLibrary.java Log: Added the jelly:j

Re: [betwixt] bug: output is in reverse order of input...

From: "Jon Scott Stevens" <[EMAIL PROTECTED]> > on 6/13/02 11:24 AM, "robert burrell donkin" <[EMAIL PROTECTED]> wrote: > > > it's hard to see how betwixt could automatically guess the ordering > > without access to the DTD. it might be necessary to create betwixt file or > > an XMLBeanInfo class

cvs commit: jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/jeez - New directory

werken 2002/06/13 21:01:54 jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/jeez - New directory -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [betwixt] bug: output is in reverse order of input...

From: "Jon Scott Stevens" <[EMAIL PROTECTED]> > on 6/12/02 11:53 PM, "James Strachan" <[EMAIL PROTECTED]> wrote: > > > This was done originally by design. The XML introspector decides the > > ordering of the bean properties. You can configure this order using a > > BeanInfo. Or you can change this

Re: [PATCH[ [BETWIXT] various..

From: "Jon Scott Stevens" <[EMAIL PROTECTED]> > on 6/13/02 6:09 AM, "Bemt, Martin van den" <[EMAIL PROTECTED]> wrote: > > > Btw Is it ok if I update the site with the cvs version of maven or do you > > prefer to just use a released version? (the one you are using). > > -1 on cvs of maven. > > Only

Re: [PATCH[ [BETWIXT] various..

Hence my comment... -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers on 6/14/02 1:47 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Jon, so should maven only use released versions of betwixt? Ther

Re: [maven-projects] sharing the navigator...

From: <[EMAIL PROTECTED]> > James, would an xml entity to include in the navigation.xml help? It could do; though I do hate XML entities (they seem to cause so much trouble). Though as a first cut this seems worth a try. Maybe once I've understood the doc generation process a bit more we could in

Re: [betwixt] [digester] Empty stack

From: "bob mcwhirter" <[EMAIL PROTECTED]> > Howdy guys-- > > This may have been covered already, but... > > Maven uses Betwixt which uses Digester. > > We see this occasionally (consistently) > > [WARN] Digester - -Empty stack (returning null) > > Is this a message that could be demoted to DEBUG,

cvs commit: jakarta-commons/betwixt/xdocs todo.xml

jstrachan2002/06/13 20:42:20 Modified:betwixt/xdocs todo.xml Log: added the issue of the digester warning which we should avoid producing when using digester Revision ChangesPath 1.5 +8 -4 jakarta-commons/betwixt/xdocs/todo.xml Index: todo.xml

Re: [JXPATH] Difference in introspection

Steve, The idea of writing a custom JXPathBeanInfo is not that bad. On the other hand, I don't see why I could not update the introspector to recursively acquire property descriptors for all those parent interfaces. The only issue with the use of the JXPathBeanInfo for the interface is that the

Re: [PATCH[ [BETWIXT] various..

on 6/14/02 1:47 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Jon, so should maven only use released versions of betwixt? There is no released version of betwixt. -jon -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [JRCS] [PATCH] upgrade to Maven b4

Okay, I think I've got some problems with my Maven b4 environment, scrap that previous patch. I'll try again later. [EMAIL PROTECTED] wrote: > Matt, > > I'd guess your maven project.xml is out of date wrt Maven b4I don't > have b4 installed, but it definitely looks like an older version

cannot find org.apache.commons.configuration.Configuration

Hi, I want to use org.apache.commons.configuration.Configuration class. However, I cannot find this class. I have looked in common-collection jar file and other jar files available on the Jakarta site. Any ideas on where I can find this class? thanks in advance Anmol Khanna -- To unsubscribe,

Re: [JRCS] [PATCH] upgrade to Maven b4

Matt, I'd guess your maven project.xml is out of date wrt Maven b4I don't have b4 installed, but it definitely looks like an older version Can you run ant maven:validate-pom and see what happens? Thanks, -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Devel

[JRCS] [PATCH] upgrade to Maven b4

This attached patch should allow JRCS to compile under Maven b4. Well, it worked for me, anyway. I had to comment-out the main tag as it was causing a NPE under Maven b4. The other changes are whitespace- and tag-folding. =Matt -- Matt Quail -- Senior Software Engineer http://www.cortexebus

cvs commit: jakarta-commons-sandbox/jrcs/src/test/org/apache/commons/jrcs/rcs ParsingTest.java idchar.testfile make_idchar_test.sh

conor 2002/06/13 18:33:31 Added: jrcs/src/test/org/apache/commons/jrcs/rcs ParsingTest.java idchar.testfile make_idchar_test.sh Log: created a test for this problem added a test RCS file, with tags with lots of graphic characters shell script for

cvs commit: jakarta-commons-sandbox/jrcs/src/java/org/apache/commons/jrcs/rcs ArchiveParser.java ArchiveParser.jj ArchiveParserConstants.java ArchiveParserTokenManager.java

conor 2002/06/13 18:32:15 Modified:jrcs/src/java/org/apache/commons/jrcs/rcs ArchiveParser.java ArchiveParser.jj ArchiveParserConstants.java ArchiveParserTokenManager.java Log: fix package delcaration brought in line with definiti

cvs commit: jakarta-commons-sandbox/jrcs project.properties

conor 2002/06/13 18:30:50 Modified:jrcs project.properties Log: Put Javacc generated files in the right location Submitted By: Matt Quail <[EMAIL PROTECTED]> Revision ChangesPath 1.2 +6 -2 jakarta-commons-sandbox/jrcs/project.properties Index

cvs commit: jakarta-commons-sandbox/jrcs build.xml

conor 2002/06/13 18:30:03 Modified:jrcs build.xml Log: * added support for copying across test RCS files into the *.tests.jar (this needs to be cleaned up). * used correct (?) variable for javacc home Submitted By: Matt Quail <[EMAIL PROTECTED]> Revision Ch

Re: [betwixt] [digester] Empty stack

Bob, all of these have gone away when my POM in maven passes validation. try maven validate-pom and see if all is really ok. -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers

RE: [JXPATH] Difference in introspection

Dmitri, I have a NodePointerFactory impl that uses the JXPathIntrospector to create a JXPathBeanInfo object for an Interface. I take it this is incorrect usage?? Looking at the code JXPathBasicBeanInfo.getPropertyDEscriptors() tests for an Interface but the BeanInfo object returned by java.beans

cvs commit: jakarta-commons/betwixt project.xml

mvdb2002/06/13 13:31:00 Modified:betwixt project.xml Log: Added myself to the list of developers Revision ChangesPath 1.5 +6 -0 jakarta-commons/betwixt/project.xml Index: project.xml =

cvs commit: jakarta-commons/cli project.xml

jkeyes 2002/06/13 13:23:08 Modified:cli project.xml Log: corrected my contact information Revision ChangesPath 1.2 +4 -4 jakarta-commons/cli/project.xml Index: project.xml === RCS f

Re: [maven-projects] sharing the navigator...

James, would an xml entity to include in the navigation.xml help? -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers

Re: [PATCH[ [BETWIXT] various..

Jon, so should maven only use released versions of betwixt? -- dIon Gillard, Multitask Consulting Work: http://www.multitask.com.au Developers: http://adslgateway.multitask.com.au/developers

RE: [Collections] Naming conventions

On Thu, 13 Jun 2002, Jack, Paul wrote: > I'm even okay with the wrapper classes being package-protected > OUTER classes defined in the same source file. Having > package-protected classes still gives us a lot of leeway with > organizing things, as technically users shouldn't be using > package-

Re: [Collections] Naming conventions

On Thu, 13 Jun 2002, Jonathan Carlson wrote: > I personally like the Lists, Sets, Collections, etc naming, > too. We could put pass-through methods to > java.util.Collections on the commons.Collections class. > That way we can have our cake and eat it too. "too" implies that Stephen was infav

Re: [Collections] Naming conventions

On Thu, 13 Jun 2002, Stephen Colebourne wrote: > What you describe does indeed compile, but isn't the proposal. The following > demonstrates (I hope) why they need to be package scoped. > > public class CollectionUtils { > public static Collection predicatedCollection(Collection coll) { > r

[betwixt] [digester] Empty stack

Howdy guys-- This may have been covered already, but... Maven uses Betwixt which uses Digester. We see this occasionally (consistently) [WARN] Digester - -Empty stack (returning null) Is this a message that could be demoted to DEBUG, or does it truly indicate that we've got an issue

RE: [Collections] Naming conventions

> I personally like the Lists, Sets, Collections, etc naming, > too. We could put pass-through methods to > java.util.Collections on the commons.Collections class. > That way we can have our cake and eat it too. I definitely agree that code like this is nicer: Bag bag = Bags.synchronizedBa

RE: [Collections] Naming conventions

> 2) Subclassing would be more complex. Currently each > Predicate decorator > implementation extends another based on the interface > hierarchy. In order to > continue this, the static nested classes would need to be > package scoped, > not private. Not a big issue, but it should be noted. I'

Torque OM Betwixt and general use

Hello, since there is no commons-user-List, i'll try my luck here. I am using Turbine along with Torque as an OM-Tool. Some data of an object generated with Torque should be stored in a XML-DB (Xindice, to be ecaxt). Now i thought i might use betwixt to map the wanted attributes to a nice XML an

Re: [Collections] Naming conventions

Concerning the Collections name collisions. Here's another option: I personally like the Lists, Sets, Collections, etc naming, too. We could put pass-through methods to java.util.Collections on the commons.Collections class. That way we can have our cake and eat it too. The only people that

cvs commit: jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/ant AntTagLibrary.java

werken 2002/06/13 15:12:41 Modified:jelly/src/java/org/apache/commons/jelly/tags/ant AntTagLibrary.java Log: Removed debugging exception. Revision ChangesPath 1.9 +0 -2 jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/t

Re: [Collections] Naming conventions

From: Michael A. Smith <[EMAIL PROTECTED]> > On Thu, 13 Jun 2002, Stephen Colebourne wrote: > > 2) Subclassing would be more complex. Currently each Predicate decorator > > implementation extends another based on the interface hierarchy. In order to > > continue this, the static nested classes wou

cvs commit: jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly/tags/core IncludeTag.java

werken 2002/06/13 14:31:14 Modified:jellyproject.properties project.xml jelly/src/java/org/apache/commons/jelly JellyContext.java jelly/src/java/org/apache/commons/jelly/expression/jexl JexlExpressionFactory.java

[Betwixt] Some ideas

Hi, A while back I looked at using Betwixt for my Bean to XML generation (Joda). In the end I rolled my own (time pressure was a factor), but I would still like to refactor Joda to use betwixt if possible in the longer term. As you are talking about a 1.0 release, I thought I'd jot down some of t

Re: [Collections] Naming conventions

On Thu, 13 Jun 2002, Stephen Colebourne wrote: > 2) Subclassing would be more complex. Currently each Predicate decorator > implementation extends another based on the interface hierarchy. In order to > continue this, the static nested classes would need to be package scoped, > not private. Not a

Re: [Collections] Naming conventions

Following this through we have Collections Lists Sets Maps Bags Trees (hopefully!) Predicates Transforms Factories Comparators Iterators I see three issues: 1) 'Collections' still clashes with java.util. We could: - say tough, use the full package name - name it ApacheCollections - name it Common

Re: JEX wants to play in the sandbox

Absolutely! The match there seems to be perfect. The only suggestion I would make is - hide the language name in the expression: Query q = persistenceManager.getQuery(MyClass.class, "javascript:someObjects.myProperty < $varName" ); This will only simplify your implementation. - Dmit

Re: [betwixt] bug: output is in reverse order of input...

on 6/13/02 11:24 AM, "robert burrell donkin" <[EMAIL PROTECTED]> wrote: > it's hard to see how betwixt could automatically guess the ordering > without access to the DTD. it might be necessary to create betwixt file or > an XMLBeanInfo class to correctly order the output. > > - robert I'm not s

Re: [betwixt] bug: output is in reverse order of input...

on 6/13/02 11:24 AM, "robert burrell donkin" <[EMAIL PROTECTED]> wrote: > am i right in assuming that ordering the element automatically from the > parsing would only work if the same XMLIntrospector instance is used to > read and write? That is the case right now for me anyway... -jon -- To

Re: [PATCH[ [BETWIXT] various..

on 6/13/02 6:09 AM, "Bemt, Martin van den" <[EMAIL PROTECTED]> wrote: > Btw Is it ok if I update the site with the cvs version of maven or do you > prefer to just use a released version? (the one you are using). -1 on cvs of maven. Only use released versions please. -jon -- To unsubscribe, e

Re: [betwixt] bug: output is in reverse order of input...

on 6/12/02 11:53 PM, "James Strachan" <[EMAIL PROTECTED]> wrote: > This was done originally by design. The XML introspector decides the > ordering of the bean properties. You can configure this order using a > BeanInfo. Or you can change this order via a .betwixt file for your bean. The output o

RE: [Collections] Naming conventions

Here's an idea. We can make the source more manageable and effectively limit the number of public classes by breaking my One Decorator Class To Rule Them All into smaller ones based on subinterface: Bags (for SortedBags too) predicatedBag predicatedSortedBag synchronizedBag

RE: [PATCH[ [BETWIXT] various..

Hi everyone, Hi was highly overwhelmed by the huge number of +1 (and even a +100 ;). (Geir : thank you too, you probably know what I mean if you followed the proposal Pier made on general) I want to thank everybody for giving me that trust and therefor the appreciation of the work I did. I will

Re: [PATCH[ [BETWIXT] various..

On Thursday, June 13, 2002, at 02:53 PM, James Strachan wrote: > From: "Bemt, Martin van den" <[EMAIL PROTECTED]> >> Thanx James, >> >> My commit test will be adding myself to the project.xml then ;). > > :-) > > Go ahead and make your own patches from now on ;-) welcome! i'd wasn't quick enou

DO NOT REPLY [Bug 9845] New: - Default LogFactory Implementation fails for Log4J

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-commons-sandbox/jexl/src/test/org/apache/commons/jexl JexlTest.java

geirm 2002/06/13 09:11:28 Modified:jexl/src/test/org/apache/commons/jexl JexlTest.java Log: Added test for resolver Revision ChangesPath 1.11 +53 -2 jakarta-commons-sandbox/jexl/src/test/org/apache/commons/jexl/JexlTest.java Index: JexlTest.java ==

cvs commit: jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl/resolver FlatResolver.java

geirm 2002/06/13 09:10:44 Added: jexl/src/java/org/apache/commons/jexl/resolver FlatResolver.java Log: resolver that just looks up the data from the context w/o regard to structure Revision ChangesPath 1.1 jakarta-commons-s

cvs commit: jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl Expression.java ExpressionImpl.java

geirm 2002/06/13 09:09:54 Modified:jexl/src/java/org/apache/commons/jexl Expression.java ExpressionImpl.java Log: Added resolver support Revision ChangesPath 1.2 +17 -1 jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl/Exp

cvs commit: jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl JexlExprResolver.java

geirm 2002/06/13 09:09:33 Added: jexl/src/java/org/apache/commons/jexl JexlExprResolver.java Log: interface for custom expression resolvers Revision ChangesPath 1.1 jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl/JexlExprResolver.java

cvs commit: jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl/resolver - New directory

geirm 2002/06/13 09:08:28 jakarta-commons-sandbox/jexl/src/java/org/apache/commons/jexl/resolver - New directory -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: [Collections] Iterators and ObjectStreams

Hello, > >> ObjectStream ... > > I\'m not sure of what you mean... > > The rationale goes like this: [.. cut..] Ok, so the idea looks very nice, however, the name ObjectStream does not fit well to JDK naming conventions. It suggests something like InputStream, and not the Iterator. Maybe it cou

RE: JEX wants to play in the sandbox

Juozas, Stephen, Sounds very exciting. The JEX APIs are not cast in stone as yet. Let me know how they should be changed to accomodate your needs. I will happily make the changes. We could also use more contributors on JEX. Thanks, - Dmitri --- Juozas Baliuka <[EMAIL PROTECTED]> wrote: > >

[HttpClient] Implementing support for authenticated proxies

Hi, Attached is a patch (diff.txt) and the full changed files (changes-evert.zip) which includes: - Sachin's changes for SSL tunneling - Changes to enable an alternative SSLSocketFactory to be set, for getting around "untrusted server certificate chain" errors. - Changes to give access to the tim

commons-logging in Applet Errors

Hello, I searched the archive for posts regarding errors in commons-logging when being used inside an applet. I was wondering if there is a workaround for this, a way to disable it, or if there is a design decision why commons-logging should not be used inside an applet. I'm tryin

cvs commit: jakarta-commons-sandbox/jelly/src/java/org/apache/commons/jelly TagSupport.java

jstrachan2002/06/13 07:07:25 Modified:jelly/src/java/org/apache/commons/jelly TagSupport.java Log: Minor patch to use 'isTrim' rather than 'getTrim' to follow the JavaBeans spec for boolean properties. Revision ChangesPath 1.10 +8 -8 jakarta-commons-sandbox/j

Re: [PATCH[ [BETWIXT] various..

From: "Bemt, Martin van den" <[EMAIL PROTECTED]> > Thanx James, > > My commit test will be adding myself to the project.xml then ;). :-) Go ahead and make your own patches from now on ;-) > Btw Is it ok if I update the site with the cvs version of maven or do you > prefer to just use a released

[GUMP] Build Failure - commons-fileupload

This email is autogenerated from the output from: Buildfile: build.xml BUILD FAILED Target `dist' does not exist in

RE: [PATCH[ [BETWIXT] various..

Thanx James, My commit test will be adding myself to the project.xml then ;). Btw Is it ok if I update the site with the cvs version of maven or do you prefer to just use a released version? (the one you are using). Mvgr, Martin -Oorspronkelijk bericht- Van: James Strachan [mailto:[EMA

Re: [JXPATH] Difference in introspection

Stephen, > Any reason why Interfaces are introspected differently Objects ? > > When an Interface is introspected "PropertyDescriptors" are created only for > methods defined on the Interface and not for inherited methods. This is not > the case when an Object is introspected. > > Is this expect

Re: [PATCH[ [BETWIXT] various..

Patches applied Martin - once again thanks! James - Original Message - From: "Martin van den Bemt" <[EMAIL PROTECTED]> To: "Jakarta Commons Developers" <[EMAIL PROTECTED]> Sent: Thursday, June 13, 2002 12:13 AM Subject: [PATCH[ [BETWIXT] various.. > Hi, > > I fixed the build.xml, which

cvs commit: jakarta-commons/betwixt build.xml

jstrachan2002/06/13 04:57:41 Modified:betwixt build.xml Log: applied Martin's patch which apparently helps him run the demos. Revision ChangesPath 1.4 +2 -2 jakarta-commons/betwixt/build.xml Index: build.xml

cvs commit: jakarta-commons/betwixt/xdocs powered.xml

jstrachan2002/06/13 04:55:08 Modified:betwixt/xdocs powered.xml Log: applied Martin's powered by patch Revision ChangesPath 1.2 +6 -0 jakarta-commons/betwixt/xdocs/powered.xml Index: powered.xml ==

Re: REPOST: Handlers for HttpClient?

Hi Matt, The LGPL license is more restrictive than the Apache license. Thus, any changes made to the Innovation HTTPClient must be distributed as LGPL. The other way around would be easier - contributing code from the Jakarta HttpClient to the Innovation HTTPClient project. I had a quick look a

Re: [Collections] Iterators and ObjectStreams

> Ok, so the idea looks very nice, however, the name ObjectStream > does not fit well to JDK naming conventions. It suggests > something like InputStream, and not the Iterator. Well, concuptually, can you tell the difference? :-) Seriously: InputStreams, Readers and Iterators all iterate (Reade

cvs commit: jakarta-commons-sandbox/jelly/src/test/org/apache/commons/jelly/expression TestExpressions.java

jstrachan2002/06/13 02:40:53 Modified:jelly/src/test/org/apache/commons/jelly/expression TestExpressions.java Log: Improved test cases for Ant style variable expressions Revision ChangesPath 1.3 +3 -0 jakarta-commons-sandbox/jelly/src/

cvs commit: jakarta-commons-sandbox/jelly/src/test/org/apache/commons/jelly/expression TestExpressions.java

jstrachan2002/06/13 02:27:14 Modified:jelly/src/test/org/apache/commons/jelly test_args.jelly jelly/src/java/org/apache/commons/jelly/expression/jexl JexlExpression.java JexlExpressionFactory.java jelly/src/test/org/apache/commons/je

[Collections] Iterators and ObjectStreams

>> ReadAheadIterator - you know what I mean > No... The ReadAheadIterator would read one object ahead in a buffer. >> ObjectStream ... > I\'m not sure of what you mean... The rationale goes like this: Iterators are not only views upon collections. An iterator/enumeration/object stream is (or

cvs commit: jakarta-commons-sandbox/jelly/src/test/org/apache/commons/jelly TestParser.java

jstrachan2002/06/13 01:16:47 Modified:jelly/src/java/org/apache/commons/jelly/tags/core CoreTagLibrary.java jelly/src/java/org/apache/commons/jelly/impl ScriptBlock.java jelly/src/java/org/apache/commons/jelly

Re: [Configuration] Proposals

Interesting. I have a config-framework myself, and lacks some of the kind of features that you listed. The features that I have in mine includes: Bean-driven: sub packages in the system simply throws empty beans into the configuration framework. The config framework populates the bean from th

RE: JEX wants to play in the sandbox

Hi, I going to use this idea to implement in memory query for persistent objects and may be for JDO QL. At 14:38 2002.06.12 +, Stephen Colebourne wrote: >Dmitri, >I have had a simiilar idea of using a prefix such as xpath:. I need to add >functionality similar to this to the Joda project to