Granite Data Services, the Flex / Java integration platform, has been
released in version 3.1.0.GA.It brings a lot of bug fixes upon GraniteDS
3.0 and some major improvements and new features:Huge performance
improvements on AMF serialization: GraniteDS is now 2 to 5 times faster
than BlazeDS.Websocket JSR 356 specification support on both client and
server. GraniteDS now supports websockets on Jetty 8/9 (server and
client), Tomcat 7/8, TomEE, GlassFish 3/4, WildFly 8 and Tyrus
(client).Support ...
// Granite Data Services is an Event-Driven, Cross-Framework,
Application Client Container //Read the full announcement on our website
here.Feedback is welcomed!Happy New Year,--Franck WolffGraniteDS
Following this discussion with Robert Petz about LCDS support in the
Gas3 code generation plugin, we are happy to announce the new version
2.3.2.GA of the GraniteDS platform. Download is available through our
community website (manual download and update-site).We hope this plugin
will be helpful to LCDS ES users and your feedback would greatly
appreciated.If you want to know more about the open-source GraniteDS
platform, visit our commercial and community sites.Many thanks to Robert
for contribu...
Here it is: GDS-224. Note that the two Java file types aren't sharing
the same configuration (you can still configure custom templates for
each one). So, if you want to use a "standalone" template, you'll have
to modify the configuration twice.
Ok, my fault, I referenced a new Eclipse 3.5+ method which didn't
compile with our Bamboo build process (based on Eclipse 3.4). Bamboo
wasn't reporting any failure and I was testing the plugin with a "home
made" build...Anyway, this is fixed now (I just made a test with the
last Bamboo build #223😞 remove any prior version of the plugin, start
and close Eclipse (so it can noticed a change), drop the new version and
start again Eclipse.Thanks.
Took me two hours to understand that you need to uninstall the builder
from the Eclipse's "Help" menu: removing manually the old version from
the plugins directory isn't enough, because the plugin was originally
installed through an update site and it still exists has a kind of ghost
extension... Hate this kind of problem .So: open Eclipse, select "Help"
-> "Install New Software...". Click on the "What is already installed?"
(bottom right of the panel), select the GraniteDS Builder in the list
a...
I ended up with the following solution (you can download a new build of
the plugin here😞In the "Java Sources" tab panel, you can now "annotate"
an included path with arbitrary options which will passed to the
template as a Map. For example, you can configure
included paths like this: path/to/managed/beans/*.java[managed=true] and
path/to/bindable/beans/*.java (default is to generate Bindable beans).In
the "Templates" tab panel, you will find a new button "Use LCDS". If you
click on it, the temp...
Quick question: how do you distinguish managed beans from bindable
beans? Is there any specific LCDS runtime annotation (eg: @Managed) on
the Java side that would indicate that we need a managed bean on the
Flex side?
I'm going to try to integrate your templates (together with a proper
As3TypeFactory) and I'll ask you to test the next build (I don't have
LCDS).No offense with your "misleading but not wrong" (though it is
quite a sophisticated distinction )F.
Robert,Thanks for the updated templates. What about contributing these
templates to GraniteDS? It wouldn't be complicated to add an option to
the GraniteDS builder (and the Ant task) so it would use your LCDS
templates instead of genuine GraniteDS' ones.If you are interested, post
a JIRA issue with your files here.And we will fix the documentation
about the misleading "file:" prefix and forward slashes, thanks for the
hint.Franck.
