Has anyone encountered this in the past couple of days? All of a sudden
in some pages in author instance, we are unable to edit anything since
the OOTB scripts required for authoring are blocked due to a new
Uncaught DOM exception caused by a cross origin script request. The
funny thing is, the same error does not occur if I rename/move the page
somewhere else. Everything works fine via IP and the issue occurs only
while accessing via DNS (all authors access via DNS). I've checked the
CORS OSGi ...
Hi Veena, yes we gave that a thought but how well do you think that will
work?Not all our components have sling models associated with them and
all our pages follow a different structure, also we have some sling
models which has dynamic objects populated from external APIs. Do do you
think there is a simple strategy to get a structured json of a page via
a servlet without having to write too much if else conditions taking the
various page structures into consideratio?
Hi Jörg, you were very right about the exporter not being registered.
Thanks for that.with that said, I created a exporter for the model as
well but I believe the whole exporter feature works only when we access
the components specifically but not for the whole page itself. What we
are trying to achieve is to give some form of meaningful json for a
mobile app developer to consume for the whole page and not for specific
components.
Thanks for the response Rampai, i do not see anything related to
exposing page data as json in the github project you had posted. have
you posted the right link?
Hi Guys, we have an existing website containing more than 2000 pages and
we are looking as exposing the content as a service so that they can be
consumed by an external mobile app. 1. I have tried looking at CaaS
feature available OOTB in 6.4 but that requires us to create content
fragments but we already have 2000 pages which needs to be exposed for a
mobile app2. I've also looked at JSON Exporter which works with the
suffic ".model.json". This gives some json data but its not really
usable sin...
Thanks Scott and Zeeshank for your response. The articles linked are the
ones I'e tried and I had no luck. I configured the max parallel jobs in
both external workflow Queue and workflow Queue. It has no effect. Also,
instead of trying to increase the max jobs, I even tried to limit them
by making it 10 instead of the default 15. Even this doesn't have any
effect, the workflow starts for all 15 files even if the limit is set
for 10. I've tried configuring the limit in both Sling Jobs and even in...
Hi Guys,I've been trying to launch workflow on a folder in Assets which
contains around 20 files. When I create a workflow post the selection, I
get a error message saying that only max of 15 assets can be selected
and that I have currently selected 20. We would like to increase this
max number of workflows to more than 20.I've tried changing the Maximum
Parallel Jobs in both the Workflow Queues, Sling Jobs etc. but it just
doesn't allow more than 15. Is there any other way to do this other than...
Jörg, I tried the other way as well to access the Datasource and even
that method ends up having the Datasource as null. When the service
event is getting registered without any errors when I click on save in
the JDBC connection pool, it means that the JDBC connection is
successful right? I'm still trying to figure what possibly is going
wrong here.
Hey Jörg,The javax.management package is indeed available in the OSGi
framework. We stopped getting the error posted above once we created the
Oracle driver using Eclipse Indigo. However, we still keep getting null
value for Datasource even after configuring the properties in JDBC
Connection pool. The funny thing is, we do not even get any error in
error.logs now. This is how the logs like once I click on save with the
JDBC properties, 10.05.2017 00:39:56.383 *INFO* [CM Event Dispatcher
(Fire Co...
Hey Scott, We are trying to connect Oracle DB as well. We have tried all
the articles listed above and we still couldn't get this connection up
and running. We tried creating the Driver bundle with ojdbc14, ojdbc6
and even ojdbc6_g (with logging enabled because we once had an error
relating to diagnosability). We even tried building the driver using
Eclipse Indigo so as to enforce automatic update of Export and Import
packages (new versions do not populate the list automatically) but the
connect...
