Sounds like a plan, no problem. [EDIT: retracting original question]On
another topic though, I wanted to note that I ran across one more
serialization difference for the LCDS typefactory: ByteArray should
import 'flash.utils.ByteArray' rather than
Looks good, awesome stuff! appreciate the LCDS integration, as I'm sure
others will as wellA tip to those who are using this:Add the Flex
library nature to your DAO project, then have Granite deploy the
Actionscript classes to a flex source folder that you defined in the
flex library build path...th...
yes, they would use the same configuration because ultimately on the
flash side the classes are the same...it only needs a mirror copy of the
entity on the client side for serialization purposes and for compiling
purposes (i.e. the client needs to know what the type 'Goal' is, but it
doesn't care ho...
I litterally just went to test this again and you posted up haha...it
adds the nature correctly now (you icon is also back), and it builds
great, but for some reason it skips any class annotated as '@Entity'...I
couldn't get it to build that by including only the path to that
package, or by having i...
strange, it's not in my installed items...but I guess that makes sense
because I didn't use an update site, I just dropped the jars into my
plugins folder. I tried the new jar, still no luck...is there a newer
version I need oft eh graniteds jar itself besides 2.3.1 GA?
Sounds like a good solution to me, but when I drop that new build in and
then add the graniteDS nature to the project it says 'the chosen
operation is not currently available'...also, oddly, the icon
dissappeared for the context window...I pulled back to the last release
build and added the nature t...
not really, unfortunately the entities are typically in a DAO which can
either be local to the project or referenced in. In our case, we
reference in the DAO and use GDS on the DAO project itself, which has no
knowledge of the service which is the only piece annotated as managed. I
just ran through ...