The product is no longer called CQ5 (that renmaing happend at least 5
years ago), so you probably do have a very old version of it running.
Regarding your question: Storing SQL data in the AEM repository is no
good idea, as it is not designed for it. If your goal is to show the
charts inside an AEM page, I would agree to the approach suggested by
@rajas66269496 and use an iframe to embed the output created by your PHP
script.
Hi,can you please describe what you mean with "session logout" in more
detail? The term "session" can describe a lowlevel implementation API,
which does have a logout method. On the other hand side it can also mean
the session of a user, which has authenticated against an AEM authoring
instance and is working, until he logs out (and cannot visit the UI of
that authoring instance until he logs in again).Dependent on that the
answer is quite different 🙂
As Varun already outlied, there are multiple factors to consider, which
will influence your overall architecture.If your other CMS is also
accessible from the audience, it's possible that the visitors fetches
data directly from that CMS; in that case some custom JS is sufficient
to request the correct HTML snippets at the right locations and inject
it into the right spot on the page.If that is not possible, you can try
to merge the final page at the dispatcher level using SSI. AEM then
renders S...
Hi Tim; in the end it doesn't matter if this is a bug or feature, it's
not us to decided. Well, more likely it's you, agree 🙂 I would
recommend you to raise a support ticket and report this.
If you really need to update 12k nodes in a single transaction, you
should really increase the heap, because this transaction must fit into
the heap. And 1GB of heapsize might be sufficient for DEV systems, but
for PROD systems you should increase the heap.Do you really need to
update these 12k in a single transaction? Isn't it possible to split it
up?
Unfortunately it isn't clear from the screenshot what is causing the
problem. The stacktrace should have some "caused by" statements as well.
Also it would help if you can share the complete output of the maven
build of the frontend module.
Well, there could be many issues, why this class is not resolved
properly. If the maven build works, it's a problem of your IDE. If the
maven build fails with compilation issues, it would be great, if you
could share the project (or a minimal sample to demonstrate the problem)
on github. The Question&Answer mode which a forum imposes is not the
best way to resolve this problem.
Hi Tim, In other words, the problem is just looking for the name of the
tags (because it's part of the reference to the tag), and not the
jcr:title of the tags, which are referenced from the assts. Is that
correct? From a technical point of view this is expected, because JCR
imposes some limitations on node names. That means if jcr:title does not
match the name, you won't find the asset. Another limitation is also,
that if you change the title of a tag but not its name, and you are
using this ne...
Anyway, next to the working solution this seems to be a short-coming of
the mocking libraries. Can you create a minimal testcase (at best
without any AEM dependency) and post it to the sling-developer list?
Hi,that looks really strange; when I look at the code that mentioned
line it makes me think that the request doesn't have an assertion at all
(unfortunately there a number of chances where a NPE can occur).Please
raise a request with support and report your problem (at best including
the relevant details about the SAML assertion attached to the request).
Jörg
Unfortunately the link does not mention if you have to make adjustments
to your pom.xml to include powermock. You should augment your
dependencies with a block like this:
org.powermockpowermock-core2.0.7test
I have a working example at
https://github.com/joerghoh/cqdump/tree/master/ca-config-example which
also includes the mentioned plugin.The maven-bundle-plugin is configured
here:
https://github.com/joerghoh/cqdump/blob/master/ca-config-example/core/pom.xml
Jörg // Update: I do use the maven-bundle-plugin and not the
bnd-maven-plugin.
Hi, when you refer to Context-Aware-Configuration, do you mean this:
https://sling.apache.org/documentation/bundles/context-aware-configuration/context-aware-configuration.html
If yes: jquery is executed within the browser, while CAC is executed on
the server-side. Mixing both approaches directly is not possible. The
only chance you have is to execute the CAC lookups on the server, and
include the result into JSON or the generated HTML, and use this data
then inside javascript/jquery.
That's not possible with AEM ootb. If you have that requirement, your
content structure is probably not in-line with the Adobe best practices.
Because there access control is a strong factor when you design it.Can
you share some of your requirements which lead you the approach of
"create ACL per template"? Jörg
The problem with some assets opening directly in the browser is the
fact, that you are displaying untrusted content. Imagine that you upload
a random HTML file into AEM, then display it, and then in the HTML there
is a POST request to a different domain, which just sends all your
cookies there. That's the reason why for some mime-types the display in
the browser is not allowed. But of course, you can reconfigure that and
also write custom code, which displays such content directly in the
browser...
Hi, I am not totally sure if that's a normal behavior. Can you check in
/system/console/jmx if the number of "SessionStatistics" entries is
growing over time. In that case you have a session leak, which often
goes together with memory issues like you described.
OSGI does not support multi-dimensional arrays of values, but just
simple lists. When you need to provide more complex data as OSGI
parameter, you should consider to package the configuration in a
different format (e.g. as JSON file in the repository, or a node
structure), and use OSGI to configure the path to it.
It's doable, but I would avoid it. Why? Because you always have to take
care that this namespace is registered. Sharing a content package with
Adobe support might not be that straight forward anymore. Full
disclosure: I never created custom namespaces in my projects. Worked
very well 🙂 And I never missed them.
Besides the "usual" recommendation to shut it down in production, I
don't see any immediate problem with it. The question remains why you
have to change it at all 🙂
Actually the mod_expires always added headers to any response, even if
this response was supposed to be uncacheable.And technically (according
to the RFCs) any request containing a query string must not be cached.
HTH,Jörg
Hi Christoph,If I understand you correctly, you would just start
registering customer exporters as selectors selectors to the cq/Page
resourcetype.Technically I don't see a problem with that, but just be
aware, that I can execute this exporter on pages where it shouldn't
work. That means you need to write some code to ensure that this
exporter is just executed on the right "type" of page, and not on any
page. If you register that SME directly to the correct resource type,
Sling does that for you...
As already outlined by the others, the "Max-Age" headers influences
caches more downstream from AEM, that means any well-configured
intermediary, including CDNs, and also your browser should respect them.
Regarding dispatcher: In most cases it must not affect dispatcher at
all. If the Max-Age has passed and clients reach back to your
dispatcher, the dispatcher might deliver the same file again (with a new
Max-Age header) if that file has not changed in the cache. Which is
default if you invalida...
The other 2 posts are already very valuable regarding the doing, but I
want to raise some other points as well.When cloning instances to a
different environment, you have to care of the environment specific
settings, which have to be different from environment to environment.For
example configured hostnames (for whatever reason) are likely to be
different from environment to environment. Then there's the question if
you can clone user information as well (assuming that on lower
environments more...
