• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WebObjects vs. Microsoft's .NET
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WebObjects vs. Microsoft's .NET


  • Subject: Re: WebObjects vs. Microsoft's .NET
  • From: Art Isbell <email@hidden>
  • Date: Wed, 28 May 2003 22:15:08 -1000

On Wednesday, May 28, 2003, at 06:18  PM, Goodbye Bill wrote:

What the heck is WebObjects good for?

If you need to ask that question, then you must not have read much about WebObjects. Do I sense some resistance in the move that you are apparently being forced to make?


From what I can tell, WebObjects brings EOModler to the table and will make
life easier for the "database-to-UI" tasks.

Actually, object-to-relational mapping is what EOModeler provides. No UI is needed; an eomodel can be used in a command-line utility that accesses a DB.


Apparently, if I want to do
anything OTHER than read from a database I've got to code a separate Java
piece and then find some way to plug that piece into the site that I've
created using WebObjects.

Each page in your Web site will have an associated Java implementation of the logic behind the page. There is no mystery in plugging that Java implementation into the site. Create a new page in WebObjects Builder and the associated Java class file will be created as well.


In my example application, I am trying to create a web-based email service
(just for the learning aspect). Based on what I am finding (or NOT
finding), here is what I appear to need...


... the database is modeled using EOModler;

Correct.

... the web-based front end is created using WO and ProjectBuilder

Project Builder - an IDE that isn't WebObjects-specific and is part of Apple's developer tools, not WO
WebObjects Builder - a Web page template builder
WO frameworks and Java libraries - the basis for the implementation of your logic


; and,
   ... I will need to create a separate Java applet for any parsing
       or manipulation of files

Nope; this functionality should be included in the Java code for the page(s) that deal with the files.


and find some way to get the WO front end
       to use those Java pieces.

WebObjects Builder does this.

Is this correct?

Not exactly.

If so, then what did I spend the $700 for?

WebObjects Builder, the WO frameworks whose API's are documented at http://developer.apple.com/techpubs/webobjects/Reference/API/ index.html, a complete Web application server that deploys under OS X, Windows 2000, Solaris, and unofficially under any Java 2 SE 1.3.1 platform.


In .NET, for
example, everything is done in one IDE,

WO has one IDE - Project Builder.

with one language,

WO has one language - Java.

and one set of
class files for everything -- although you CAN break out the various classes
and objects into separate projects, you are not forced to.

Same with WO.

Can someone tell me what I'm missing?

A genuine desire to learn WO?

Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: WebObjects vs. Microsoft's .NET
      • From: Goodbye Bill <email@hidden>
References: 
 >WebObjects vs. Microsoft's .NET (From: Goodbye Bill <email@hidden>)

  • Prev by Date: Re: File access...
  • Next by Date: getting out of the sandbox
  • Previous by thread: Re: WebObjects vs. Microsoft's .NET
  • Next by thread: Re: WebObjects vs. Microsoft's .NET
  • Index(es):
    • Date
    • Thread