• 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: Packaging a WO Application
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Packaging a WO Application


  • Subject: Re: Packaging a WO Application
  • From: Michael Engelhart <email@hidden>
  • Date: Fri, 18 Jun 2004 08:08:19 -0500

The only open source alternative that I know of that is based on the concepts of WebObjects is Tapestry at http://jakarta.apache.org/tapestry. You can use Hibernate and/or Cayenne to replace EOModeler apparently although I've never done anything other then download Tapestry and run the example app so it may or may not help you. As for being "forced into a license" by using WebObjects, that's true of open source as well and no one is actually forcing anybody as far as I know. Even with Open Source software you're still legally bound to the license agreement that comes with it (which is the Apache Software license in the case of Tapestry). You may want to read those licenses before switching to a fully open source system. They can be just as restrictive as a commercial license in some ways depending on what you're trying to do. That said, I use open source all the time in most aspects of my development. YMMV.

Mike
On Jun 18, 2004, at 6:28 AM, Lotsa Cabo wrote:

Art / Chuck,

Man, I love you guys.  You've been here forever and always have the
best advice.  It's a very comforting feeling to get replies from you
guys.

Well, I kinda knew the answer before I asked.  Let's get creative
here... Is there any way to use the point-n-click design methods, as
with Interface Builder for WebObjects, but either in a different IDE or
to build something other than a WebObjects application?  Assuming that
I will may end up using something like "Hibernate" to replicate the EO
functionality, the only major remaining piece would be the front end
work and how they tie in together.  Any ideas?

The goal here is to have the speed of development that WebObjects
provides but to not be forced to deploy a true WebObjects
license/configuration (e.g. monitor, etc.).  If not, then I guess we're
left with something like DreamWeaver and their JSP templates (not
really the level of quality I wanted).

R/S
Ryan
_________________________
Tired of spam? Signup for a FREE SpamJammer.Com account and say
goodbye to junk email forever!
_______________________________________________
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.
_______________________________________________
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: Packaging a WO Application
      • From: Lotsa Cabo <email@hidden>
References: 
 >Packaging a WO Application (From: Lotsa Cabo <email@hidden>)
 >Re: Packaging a WO Application (From: Art Isbell <email@hidden>)
 >Re: Packaging a WO Application (From: Lotsa Cabo <email@hidden>)

  • Prev by Date: Re: EODisplayGroup
  • Next by Date: Re: An error has occurred in the Java Bridge
  • Previous by thread: Re: Packaging a WO Application
  • Next by thread: Re: Packaging a WO Application
  • Index(es):
    • Date
    • Thread