Slashdot Mirror

Yes, but object persistence frameworks are really cool! Get all the benefits of your relational database, but use only [Java] code to access it! SQL is great for some things (generating reports, data mining, etc), but often in an application you just want to map your objects to the DBs and back again.

Actually, Apache is a derivative (i.e. a fork) of NCSA httpd

Looks like you're right. I couldn't remember if it was a clone, fork or if it shared some code. Now we know.

The name "Apache" derives from being "a patchy server"

That's what I've always read, but when finding the above link I ran accross this which claims it was named with respect to the Apache Nation and that the "A PAtCHy server" reference is incorrect, although popular. I get the feeling they're trying to rewrite history to be politically correct. Given how open source project names come about I find the common explanation more likely, but what do I know?

I suppose next they'll tell us the Gimp was named in honor of disabled people or the character in Pulp Fiction.

Actually, Apache is a derivative (i.e. a fork) of NCSA httpd

Looks like you're right. I couldn't remember if it was a clone, fork or if it shared some code. Now we know.

The name "Apache" derives from being "a patchy server"

That's what I've always read, but when finding the above link I ran accross this which claims it was named with respect to the Apache Nation and that the "A PAtCHy server" reference is incorrect, although popular. I get the feeling they're trying to rewrite history to be politically correct. Given how open source project names come about I find the common explanation more likely, but what do I know?

I suppose next they'll tell us the Gimp was named in honor of disabled people or the character in Pulp Fiction.

I suspect IBM will want to be able to import MS Office files into their system... perhaps they'll share some code with the OpenOffice gang.

I suspect they were already doing this via the Apache Jakarta POI project.

You might be able to write a generator for Torque that can generate classes enabling you to communicate with your mystery format. Torque was recently refactored out of the Jakarta Turbine project so that it could be used independently as an object-persistence layer for any Java application. You define your database schema in an xml meta-file and Torque uses a generator to create the Java classes that you use to access the data store. In this way you don't have to muck around with JDBC. There are existing generators for most well-known databases already.

AFAIK this is not information everybody can use since this feature only exists on OpenBSD. Apache is patched to chroot() to it's own folder. The -u flag does not exist on standard Apache.

Get it here!

Oh, and last post.

Anyone use any?

In My Experience, I've been finding free software alot like commercial software: alot of it is drek, some of it is ok, and a few apps are excellent (Postnuke, for instance, works very well for a web portal), as does MySQL for a database. O and Apache, is it working ok for you too?

The decision to use is about the same, gently pry the slick brochures from the boss's hands, research reviews, comments on industry forums, opinions of friends, colleagues, etc., and if all checks out install and test. Obviously you probably don't want free software where there are few posts/changes/sourceforge updates in the last year, similarly with commercial software, except with most free stuff it's much easier to tell how many developers are currently working on the project.

Since I very rarely have found even very expensive software that had company support worth a dang, I've gotten used to getting support off of web forums and google searchs, so supporting free OSS software is about the same as supporting most commercial software.

One big difference of course is price, but another huge difference is that when there is a problem/missing feature in OSS, I can write it in or have it written in, and/or if it is a big problem in an OSS with a large user base, I have found that it gets fixed very quickly, esp. where the core code programmers are using their own product.

[1] In other words, non-XHTML XML styled with CSS or XSL, if you want to get *really* technical. Using a multiple-output-type delivery system like Apache Cocoon, you can still support older browsers and serve this up to browsers which support it. (Make sure your outgoing proxy, if any, supports the HTTP Vary header though!)

Well, I've been using Apache 2.0.x Mod_SSL OpenSSL since, Apache 2.0.35, on Windows NT 5 (Win2k). Get a compiler the instructions are available publicly.

The only reason it is not pre-compiled for binary release (win32) with OpenSSL by Apache Group is legal concerns over strong encryption:

"This version is only available at present in a -no_ssl flavor, due to ongoing questions of strong crypto redistribution. When a binary build with mod_ssl compiled in is made available, the -no_ssl flavor will remain as an option for those in jurisdictions that restrict ssl encryption, as well as those T8 prohibited from downloading from the ASF's US-based servers." Source:

