| 0.8 M2 RUI Properties Library generated code error [message #814828] |
Tue, 06 March 2012 18:25  |
Dan Darnell Messages: 145 Registered: November 2011 Location: Arkansas |
Senior Member |
|
|
0.8 M2 release...
With the following:
library Properties type RUIPropertiesLibrary {}
upsAccessKey string;
upsUserID string;
upsPassword string;
end
The generated Java code has an error on the import:
import eglx.ui.rui.NLSLibrary;
The error is "The import eglx.ui.rui cannot be resolved".
Need a bug submission on this or did I screw something up?
--Dan
p.s. Do you want to know about things like this on milestone releases?
[Updated on: Tue, 06 March 2012 18:25] Report message to a moderator
|
|
|
|
|
| Re: 0.8 M2 RUI Properties Library generated code error [message #815435 is a reply to message #815316] |
Wed, 07 March 2012 11:55  |
Dan Darnell Messages: 145 Registered: November 2011 Location: Arkansas |
Senior Member |
|
|
Oh, right. Duh. I put the RUI properties library into the "common" package. I should have put it in the "client".
You know though, while we are on the topic, I recall that even in RBD I've been jumping through hoops to be able to have the same properties available in Java that I have in JavaScript via the RUIPropertiesLibrary. In the JSF world I used getMessage() to access externalized properties and while this is still available on the Java side of a RUI app it takes extra configuration (and a copy of the properties file in a different location) to make it work.
I am wondering if anyone else thinks it would be helpful to rethink properties in terms of a "PropertiesLibrary" type that can be generated to both JS and Java?
--Dan
|
|
|
Powered by
FUDForum. Page generated in 0.01620 seconds