Thanks David for the follow-up.
Could this be a result of the new PersistentUnitCache / generator caching
stuff?
I tried having a different generator class for each value but I still
had the same issue.
Also, Soft Permutations would cause this, so make sure those are not on.
I don't use the
Hi Pierre,
Response from Ray Cromwell on our internal mailing list:
Could this be a result of the new PersistentUnitCache / generator caching
stuff?
Typically in GWT, people have two different Generator implementations,
so there would be a MyGeneratorFirefoxImpl and a
MyGeneratorDefaultImpl.
I don't know the answer to your question, but there is a mistake in the gwt.xml
fragment you posted. You assign myProperty=value1 when user.agent equals FF and
also when user.agent is not FF. You never assign myProperty = value2.
HTH
Paul
On 27/09/11 05:37, Pierre Coirier wrote:
Hi,
I got
Thanks for pointing that out. It was a typo error, in my code I do
have myProperty = value2.
If it helps, you can find the code that I'm using to reproduce the
error: http://mvp4g.googlecode.com/svn/temp/gwt-example.zip and the
soyc report: http://mvp4g.googlecode.com/svn/temp/compile-report.zip
I added logs to my generator and it seems the generator is called when
it is supposed to (aka only once for each permutation with the right
value for myProperty):
Computing all possible rebind results for
'com.mvp4g.client.Mvp4gModule'
Rebinding com.mvp4g.client.Mvp4gModule
Hi,
I got an issue with deferred property and code splitting.
In my GWT configuration file, I have defined the following property:
define-property name=myProperty values=value1,value2 /
set-property name=myProperty value=value1
when-property-is name=user.agent value=gecko1_8 /
/set-property
