Hi.
I have just applied for a position that requires a "commitment to leaning WebObjects"
Cool. Not many positions out there with that. ;-)
I am excited about this, but am not sure where to start.
http://www.objectstyle.org/confluence/display/WOL/Tutorials Start with Eclipse and WOLips. The start is a bit harder because there a a couple of rough edges, but it will pay of on the long run. Apple has announced not to support the JavaBridge anymore, so WebObjects development with Xcode, WebObjects Builder, EOModeler and most of the other tools is not anymore really recommended. The tools won't go away soon, but I think it's generally a good idea to start using Eclipse now.
I have been reading through all the documentation from Apple, but am getting somewhat bogged down.
Normal feelings ... :-)
require them to use WebObjects, what would you like to see from them, knowing that they have no previous experience?
First of all, WebObjects development is divided in two big parts: - business logic development - Web application development The business logic is often a combination of an existing database (or a db you or your team has to build) and a lot of Java logic in certain places of the enterprise objects. There is validation, default settings and so on. A lot of the magic of WebObjects is in the EOF layer - that is the part handling the mapping between the database and Java. Business processes are also often modeled there. The web application itself is build with components: page level components, property level components (to display certain properties of your enterprise objects), wrapper components, and subcomponents as parts with which you build your pages according to DRY (don't repeat yourself). Book: I really liked the book from George Ruzek, "WebObjects - web application construction kit" for a start. It is a bit hard to get started with it, because it was written for older WO versions, but by only reading it, you get a good idea of what is possible, how things are done, and how you can solve certain problems. Then there are several things you have to be aware of as a WO developer: database knowledge is essential if you are working on the EOF level, sometimes you need to use raw sql, often WebObjects teams are very small so they have to act as database engineers, administrators and so on. Also you have to know a good bunch of object orientation, Java, HTML, CSS and web application problems in general. cug -- PostgreSQL Bootcamp, Big Nerd Ranch Europe, Nov 2006 http://www.bignerdranch.com/news/2006-08-21.shtml _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
