• 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: Exception only when framework is embedded
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Exception only when framework is embedded


  • Subject: Re: Exception only when framework is embedded
  • From: Mike Schrag <email@hidden>
  • Date: Fri, 8 Aug 2008 11:46:03 -0400

You want them running through the normal eclipse java launching process so you can do hot-code replacement, etc, when it runs in debug mode. Plus we get a lot of behaviors for free by piggy-backing on the Java launching process.

<mini-rant>If it doesn't work like in deployment like it does in Eclipse it's either a failure of the build system which (should be replaced|is being replaced) or it's a failure of WOBoostrap which (should be replaced|is being replaced). There's no reason why all the features that Eclipse provides in terms of dependencies and classpath ordering should not be fully supported during build and deployment. Anjo and I have talked about this several times that the framework Info.plist needs to support the definition of framework dependencies and/or its internal jar ordering, which should be interpreted by a replacement WOBootstrap to dynamically build what is currently the MacOSClassPath.txt file, which I personally despise. In general, the WO build process and deployment process is way too complicated and nasty, and it would be nice to have the tools make this suck less.</ mini-rant>

ms

On Aug 8, 2008, at 11:20 AM, Florijan Stamenkovic wrote:

To digress a bit,

I was wondering why WOLips wo app launch configs do not launch in the cmd line style. They seem to simulate the launching of a standard Java app, which can make the behavior between launching from Eclipse and deploying inconsistent. From what I understand Art's example is a good illustration of this, since I assume WOCommon gets resolved, when running from Eclipse, according to Eclipse's classpath.

F

On Aug 07, 2008, at 22:06, Art Isbell wrote:

Waldo runs without error from within Eclipse running in Web server connect mode.

_______________________________________________ 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


_______________________________________________
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: Exception only when framework is embedded
      • From: Florijan Stamenkovic <email@hidden>
References: 
 >Exception only when framework is embedded (From: Art Isbell <email@hidden>)
 >Re: Exception only when framework is embedded (From: Florijan Stamenkovic <email@hidden>)

  • Prev by Date: Re: Exception only when framework is embedded
  • Next by Date: Re: Inheritance and relationships
  • Previous by thread: Re: Exception only when framework is embedded
  • Next by thread: Re: Exception only when framework is embedded
  • Index(es):
    • Date
    • Thread