Checking with the DOc team.

You are trying to build a bundle the way they were built in AEM 5.x. That is - trying to reference separeate JAR files - that does not work now.In AEM 6.4 - you build with Maven Archetype and reference the UBER JAR - as discussed here:Creating an Adobe Experience Manager 6.4 Project using Adobe Mave...

When using HTL - to get values to Java, you can either use:1 - a component dialog - Creating an Adobe Experience Manager 6.4 HTL component that uses the WCMUsePojo API2 - or use a HTTP POST or GET operation - this would be sent to a servlet however.In your form use case - you can use AJAX to sent th...

Are you following an online doc - if so please point community to it.An unsatisfied Reference typically means that there is no target service available in the service registry. Therefore your component is not satisfied.

When using Sling Models, its better to have values - like a image for a Banner-  to be set via the component's dialog - as shown in this article:Creating an Experience Manager 6.4 Responsive Banner Componentie --@Model(adaptables = Resource.class)public class BannerList {      private final Logger L...

Nice reply Navin!

YOu may have found a bug. IN your sample - you are using JSON and in mine - we are using a MAP and DataSource which is populating the Select field. As i showed in video - i am not experiencing your reported issue. I can save the dialog with no options.

See this KB - http://exploreadobe.com/dynamic-media-upgrade/dynamic-media-feature-list.html In this doc -  Dynamic Media Classic is S7.

Have you tried using the logic in the article - Adobe Experience Manager Help | Using an WCMUsePojo class to populate an Experience Manager Touch UI Select Field As I showed in the 2nd video - this issue does not appear when using this Java logic.

That doc lists all of the OOTB RTE plug-ins.