Re: Modelling boolean in D2W compliant way
Re: Modelling boolean in D2W compliant way
- Subject: Re: Modelling boolean in D2W compliant way
- From: Markus Ruggiero <email@hidden>
- Date: Sat, 19 Mar 2011 13:44:35 +0100
On 16.03.2011, at 14:53, Markus Ruggiero wrote: I have a (Oracle) table where boolean attributes are defined as char(1) with possible values "Y", "N", or NULL (is equivalent to "N"). Due to 3rd party apps I cannot change the database to char(5) and use the standard modelling technique of toString() and valueOf() with Strings "true" and "false" in the DB. How can I model such an attribute in a D2W compliant way? I have tried the following: rename the attribute in EOModel to "publishedYN" but leave the column name "published" and added published() and setPublished() to the business logic. This works and I can e.g. use ERD2WCustomeQueryBoolean in my query page configuration. However when I click query I get the following exception:
java.lang.IllegalStateException: sqlStringForKeyValueQualifier: attempt to generate SQL for com.webobjects.eocontrol.EOKeyValueQualifier (publish = (java.lang.Boolean)'false') failed because attribute identified by key 'publish' was not reachable from from entity 'TechdocType'
Yes, there is no such attribute and thus the crash makes sense. How can I fix this? Any ideas? Unfortunately it is not possible to extend java.lang.Boolean
Nobody? Really? Someone must have had the same or a similar issue! How did you solve this?
Oh well, I seem to have found the ultimate not-yet-solved-issue(TM)
Fun to you and have a great weekend ---markus---
|
_______________________________________________
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