@Manikumar,
I was able to replicate your problem.
In detail, I will repeat your problem, so that the next reader understands a clearer picture.
What's Happening?
Within the Touch UI page editor, A Classic UI component, component-a, is added to the page. The component-a has a "cq:include" to incclude another component, component-b, to the page. Component-b is also only Classic UI. The author was able to configure component-b with Classic UI in the Touch UI page editor. All the properties configured on component-b was saved as expected (confirmed in CRX/DE) except for the sling:resourceType property. The sling:resourceType property was not saved. However, in the Classic UI page editor, the component-b is saving as expected.
Why is the sling:resourceType not saved?
When dealing with the Touch UI page editor, I've noticed that whenever a component is included into a page via JSP or Sightly, if the component included only has Classic UI, then the problem will persist with sling:resourceType as not being saved. The included component must have Touch UI enabled.
Take Aways:
- Touch UI Page Editor with a component that includes another component with only Classic UI enabled, the sling:resourceType does not save.
- Touch UI Page Editor with a component that includes another component with Touch UI enabled, the sling:resourceType will be saved.
- Classic UI Page Editor with a component that includes another component with only Classic UI enabled, the sling:resourceType will be saved.
I hope this helps.