Check the configuration under Apache Sling Content Disposition Filter or
Adobe Granite REST Assets Content-Disposition Filter @
patterns/extensions Content-Disposition header's value inline vs
attachment does that magic Reference:
Could you share appropriate screenshots of the issue?Check the steps
for 0x8007007f errorRemove the ISAPI filter that is not valid. To do
this, follow these steps:Click Start, click Run, type inetmgr.exe, and
then click OK.In IIS Manager, expand server name, expand Web sites, and
then click the Web site that you want to modify.In Features view,
double-click ISAPI Filt...
In that case you may write a custom code to export json using
Jackson/GSON API. Obviously, you'd end up writing a lot of boilerplate
Otherwise, as recommended by Adobe, u...
Did you/your team get a chance to debug its root cause? Does it throw
any error in logs? It seems that you plan to send an automated alert so
that someone could manually restart the bundle as a workaround each time
Why do you instantiate the service in your code yourself? -
AspectServiceImpl objAspectServiceImpl = new AspectServiceImpl();Can you
confirm that your scheduler is annotated with SCR/OSGI annotations?Refer
code samples here
at master · Adobe-Consulting-Services/acs-aem…
check Security Checklist Check if the CRX development bundles are
presentThese development OSGi bundles should be uninstalled on both
author and publish productive systems before making them
accessible.Adobe CRXDE Support (com.adobe.granite.crxde-support)Adobe
Granite CRX Explorer (com.adobe.granite.crx-explorer)Adobe Granite CRXDE
Enable/Configure debug logs on "com.sunita.wpr.aem", "org.apache.http"
and "org.apache.sling" and checkDo you see this servlet/service
registered and enabled in felix console?What do you see in the browser
console logs? Use developer tools or Fiddler or any other proxy and
check the headers on request/responseCheck if there are any errors
related to CORS/CSRF/Referrer Filter?
I assume your question is related to SCR/OSGI annotations in the java
code/bundles and not best practices like repository restructuring
aspects of 6.4, CRX2OAK migration, configuring lucene indexes etc. it
would still continue to work in 6.4.3 till the time required
dependencies are met. The AEM version would still be 6.4.3 in your case
however, the application may/may not be adhere to Adobe recommended best
In your scenario, POSTMAN is replaced by AEM to access the API endpoint,
hence you may not need -- post.setHeader("Postman-Token", "xxxx"); You
may go through following links to set up OAuth. There are a lot of
articles available on AEM-OAuth integration in this forum and on
I'm unable to understand why do you want to pass postman-token in this
request.For bearer token try this -- post.setHeader("Authorization",
"Bearer " + token); or httpClient.DefaultRequestHeaders.Authorization =
new AuthenticationHeaderValue("Bearer", "Your Oauth token"); For passing
json, you have already written the code to set the body/json in
HttpEntity -- post.setEntity(requestEntity);
The screenshot shows "admin" as the user while you mention "aemserver"
userCould you share the docs url that you followed to configure it?Refer
or Integrating with Adobe Campaign 6.1 based on your AEM version.
Not sure if you have already gone through this doc -- SPA Editor
Overview This diagram explains that if you don't rely on existing/OOB
core components/Sling Models/Sling Model Exporters and build custom
components then you would need to wire each entity in a correct way
either using OOB models/exporters or otherwise with custom
If you plan to keep SCR annotations in 6.4 then update the jar versions.
e.g. try using 1.20.0 or above for maven-scr-plugin and 1.9.0 for
scr-annotations. Similar approach goes for compile time
dependencies/plugins like 'servlet-api' etc.A clean & time saving
approach would be to use maven archetype and create a new project from
scratch if that's feasible. You could also choose a hit n trial approach
- create a reference project using maven archetype and then utilize
specific jar/versions into ...
The version of esapi, servicemix and its dependencies could vary based
on your AEM version. What version of AEM do you use?There must be logs
related to bundle not starting up due to some dependencies either in
error.log or stderr.log Could you share that?When you click on the
"installed" bundle you'd see the unsatisfied dependencies along with
versions. Could you share that?
I haven't seen any papers on SPA-ecomm integration as a recommended
path. In my mind, I'm not sure of the benefits of SPA owning it rather
than AEM with GraphQL route. I'd probably do more research
later.Alternate route per Adobe's own CIF -- Integrations Integration
patternThe AEM Venia Store front is a mixed page application in which
AEM owns the glass and Magento powers the commerce backend in a headless
way. Both server-side rendering and client-side rendering are used in
the storefront. Ser...
Is maven-scr-plugin:1.7.4 generated by archetype 11 or is it carried
over from your 6.1 pom.xml?A best practice - It’s recommended to place
Uber jar at the bottom of the dependency list so that Maven will honor
any newer versions of dependencies that is explicitly declared inside
the project POM.
Most likely an issue with the plugin that you're using. Try npm route if
gcc doesn't workCheck - Add missing semicolons to avoid minification
issues · Issue #420 · github/fetch · GitHub fetch-min - npm