Why XUpdateQueryResolver is declared final?

Hi all, I work on project where the XUpdate query triggers JMS message. One possibility would be to extend XUpdateQueryResolver class but it's declared final. Is there some security or other considerations for doing that? Thanks, Bob Stone

Re: [ANN] xmldb jars now accessible via Maven from ibiblio

> For those of you using maven for building, the current xmldb jars are > now accessible from the maven repository. Be aware that Xindice uses _patched_ versions of the xmldb jars. -Vladimir -- Vladimir R. Bossicard Apache Xindice - http://xml.apache.org/xindice

[ANN] xmldb jars now accessible via Maven from ibiblio

For those of you using maven for building, the current xmldb jars are now accessible from the maven repository.   -Kevin Ross

Re: minimum jvm requirements for xindice 1.1?

I've submitted a patch for the bat and sh files to use straight jetty and generate the classpath via the lcp.bat mechanism ( on Windows ) used by Ant and a couple other projects. I could spend some time and get loader working, too, I'm sure, which also was pretty straightforward. Gianugo Rabe

Re: minimum jvm requirements for xindice 1.1?

Kevin Ross wrote: Do whatever you need to make it work. Less code is better and more maintainable (either way). If we don't *need* to use forehead, then lets not, unless of course, it is less code than the alternative. You'll be able to tell best... Forehead was only a clever idea from werken: wi

Re: minimum jvm requirements for xindice 1.1?

Users of the embedded version may care more about this choice. As for me, stuck on 1.3 for now due to reasons beyond my control. So, I request JVM >= 1.3. -Terry Kevin Ross wrote: My vote, 1.4+ BUT, that's just me. Everyone else? I'm afraid some people might be stuck on older vm(s) bas

RE: minimum jvm requirements for xindice 1.1?

Do whatever you need to make it work. Less code is better and more maintainable (either way). If we don't *need* to use forehead, then lets not, unless of course, it is less code than the alternative. You'll be able to tell best... -Kevin -Original Message- From: Gianugo Rabellino [mail

Re: minimum jvm requirements for xindice 1.1?

Mailing Lists (Aadi) wrote: i vote for 1.3 also ( same reason ) , so if consensus is reached on using 1.3, is it necessary to use Forehead to start up the jetty server? Please blast it at will. It was just a pleasant cross-platform shortcut but given that it doesn't work, just go ahead and ch

Re: minimum jvm requirements for xindice 1.1?

Vladimir R. Bossicard wrote: BUT, that's just me. Everyone else? I'm afraid some people might be stuck on older vm(s) based on corporate policy or platform...Speak up everyone! Exactly... => JVM 1.3 -Vladimir i vote for 1.3 also ( same reason ) , so if consensus is reached on using 1.3,

Re: minimum jvm requirements for xindice 1.1?

Kevin Ross wrote: My vote, 1.4+ BUT, that's just me. Everyone else? I'm afraid some people might be stuck on older vm(s) based on corporate policy or platform...Speak up everyone! I'm on 1.4.1 but I'd say it's best to support 1.3 if at all possible, as the 1.3 to 1.4 switch was a pretty big one.

RE: minimum jvm requirements for xindice 1.1?

> BUT, that's just me. Everyone else? I'm afraid some people might be > stuck on older vm(s) based on corporate policy or platform...Speak up > everyone! Exactly... => JVM 1.3 -Vladimir -- Vladimir R. Bossicard www.bossicard.com

RE: minimum jvm requirements for xindice 1.1?

My vote, 1.4+ BUT, that's just me. Everyone else? I'm afraid some people might be stuck on older vm(s) based on corporate policy or platform...Speak up everyone! -Kevin -Original Message- From: Mailing Lists (Aadi) [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:51 AM To: [EMA

minimum jvm requirements for xindice 1.1?

one of the problems i'm trying to work out right now is fixing the start scripts ( xindice.bat/xindice.sh ) and I just switched today to a 1.4.1 vm and the script all of a sudden worked. Switching back to the 1.3.1 VM gave me the same NumberFormatException as before. If Xindice is going to 1.

RE: cvs commit: xml-xindice/java/src/org/apache/xindice/core Collection.java

Sorry Vladimir, it was I who did not sync...it should be good now. -Kevin -Original Message- From: Kevin Ross [mailto:[EMAIL PROTECTED] Sent: Friday, June 13, 2003 9:11 AM To: [EMAIL PROTECTED] Subject: RE: cvs commit: xml-xindice/java/src/org/apache/xindice/core Collection.java I don't

RE: cvs commit: xml-xindice/java/src/org/apache/xindice/core Collection.java

I don't think you updated everything when you made this change. It immediately broke my build. Would you try to sync the whole tree again and make sure it builds for you. I have reverted to 1.16 -Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday

Re: xindice.bat / xindice.sh scripts broken in CVS ?

On Thu, 12 Jun 2003 13:54:10 -0700 (Subject: RE: xindice.bat / xindice.sh scripts broken in CVS ?) "Vladimir R. Bossicard" <[EMAIL PROTECTED]> wrote: > > >> create nightly releases (simply put them into your cvs.apache account > > > > Vladimir, I've never used the account (other than for cvs ac

cvs commit: xml-xindice/java/src/org/apache/xindice/core Collection.java

vladimir2003/06/12 20:45:24 Modified:java/src/org/apache/xindice/core Collection.java Log: Fixing the build. Revision ChangesPath 1.17 +4 -4 xml-xindice/java/src/org/apache/xindice/core/Collection.java Index: Collection.java =

document Questions

Hi All, A few questions On Wed, 11 Jun 2003 19:29:53 +0200 Gianugo Rabellino <[EMAIL PROTECTED]> wrote: > Thanks to all of you willing to help us with the documentation. The > easiest way for us would be to have documents that follow the Apache > document DTD used in forrest. What you have to d