[discuss] asynchronous servlets with a rewriter impl

Not necessarily the rewriter as it's currently written. I was looking into how I can modify content while it's being generated and I had forgotten about the fact that we now support asynchronous servlets and filters. I haven't dived to far into this yet but the basic idea would be # determine

Re: [VOTE] Release Apache Sling Scripting HTL Runtime 1.0.0-1.4.0, Apache Sling Scripting HTL Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Java Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Eng

+1 regards, Karl On Wednesday, October 31, 2018, Andrei Dulvac wrote: > +1 and +1 for the prize > > On Wed, Oct 31, 2018, 18:29 Radu Cotescu wrote: > > > +1 > > > > (And I should also get a prize for the longest subject line of a release > > mail...) > > > > > On 31 Oct 2018, at 18:28, Radu

Re: [VOTE] Release Apache Sling Scripting HTL Runtime 1.0.0-1.4.0, Apache Sling Scripting HTL Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Java Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Eng

+1 and +1 for the prize On Wed, Oct 31, 2018, 18:29 Radu Cotescu wrote: > +1 > > (And I should also get a prize for the longest subject line of a release > mail...) > > > On 31 Oct 2018, at 18:28, Radu Cotescu wrote: > > > > Please vote to approve this release: > > > > [ ] +1 Approve the

[GitHub] raducotescu opened a new pull request #4: SLING-8012 - Extract an HTL runtime bundle from the existing HTL modules

raducotescu opened a new pull request #4: SLING-8012 - Extract an HTL runtime bundle from the existing HTL modules URL: https://github.com/apache/sling-org-apache-sling-starter/pull/4 * updated HTL modules (to be merged after the release vote is finalised)

Re: [VOTE] Release Apache Sling Scripting HTL Runtime 1.0.0-1.4.0, Apache Sling Scripting HTL Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Java Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Eng

+1 (And I should also get a prize for the longest subject line of a release mail...) > On 31 Oct 2018, at 18:28, Radu Cotescu wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote

[VOTE] Release Apache Sling Scripting HTL Runtime 1.0.0-1.4.0, Apache Sling Scripting HTL Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Java Compiler 1.1.0-1.4.0, Apache Sling Scripting HTL Engine

Hi, We solved 2 issues in these releases: https://issues.apache.org/jira/projects/SLING/versions/12344330 https://issues.apache.org/jira/projects/SLING/versions/12344325

Re: Sling 12 themes[HTL Rant]

Hi Jason, Thank you very much for sharing your thoughts! On Wed, Oct 31, 2018 at 4:32 PM Jason E Bailey wrote: > ...Then BAMM all of a sudden it's the only official way of creating components > in AEM. There's people posting on Stackoverflow how it's "best practices." > Throw > a stone at an

Re: Sling 12 themes[HTL Rant]

Hi Jason, Thanks for taking the time to write such a detailed reply. > On 31 Oct 2018, at 16:32, Jason E Bailey wrote: > > First there were the initial use cases that didn't make much sense to me. > > 1. There wasn't anything else out there that did this. -> (*cough* *cough* > thymeleaf) >

Re: Sling 12 themes[HTL Rant]

First there were the initial use cases that didn't make much sense to me. 1. There wasn't anything else out there that did this. -> (*cough* *cough* thymeleaf) 2. That it allowed you to separate front end and back end developers so that back end developers wouldn't be thrown by the

[jira] [Commented] (SLING-8064) Support marking a feature as final

