Any idea why I get the following NPE? Did I screew something upp in the EO
model .. Any idea what?
Database Exception occured: java.lang.NullPointerException
java.lang.NullPointerExceptionat
com.webobjects.eoaccess.EODatabaseContext._objectFaultWithSnapshotRelationsh
Hi All,
Quick question about the Ajax Slider component in Wonder. What is the
rationale behind the OnChangeServer binding? The behavior seems to be
that if the binding is set - regardless of its value - an ajax post
occurs to set the value. A quick peek at the source confirms that's
When I do an ant build I end up with the two tarballs (one for the
app, the other for WSR.) All seems fine. When I deploy, the paths for
WSR are wrong. The app is looking for WSR as if it was not a split
install.
This is a new app built against 5.4.3, latest Wonder, nightly of
WOLips and
I am in the process of migrating our WebObjects application to Eclipse /
WOLips. When I view the warnings in entity modeler like The relationship to
table Employee is optional but the attribute employeeNumber does not allow
nulls. I tried the check the checkBox to allow nulls for employeeNumber,
Hi all,
I' starting using the beautiful Drag and Drop feature.
Is possible to update an AjaxContainerId after the drag and drop action?
thanks
Amedeo
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list
I am creating new EO objects and I need them to be saved to the DB in the
same order that they were created so their primary keys will be in the order
created. It seems like when I call saveChanges on the editing context that
the records are just being saved to the DB all willy nilly.
It looks
Hello Dawn;
If you are using the keys as a reliable sequence, it may be better to
instead keep a separate ordering attribute rather than use the
generated keys.
cheers.
I am creating new EO objects and I need them to be saved to the DB
in the
same order that they were created so their
Oy. Is this a legacy schema that you can't modify such that the
primary keys aren't actually used for anything?
tb
On Jan 12, 2009, at 4:17 PM, Dawn Lockhart wrote:
I am creating new EO objects and I need them to be saved to the DB
in the
same order that they were created so their primary
Dawn,
I second this, whole heartedly. Don't put business meaning on the keys
(primary or foreign) of a database table. They are an artifact of the
database. You are only asking for trouble in the future when someone
says that they want to change the order, or some other horrific thing
First thought out of my head would be to try using
primaryKeyForTransaction() (spelled sth like that) in Wonder's
ERXGenericRecord in awakeFromInsertion . if awakeFromInsertion is
too early to call that, then look for some of the other State
Transition methods in Wonder's
Thanks, I'll try that.
I guess I should have mentioned that I am writing to a DB table owned by
another system and they want me to insert the records in a specific order.
Unfortunately, I have no control over the DB table design. They actually do
have a sequence number column in the DB table, but
Hi Travis,
I am experiencing the same change in the WSR path since I switched to
WO 5.4.3. There is a thread -WOFrameworksBaseURL not working -
WebObjects 5.4.3 BUG on the wo-deploy mailing list that describes
exactly that problem. Seems that it is a bug in the current WO version.
jw
Am
Just an update, this does appear to be a difference between 5.3 and
5.4.3, as I built the same app using WO 5.3 and everything worked fine.
On Jan 12, 2009, at 12:37 PM, Travis Britt wrote:
When I do an ant build I end up with the two tarballs (one for the
app, the other for WSR.) All seems
For the benefit of those not on the webobjects deploy mailing list the
workaround is to add the following two lines to your Application
constructor.
public Application() {
NSLog.out.appendln(Welcome to + name() + !);
/* ** put your initialization
Thanks! That works perfectly.
Was this filed with Apple yet?
tb
On Jan 12, 2009, at 5:57 PM, D Tim Cummings wrote:
For the benefit of those not on the webobjects deploy mailing list
the workaround is to add the following two lines to your Application
constructor.
public
On 13/01/2009, at 12:08 AM, Atli Páll Hafsteinsson wrote:
Any idea why I get the following NPE? Did I screew something upp in
the EO
model .. Any idea what?
Firstly, a little more detail. What's your environment? Version of WO,
DB, Wonder, etc?
Assuming you're using WO5.4.3, it's NPEing
Yes, bug radar 6487590
Tim
On 13/01/2009, at 9:31 AM, Travis Britt wrote:
Thanks! That works perfectly.
Was this filed with Apple yet?
tb
On Jan 12, 2009, at 5:57 PM, D Tim Cummings wrote:
For the benefit of those not on the webobjects deploy mailing list
the workaround is to add the
I'd installed a separate 3.4 and hotness a while back and wanted to
start really trying to use it this evening, so fired it up; Software
Updates, selected all the standard stuff and then got:
Update has encountered a problem.
An error occurred while collecting items to be installed
No
On 13/01/2009, at 11:14 AM, D Tim Cummings wrote:
Yes, bug radar 6487590
This may, of course, not be a bug of Apple's but with the final build.
Check the executable script for your app. i.e.,
$ less YourApp.woa/YourApp
The last line of mine has this:
eval exec ${JAVA_EXECUTABLE}
I'd installed a separate 3.4 and hotness a while back and wanted to
start really trying to use it this evening, so fired it up; Software
Updates, selected all the standard stuff and then got:
Update has encountered a problem.
An error occurred while collecting items to be installed
No
20 matches
Mail list logo
