Re: Deferred Binding - Rebind Result must be a class

Hi Thomas I was able to find the user error (me in this case). It seems like regardless of the conditions found in the X.gwt.xml I was not accounting for a default case. So I added a third replace-with as a default case and it's all good now. So your previous answer def. pointed me in the right direction.

Thanks again for the response. It's really appreciated.

Alfredo

On Tue, Nov 1, 2011 at 10:23 AM, Alfredo Quiroga-Villamil <lawwton@gmail.com> wrote:

Hi Thomas, appreciate the response.

I am defining them as follows:

MobileFactor.gwt.xml

<define-property name="mobilefactor" values="desktop,tablet,mobile" />

<collapse-property name="mobilefactor" values="*" />

I have additional lines that are from the mobilewebapp sample you mentioned determining the User Agent and setting it up according to the values shown above (the js part)

In my Application X.gwt.xml I then do an inherit of MobileFactory.gwt.xml and have the lines I sent before for the ClientFactory Implementations with their corresponding conditions. The strange thing that is really throwing me off is that it runs in Dev mode. There it all seems to be ok. However, when I try to compile even when I do it directly from within the IDE that is being used to run it, the exception is thrown. I changed the interface to a regular class and it all works also (compile), but that would defeat the purpose of the ClientFactory implementation at that point. Abstract classes also bark.

I am on GWT 2.1. I've searched and came across some posts but was unable to determine if this is simply user error on my part or it's a bug in the version of GWT I currently have.

Any ideas are really appreciated.

Thanks again,

Alfredo

On Tue, Nov 1, 2011 at 6:03 AM, Thomas Broyer <t.broyer@gmail.com> wrote:

What values can "mobilefactor" take?

For instance, the FormFactory module from the mobilewebapp sample defines 3 values: desktop, table, and mobile. You have to define a rebind rule for each one of these values, or set the property to a subset of the values (e.g. <set-property name="formfactor" value="mobile,desktop" />) otherwise the compiler will use the "when-type-is" value (i.e. the interface here) when it cannot find a rule, which would cause the error you're seeing.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/mPLfSxXM-QoJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM:  lawwton

--
Alfredo Quiroga-Villamil

AOL/Yahoo/Gmail/MSN IM:  lawwton

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.