From dandrews at mediaspansoftware.com Wed Dec 5 08:37:10 2007 From: dandrews at mediaspansoftware.com (Doug Andrews) Date: Wed Dec 5 09:37:58 2007 Subject: JavaMonitor Path Wizard Message-ID: We are running JavaMonitor on OS X 10.5.1, with WO deployment 5.4 and java 1.5.0. When configuring an application, the path wizard only shows folders and no files. No files, only folders, can be selected. I know we can just type the file into the text field, but i was wondering if anyone else had this problem and if there is was solution. -Doug Andrews -Mediaspan Software From bob at apple.com Thu Dec 6 14:57:06 2007 From: bob at apple.com (Bob Frank) Date: Thu Dec 6 14:58:07 2007 Subject: MEETING: Chicago CocoaHeads / CAWUG - Dev Tools & ObjC2 - Tuesday December 11th 7:00 PM Message-ID: <67344C17-68F5-4F8C-962C-40791659E740@apple.com> IMPORTANT NOTES: Our meetings will be permanently starting at ** 7:00 ** instead of 6:00 We have a new mailing list URL: http://groups.google.com/group/cawug Email Address: cawug@googlegroups.com You can email here to subscribe immediately: cawug-subscribe@googlegroups.com -------- Hi all, Just a quick reminder. The Chicago CocoaHeads / Chicago Cocoa and WebObjects User Group (CAWUG) is holding our next meeting tonight Tuesday, December 11th, at 7:00 PM at the Apple Store on Michigan Ave. Agenda: - Introductions & Announcements - Dave Dribbin with lots Leopard Dev Tools Demos - adjournment to O'Toole's When: Tuesday, December 11th, 6:00 PM Where: Apple Store Michigan Avenue 679 North Michigan Ave. (at the corner of Huron & Michigan Ave.) Chicago, IL 60611 http://maps.yahoo.com/maps_result? ed=gYbE5Op_0Tokf_p7h61dwjbWtjC2r1YehzWw&csz=60611 http://tinyurl.com/26z5nb (in case long URL gets cut) - Dave on Leopard Tools Leopard has tons of changes under the hood that will have developers itching to try it out. Dave Dribin will be talking about the highlights of what's new for the developer in Leopard, such as development tools, Objective-C 2.0, and new and improved APIs. Dave Dribin is an independent Mac developer and consultant doing business under Bit Maki, Inc. He is also a regular columnist for MacTech magazine. - O'Tooles We will continue the discussion at our local watering hold Timothy O'Toole's at 622 Fairbanks (2 blocks east of the store). We also wish to thank the folks who run the theater space at the Apple store for letting us have our meetings there, and Jonathan 'Wolf' Rentzsch for hosting the new and revived CAWUG web site. Thanks all. Also, if you are working on a project and would like to talk about it briefly / promote it, I think it would be fun for people to hear about other people's projects. Please email me off line and you can talk at a future meeting or would like a book to review we would welcome that too. Future meetings dates and tentative topics: 1/8/08, 2/12/08, 3/11/08 January - Bob on DTrace & Instruments February - TBD on developing for WebObjects in Leopard with Eclipse and the other new tools March - TBD if the iPhone SDK is out, we hope to talk about it., if not topic TBD CAWUG Resources Mail list: http://groups.google.com/group/cawug Google Site: http://groups.google.com/group/cawug Web Site: http://www.cawug.org/ RSS feed: http://www.cawug.org/rss.xml iCal: http://ical.mac.com/chicagobob/ Chicago-CocoaHeads-CAWUG (view on the web) iCal: webcal://ical.mac.com/chicagobob/Chicago-CocoaHeads-CAWUG.ics (subscribe to in iCal) Cocoa Heads web site: http://cocoaheads.org/us/ChicagoIllinois/index.html Hope to see you at the meeting. --- Bob Frank bob@apple.com (312) 961 - 0509 [cell] (312) 902 - 7393 [office] Senior Consulting Engineer Apple Education Services From paul at plsys.co.uk Fri Dec 7 09:56:56 2007 From: paul at plsys.co.uk (Paul Lynch) Date: Fri Dec 7 09:57:15 2007 Subject: Need some advice on handling EO validation errors In-Reply-To: References: <1129FC2E-7C28-4826-BFC8-B399BBDF3432@paperfree.net> Message-ID: On 7 Dec 2007, at 16:03, Alan Ward wrote: > > The unsaved objects(s) are still in your EOEditingContext and thus > any future attempts to save > will try to save them again (along with any subsequent changes). > The approach that you describe > below is not the best one. What you want to do is to catch the > exception from ec.saveChanges() > and depending on what caused it either a) fix your code to prevent > it happening, b) modify the > EO's in your EC such that they can be saved or c) revert the EC and > abandon the unsaved changes. > If you do none of the above and keep trying to save that > editingContext then you'll just keep getting > the same error as EOF tries to persist your changes to the database. This is good advice. If you want to discard changes from your editing context, use revert(); or, in some cases, refetch() may be appropriate - but usually revert() is correct. > On Dec 7, 2007, at 8:48 AM, Greg Lappen wrote: > >> Hi all, >> >> I just recently ran into an issue where my application tried to >> save a new object to the database, the save failed, and every >> subsequent save failed with the same error. It seems that >> WebObjects maintains a queue of updates/saves to write to the >> database, and when one fails, it essentially clogs up the queue >> because WO keeps trying to save it eveytime someone calls >> saveChanges() on an editing context. What I'd like to do is set up >> a global exception handler in my application that runs whenever an >> exception is not caught by my code, and in that error handler I >> want to reset the whole EnterpriseObject stack - the cache, the >> update/save queue, everything - so that other work in the >> application can continue and not worry about cache corruption or >> anything like that. >> >> Is this possible to do? Anyone know how to do it? It is possible to do this. Implement handleException in your Application class; this isn't the best place to handle database validation errors, but it's one way of preventing uses seeing the famous WO exception page. Paul From chill at global-village.net Fri Dec 7 10:28:47 2007 From: chill at global-village.net (Chuck Hill) Date: Fri Dec 7 10:28:54 2007 Subject: Need some advice on handling EO validation errors In-Reply-To: <1129FC2E-7C28-4826-BFC8-B399BBDF3432@paperfree.net> References: <1129FC2E-7C28-4826-BFC8-B399BBDF3432@paperfree.net> Message-ID: <19FF1B38-CB73-4334-B074-0E251567B69F@global-village.net> On Dec 7, 2007, at 7:48 AM, Greg Lappen wrote: > Hi all, > > I just recently ran into an issue where my application tried to > save a new object to the database, the save failed, and every > subsequent save failed with the same error. It seems that > WebObjects maintains a queue of updates/saves to write to the > database, and when one fails, it essentially clogs up the queue > because WO keeps trying to save it eveytime someone calls > saveChanges() on an editing context. What I'd like to do is set up > a global exception handler in my application that runs whenever an > exception is not caught by my code, and in that error handler I > want to reset the whole EnterpriseObject stack - the cache, the > update/save queue, everything Why stop there? Why not just shell out a 'sudo reboot now' and be _really_ sure. > - so that other work in the application can continue and not worry > about cache corruption or anything like that. > > Is this possible to do? Anyone know how to do it? Honestly, short of terminating the application or actually rebooting the server, I can't think of a _worse_ way to handle this. You really need to get more familiar with EOEditingContext and EOValidation. You code is simply not handling the save process correctly. The situation you are seeing can also happen if you are editing in the session's default editing context, there is a validation error, and the user clicks away from the page. Rather than worry about all that, I recommend never (or really, really rarely) performing any edits (create, delete, or update) in the session's default editing context. Instead, use a peer editing context specific to the editing process (often that means specific to a page). Note carefully that _you_ are responsible for locking and unlocking peer editing contexts. The _only_ foolproof ways to do this are to use Project Wonder's ERXEC or the MultiECLockManager class. Chuck -- Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects From webobjects-lists at houdah.com Fri Dec 7 12:56:21 2007 From: webobjects-lists at houdah.com (Pierre Bernard) Date: Fri Dec 7 13:59:08 2007 Subject: Need some advice on handling EO validation errors In-Reply-To: References: <1129FC2E-7C28-4826-BFC8-B399BBDF3432@paperfree.net> Message-ID: It is important to see the EOEditingContext as a sandbox. It's the EC that contains your unsaved changes. It's not the "EOF stack" that is clogged with pending updates. Other clients of the EOF stack will not even see your local changes until they are committed. When saving fails over a validation error, you get a chance to modify your sandbox until it is in a valid state. This also implies that your EC should preferably have a rather short lifespan and a limited scope. E.g. it should no live for as long as your application instance and carry uncommited data between unrelated bits of code. I for one consider the session default editing context to be mostly a convenience for smaller applications. I use it only to load data that shares the lifespan of the session. And I never ever use this context for write operations. Pierre On Dec 7, 2007, at 5:03 PM, Alan Ward wrote: > > The unsaved objects(s) are still in your EOEditingContext and thus > any future attempts to save > will try to save them again (along with any subsequent changes). > The approach that you describe > below is not the best one. What you want to do is to catch the > exception from ec.saveChanges() > and depending on what caused it either a) fix your code to prevent > it happening, b) modify the > EO's in your EC such that they can be saved or c) revert the EC and > abandon the unsaved changes. > If you do none of the above and keep trying to save that > editingContext then you'll just keep getting > the same error as EOF tries to persist your changes to the database. > > Alan > > On Dec 7, 2007, at 8:48 AM, Greg Lappen wrote: > >> Hi all, >> >> I just recently ran into an issue where my application tried to >> save a new object to the database, the save failed, and every >> subsequent save failed with the same error. It seems that >> WebObjects maintains a queue of updates/saves to write to the >> database, and when one fails, it essentially clogs up the queue >> because WO keeps trying to save it eveytime someone calls >> saveChanges() on an editing context. What I'd like to do is set up >> a global exception handler in my application that runs whenever an >> exception is not caught by my code, and in that error handler I >> want to reset the whole EnterpriseObject stack - the cache, the >> update/save queue, everything - so that other work in the >> application can continue and not worry about cache corruption or >> anything like that. >> >> Is this possible to do? Anyone know how to do it? >> >> Thanks so much for any help. >> >> Greg >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/webobjects-dev/award%40apple.com >> >> This email sent to award@apple.com > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > http://lists.apple.com/mailman/options/webobjects-dev/webobjects-lists%40houdah.com > > This email sent to webobjects-lists@houdah.com - - - Houdah Software s. ? r. l. http://www.houdah.com HoudahGeo: One-stop photo geocoding HoudahSpot: Powerful Spotlight frontend From juergen.rohrbach at xs-solutions.de Thu Dec 13 22:33:28 2007 From: juergen.rohrbach at xs-solutions.de (=?ISO-8859-1?Q?J=FCrgen_Rohrbach?=) Date: Thu Dec 13 23:33:32 2007 Subject: Leopard, WebObjects 5.4, MySQL 5.0 deadlock Problem Message-ID: <37EF5DE5-789F-489F-A895-6F43B9ECB77A@xs-solutions.de> Hello, i have ported my apps to leopard and webobjects 5.4. now sometime when i create new record in my app i get a deadlock. previous version on tiger and mysql 4.x works fine. now my questions: 1) is there a known deadlock problem? 2) which mysql-connector should i use? 5.x or 3.x? 3) does anybody have a similar problem? thanks juergen From juergen.rohrbach at xs-solutions.de Fri Dec 14 03:16:44 2007 From: juergen.rohrbach at xs-solutions.de (=?ISO-8859-1?Q?J=FCrgen_Rohrbach?=) Date: Fri Dec 14 03:16:51 2007 Subject: WebObjects 5.4 ValidationExceptions Message-ID: hello, after updating to 5.4 i get the exception page of webobjects when i enter a text into a number field. how can i get ride of the exception page? i want to ignore wrong inputs and convert them to null! thanks, juergen From payroll at payonline.com Fri Dec 21 08:36:43 2007 From: payroll at payonline.com (Ed Herd) Date: Fri Dec 21 08:36:49 2007 Subject: Depreciated WOBuilder Message-ID: <01C16D3F-188E-4162-B857-EAE7967F799A@payonline.com> WOBuilder made my life easier even with the crashes. I understand that it is no longer supported by Apple. Does this mean that it is broken in OS10.5+? Is it usable in Leopard? Thanks in advance for any advise. Ed From dleber at codeferous.com Fri Dec 21 08:38:34 2007 From: dleber at codeferous.com (David LeBer) Date: Fri Dec 21 08:38:38 2007 Subject: Depreciated WOBuilder In-Reply-To: <01C16D3F-188E-4162-B857-EAE7967F799A@payonline.com> References: <01C16D3F-188E-4162-B857-EAE7967F799A@payonline.com> Message-ID: <06817D9E-F81C-4AB0-8101-F92203A2C3C5@codeferous.com> On 21-Dec-07, at 11:36 AM, Ed Herd wrote: > WOBuilder made my life easier even with the crashes. I understand > that it is no longer supported by Apple. Does this mean that > it is broken in OS10.5+? > Is it usable in Leopard? > Thanks in advance for any advise. Dead, gone, buried. The frameworks required for it to run no longer exist. ;david -- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber -- Toronto Area Cocoa / WebObjects developers group: http://tacow.org From jerrywwalker at gmail.com Fri Dec 21 09:08:16 2007 From: jerrywwalker at gmail.com (Jerry W. Walker) Date: Fri Dec 21 09:08:24 2007 Subject: Depreciated WOBuilder In-Reply-To: <06817D9E-F81C-4AB0-8101-F92203A2C3C5@codeferous.com> References: <01C16D3F-188E-4162-B857-EAE7967F799A@payonline.com> <06817D9E-F81C-4AB0-8101-F92203A2C3C5@codeferous.com> Message-ID: <5181A553-B7EF-457C-8337-33CF5D34194D@gmail.com> Hi, Ed, Though WOBuilder is dead in Leopard, it has been replaced (and no longer just for the cool kids) by Mike Schrag's Component Editor under Eclipse/WOLips. Google for "+'Component Editor' +WebObjects" and you'll probably see more information about it than you wanted to know. If it helps any, for all its flaws, I miss WOBuilder too. But life moves on. Regards, Jerry On Dec 21, 2007, at 11:38 AM, David LeBer wrote: > > On 21-Dec-07, at 11:36 AM, Ed Herd wrote: > >> WOBuilder made my life easier even with the crashes. I >> understand that it is no longer supported by Apple. Does this >> mean that it is broken in OS10.5+? >> Is it usable in Leopard? >> Thanks in advance for any advise. > > Dead, gone, buried. > > The frameworks required for it to run no longer exist. > > ;david > -- __ Jerry W. Walker, WebObjects Developer/Instructor for High Performance Industrial Strength Internet Enabled Systems jerrywwalker@gmail.com 203 278-4085 office From programmingosx at mac.com Fri Dec 21 09:15:17 2007 From: programmingosx at mac.com (David Holt) Date: Fri Dec 21 09:16:43 2007 Subject: Depreciated WOBuilder In-Reply-To: <5181A553-B7EF-457C-8337-33CF5D34194D@gmail.com> References: <01C16D3F-188E-4162-B857-EAE7967F799A@payonline.com> <06817D9E-F81C-4AB0-8101-F92203A2C3C5@codeferous.com> <5181A553-B7EF-457C-8337-33CF5D34194D@gmail.com> Message-ID: What a coincidence, this was just posted by Pascal last night! > New to WOLips ? Check out how to use Component Editor: > > http://www.wocommunity.org/podcasts/Component_Editor_Howto.mov On 21-Dec-07, at 9:08 AM, Jerry W. Walker wrote: > Hi, Ed, > > Though WOBuilder is dead in Leopard, it has been replaced (and no > longer just for the cool kids) by Mike Schrag's Component Editor > under Eclipse/WOLips. > > Google for "+'Component Editor' +WebObjects" and you'll probably > see more information about it than you wanted to know. > > If it helps any, for all its flaws, I miss WOBuilder too. But life > moves on. > > Regards, > Jerry > > On Dec 21, 2007, at 11:38 AM, David LeBer wrote: > >> >> On 21-Dec-07, at 11:36 AM, Ed Herd wrote: >> >>> WOBuilder made my life easier even with the crashes. I >>> understand that it is no longer supported by Apple. Does >>> this mean that it is broken in OS10.5+? >>> Is it usable in Leopard? >>> Thanks in advance for any advise. >> >> Dead, gone, buried. >> >> The frameworks required for it to run no longer exist. >> >> ;david >> > > > > -- > __ Jerry W. Walker, > WebObjects Developer/Instructor for High Performance Industrial > Strength Internet Enabled Systems > > jerrywwalker@gmail.com > 203 278-4085 office > > > > _______________________________________________ > WebObjects-dev mailing list > WebObjects-dev@omnigroup.com > http://www.omnigroup.com/mailman/listinfo/webobjects-dev From ray at ganymede.org Fri Dec 21 11:43:39 2007 From: ray at ganymede.org (ray@ganymede.org) Date: Fri Dec 21 11:50:22 2007 Subject: Depreciated WOBuilder Message-ID: <20071221124339.8b79f13574b427bb2420aeb3fe71361d.2914c92688.wbe@email.secureserver.net> An HTML attachment was scrubbed... URL: /mailman/archive/webobjects-dev/attachments/20071221/3743403b/attachment.html