@Jens: thanks for your feedback. I looked at it. I like the component-based
annotation approach.
It sure gives me inspiration. It would be nice if this templating mechanism
can be used independently of the rest of the platform (haven't looked at it
yet), and that it's flexible to extend it (It
FYI: the IsElement interfaces corresponds to issue 7497:
http://code.google.com/p/google-web-toolkit/issues/detail?id=7497
On Fri, Jun 7, 2013 at 5:03 AM, Stephen Haberman
step...@exigencecorp.comwrote:
If nobody else has any other concerns, I recommend you to start with
an example
Hi,
I am a bit lost here.
I mean, I don't really understand why I even need these policy files and why
they aren't more flexible in usage (maybe even optional).
If I am correct, it's there for security reasons, it's used to indicate
which objects are allowed to be (de)serialized.
But what if I
He,
to fetch them using HTTP connection to appropriate client.
Indeed, that doesn't sound that bad, but I will need to maintan a mapping
between the moduleBaseUrl that I receive in the backend and the actual http
url of the module location where I can find the policy file. And these
mappings are
Hi Ladislav,
Thanks for your response.
I do almost the same thing as Acris does, I only have my files located in
the classpath (I also use GWT-SL to read my policy files)..
But Acris also doesn't solve the problem of having all these policy files
scattered around and assumes that you have them
