Open-Xchange goes Express, sheds its SUSE roots
240395
Blog: Open-Xchange is releasing an easy to use, SMB-focused version of its email/collaboration software. What's particularly interesting is that it's built on Ubuntu, not SUSE, despite the founders' history with SUSE.
638567
Webmail.us is announcing improvements to its service next week and will migrate its core e-mail platform from Microsoft Windows to an open-source platform.
517091
Fixes made for "critical" JavaScript vulnerability in the Firefox browser and the SeaMonkey application suite.
512802
(InfoWorld) - Looking to bolster AJAX (Asynchronous JavaScript and XML) and development of Web 2.0 applications, the OpenAjax Alliance on Wednesday plans to introduce a project that addresses AJAX interoperability issues. The alliance, which features vendors such as IBM, Oracle, and Sun Microsystems, will roll out its OpenAjax Hub project. This effort involves developing a standard set of JavaScript functionality to tackle problems with interoperability arising when multiple AJAX libraries are used within the same Web page. With the hub, multiple AJAX run-time libraries would be able to coexist on a page. Version 1.0 of the OpenAjax Hub is planned for completion by the end of this calendar year; integration of the hub into AJAX toolkits expected in early 2007. "[In] today's world, AJAX libraries in general believe they own the entire browser [and] JavaScript environment, that they're the first one and the last one, so they assume a consequence-free environment where they can do whatever they want to do," said Jon Ferraiolo, acting director of the alliance and a Web architect in the emerging technologies group at IBM. What results, he said, are collisions of JavaScript objects and the toolkits managing HTML markup, and an inability to integrate functions such as drag and drop events. With development of the hub, the alliance is dealing with its top priority, said Jason Bloomberg, senior analyst at ZapThink, in an e-mail response to questions. "There is a critical need for OpenAjax at this point in time, because each vendor's AJAX implementation is generally incompatible with the others," Bloomberg said. "Basically, even though each AJAX widget leverages XML and JavaScript, both of which are open standards, that doesn't mean that one widget from one toolkit will work with another widget from some other toolkit. The most important goal of OpenAjax is figuring out how to resolve this interoperability problem. Clearly, Ajax will be far more successful if any widget works with any other widget, toolkit, or platform." Support for the hub is expected in toolkits such as Dojo and script.aculo.us as well as in AJAX frameworks such as Tibco General Interface and offerings from Backbase, JackBe and Nexaweb. "No one has made any commitments [to use the hub yet] but generally, [the parties cited] are all active in the alliance," said Ferraiolo. The unveiling of the hub is part of an update on the alliance's activities that is being provided Wednesday. The group will announce a near-doubling of its membership since its formation in February. New members include The Ajaxian, American Greetings, Bling Software, Curl, edge IPK, eLink Business Innovations, ENOVIA, MatrixOne, Finetooth, The Front Side, Ikivo, ILOG, IN2, IT Mill, Javeline, JWAX, Merced Systems, Nexaweb, Nitobi, OpenLink Software, Seagull Software, Sitepen, Sun, Vertex Logic, Vircon, Webtide, and Zoho. Previously announced members of the alliance include: Adobe, Backbase, BEA Systems, Borland, the Dojo Foundation, Eclipse Foundation, Fair Isaac, Google, IBM, ICEsoft, Innoopract, Intel, JackBe, Laszlo Systems, Mozilla Corporation, Novell, Openwave Systems, Opera, Oracle, Red Hat, SAP, Scalix, Software AG, Tibco, XML11, Zend, and Zimbra. While the alliance already has an impressive list of members, one name remains conspicuously absent: Microsoft. "Yes, we have extended an invitation and attempted to recruit Microsoft to join," Ferraiolo said. "We would love to have Microsoft participate in the alliance." "The purpose of the alliance is to make interoperability successful such that you can take AJAX technologies from one source and use it with another vendor's. Microsoft is one of [those] vendors and an important vendor in the AJAX community and it would be to everybody's advantage, particularly customers, if Microsoft's products would interoperate well with other people's products," said Ferraiolo. He added he was not making a statement that Microsoft products currently do not interoperate. Although Microsoft has promoted AJAX via its Atlas technologies, Microsoft currently does not have plans to join. "Microsoft has no firm plans to join the OpenAjax Alliance. However, Microsoft is very committed to working with the developer community and is engaged in dialogue with the OpenAjax Alliance organizers to learn more about the initiative," Microsoft said in a prepared statement. The alliance seeks to serve as an industry catalyst to boost AJAX-enabled Web 2.0 applications. Ferraiolo defines Web 2.0 as a new generation of the Web focused on collaboration. OpenAjax technologies are intended to produce lower development costs, faster delivery of applications, vendor choice, interoperability, and a richer Web experience. Greater collaboration capabilities that can be added to existing HTML sites or used for new applications is another goal. Also being unveiled on Wednesday is the organization's Web site and a white paper covering a description of AJAX, the AJAX value proposition and a technical section on AJAX architectures. These architectures include single and dual DOMs (Document Object Model), in which the single model involves processing everything in HTML browsers, while the dual approach involves using an XML parser that holds the description of the UI. The dual model offers a richer set of functionality but requires a larger download, typically, Ferraiolo said. AJAX in the open source world also is being included in the alliance's list of issues to cover. One of the goals for the alliance is the ability to have a zero-cost option, but it's not trying to lock out vendors from making money at all," said Ferraiolo. A second meeting of the alliance is planned for Oct. 5-6 in Santa Clara, Calif. The alliance on Oct. 5 plans to announce it has moved to a formal governance model that includes a steering committee. Goals and procedural issues also will be discussed. Security of AJAX also will be on the agenda, Ferraiolo said.
355339
(InfoWorld) - Open-source players MySQL and Open-Xchange are teaming up so Open-Xchange can embed MySQL's database into its Linux-based collaboration server. The two companies announced a partnership and support agreement Thursday to optimize the interaction between MySQL databases and Open-Xchange groupware functions. Open-Xchange customers won't have to pay extra for product support for MySQL, they said. The partnership will result in more choice for customers in the way that they use the Open-Xchange server and can help users cut costs, according to Open-Xchange. MySQL was interested in supporting the integration because an increasing number of companies are choosing open-source collaboration products, like Open-Xchange, instead of proprietary products, the database vendor said. Open-Xchange competes with other open-source collaboration products from ScalixÂ and Zimbra as well as established proprietary software including Microsoft's Exchange and IBM's Notes/Domino. The move is typical of a growing wave of significant partnerships being struck between commercial open-source players designed to simplify the integration of their respective products. For instance, back in June, open-source customer relationship management software vendorÂ SugarCRM announcedÂ a relationship with open-source business intelligence company JasperSoftÂ to allow SugarCRM users to generate reports using the co-developed JasperReports for the SugarCRM reporting engine.
697275
Blog: It's true that open source applications and infrastructure don't necessarily play well together today, as Microsoft suggests.  But it's also true that more than enough integration is in place for current market demand.
89340
Blog: The software giant follows through on better support for dynamic, or scripting, languages for Web development.
16286
As open source becomes pervasive, software giants like Microsoft, Oracle and Sun are adapting in different ways.
467825
(InfoWorld) - The OpenAjax Alliance, formed to boost interoperability in the AJAX (Asynchronous JavaScript and XML) realm, has put forth an aggressive roadmap that recognizes the growing trend toward mashups. Speaking at the AJAXWorld conference in Santa Clara on Monday, Jon Ferraiolo, OpenAjax operations manager and an IBM Web architect, detailed the upcoming release of the OpenAjax Hub 1.0 and the follow-up 1.1 release. Other projects including the OpenAjax Registry and IDE accommodations for AJAX also were noted by Ferraiolo. With the hub, the alliance aims to iron out interoperability issues between AJAX toolkits. "Sometimes, they actually prevent each other from working. They step on each other," Ferraiolo said. Developers can use the hub to integrate multiple toolkits within the same Web page while toolkit developers can use it to allow toolkits to talk to other toolkits. While the 1.0 hub is useful in mashup scenarios where all components come from a trusted source, version 1.1 adds a security layer for untrusted components to protect from any components that might be malicious. The 1.0 version of the hub, to include AJAX library registration and a publish-and-subscribe engine, is due by the end of this year. Version 1.1 is planned for approval next year, although a full implementation is slated to be ready by the end of 2007. "One of the key features [in version 1.1] is secure mashups," said Ferraiolo. "It's very much a security-focused enhancement providing a secure mashup framework," he said. IBM-contributed technology called SMash, for Secure Mashups, is being included in version 1.1. It provides for secure handling of third-party mashup components. Also in the security arena, the alliance has formed an AJAX Security Task Force Version 1.1 also is slated to include publishing and subscribing across frames as well as publish-and-subscribe between clients and servers. Also featured is support for the Comet programming technique to push data from the server to client. Server push is desirable particularly in mashups and portals, according to the alliance. The hub was called "absolutely essential" by attendee and author Dave Mosby. "It provides mechanisms for us to bridge between different components so that they can begin to talk to each other," Mosby said.Â  In other develpments at the alliance, the planned OpenAjax Registry will provide an AJAX toolkit and JavaScript global object registration authority to prevent JavaScript object collision within complex AJAX applications. The registry is to be managed by the OpenAjax Interoperability Working Group. Population of the registry begins this fall. OpenAjax is holding an event this week called OpenAjax InteropFest, in which companies like Microsoft are testing their AJAX toolkits for conformance with OpenAjax. Microsoft, with its Microsoft AJAX Library, has passed the conformance test, according to Microsoft.Â  The alliance also has launched a task force for mobile AJAX with a white paper planned on how to be successful with the concept. Also, the alliance will explore APIs for access to mobile device services. Device APIs would be exposed to JavaScript on these devices. A mobile AJAX workshop is planned for this Friday. "Mobile devices are getting AJAX," said Ferraiolo. An AJAX management task force, meanwhile, is being launched to make sure AJAX applications perform on a consistent basis. Another task force to be formed will focus on searchability to optimize the ability for search engines to find AJAX applications. Another OpenAjax effort is its IDE working group, which will attempt to accommodate multiple AJAX toolkits and IDEs. The alliance is trying to develop a standard XML file that describes JavaScript functions and other APIs, widgets and their properties. This project is intended to assist developers with user interface components such as widget pallets. Code compilation and type-checking on JavaScript functions also would be part of the effort. Proposals from Microsoft, Adobe Systems, and Aptana have been submitted for consideration by the IDE working group. OpenAjax Alliance features members like IBM and Microsoft.
667398
One of the major contributors to the leading open source alternative to the Microsoft Office Suite announced early this morning it will be offering additions to OpenOffice enabling it to support Office 2007's new XML-based Office Open XML format.
369995
New .mobi and .jobs, a shift in the ownership of .net
667367
Binding end-user access to once disparate technologies, vendors such as IBM Lotus and Open Text are launching products designed to pull a variety of point products into a single platform.
4935
Open source doesn't necessarily automatically translate into better paid support for customers.  But it does offer a lot more options and aligns customers with vendors more tightly.
349743
Interoperability is the great challenge facing the open-source movement.
4748
(InfoWorld) - In February, a group of technology vendors, including BEA Systems, Google, IBM, and Oracle, formed the OpenAjax Alliance, with the goal of promoting the popular AJAX (Asynchronous JavaScript and XML) Web development technique. Since then, more vendors, such as Sun Microsystems, have joined, and the alliance has launched its OpenAjax Hub project to boost interoperability among AJAX libraries. One of the founders of OpenAjax was David Boloker, who holds the titles of distinguished engineer and CTO of emerging Internet technologies at the IBM software group. He also serves on the alliance's steering committee. InfoWorld Editor at Large Paul Krill spoke with Boloker at the AJAXWorld Conference and Expo in Santa Clara, Calif., on Wednesday about AJAX, the security issues around it, and the possibilities of other vendors such as Microsoft and Apple joining the alliance. InfoWorld: Why did you found OpenAjax? Boloker: If you go back nine months, the key problem that folks were having was, one, What exactly is the definition of AJAX? The second [problem was], How do you get [a] message out to all parties that would be cross-vendor? The third thing was, From a technology standpoint, how can you basically start looking at what was going to happen when looking across toolkits? So you can have one personâs UI widget working with your UI widget, and these are all in JavaScript. And each and every one of the toolkits today, actually, expects to own the whole page; so theyâre going to basically take control, and expect to; then, when you leave their page, they lose control. Well, what really is going to have to happen is, you may like someoneâs Accordion control from one toolkit and want to use it, for example, with Tibcoâs. So one of the things which we started working on was something called OpenAjax Hub inside of OpenAjax, which is [aimed at allowing that interoperability], and thatâs going to be an open source plan. So [those were] the reasons why we started OpenAjax. Now, when you start looking at the bigger picture here and at what IBM is doing in this space, [you'll see that it] is in parallel to starting OpenAjax; what we did [at IBM] is, we started a project inside IBM to work on trying to bring down the level of complexity of writing and debugging applications, AJAX applications in particular. And the way we did it was, we built a piece of code called the AJAX Tooling Framework which went on top of Eclipse, which is the core foundation for tooling that we are using, and we can demo the AJAX Tooling Framework with the whole idea behind it [being] to bring down that level of not only complexity but also to allow someone to write a lot more AJAX code in a much shorter amount of time and get it published faster. InfoWorld: What about Microsoft -- which has its AJAX technology, Atlas -- not being a part of OpenAjax? Are there any more overtures being made? Are they just going to sit on the sidelines like they seem to do with other industry initiatives, like Eclipse? Whatâs going on there with Microsoft? Boloker: I actually just spoke with Microsoft yesterday about joining OpenAjax, and theyâve taken back the details and are thinking about it, and theyâll get back to us. InfoWorld: What do you think the impact is of Microsoft not participating? You have this massive PC software company, and theyâre not participating. Do you think it's detrimental for them to not participate, or does it not make a difference? Boloker: Well it makes a difference because Iâd actually like to have them at the table. They have some very, very skilled developers, and theyâve thought about the area a lot, just as Tibco has and IBM has and JackBe has and others. It would be actually great if we actually can get everyone to the table, and Iâm really hoping that we can do it. InfoWorld: Do you think you will? Boloker: Optimistic. InfoWorld: But they have not made any commitments to joining at this point? Boloker: None. Theyâre thinking about it at this point. InfoWorld: Are there any other major companies on the sidelines? I canât think of any right now. Boloker: Thereâs plenty of people that are in discussions with us, and those people in discussions with us are folks like Apple. Letâs see, who else would be in it? Weâre looking at Cisco as another. Cisco [is not] core to the Web piece of this. The other companies are mostly in Asia. InfoWorld: What about the issues of security around AJAX? Apparently there are a lot of them. What are you doing about that? Boloker: Security around AJAX is actually security around the Web. So thereâs many sets of issues here, and one of the things which weâre actually going to cover inside of OpenAjax is a whole discussion on security, at the meeting at the end of the week. And one of the topics is not only from a Web standpoint of cross-app scripting, which has been a problem in the Web for many, many years, when you have cross-application scripting between servers. But this whole concept of when youâre doing mashups, if youâre doing mashups all within your establishment or customer shop or you have trusted parties, mashups are secure. Itâs when you do unsecure mashups between, say, myself and someone I donât really know; that other personâs JavaScript could be misformed, or [it could] try to take control of my machine. And this is really where a question of needing to do some technology work between ourselves, the companies, as well as maybe even in the W3C to look at [the question], How do I basically bring an access list to give someone approval to use the mashup or not to use the mashup? InfoWorld: Apparently there are issues with inexperienced developers, there are issues with the cross-site scripting, there are issues with Web services. Even Jesse James Garrett who founded the term AJAX said there are a lot of issues and weâre going to have to almost patch them one by one. So how can people rely on AJAX if itâs got all these security issues? I talked to one AJAXWorld attendee yesterday, and she said she wasnât using AJAX yet, but the one thing she knew was that it apparently had a lot of security concerns. Boloker: So there are security concerns. Actually, if you look at the security concerns you have when doing Web services, there actually was work done for Web services in the area of WS-Security. A lot of folks who are looking at this are looking at it for the first time. Well, the folks that actually have looked at service-oriented architecture said, "Well, if Iâm actually going to start calling something, I want to, No. 1, ensure that I can call the resource, and then if I can call the resource that Iâm actually entitled to, go deeper and actually access the data." The second piece of this is this cross-site scripting; this has been a known problem in the Web, and itâs a server-side problem that people have been dealing with. Now, the other issues that you start looking at in the area of mashups, again, this is -- youâre absolutely correct. You have people that are writing JavaScript that donât really know how to write it, and if you create a mashup, you could end up with a serious problem. Now, if you look at the mashups that have been created up to this point, theyâve been done by very highly skilled and very knowledgeable Web programmers who know what theyâre doing. Now, one of the reasons why we founded OpenAjax was this exact problem was when Scott [Dietzen, CTO of Zimbra, who helped co-found OpenAjax,] and I looked at this problem in late 2005, we pretty much decided that the number of problems that would be confronting people, youâd probably find one in 40 developers actually having all of the right capabilities to actually write good AJAX and secure AJAX. InfoWorld: So what are you going to do? Boloker: The first thing we started doing is weâre attacking the problem not one at a time, weâre doing it in multiple fronts. The first thing was, How do we basically build AJAX, and how do we debug AJAX? And how do we see whatâs going from the client side of this to the server? And thatâs what IBM was working on, and Bob [Goodman, a senior programmer at IBM,] was doing with the AJAX Tooling Framework. The second side of this is that we needed to get the knowledge out about what are the issues. You donât want to scare people away, but at the same token, you need to basically educate them. And this, again, was part of this whole side of what OpenAJAX was about. The third side of this is, How do you then look at it from an industry standpoint of coming out with the best practices? So this is a document that people [would] write to give to AJAX programmers. And then the fourth thing is to look for the technology side of it. How can we basically start securing the technology? And that work is under way right now. And [while] there are no great answers at this exact second, thereâs a very good understanding of the problem, and people are discussing whatâs the right way to do it. InfoWorld: What is the attraction of AJAX? Boloker: AJAX enables you in a Web browser to actually have some of the same qualities of an interaction that you used to have only in a fat client setting. InfoWorld: How does it do that? Boloker: Well, what happens is, AJAX is actually, if you want to look at a set of standards that were [to] form a programming model, and those standards start off with DHTML and JavaScript and XML and thereâs Cascading Style Sheets, thereâs Web services, thereâs all of these things that are falling into this, and each and every one of these is a standard. And the use of them all together creates a toolkit. And today there are probably 200-some-odd toolkits, between closed source and open source, and each of the toolkits does things very differently. So the first thing you have to worry about is, How does it work within Firefox? How does it work within Internet Explorer? These are all different. And then, once you get beyond [that], how do I get it render effectively? Then you can start looking at, well, What are the qualities of the AJAX implementation? Can I do drag-and-drops? Can you do cut and paste, for example, from the browser and move it somewhere else? But the key thing you start looking at is, if you [look at] a great example of an AJAX application, and there are many on the Web today, [there] is one that started off with the folks from a company acquired by Yahoo called Oddpost. And the Yahoo Beta Mail actually uses Oddpost, some of the core pieces. â¦ Thereâs a group of developers that did very early work on [finding] how do I get a very, very high-quality Outlook-type mail client into a browser? And they basically were acquired by Yahoo and became Beta Mail. And if you look at what goes on inside Yahoo Mail, the first thing thatâs so apparent to you is you have the full services of a drag-and-drop all within the browser. The second thing you start looking at is the setting that youâre having is they allow you to do RSS feeds. You can look at RSS and Atom feeds. I mean, theyâre just one example. InfoWorld: Before AJAX, or theoretically before AJAX, you had Flash. Do you see Flash as a competitor, as a complementary? It just seems like it is kind of a competitive technology even if Adobe says itâs not. Boloker: I was going to tell you to ask Adobe what their opinion was. Flash is yet another example of a Web-based technology, and there are reasons why customers might want to use Flash to have an environment, a full environment, and you know there are reasons why people might want to do something just purely in DHTML and JavaScript. I mean the first obvious reason is DHTML and JavaScript [are] installed on everyone elseâs desktop today and is immediately used, whereas Flash was a plug-in. Now, that plug-in happens to be pretty much on most peopleâs machines. InfoWorld: AJAX is a technique. Is there going to be an AJAX 2.0, 3.0? Do you see an evolution of it, or is it just that this is the technique for doing something and if you get too far away from it, then itâs not AJAX anymore? Boloker: Well, itâs a programming paradigm, and with all programming paradigms, whether itâs AJAX 2.0 or AJAX 3.0, it started off as AJAX. And itâll always be AJAX. And what youâre going to do is learn, as an industry weâre all going to learn nuances to do something easier or make it much more secure, the points you brought up before. InfoWorld: So OpenAjax is not going to come out with the next version of AJAX, right? Boloker: No, OpenAjax is definitely not going to come out with another version of AJAX. OpenAjax is really going to be looking at [this] from a full industry partnership on how to move AJAX forward. Now, one might say that as we start looking at AJAX Hub and things like that, that people might say that, well, thatâs another version of AJAX. But in reality itâs the same version of AJAX. Weâre just working to build it out. InfoWorld: Any final thoughts that you want to add? Boloker: I think my only final words really come back to, Iâve been working in technology for many years, and as with any technology thatâs coming on the scenes, there are initially problems. Some of the problems have to do with, first of all, education of the audience, and the second thing has to do always with security, manageability, scalability, and things like that. Our friends from Google proved that AJAX can scale through Google Maps. For that matter, in a lot of cases I think that theyâve proved that you can run a pretty secure shop with AJAX. There are security problems that the industry.
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....
123580
openCRX is a professional CRM solution (customer relationship management) deployable to all major platforms. openCRX is multi-entity enabled, scalable, a real enterprise-class CRM-solution - new: Activity Management, Bug Tracking - try our Demo Server   openCRX - Limitless Relationship Management     openCRX version 1.11.0 is available from:   http://www.opencrx.org/     The release notes are available at:  http://sourceforge.net/project/shownotes.php?release_id=535085&group_id=95219    If you have openCRX v1.10.0 installed, you can upgrade to openCRX v1.11.0 by following instructions available at:  http://www.opencrx.org/faq.htm#110to111   Highlights:   * support for JDK 1.5 * JDO/JPOX compatible DB schemas * GUI: multi-level grid drill down * DataBindings * enhanced facility management with inventory items * new locales: es_CO and ja_JP   see http://www.opencrx.org/opencrx/1.11/new.htm for details     We also published new/updated guides at:  http://www.opencrx.org/documents.htm       Your openCRX Team