|
Re: IWAV0177E Expression 'xxx' is too complicated [message #126574 is a reply to message #126561] |
Tue, 20 June 2006 21:33 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
It doesn't stop things from working, it just won't apply it to the
object during VE editing. It will still work fine.
If you are at VE 1.1.0.1 or lower we don't handle expressions that refer
to members or methods of the class that are not beans that we know about
(i.e. the visuals). In VE 1.2 we do a better job of this and can
handle more types of expressions.
The standard expressions in VE 1.1.0.1 that are not too complicated are
calls to static methods, primitives, strings, constructors.
Hung wrote:
> Hello,
>
> My composite has a setter that accepts an object of Class A. VE doesn't
> seem to invoke this setter, I got this message "IWAV0177E Expression
> 'xxx' is too complicated". Other setters that have
> arguments of primitive classes are OK.
>
> Does anyone know how to get around this problem? Thanks.
--
Thanks,
Rich Kulp
|
|
|
Re: IWAV0177E Expression 'xxx' is too complicated [message #126643 is a reply to message #126574] |
Wed, 21 June 2006 03:01 |
hung Messages: 117 Registered: July 2009 |
Senior Member |
|
|
Hello Rich,
Thanks for the response. I am using VE 1.2 RC1. Our composite depends on
that value for rendering during VE editing and runtime, if the value is not applied during
VE editing, our composite doesn't display anything. Is there guidelines on how to convert
this expression to something that can be handled by VE during editing? Thanks.
Rich Kulp wrote:
> It doesn't stop things from working, it just won't apply it to the
> object during VE editing. It will still work fine.
>
> If you are at VE 1.1.0.1 or lower we don't handle expressions that refer
> to members or methods of the class that are not beans that we know about
> (i.e. the visuals). In VE 1.2 we do a better job of this and can handle
> more types of expressions.
>
> The standard expressions in VE 1.1.0.1 that are not too complicated are
> calls to static methods, primitives, strings, constructors.
>
> Hung wrote:
>
>> Hello,
>>
>> My composite has a setter that accepts an object of Class A. VE
>> doesn't seem to invoke this setter, I got this message "IWAV0177E
>> Expression 'xxx' is too complicated". Other setters that have
>> arguments of primitive classes are OK.
>>
>> Does anyone know how to get around this problem? Thanks.
>
>
|
|
|
Re: IWAV0177E Expression 'xxx' is too complicated [message #126669 is a reply to message #126643] |
Wed, 21 June 2006 14:13 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
There are no general rules. It tries as best it can. Can you put a
snippet here to show what the expression looks like?
Hung wrote:
> Hello Rich,
> Thanks for the response. I am using VE 1.2 RC1. Our composite depends on
> that value for rendering during VE editing and runtime, if the value is
> not applied during
> VE editing, our composite doesn't display anything. Is there guidelines
> on how to convert
> this expression to something that can be handled by VE during editing?
--
Thanks,
Rich Kulp
|
|
|
Re: IWAV0177E Expression 'xxx' is too complicated [message #613376 is a reply to message #126561] |
Tue, 20 June 2006 21:33 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
It doesn't stop things from working, it just won't apply it to the
object during VE editing. It will still work fine.
If you are at VE 1.1.0.1 or lower we don't handle expressions that refer
to members or methods of the class that are not beans that we know about
(i.e. the visuals). In VE 1.2 we do a better job of this and can
handle more types of expressions.
The standard expressions in VE 1.1.0.1 that are not too complicated are
calls to static methods, primitives, strings, constructors.
Hung wrote:
> Hello,
>
> My composite has a setter that accepts an object of Class A. VE doesn't
> seem to invoke this setter, I got this message "IWAV0177E Expression
> 'xxx' is too complicated". Other setters that have
> arguments of primitive classes are OK.
>
> Does anyone know how to get around this problem? Thanks.
--
Thanks,
Rich Kulp
|
|
|
Re: IWAV0177E Expression 'xxx' is too complicated [message #613381 is a reply to message #126574] |
Wed, 21 June 2006 03:01 |
hung Messages: 117 Registered: July 2009 |
Senior Member |
|
|
Hello Rich,
Thanks for the response. I am using VE 1.2 RC1. Our composite depends on
that value for rendering during VE editing and runtime, if the value is not applied during
VE editing, our composite doesn't display anything. Is there guidelines on how to convert
this expression to something that can be handled by VE during editing? Thanks.
Rich Kulp wrote:
> It doesn't stop things from working, it just won't apply it to the
> object during VE editing. It will still work fine.
>
> If you are at VE 1.1.0.1 or lower we don't handle expressions that refer
> to members or methods of the class that are not beans that we know about
> (i.e. the visuals). In VE 1.2 we do a better job of this and can handle
> more types of expressions.
>
> The standard expressions in VE 1.1.0.1 that are not too complicated are
> calls to static methods, primitives, strings, constructors.
>
> Hung wrote:
>
>> Hello,
>>
>> My composite has a setter that accepts an object of Class A. VE
>> doesn't seem to invoke this setter, I got this message "IWAV0177E
>> Expression 'xxx' is too complicated". Other setters that have
>> arguments of primitive classes are OK.
>>
>> Does anyone know how to get around this problem? Thanks.
>
>
|
|
|
Re: IWAV0177E Expression 'xxx' is too complicated [message #613383 is a reply to message #126643] |
Wed, 21 June 2006 14:13 |
Eclipse User |
|
|
|
Originally posted by: richkulp.us.NO_SPAM.ibm.com
There are no general rules. It tries as best it can. Can you put a
snippet here to show what the expression looks like?
Hung wrote:
> Hello Rich,
> Thanks for the response. I am using VE 1.2 RC1. Our composite depends on
> that value for rendering during VE editing and runtime, if the value is
> not applied during
> VE editing, our composite doesn't display anything. Is there guidelines
> on how to convert
> this expression to something that can be handled by VE during editing?
--
Thanks,
Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.03624 seconds