We still see the issue with every new instance of AEM 6.1 we start.  I have a package that i took from another instance that contains the tree activation page.  If you shoot me a private message, i can forward the package over to you.

That's because OOTB the redirect functionality checks to see if the location is internal or external (see /libs/foundation/components/page/page.jsp).  If it determines it's internal (i.e. doesn't contain :/) then it appends .htmlYou could overlay the page.jsp in your page component and check to see ...

I believe there is a caching issue in the Touch UI that prevents new components from showing up.  I see this issue very frequently, and it's rather annoying.  Easiest way to solve is to shut down your instance and restart it - at least until Adobe releases a fix.

You can absolutely do that by either pointing to the asset in the DAM, or by specifying an absolute URL.  The trick from an SEO perspective is that you'll want to open it in a new window so you keep people on your site.  We typically use a link helper class where the link path/url is passed into a s...

I would re-think how you're structuring your component before you go build a custom xtype.  There is always a way to achieve the functionality you need without going down the rabbit hole that is custom xtypes (not to mention the classic UI will go away and be unsupported).What's your use case?

In your code package, you should have your configurations broken out into/apps/project/config/apps/project/config.author/apps/project/config.publishat a minimum, when needed.  Obviously if there is a cross-instance configuration, then place it inside of "config" as it will take affect on both author...

This isn't really a restriction of AEM more than it is a restriction of Windows/Java.  There is an ODBC/JDBC bridge, but it will only work on a Windows environment and requires you to have a whole other setup for ODBC.  All the bridge does is allow JDBC to communicate with ODBC.  Certainly not somet...

@Component(metatype = true, label = "Configuration Factory", description = "Configuration Factory", configurationFactory = true) @Service public class TestConfigurationFactory { @Property(label = "Property 1", propertyPrivate = false, description = "Property 1") private static final String PROPERTY_...

Yes you can.  Your service needs to be a component factory.  See below.@Component(metatype = true, label = "Configuration Factory", description = "Configuration Factory", configurationFactory = true) @Service

Really the solution to this is just manage the properties on production manually.  You're not going to just be adding new instances of AEM to production, so manually set it up once and you're done.