Re: Proposal to make BSF an ASF project
>"Pier P. Fumagalli" wrote: >> >> Sam Ruby at [EMAIL PROTECTED] wrote: >> >> > Craig R. McClanahan wrote: >> >> >> >> +1 for BSF as a Jakarta project. >> > >> > Ditto. >> >> Doh :) +1 >> >> Pier > >Re me > >+1 > >geir +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
"Pier P. Fumagalli" wrote: > > Sam Ruby at [EMAIL PROTECTED] wrote: > > > Craig R. McClanahan wrote: > >> > >> +1 for BSF as a Jakarta project. > > > > Ditto. > > Doh :) +1 > > Pier Re me +1 geir -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Developing for the web? See http://jakarta.apache.org/velocity/ You have a genius for suggesting things I've come a cropper with! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
+1 for BSF as a Jakarta project. Bill Stoddard wrote: > > BSF is IBM's Bean Scripting Framework. Find a description here: > http://oss.software.ibm.com/developerworks/projects/bsf > > Jakarta already hosts some BSF related stuff here: > http://jakarta.apache.org/taglibs/doc/bsf-doc/intro.html > > To the best of my recollection, Sam Ruby started a discussion about BSF becoming an >ASF > project a number of months ago and the concensus was that this was a "good thing" and > should happen. Is that still the concensus? > > If the Jakarta PMC supports making BSF an ASF project, I will work to get IBM >permission > to make it happen. There is no such thing as a "sure thing" but last time I checked, >I was > reasonably sure that I could get approval donate BSF to the Apache Software >Foundation > (with appropriate license changes, etc.). > > Assuming I can get IBM approval and general concensus from ASF developers, Chuck >Murcko > and Victor Orlikowski will be involved in the project from IBM's side (and will do >the > work to get the code base into CVS, set up a mailing list, and BSF home page). My >thinking > would be to essentially shut down the developerworks project and migrate the few >folks on > the existing BSF mailing list to the BSF mailing list hosted the ASF. And the more >folks > interested in participating the better. > > Please let me know if I should spend my time getting IBM approval to donate BSF to >the > Apache Software Foundation. > > Thanks, > > Bill > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
Sam Ruby at [EMAIL PROTECTED] wrote: > Craig R. McClanahan wrote: >> >> +1 for BSF as a Jakarta project. > > Ditto. Doh :) +1 Pier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
On 6/22/01 1:28 PM, "Sam Ruby" <[EMAIL PROTECTED]> wrote: > Craig R. McClanahan wrote: >> >> +1 for BSF as a Jakarta project. > > Ditto. > > - Sam Ruby +1 > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
Craig R. McClanahan wrote: > > +1 for BSF as a Jakarta project. Ditto. - Sam Ruby - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
On Fri, 22 Jun 2001, Bill Stoddard wrote: > > The common criteria that we use for any new project is to ask what the > > existing developer and user community is like. I know that there is a large > > user community, but what is the developer community like? > > BSF does not have a large developer community; Victor, Chuck and perhaps 3 other >folks > from IBM and a handful of occasional submitters. This is definitely not a high >volume > project. > > Bill > > +1 for BSF as a Jakarta project. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WA S : XML parser: old version
I'd like to have a release since when I try to rebuild the latest 1.1 (april) I got the following error : Buildfile: build.xml jaxp.jar: [copy] Could not find file /root/crimson-1.1/lib/jaxp.jar to copy. prepare: [mkdir] Created dir: /root/build/crimson [mkdir] Created dir: /root/build/crimson/classes compile: [javac] Compiling 98 source files to /root/build/crimson/classes [javac] /root/crimson-1.1/src/org/apache/crimson/jaxp/SAXParserFactoryImpl.java:154: cannot resolve symbol [javac] symbol : method getXMLReader () [javac] location: class javax.xml.parsers.SAXParser [javac] xmlReader = newSAXParser0().getXMLReader(); [javac] ^ [javac] /root/crimson-1.1/src/org/apache/crimson/jaxp/DocumentBuilderImpl.java:152: cannot resolve symbol [javac] symbol : method isIgnoringElementContentWhitespace () [javac] location: class javax.xml.parsers.DocumentBuilderFactory [javac] builder.setIgnoreWhitespace(dbf.isIgnoringElementContentWhitespace()); [javac]^ [javac] /root/crimson-1.1/src/org/apache/crimson/jaxp/DocumentBuilderImpl.java:153: cannot resolve symbol [javac] symbol : method isExpandEntityReferences () [javac] location: class javax.xml.parsers.DocumentBuilderFactory [javac] builder.setExpandEntityReferences(dbf.isExpandEntityReferences()); [javac] ^ [javac] /root/crimson-1.1/src/org/apache/crimson/jaxp/DocumentBuilderImpl.java:154: cannot resolve symbol [javac] symbol : method isIgnoringComments () [javac] location: class javax.xml.parsers.DocumentBuilderFactory [javac] builder.setIgnoreComments(dbf.isIgnoringComments()); [javac] ^ [javac] /root/crimson-1.1/src/org/apache/crimson/jaxp/DocumentBuilderImpl.java:155: cannot resolve symbol [javac] symbol : method isCoalescing () [javac] location: class javax.xml.parsers.DocumentBuilderFactory [javac] builder.setPutCDATAIntoText(dbf.isCoalescing()); [javac]^ [javac] 5 errors BUILD FAILED /root/crimson-1.1/build.xml:47: Compile failed, messages should have been provided. The latest xml-crimson from cvs works but I'd like to a release (may be 1.1.1 ?) Regards - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-Original Message- >From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]] >Sent: Friday, June 22, 2001 4:26 PM >To: [EMAIL PROTECTED] >Subject: Re: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : >WA S : XML parser: old version > > >For Tomcat defintely the best option would be CRIMSON, as it's >TINY, fast, >compliant, and it works... And it shouldn't crash the whole >shit if you have >JAXP already installed somewhere > >Pier > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > : - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WAS : XML parser: old version
For Tomcat defintely the best option would be CRIMSON, as it's TINY, fast, compliant, and it works... And it shouldn't crash the whole shit if you have JAXP already installed somewhere Pier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
My own personal POV is that it would make a welcome addition to the ASF, assuming that it doesn't better "fit in" with a pre-existing project. Bill Stoddard wrote: > > > The common criteria that we use for any new project is to ask what the > > existing developer and user community is like. I know that there is a large > > user community, but what is the developer community like? > > BSF does not have a large developer community; Victor, Chuck and perhaps 3 other >folks > from IBM and a handful of occasional submitters. This is definitely not a high >volume > project. > > Bill > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- === Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "It's *good* to be the King." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Proposal to make BSF an ASF project
> The common criteria that we use for any new project is to ask what the > existing developer and user community is like. I know that there is a large > user community, but what is the developer community like? BSF does not have a large developer community; Victor, Chuck and perhaps 3 other folks from IBM and a handful of occasional submitters. This is definitely not a high volume project. Bill - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What are we doing in regards to JDK 1.4?
> What I really think should happen is that Sun should manage the >language (things like syntax, language enhancements and things >that abstract >the hardware). If they want to, they could have a separate group that >programs extensions, but these should be optional and not >bundled with the >JVM (after all, bundling with a package is what got Microsoft >in trouble). +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What are we doing in regards to JDK 1.4?
> -Original Message- > From: Endre Stølsvik [mailto:[EMAIL PROTECTED]] > Sent: Friday, June 22, 2001 3:59 AM > To: [EMAIL PROTECTED] > Subject: Re: What are we doing in regards to JDK 1.4? > > > > Isn't it actually quite cool that Sun is including lots of > functionality > with it's Java core? I kind of feel that this is among what > makes Java so > extremely cool, that a _lot_ of commonly used functionality > is already in > the core. And you're guaranteed that it will be there when > you deploy your > little program somewhere else. This, of course, especially > goes for the > native parts of the language, like GUI and Connections and other HW > interfacing parts. > But this adds to larger JVM installs and increases the size of installed applications. In today's JVM if I don't need reg-ex in my application then I don't have to take the storage space hit. A package or two might not seem like a lot, but when you add up all the separate packages they have added (Swing, Collections, java.text, etc) you start seeing the bloat. When you distribute an application with a JRE, your installer size keeps growing and it takes your users longer and longer to download and more and more disk space to install. What I really think should happen is that Sun should manage the language (things like syntax, language enhancements and things that abstract the hardware). If they want to, they could have a separate group that programs extensions, but these should be optional and not bundled with the JVM (after all, bundling with a package is what got Microsoft in trouble). Randy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FW: [POLL] Tomcat 3.x RPMS : Which XML Parser to be put in ? : WA S : XML parser: old version
Thanks for any POSITIVE comments. >From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] >Sent: Friday, June 22, 2001 11:42 AM >To: [EMAIL PROTECTED] >Subject: RE: [POLL] Tomcat 3.x RPMS : Which XML Parser to be >put in ? : WA S : XML parser: old version > > >>> I launch that poll to see if which XML parser RPMS users want to >>> see included by default. >>Probably no XML parser should be included. . Just document the >>fact that >>admin should synlink necessary jars to the tomcat lib >>directory. IMHO it >>is wrong idea to include parser with any java app which requires it. >>JAXP API makes this unnecessary (definitely unless Tomcat uses some >>special private API from crimson or xerces). > >If I didn't include a default XML parser, we'll receive just too many >emails from new users telling about 'tomcat couldn't find XML parser'. > >The XML parser should be included in the distro since new and average >users MAY never use XML in their apps. > >The experienced users in XML known what is JAXP, NAMESPACE, and also >know what parser they want to be used. Note that with TC 3.3/4.0 you'll >could use a different parser... > >The real question is what could be a reasonable choice as XML for >Tomcat (size, functionnalities, stability...) > >I'll forward the POLL to general-xml and general-jakarta !: > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What are we doing in regards to JDK 1.4?
[ -- cut -- ]
| A couple of years ago, Rick Ross wrote an editorial about the problem of
| Sun putting Java companies out of business by putting the functionality
| of their products into the Java core ("Tools Before Jewels", Java Developer's
| Journal, April 1999 http://www.sys-con.com/java/archives/subscribe/0404/)
[ -- cut -- ]
| It's unfortunate that the JCP is leading to the unnecessary bloat of the
| Java core by introducing functionality that is already provided by
| numerous third-parties
Isn't it actually quite cool that Sun is including lots of functionality
with it's Java core? I kind of feel that this is among what makes Java so
extremely cool, that a _lot_ of commonly used functionality is already in
the core. And you're guaranteed that it will be there when you deploy your
little program somewhere else. This, of course, especially goes for the
native parts of the language, like GUI and Connections and other HW
interfacing parts.
If you look at it this way, then I feel that Sun is doing the right thing.
If a company comes up with something really smart, why shouldn't Sun
include it? Make a similar/better core-part of it? I feel that it's
_really_ cool that this happens, it makes the Java language evolve and
stay up-to-date.
But, if they use it exclusively to close down competiotion, then they're
not much better than MS. But I have this good trust and faith in Sun, Sun
is Cool, Sun is Nice (brainwashed some time ago ;), and I believe that
they do most of their stuff "to be nice"..
But yes, I do agree that it might seem like the JCP is way to closed, and
that Sun and their heavy _money_ partners (but not necessarily with that
much more _brains_ than the OS community) should listen to feedback a bit
more.
--
Mvh,
Endre
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
