If you're using 5.3, it appears that "className" is not actually a
prototyped field ... valueClassName is, and className is set when you
explicitly setValueClassName. What I don't know is whether className
is set when the prototype is inherited.
On Jan 6, 2009, at 6:24 AM, Riccardo De Menna wrote:
> Replying to myself...
>
> If I change in EntityModeler the prototype setting of a particular
> attribute (ie a String for instance) to use no prototype and I fill
> in all the custom fields exactly as the prototype would (mostly that
> means className = java.lang.String) it works. The
> EOAttribute.className return java.lang.String as expected and thus
> all the rules fire as they should.
>
> This thing is locking all D2W apps to me... could it be I'm the only
> one experiencing it? Using nightly 3.4.5594...
>
> rdm
>
> On 05/gen/09, at 14:13, Riccardo De Menna wrote:
>
>> Hi,
>>
>> I'm having a weird issue and someone might be able to point me out
>> in the right direction.
>> After coming back from holidays my D2W projects all seem to
>> malfunction: Any text field for 'edit' tasks does not show at all.
>>
>> This is because for some reason both rules:
>>
>> (task = 'edit' and attribute.className = 'java.lang.String') =>
>> componentName = D2WEditString
>> (task = 'edit' and smartAttribute.className = 'java.lang.String')
>> => componentName = ERD2WEditString
>>
>> Are not getting fired cause className returns and empty string. The
>> result is that D2WDisplayString get's used instead.
>> Any other EOAttribute method works fine (smartAttribute.entity for
>> instance)... just className returns null.
>>
>> How can the EOAttribute.className be empty? Can it have anything to
>> do with the Entity Modeler in WOLips?
>>
>> Riccardo De Menna
>
This archive was generated by hypermail 2.0.0 : Fri Jan 23 2009 - 15:17:05 EST