Apache 2.0.44 and the latest OpenSSL 0.9.7a were, well, a bit of a challenge to compile, but it's done (and that was mostly to do with OpenSSL 0.9.7a). Now on to 2.0.45!

when will SSL support be ported for Apache 2?

Apache is doing it already:

http://cvs.apache.org/~dirkx/sgala.html

Or play with this also http://demo.asemantics.com/wms/asf?styles=emotions &VERSION=1.1.0&layers=rawworld,comloc&width=600&he ight=300&request=getMap&format=png&bbox=-180,-90,1 80,90
. Similar stuff for freebsd is at the same location http://http://demo.asemantics.com/zoom.pl and more powerfull www.asemantics.com/showcase/zoom.html.

FUN!

You might be looking for this:

http://jakarta.apache.org/lucene/docs/index.html

There's a reason other popular IDEs like Eclipse and JBuilder include support for Ant build.xml files!

As for free software in java, try looking at all the serverside tools.

jakarta
jboss
(and about a million other projects...)

for client developer tools
tigris

I don't understand the distinction of development shops. If anything, developers are less tolerant of poorly performing tools than consumers, at least in my experience...

The idea of embedding code in XML is a perverse distortion of what XML is really about.

XSP is really just fine. Well, it may not be embedding as we used to know it; it is specification of XML-generating Java code in XML. This way it is even able to provide some features typical for scripting languages to Java developers without the need to use the reflection API.

XML does allow for ambiguity. However, it also allows for a lot of control -- it's just that many users don't make use of it.

If you wanted to, you could write an XML document without any sort of DTD or schema. It validates, because there's nothing to validate it against. Similarly, many companies create XML files without bothering to create schemas, and so they run into problems because they didn't define their own document structures first.

XML has its own standard, but that standard isn't meant to extend to the content. It's just a few simple rules on syntax, not a tag structure. You are left to do that on your own. Similarly, the tools out there can validate XML documents against schemas or DTDs (ever tried Xalan?) but they can't do a dang thing if you don't have a schema to go with your file.

You seem to be blaming the W3C and an open file standard for your own problems with document structure. It appears you're not using the right tools.

XML needed to have the ability to embed things like Visual Basic and JavaScript in it to be really useful. I think that this is a horrible idea.

Xerces XML Apache page is pretty good. Quite powerful, nice license, good examples, but (certainly with the older versions) not terribly fast.

Flash should be replaced by a proper W3C standard, that way everybody can play without running closed code from Macromedia.

Lo and behold, just such a thing exists!!!
It's called Scalable Vector Graphics (SVG) http://www.w3.org/TR/SVG/

Don't worry, you can still do all your stupid, annoying animated 'punch the monkey' type of nonsense, but at least your monkey is standard XML. And your audience can 'view-source' your monkey if they like, thus enabling a whole community of open-sourced monkey punching animations.

You can generate it server-side (or even rasterize it for those with crappy browsers) with a spiffy batch of tools by those same people who brought you the Apache HTTP server.

There's even a very nice gtk SVG editor app available for X11, and Win32 available here.

Of course, there is a small downside, as of yet, mozilla (and IE) only support it with the use of a plugin, but if you're used to flash, you shoudln't mind that. As soon the the mozilla folks get around a liscencing issue, moz should support it natively (some builds already do).

In summary:
Proprietary 'punch the monkey' things suck ass.
Open standards-based 'punch the monkey' things suck considerably less.

Flash should be replaced by a proper W3C standard, that way everybody can play without running closed code from Macromedia.

Lo and behold, just such a thing exists!!!
It's called Scalable Vector Graphics (SVG) http://www.w3.org/TR/SVG/

Don't worry, you can still do all your stupid, annoying animated 'punch the monkey' type of nonsense, but at least your monkey is standard XML. And your audience can 'view-source' your monkey if they like, thus enabling a whole community of open-sourced monkey punching animations.

You can generate it server-side (or even rasterize it for those with crappy browsers) with a spiffy batch of tools by those same people who brought you the Apache HTTP server.

There's even a very nice gtk SVG editor app available for X11, and Win32 available here.

