2) a "custom DataSource" is actually a SmartGWT concept. See this sample. You can most likely write a single DataSource class that can be reused for all of your EJB entities, so that all you need to do to connect to a new EJB entity is create a .ds.xml file for it (or generate it, if you have Enterprise). A forthcoming example will show doing this for Hibernate.
1) Yes that's correct if you choose to go with EJB and you use DMI as your integration approach. A custom DataSource will result in less code overall as soon as you connect to 2 or more EJBs.
Note that in both of the above approaches, creating the DataSource .ds.xml file itself is not a redundant step because this DataSource is used to provide fields for UI components, as well as server-side validation and many other functions.
3) Messaging hasn't been ported to SmartGWT Enterprise yet, but it will appear there soon. Yes it's comparable to Lightstreamer, fast and stable.
On security: normal J2EE security approaches work, and SmartGWT EE 1.2 / SmartClient 7.1 will include built-in support for declarative role-based security that connects to JEE security or JAAS.
On docs: See the sticky thread "SmartGWT documentation" - SmartClient and SmartGWT share the same server framework, it all applies.
Thanks for the answer. I looked at the example with the custome datasource but still can't make it clear. I hope the forthcoming example will explain the things.
Comment