5.4.3 / September 15, 2008; 10 years ago ( 2008-09-15) Written in Web Website WebObjects is a web and a server-based originally developed by As of 2009 the software has been independently maintained by a volunteer community. WebObject's hallmark features are its, database connectivity, and prototyping tools. Applications created with WebObjects can be deployed as web sites, Java desktop applications, and/or standards-based. The deployment is pure Java, allowing developers to deploy WebObjects applications on platforms that support Java. One can use the included WebObjects application server or deploy on third-party application servers such as, Apache, or IBM. Contents. History WebObjects was created by, first publicly demonstrated at the Object World conference in 1995 and released to the public in March 1996.
The time and cost benefits of rapid, object-oriented development attracted major corporations to WebObjects in the early days of, with clients including,. However, following 's merger into in 1997, WebObjects' public profile languished. Many early adopters later switched to alternative technologies, and currently Apple remains the biggest client for the software, relying on it to power parts of its online and the — WebObjects' highest-profile implementation. WebObjects was part of Apple's strategy of using software to drive hardware sales, and in 2000 the price was lowered from $50,000 (for the full deployment license) to $699. From May 2001 WebObjects was included with, and no longer required a license key for development or deployment.
WebObjects transitioned from a stand-alone product to be a part of with the release of version 5.3 in June 2005. The developer tools and frameworks, which previously sold for US$699, were bundled with Apple's. Support for other platforms, such as, was then discontinued. Apple said that it would further integrate WebObjects development tools with in future releases. This included a new EOModeler Plugin for Xcode. This strategy, however, was not pursued further. In 2006, Apple announced the deprecation of Mac OS X's Cocoa-Java bridge with the release of Xcode 2.4 at the August 2006 Worldwide Developers Conference, and with it all dependent features, including the entire suite of WebObjects developer applications: EOModeler, EOModeler Plugin, WebObjects Builder, WebServices Assistant, RuleEditor and WOALauncher.
Apple had decided to concentrate its engineering resources on the runtime engine of WebObjects, leaving the future responsibility for developer applications with the open-source community. The main open-source alternative — the with the WOLips suite of plugins — had matured to such an extent that its capabilities had, in many areas, surpassed those of Apple's own tools, which had not seen significant updates for a number of years.
Java Web Application
Apple promised to provide assistance to the community in its efforts to extend such tools and develop new ones. In a posting to the webobjects-dev mailing list, Daryl Lee from Apple's WebObjects team publicly disclosed the company's new strategy for WebObjects. It promised to 'make WebObjects the best server-side runtime environment' by:. Improving performance, manageability, and standards compliance. Making WebObjects work well with Ant and the most popular IDEs, including Xcode and Eclipse. Opening and making public all standards and formats that WebObjects depends upon WebObjects 5.4, which shipped with in October 2007, removed the license key requirement for both development and deployment of WebObjects applications on all platforms. All methods for checking license limitations were then deprecated.
In 2009, Apple stopped issuing new releases of WebObjects outside Apple. The community decided to continue development with, an open-source framework built on top of the core WebObjects frameworks and extends them. For example, Project Wonder has updated development tools and provides a framework that was not part of the original WebObjects package. Though once included in the default installation of Mac OS X Server, WebObjects was no longer installed by default starting with and shortly after, Apple ceased promoting or selling WebObjects. As of 2016, WebObjects is actively supported by its developer community, the 'WOCommunity Association', by extending the core frameworks and providing fixes with. The organization last held a Worldwide WebObjects Developer Conference, WOWODC, in 2013. In May 2016, Apple confirmed that WebObjects had been discontinued.
Tools As of 2016 most WebObjects architects and engineers are using the tools being developed by the WebObjects community. These tools run within the and are open-source.
The WebObjects plug-ins for Eclipse are known as. Building WebObjects frameworks and applications for deployment is typically achieved using the WOProject set of tools for. These tools are distributed with WOLips. Core frameworks A WebObjects application is essentially a server-side executable, created by combining prebuilt application framework objects with the developer's own custom code.
WebObjects' frameworks can be broken down into three core parts:. The WebObjects Framework (WOF) is at the highest level of the system. It is responsible for the application's user interface and state management. It uses a template-based approach to take that object graph and turn it into, or other tag-based information display standards, such as. It provides an environment where you can use and create reusable components.
Components are chunks of presentation (HTML) and functionality (Java code) often with a parameter list to enhance reusability. WebObjects Builder is used to create the and creates the.wod-file linking, for instance, a Java String object to interface objects like an input field in a web form. The (EOF) is, perhaps, the hallmark feature of WebObjects. EOF communicates with and turns database rows into an object graph. Using the developer can create an abstraction of the database in the forms of Java objects.
In order to access or insert information into the database the developer simply accesses the Java Enterprise Objects (EOs) from their business logic. After that EOF manages the Enterprise Objects and automatically creates the required -code to commit the changes to the database. Java Foundation. Both Enterprise Objects and WebObjects rest on the aptly named Java Foundation classes. This framework contains the fundamental data structure implementations and utilities used throughout the rest of WebObjects. Examples include basic value and collection classes, such as, (objects that contain key-value pairs) and formatting classes.
Java Foundation is similar to the Foundation framework contained in Apple's for desktop applications, however Java Foundation is written in Pure Java as opposed to Cocoa's Objective-C (with its Java bridge runtime wrapper). Foundation classes are prefixed with the letters 'NS' (a reference to their OS heritage). Since the transition of WebObjects to Java in 2000, the functionality of many of Apple's Java Foundation classes is replicated in Sun's own. However, they persist largely for reasons of backwards-compatibility and developers are free to use whichever frameworks they prefer. Rules-Based Rapid Application Development (RBRAD) WebObjects features a set of rapid development technologies that can automatically create a Web application without the need to write any code. Given a model file for a database, WebObjects will create an interface supporting nine common database tasks, including querying, editing and listing.
Such applications are useful for prototyping or administering a database, perhaps to check or to seed the database with data. The user interface is generated dynamically, on-the-fly at runtime using a rules-based system—no code is generated.
Consequently, one can modify an application's configuration at (using an assistant program) without recompiling or relaunching the application. Developers can utilize one of three different technologies, depending upon the type of interface they wish to employ:. Direct To Web (D2W) allows developers to rapidly create an HTML-based Web application that accesses a database. Direct To Java Client allows developers to rapidly create a client desktop application using the toolkit. An advantage of Java Client applications is that they can take advantage of the processing power of the client computer to perform operations such as sorting a list of items received from the server.
Direct To Web Services allows developers to rapidly develop Web service-based applications that provide access to a data store. Advantages of RBRAD. Vastly decreased development and debugging time;.
Increased stability through the use of highly exercised code;. By using the information contained in the data model file, applications will not violate database integrity. Normally you would have to write code to avoid such situations and handle errors generated by bad data;. Fully utilizes the validation services provided by WebObjects and Enterprise Objects. Java compatibility WebObjects is a 100% Java product with the following Java-based features:. Deployment: Applications can be deployed on any operating system that has Java 1.3 or later. Many developers have successfully deployed on and various systems such as,.
Free Java Download For Mac
Applications can also be hosted on any compatible application server such as. Java EE integration: WebObjects applications can be packaged in a single directory (an exploded.war file) that make it easier to deploy to a container.
JDBC: Since WebObjects uses for database connectivity any that has a JDBC-driver can be used within WebObjects. Swing interface: WebObjects applications can be delivered to the user as a 'Java Client application' or as a Java applet. Version history WebObjects was originally released by in March 1996, but was acquired by with their acquisition of NeXT in December of that year.
Mac users reporting problem with using Share Desktop' content in LiveMeeting web client after applying the java 1.6 update. Tried to open a ticket in Livemeeting Support (SRXID ) but got zero support from representative.:( Here is the exception from Java Console when attempting to share a Desktop in Livemeeting (web-based client running on Safari) 2009-Dec-09 02: PM: CollabWorker SIMPLE: onDone called. I can confirm what Ricardo stated above. I have a Mac and we had an update that upgraded our Java to 1.6.0.
I am running OSX 10.6.2 and Safari 4.0.4. Ever since this Java update to 1.6 happened, I have not been able to share my desktop using Livemeeting. Anytime I do, I receive an error from the Java Applet Window 'An error occured during installation of the application sharing components. For more information click here' but when you click on the link it goes to a page cannot be displayed.
I think this is link it's trying to go to: http://r.office.microsoft.com/r/rlidLiveMeeting?p1=7&p2=enus&p3=LMInfo&p4=wbcappsharemsg.