Of course, there is a small downside, as of yet, mozilla (and IE) only support it with the use of a plugin, but if you're used to flash, you shoudln't mind that. As soon the the mozilla folks get around a liscencing issue, moz should support it natively (some builds already do).

In summary:
Proprietary 'punch the monkey' things suck ass.
Open standards-based 'punch the monkey' things suck considerably less.

One Word: "TomCat

Hehe, you said struts.

Perhaps I am misunderstanding what you need, but the FOP project might do the trick. No need to reinvent the wheel, nor pay for it either.

why not just have a stand XML scripting language

You mean like Jelly?

Check out the XML Digester from the Apache Jakarta project, it makes parsing xml and populating data objects from xml very easy. The problem is just as someone else stated - people are using sledgehammers (SAX and DOM parsers) to swat at flies. Perhaps the Digester should be ported to Perl?

David Charboneau

Check out the XML Digester from the Apache Jakarta project, it makes parsing xml and populating data objects from xml very easy. The problem is just as someone else stated - people are using sledgehammers (SAX and DOM parsers) to swat at flies. Perhaps the Digester should be ported to Perl?

David Charboneau

Sitting on security vulnerabilities until several fixes are available and releasing them as one advisory is a good trick to try to reduce the overal number of advisories, without actually having to improve the quality or security of the product.

For a while patches were announced on Thursdays and for a while before that it was Fridays. Fridays must have run too much overtime and shown up on the boardroom radar. Thursday in Seattle is already Friday in Europe so maybe this is a play to get MSTD-induced overtime back off the radar of European managers. With a legal cap of around 37.5 hours per week per tech, business can't afford too many IIS servers.

It is strange that any would try to. Microsoft-IIS is not a viable alternative to Zeus or Apache.

If you need to hit the DB from some type of programming environment I'd recommend using a DB with an implementation of the XML:DB API. I've been looking at Xindice, and Software AG's Tamino, both of which support the Java XML:DB API, which actually seems rather nice.

As for the speed, I can't comment from personal experience, but according to the Software AG folks it's quite fast even for their customers who are indexing terabytes of data. Of course, that's pr bunny speak so it's to be taken with a grain of salt.

I'm not sure exactly how native XML DB's work, but from my research (e.g.)it seems that implementations are based on hierarchical data bases: e.g. Adabas -> Tamino.

the wiki that cocoon uses works very well...

It would also be nice to be able transform the XML via a provided XSLT into fo (FO at W3C and FOP). Then you could present the document as a PDF, RTF, Doc, Java applet, or whatever.

If it's that easy to make stuff insecure without realising it, then the httpd.conf file needs more obvious comments.

Hey - toss me a bone here :-) this is open source, tell me/us what annotations should be added to httpd.conf.. and we'll make apache a beter product.

Action >> Reaction ;-)

Dw.

Why is it that whenever someone mentions Perl, everyone has to mention how superior insert favourite language is. Does everyone feel that threatened by Perl? Do that many people hate Perl that much?

I use Perl because it lets me get the job done with little or no hassle. I like the TMTOWTDI nature of Perl, and Perl had one of the best support communities out there. There is a huge public codebase that you can draw from. And if you are building websites, there is a plethora of application frameworks and templating languages to choose from (HTML::Mason, Apache::ASP, OpenInteract, CGI::Application, AxKit, Embperl, Apache::PageKit, Template Toolkit, HTML::Template just to name a few).

What really annoys me is most of the time the complaints made against Perl are completely unfounded (like the claims made by the parent post). If someone wants me to refute the complaints made about Perl in the parent post I can, but for now I'll just end my rant here...

If you haven't used Perl before, try it, it's good!

From the apache site:

http://www.apache.org/dist/httpd/

How about blocks in Java, or functors in the Jakarta Commons Sandbox?

One problem with the way serialization is implemented in Java is that minor modifications are enough to change the "Serialization UID" of a class, which makes it impossible to deserialize objects that have been written using an earlier version of the class.

Of course, in part this is a conceptual problem not confined to Java, but in Java it's particularly nasty. Adding a column to an SQL table is a no-brainer. But add a field to a Java class and all previously serialized objects of that class will become useless.

