• 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: Deployment rather than development mode
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Deployment rather than development mode


  • Subject: Re: Deployment rather than development mode
  • From: Ken Anderson <email@hidden>
  • Date: Thu, 29 Sep 2005 09:42:56 -0400

Mark,

There should be a WebObjects script in /System/Library/StartupItems/ WebObjects. There's a few places to uncomment to get wotaskd and JavaMonitor running.

Ken

On Sep 29, 2005, at 6:40 AM, Mark Wardle wrote:

Hi.

I'm having trouble getting WebObjects to run on system startup. I'm trying to move away from developing in "direct" mode to running in deployment mode.

I installed WO5.2 on Panther and recently upgraded to Tiger and WO5.3

SystemStarter start WebObjects doesn't work (but then again, it seems to fail with any service I enter now - it did used to work before the Tiger upgrade)
Running wotaskd manually *does* work.
I don't have any kind of WebObjects launchdaemons in /Library or / System/Library. I thought I'd find com.apple.wotaskd sitting there ready to be activated, but it isn't there!


I was inclined to re-install (also wondering maybe it was because I installed as a non-root administrative user - that used to be a known bug didn't it?) but I have WO5.3 now, and didn't want to further mess up my installation by re-installing WO5.2 and then upgrading. How would one re-install WO5.3 without going through the WO5.2 reinstall+upgrade?

Finally, does anyone know the roadmap for WebObjects (well EOF to be precise)? I'm slightly worried about where things are going as WO is now no longer supported on anything but Mac OS X. Does that mean Mac OS X specific features will creep in and make deployment on other platforms impossible? Should I have stayed with 5.2? Then again, why was EOF originally made in ObjC, moved to Java, and then a different, but less powerful framework created for ObjC(Core data)? It's certainly got me puzzled. Why can't I use the same frameworks in client- and server-based applications? It would be nice to create standalone client applications that could synchronise data changes with a server and thus support "disconnected mode" - there's no easy way of doing this as far as I can see. Why has the Java bridge been deprecated - Does that mean things are going to be increasingly difficult to support as the system evolves? Would I be better tossing the whole lot in and going for hibernate/cayenne?!? I'd rather not, as I've never been more productive than with WO/EOF, but such is the problem with tracking a proprietary platform. It would just be nice to know where we're going to be taken!

Thanks,

Mark
--
Dr. Mark Wardle
Clinical research fellow and Specialist Registrar in Neurology,
C2-B2 link, Cardiff University, Heath Park, CARDIFF, CF14 4XN. UK
email: email@hidden    email@hidden
office: +44(0)2920743454 facsimile: +44(0)2920743798
mob: +44(0)7786196137 home: +44(0)2920216341



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40anderhome.com


This email sent to email@hidden


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Deployment rather than development mode --> StartupItems fix
      • From: LD <email@hidden>
References: 
 >Deployment rather than development mode (From: Mark Wardle <email@hidden>)

  • Prev by Date: Deployment rather than development mode
  • Next by Date: Re: Merchat account
  • Previous by thread: Deployment rather than development mode
  • Next by thread: Re: Deployment rather than development mode --> StartupItems fix
  • Index(es):
    • Date
    • Thread