[ https://issues.apache.org/jira/browse/SLING-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670162#comment-16670162 ] Carsten Ziegeler commented on SLING-8064: - Added a "markAsFinal" parameter to the aggregate mojo

[jira] [Updated] (SLING-8064) Support marking a feature as final

[ https://issues.apache.org/jira/browse/SLING-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8064: Fix Version/s: slingfeature-maven-plugin 1.0.0 > Support marking a feature as final >

Re: Sling 12 themes

Hi Jason, There’s nothing wrong with that. Any Script Engine that we have in Sling is just a tool in the chest. :) Can I ask, though, why do you say it was forced on you? Thanks, Radu > On 30 Oct 2018, at 21:07, Jason E Bailey wrote: > > Since this is a public record, I'm going to clarify

[jira] [Resolved] (SLING-8064) Support marking a feature as final

[ https://issues.apache.org/jira/browse/SLING-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8064. - Resolution: Fixed Added support for the final flag in json reader and writer in rev

[jira] [Commented] (SLING-8064) Support marking a feature as final

[ https://issues.apache.org/jira/browse/SLING-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670098#comment-16670098 ] Carsten Ziegeler commented on SLING-8064: - Added a final flag to a feature in rev 2d1ec06 >

Re: Sling 12 themes

I think this is a legitimate ask. This goes back to a "what is sling" fundamental. If Sling is only there to produce HTML and json is a convenience then a rewriter for JSON doesn't make sense. If, however, JSON is a truly supported output model, then we need to consider how we support such

[jira] [Updated] (SLING-8064) Support marking a feature as final

[ https://issues.apache.org/jira/browse/SLING-8064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8064: Fix Version/s: Feature Model IO 0.1.4 > Support marking a feature as final >

[jira] [Created] (SLING-8064) Support marking a feature as final

Carsten Ziegeler created SLING-8064: --- Summary: Support marking a feature as final Key: SLING-8064 URL: https://issues.apache.org/jira/browse/SLING-8064 Project: Sling Issue Type:

[jira] [Created] (SLING-8063) CMS - UI restructure action resources

Jason E Bailey created SLING-8063: - Summary: CMS - UI restructure action resources Key: SLING-8063 URL: https://issues.apache.org/jira/browse/SLING-8063 Project: Sling Issue Type:

[jira] [Created] (SLING-8062) CMS - UI move modal structure to resource

Jason E Bailey created SLING-8062: - Summary: CMS - UI move modal structure to resource Key: SLING-8062 URL: https://issues.apache.org/jira/browse/SLING-8062 Project: Sling Issue Type:

[jira] [Resolved] (SLING-8028) Split FeatureExtensionHandler into MergeHandler and PostProcessor

[ https://issues.apache.org/jira/browse/SLING-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-8028. - Resolution: Fixed > Split FeatureExtensionHandler into MergeHandler and PostProcessor >

[jira] [Commented] (SLING-8028) Split FeatureExtensionHandler into MergeHandler and PostProcessor

[ https://issues.apache.org/jira/browse/SLING-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669978#comment-16669978 ] David Bosschaert commented on SLING-8028: - And the slingfeature-maven-plugin also needs to be

[jira] [Updated] (SLING-8028) Split FeatureExtensionHandler into MergeHandler and PostProcessor

[ https://issues.apache.org/jira/browse/SLING-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8028: Fix Version/s: slingfeature-maven-plugin 1.0.0 > Split FeatureExtensionHandler into

[jira] [Updated] (SLING-8028) Split FeatureExtensionHandler into MergeHandler and PostProcessor

[ https://issues.apache.org/jira/browse/SLING-8028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated SLING-8028: Fix Version/s: (was: slingfeature-maven-plugin 1.0.0) > Split FeatureExtensionHandler

[jira] [Resolved] (SLING-7752) Deserializing and serializing a feature model file suffles the configurations

[ https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved SLING-7752. - Resolution: Fixed > Deserializing and serializing a feature model file suffles the

[jira] [Commented] (SLING-8058) Make configuration of slingfeature-maven-plugin consistent

[ https://issues.apache.org/jira/browse/SLING-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669812#comment-16669812 ] Carsten Ziegeler commented on SLING-8058: - yes, and we might have other configurations for the

[jira] [Commented] (SLING-8058) Make configuration of slingfeature-maven-plugin consistent

[ https://issues.apache.org/jira/browse/SLING-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669809#comment-16669809 ] David Bosschaert commented on SLING-8058: - +1 Just to note that the {{aggregate-features}} goal

[jira] [Resolved] (SLING-8056) Add support for automatically updating versions in a feature

[ https://issues.apache.org/jira/browse/SLING-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-8056. - Resolution: Fixed No need to use the versions plugin anymore, using versions API rev

[jira] [Commented] (SLING-8061) sling-mocks: Make compatible when Johnzon is managed to version 1.1

[ https://issues.apache.org/jira/browse/SLING-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669785#comment-16669785 ] Konrad Windszus commented on SLING-8061: This is not that easy to solve, because referencing

[jira] [Commented] (SLING-8058) Make configuration of slingfeature-maven-plugin consistent

[ https://issues.apache.org/jira/browse/SLING-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669773#comment-16669773 ] Karl Pauls commented on SLING-8058: --- +1 > Make configuration of slingfeature-maven-plugin consistent >

[jira] [Updated] (SLING-8061) sling-mocks: Make compatible when Johnzon is managed to version 1.1

[ https://issues.apache.org/jira/browse/SLING-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8061: --- Fix Version/s: Testing Sling Mock 2.3.6 > sling-mocks: Make compatible when Johnzon is

[jira] [Updated] (SLING-8061) sling-mocks: Make compatible when Johnzon is managed to version 1.1

[ https://issues.apache.org/jira/browse/SLING-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8061: --- Summary: sling-mocks: Make compatible when Johnzon is managed to version 1.1 (was: Make

[jira] [Updated] (SLING-8061) sling-mocks: Make compatible when Johnzon is managed to version 1.1

[ https://issues.apache.org/jira/browse/SLING-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-8061: --- Description: Whenever sling-mock is used where {{johnzon-core}} is managed from 1.0.0 to

[jira] [Created] (SLING-8061) Make compatible when Johnzon is managed to version 1.1

Konrad Windszus created SLING-8061: -- Summary: Make compatible when Johnzon is managed to version 1.1 Key: SLING-8061 URL: https://issues.apache.org/jira/browse/SLING-8061 Project: Sling

[jira] [Commented] (SLING-7752) Deserializing and serializing a feature model file suffles the configurations

[ https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669703#comment-16669703 ] Carsten Ziegeler commented on SLING-7752: - [~bosschaert] I think this is now fully working, or is

[jira] [Commented] (SLING-8056) Add support for automatically updating versions in a feature

[ https://issues.apache.org/jira/browse/SLING-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16669702#comment-16669702 ] Carsten Ziegeler commented on SLING-8056: - Added support for -Dincludes=, -Dexcludes= and

[jira] [Updated] (SLING-8056) Add support for automatically updating versions in a feature

[ https://issues.apache.org/jira/browse/SLING-8056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8056: Component/s: Feature Model > Add support for automatically updating versions in a feature

[jira] [Updated] (SLING-8058) Make configuration of slingfeature-maven-plugin consistent

[ https://issues.apache.org/jira/browse/SLING-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8058: Component/s: Feature Model > Make configuration of slingfeature-maven-plugin consistent >

[jira] [Updated] (SLING-8047) Rendered/exported JSON requested via SlingRequestProcessor is not written to output stream

[ https://issues.apache.org/jira/browse/SLING-8047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8047: Component/s: (was: Feature Model) > Rendered/exported JSON requested via