Another problem with serialization in Java is that in practice it works only if you always use the same VM for both serializing and deserializing, which essentially means that you won't be able to upgrade easily as long as you have serialized data sitting on your hard drive. This is true for both the Sun and the IBM implementations.

I personally go a long way round Java serialization for these reasons. Java is fine, but you're better off using one of the other available persistence layers. EJB (whose initial version sucked, but 2.0 is cool) and JDO already have been mentioned, Xindice may also be worth a look at - it allows you to query data using XPath expressions. Like Prevailer this is only suited for small-scale applications that can do without ACID, though. May be interesting for reading/writing XML configuration files, storing and retrieving XSL templates for CM systems, stuff on that level.

don't forget Apache James.

I'm pretty sure that you're talking about Xindice or possibly Torque

I'm pretty sure that you're talking about Xindice or possibly Torque

Huh? Many of the software packages I use are configured via plaintext files and perform extremely well, and are very easy to maintain in an enterprise enviroment.

Sounds a hell of a lot like CVS + Apache + CVSWeb.

Free yourself from J2EE:
Avalon Project: (a well thought out framework for server development)
Phoenix Server Microkernel: (a very good implementation of the avalon framework)
Enterprise Object Broker: (allows publication of any java class as a "bean" without having to conform to Enterprise Bean Spec, with hairthin differentiation between local and remote object invocation)

I myself have always believed that server software development has always been unnecessarily complex. If you like actually being able to simply, freely, quickly create a server app, then these products are for you.

Free yourself from J2EE:
Avalon Project: (a well thought out framework for server development)
Phoenix Server Microkernel: (a very good implementation of the avalon framework)
Enterprise Object Broker: (allows publication of any java class as a "bean" without having to conform to Enterprise Bean Spec, with hairthin differentiation between local and remote object invocation)

I myself have always believed that server software development has always been unnecessarily complex. If you like actually being able to simply, freely, quickly create a server app, then these products are for you.

"Most sites have less than 10Mbits of outgoing bandwidth, which Apache can fill using only a low end Pentium-based webserver."

Dunno how you come up with SSL when IPv6 is the topic ;-)
But anyway:

Apache FAQ

Should answer your Question.

Microsoft's CEOs have made it "patently" clear that they intend to restrict competing .Net implementations by cultivating Microsoft's patents, such as United States Patent Application #20020059425 "Distributed computing services platform" which covers the design and inter-operation of .NET based implementations.
Although there is prior art examples of individual technologies such as the JVM etc, Microsoft patents such as the one mentioned, define and claim the interoperation of the components, in such a way that any re-implementations will be sure to be covered by the patents. This remains true even for the Microsoft specs submited to standard

In comparison, Sun has granted the Apache and all open source developers FULL access to the specs, test kits and granted the full rights to develop competing products under the JSPA . Sun has also fully pened up the Java development standards process under the new Java Community Process (JCP) . Even to the point of granting full open source re-implentations of J2EE such as JBoss ...

JBoss received the green light last week, after Sun told ComputerWire that it would allow all of the APIs contained in J2EE 1.4 to be open sourced. Fleury had expressed concern that certain critical APIs, including Enterprise Java Beans (EJB) 2.1, would be not be made available to open source organizations.

However, Java Community Process director Onno Kluyt said: "Sun's plan with 1.4 is that although it started before JCP 2.5, by the time it ships it will allow the creation of independent implementations. I don't think the APIs are that interesting, because the license that sits on top of J2EE will allow that [independent implementations]".

There those that claim that .NET is open to re-implementation, but until Microsoft make a simliar public legal declaration to Sun's JSPA, any .NET reimplementation represents a pending legal mindfield.

Good point. Apache strikes me as more BSD-ish than GPL (see the license for more info. According to the Open Source Definition, the BSD and Apache licenses are both Open Source.

Still, you're right. Since the author goes out of his way to tout the GPL as better than the BSD License, this discrepancy should be brought to the author's attention.

That oughta get the zealots cheering.

Several Jakarta Subprojects are becoming top level projects:

db.apache.org (OJB and Torque)

avalon.apache.org (The Avalon server framework).

Plus Tapestry is moving into Jakarta. If you look around there really is a lot going on over at Apache, especially within the Jakarta projects.