On Sep 1, 2006, at 4:00 PM, Jonny Meijer wrote:
Richard,
WO 5.3.x comes free with the latest versions of XCode 2.x, which
are available with a free ADC account. Therefore there is no need
to buy anything. I hope this reduces the uneasiness!
Jonny
On Sep 1, 2006, at 3:50 PM, Richard B
Richard,
WO 5.3.x comes free with the latest versions of XCode 2.x, which are
available with a free ADC account. Therefore there is no need to buy
anything. I hope this reduces the uneasiness!
Jonny
On Sep 1, 2006, at 3:50 PM, Richard Bruch wrote:
Ken,
thank you for fast feedback. My
Note that WOBuilder (or at least in the past ... haven't tried recently) complains that the html is invalid if you put a WO tag inside an html one...JonnyOn Aug 14, 2006, at 3:29 PM, Mike Schrag wrote:Not simplistic thinking at all, however, where things break down is that it's perfectly valid WO t
Woops ... meant to send it to the list ...
Jonny
On 11-Aug-06, at 10:38 PM, Jonny Meijer wrote:
On 11-Aug-06, at 8:25 PM, Gavin Eadie wrote:
At 12:04 AM +0100 8/12/06, Simon wrote:
i have to say that i, as one of the many dedicated webobjects
developers who couldn't attend WWDC
On Sept 15, 2005, Kevin Carlin suggested on this list the following
for v5.3 of WOBuilder:
In a bash shell, type:
defaults delete com.apple.WebObjectsBuilder
Perhaps this would work?
Jonny
On Aug 3, 2006, at 12:45 PM, Guido Neitzer wrote:
On 03.08.2006, at 16:56 Uhr, William Hatch wrote:
Oh yeah, I forgot that using XCode can cause those issues ... that's
what I get for using Eclipse and then getting real exceptions!
Jonny
On Aug 2, 2006, at 1:07 PM, Chuck Hill wrote:
When this happens the first thing I do is swear. :-) Then I quit
Xcode, rm -r build/ in the project(s).
Can't say I have nailed this one down ... it has occurred in two different cases (in the same entity, incidentally). According to the snapshot, the value of the attribute is null, yet according to EOF it's not (empty string perhaps?), I would suggest looking at your EOModel to see where EOF could
I have seen such an exception most often when there was locking on a
timestamp attribute. The exception would happen because of an issue
with the precision, I think. Regardless, the solution was to remove
locking on that attribute.
Jonny
On Jul 25, 2006, at 12:06 PM, Randy Wigginton wrot
