[jira] [Commented] (SLING-4307) Avoid caching JCR property values

[ https://issues.apache.org/jira/browse/SLING-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276820#comment-14276820 ] Felix Meschberger commented on SLING-4307: -- How about keeping a week refer

[jira] [Comment Edited] (SLING-4305) Refactor the Record interface

[ https://issues.apache.org/jira/browse/SLING-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276746#comment-14276746 ] Felix Meschberger edited comment on SLING-4305 at 1/14/15 10:2

[jira] [Commented] (SLING-4305) Refactor the Record interface

[ https://issues.apache.org/jira/browse/SLING-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276746#comment-14276746 ] Felix Meschberger commented on SLING-4305: -- That would be {{getPropertyN

[jira] [Commented] (SLING-4307) Avoid caching JCR property values

[ https://issues.apache.org/jira/browse/SLING-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276736#comment-14276736 ] Felix Meschberger commented on SLING-4307: -- I think we can do away with

[jira] [Comment Edited] (SLING-4307) Avoid caching JCR property values

[ https://issues.apache.org/jira/browse/SLING-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276736#comment-14276736 ] Felix Meschberger edited comment on SLING-4307 at 1/14/15 10:1

Re: [Authentication] option to close session passed as "user.jcr.session"

Hi > Am 14.01.2015 um 04:01 schrieb Alexander Klimetschek : > > On 12.01.2015, at 14:53, Alexander Klimetschek wrote: >> Ack, sounds good. I created https://issues.apache.org/jira/browse/SLING-4301 > > I attached a patch. > > But while testing it, I had a problem, see > https://issues.apache.

[jira] [Commented] (SLING-4301) Support user.jcr.session.logout option for the jcr resource provider

[ https://issues.apache.org/jira/browse/SLING-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276628#comment-14276628 ] Felix Meschberger commented on SLING-4301: -- This is really weird and unexpe

[jira] [Comment Edited] (SLING-4301) Support user.jcr.session.logout option for the jcr resource provider

[ https://issues.apache.org/jira/browse/SLING-4301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276628#comment-14276628 ] Felix Meschberger edited comment on SLING-4301 at 1/14/15 8:0

[jira] [Commented] (SLING-4298) make BufferedServletOutputStream and CaptureResponseWrapper available to other scripting implementations

[ https://issues.apache.org/jira/browse/SLING-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274089#comment-14274089 ] Felix Meschberger commented on SLING-4298: -- I have the impression, that

Re: [Authentication] option to close session passed as "user.jcr.session"

Hi IIRC we have been discussing that before … Not sure what the resolution was and I actually was under impression we agreed to do it. Maybe it just fell off the trenches. Yes, I think a new constant > JcrResourceContstants.AUTHENTICATION_INFO_SESSION_LOGOUT = > „user.jcr.session.logout“; So

[SLING-4275] API: Record Interface

Hi all Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since this issue covers 4 topics, I think it would be best to quickly discuss these topic in separate threads. #3 Record Interface The Record interface is used primarily by the Java POJO UseProvider to inject propertie

[SLING-4275] API: RenderContext Object Traversal

Hi all Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since this issue covers 4 topics, I think it would be best to quickly discuss these topic in separate threads. #4 RenderContext Object Traversal The Sightly Engine provides functionality for extensions to transparently

[SLING-4275] API: ResourceResolution helper

Hi all Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since this issue covers 4 topics, I think it would be best to quickly discuss these topic in separate threads. #5 ResourceResolution helper The ResourceResolution helper kind of duplicates and/or extends functionality

[SLING-4275] API: RuntimeExtension and ExtensionInstance

Hi all Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since this issue covers 4 topics, I think it would be best to quickly discuss these topic in separate threads. #2 RuntimeExtension and ExtensionInstance Currently the RuntimeExtension is a service and called to return a

[SLING-4275] API: Exceptions

Hi all Carsten started to review the Sightly Engine API in SLING-4275 [1]. Since this issue covers 4 topics, I think it would be best to quickly discuss these topic in separate threads. #1 Exceptions The root exception is SightlyException extends SlingException. As such it is a RuntimeExcepti

[jira] [Updated] (SLING-4293) [XSS] Reduce footprint and dependencies

[ https://issues.apache.org/jira/browse/SLING-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4293: - Attachment: SLING-4293.patch Proposed patch with Conditional-Package. This needs thorough

[jira] [Created] (SLING-4293) [XSS] Reduce footprint and dependencies

Felix Meschberger created SLING-4293: Summary: [XSS] Reduce footprint and dependencies Key: SLING-4293 URL: https://issues.apache.org/jira/browse/SLING-4293 Project: Sling Issue Type

[jira] [Resolved] (SLING-4282) [Sightly] Fully qualified Use POJOs are not correctly identified in the repository

[ https://issues.apache.org/jira/browse/SLING-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4282. -- Resolution: Fixed Thanks for providing the patch. I have applied it in Rev. 1650895

[jira] [Assigned] (SLING-4282) [Sightly] Fully qualified Use POJOs are not correctly identified in the repository

[ https://issues.apache.org/jira/browse/SLING-4282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4282: Assignee: Felix Meschberger > [Sightly] Fully qualified Use POJOs are

Re: How to override install run modes at startup?

Hi Ok, according to an off-line discussion, this is really related to the question of how to make sure Sling starts in the correct runmode after having migrated the JCR repository from, say, Jackrabbit 2 to Oak. First I think, the migration of the persistence is an explicit and different step

Re: broken documentation URLs returned by google

Hi Strange, this seems to gave been a temporary issue. At first, I could reproduce, but now I get all these pages back … Regards Felix > Am 08.01.2015 um 02:20 schrieb Yogesh Upadhyay : > > Yes. I saw that today as well. Most of the link are referred from original > sling doc. > > Yogesh > O

[jira] [Commented] (SLING-4275) Review of the Sightly API

[ https://issues.apache.org/jira/browse/SLING-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264423#comment-14264423 ] Felix Meschberger commented on SLING-4275: -- Thanks, [~cziegeler]. I would

[jira] [Commented] (SLING-4275) Review of the Sightly API

[ https://issues.apache.org/jira/browse/SLING-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264327#comment-14264327 ] Felix Meschberger commented on SLING-4275: -- bq. 1. There are several except

[jira] [Resolved] (SLING-4241) Improve Sightly JS Provider performance

[ https://issues.apache.org/jira/browse/SLING-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4241. -- Resolution: Fixed Thanks for providing the patch. I have applied it in Rev. 1645656

[jira] [Resolved] (SLING-4240) Improve Sightly engine performance

[ https://issues.apache.org/jira/browse/SLING-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4240. -- Resolution: Fixed Thanks for providing the patch. I have applied it slightly modified

[jira] [Assigned] (SLING-4240) Improve Sightly engine performance

[ https://issues.apache.org/jira/browse/SLING-4240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4240: Assignee: Felix Meschberger > Improve Sightly engine performa

[jira] [Assigned] (SLING-4241) Improve Sightly JS Provider performance

[ https://issues.apache.org/jira/browse/SLING-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4241: Assignee: Felix Meschberger > Improve Sightly JS Provider performa

[jira] [Resolved] (SLING-4236) The XSSAPI's encode methods should return null for null input

[ https://issues.apache.org/jira/browse/SLING-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4236. -- Resolution: Fixed Fix Version/s: XSS Protection API 1.0.0 Fixed in Rev. 1644580

[jira] [Assigned] (SLING-4236) The XSSAPI's encode methods should return null for null input

[ https://issues.apache.org/jira/browse/SLING-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4236: Assignee: Felix Meschberger > The XSSAPI's encode methods should return

[jira] [Comment Edited] (SLING-4236) The XSSAPI's encode methods should return null for null input

[ https://issues.apache.org/jira/browse/SLING-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241653#comment-14241653 ] Felix Meschberger edited comment on SLING-4236 at 12/10/14 8:1

[jira] [Commented] (SLING-4236) The XSSAPI's encode methods should return null for null input

[ https://issues.apache.org/jira/browse/SLING-4236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241653#comment-14241653 ] Felix Meschberger commented on SLING-4236: -- Interestingly, the o

[jira] [Resolved] (SLING-4232) The PojoUseProvider should log errors only for Java classes

[ https://issues.apache.org/jira/browse/SLING-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4232. -- Resolution: Fixed Thanks for providing the patch. Applied in Rev. 1644369 >

[jira] [Resolved] (SLING-4231) [Sightly] The XSSRuntimeExtension should not escape the "ul" tag for element names

[ https://issues.apache.org/jira/browse/SLING-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4231. -- Resolution: Fixed Thanks for the patch. I have applied it in Rev. 1644367 > [Sigh

[jira] [Assigned] (SLING-4232) The PojoUseProvider should log errors only for Java classes

[ https://issues.apache.org/jira/browse/SLING-4232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4232: Assignee: Felix Meschberger > The PojoUseProvider should log errors only for J

[jira] [Assigned] (SLING-4231) [Sightly] The XSSRuntimeExtension should not escape the "ul" tag for element names

[ https://issues.apache.org/jira/browse/SLING-4231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4231: Assignee: Felix Meschberger > [Sightly] The XSSRuntimeExtension should not esc

[jira] [Commented] (SLING-4233) Change distribution component creation from osgi config factories to osgi component factories

[ https://issues.apache.org/jira/browse/SLING-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240878#comment-14240878 ] Felix Meschberger commented on SLING-4233: -- I agree that storing configura

Re: Creating new threads in sling code

Hi Jörg > Am 08.12.2014 um 22:31 schrieb Jörg Hoh : > > Hi Felix > > 2014-12-08 14:34 GMT+01:00 Felix Meschberger : > > > >> >> >>> * The J2E programming model discourages the creation of threads; instead >>> one is supposed to

[jira] [Resolved] (SLING-4227) [sightly] Rename RuntimeExtension.SCR_PROP_NAME

[ https://issues.apache.org/jira/browse/SLING-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4227. -- Resolution: Fixed Renamed property to NAME in Rev. 1643823 > [sightly] Ren

[jira] [Updated] (SLING-4227) [sightly] Rename RuntimeExtension.SCR_PROP_NAME

[ https://issues.apache.org/jira/browse/SLING-4227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4227: - Fix Version/s: (was: Scripting Sightly JS Use Provider 1.0.0) > [sightly] Ren

[jira] [Created] (SLING-4227) [sightly] Rename RuntimeExtension.SCR_PROP_NAME

Felix Meschberger created SLING-4227: Summary: [sightly] Rename RuntimeExtension.SCR_PROP_NAME Key: SLING-4227 URL: https://issues.apache.org/jira/browse/SLING-4227 Project: Sling Issue

Re: Creating new threads in sling code

Hi > Am 08.12.2014 um 12:41 schrieb Jörg Hoh : > > Hi, > > It already fell a number of times over code in sling, where threads are > created manually like this: > > Thread t = new Thread(someRunnable); > t.start(); > > I understand, that this is convenient and solves the problem in most of the

Re: Using adapters on Sling startup

Hi > Am 04.12.2014 um 16:25 schrieb Bertrand Delacretaz : > > Hi, > > On Thursday, December 4, 2014, Robert Munteanu wrote: >> ... >> @RequiresAdapter(adaptable=Resource.class, adapter=MyClass.class) >> ... > > This looks good to me, although it would be even more obvious as > > @RequiresAda

Review Request 28758: @AdapterReference annotation prototype

-CREATION Diff: https://reviews.apache.org/r/28758/diff/ Testing --- Thanks, Felix Meschberger

Re: Review Request 28751: SLING-4217 - Register OSGi services corresponding to available adapter factories

Hi Robert Thanks for starting the review. Looks like the Adaption interface is missing from the review ? Regards Felix > Am 05.12.2014 um 12:02 schrieb Robert Munteanu : > > > --- > This is an automatically generated e-mail. To reply, vi

[jira] [Resolved] (SLING-4220) SlingException constructor must not call initCause

[ https://issues.apache.org/jira/browse/SLING-4220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4220. -- Resolution: Fixed Fixed in Rev. 1643255 Also added a unit test to make sure, this now

[jira] [Resolved] (SLING-4219) [Sightly] Unrecognised operators in expressions are not properly reported as syntax errors

[ https://issues.apache.org/jira/browse/SLING-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4219. -- Resolution: Fixed Thanks for providing the patch. I have applied it in Rev. 1643248

[jira] [Created] (SLING-4220) SlingException constructor must not call initCause

Felix Meschberger created SLING-4220: Summary: SlingException constructor must not call initCause Key: SLING-4220 URL: https://issues.apache.org/jira/browse/SLING-4220 Project: Sling

[jira] [Assigned] (SLING-4219) [Sightly] Unrecognised operators in expressions are not properly reported as syntax errors

[ https://issues.apache.org/jira/browse/SLING-4219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4219: Assignee: Felix Meschberger > [Sightly] Unrecognised operators in expressions

[jira] [Updated] (SLING-4177) Sightly: StyleString context doesn't properly escape

[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4177: - Component/s: Extensions > Sightly: StyleString context doesn't properl

[jira] [Resolved] (SLING-4177) Sightly: StyleString context doesn't properly escape

[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4177. -- Resolution: Fixed Fix Version/s: XSS Protection API 1.0.0 Thanks for providing

[jira] [Assigned] (SLING-4177) Sightly: StyleString context doesn't properly escape

[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4177: Assignee: Felix Meschberger > Sightly: StyleString context doesn't properl

Re: Servlet Filter Support adding sling.filter.pattern support

Hi The point is that we should implement what we need and ignore what we don’t need. For some use cases it would indeed be good to be simply able to filter on the URL path (or resource path) like in the Servlet API itself. Consider for example a content management system where you want to appl

Re: Using adapters on Sling startup

Hi > Am 04.12.2014 um 15:00 schrieb Bertrand Delacretaz : > > On Wed, Dec 3, 2014 at 9:11 PM, Robert Munteanu wrote: >> ...When Sling starts up, it's perfectly legal for Bundle B to be STARTED >> while Bundle A is just RESOLVED > > Would the OSGi Require-Capability help make sure that the r

Re: Tenant change events

/jira/browse/SLING-4207 > Am 28.11.2014 um 12:52 schrieb Felix Meschberger : > > Hi > > This sounds useful to me. > > Lets do OSGi events to decouple the actual listener handling and event > distribution from the tenant manager. > > Regards > Felix > >

[jira] [Commented] (SLING-4177) Sightly: StyleString context doesn't properly escape

[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228390#comment-14228390 ] Felix Meschberger commented on SLING-4177: -- No problem. Thanks. Standin

[jira] [Assigned] (SLING-4207) Add notifications upon tenant changes

[ https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4207: Assignee: Felix Meschberger > Add notifications upon tenant chan

[jira] [Commented] (SLING-4207) Add notifications upon tenant changes

[ https://issues.apache.org/jira/browse/SLING-4207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228340#comment-14228340 ] Felix Meschberger commented on SLING-4207: -- A note to bug handlers: As discu

[jira] [Commented] (SLING-4177) Sightly: StyleString context doesn't properly escape

[ https://issues.apache.org/jira/browse/SLING-4177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228332#comment-14228332 ] Felix Meschberger commented on SLING-4177: -- [~vladb] I am a bit confused a

Re: Tenant change events

7;ll update the PR with the OSGI approach. Regards, Timothee 2014-11-28 12:52 GMT+01:00 Felix Meschberger mailto:fmesc...@adobe.com>>: Hi This sounds useful to me. Lets do OSGi events to decouple the actual listener handling and event distribution from the tenant manager. Regards Felix -

[jira] [Resolved] (SLING-4209) [Sightly] Provide JS files as bundle resources instead of copying to repository

[ https://issues.apache.org/jira/browse/SLING-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4209. -- Resolution: Fixed Fix Version/s: Scripting Sightly JS Use Provider 1.0.0 Changed

[jira] [Updated] (SLING-4209) [Sightly] Provide JS files as bundle resources instead of copying to repository

[ https://issues.apache.org/jira/browse/SLING-4209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4209: - Affects Version/s: (was: Scripting Sightly JS Use Provider 1.0.0) > [Sightly] Prov

[jira] [Created] (SLING-4209) [Sightly] Provide JS files as bundle resources instead of copying to repository

Felix Meschberger created SLING-4209: Summary: [Sightly] Provide JS files as bundle resources instead of copying to repository Key: SLING-4209 URL: https://issues.apache.org/jira/browse/SLING-4209

[jira] [Commented] (SLING-4182) Cleanup Sightly Engine dependencies

[ https://issues.apache.org/jira/browse/SLING-4182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228281#comment-14228281 ] Felix Meschberger commented on SLING-4182: -- In Rev. 1642292 I also downgr

Re: Tenant change events

Hi This sounds useful to me. Lets do OSGi events to decouple the actual listener handling and event distribution from the tenant manager. Regards Felix -- Typos caused by my iPhone > Am 27.11.2014 um 16:56 schrieb Timothée Maret : > > Hi, > > Currently, there is no clean way to detect when

[jira] [Resolved] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4206. -- Resolution: Fixed After properly declaring the Record interface to be @ConsumerType in

[jira] [Updated] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4206: - Fix Version/s: Scripting Sightly JS Use Provider 1.0.0 > [Sightly Engine] Refactor

[jira] [Commented] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228221#comment-14228221 ] Felix Meschberger commented on SLING-4206: -- And removed empty folders a

[jira] [Commented] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14228218#comment-14228218 ] Felix Meschberger commented on SLING-4206: -- Applied the patch in Rev. 164

Re: [Sightly] API vs. Implementation

of commit messages coming along … Regards Felix [1] https://github.com/fmeschbe/sling.git [2] https://issues.apache.org/jira/browse/SLING-4206 > Am 25.11.2014 um 15:46 schrieb Felix Meschberger : > > Hi Radu > > Cool, thanks. I'll review and get back to you.

[jira] [Updated] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4206: - Component/s: Scripting > [Sightly Engine] Refactor the Sightly Engine

[jira] [Assigned] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

[ https://issues.apache.org/jira/browse/SLING-4206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4206: Assignee: Felix Meschberger > [Sightly Engine] Refactor the Sightly Engine

[jira] [Created] (SLING-4206) [Sightly Engine] Refactor the Sightly Engine API

Felix Meschberger created SLING-4206: Summary: [Sightly Engine] Refactor the Sightly Engine API Key: SLING-4206 URL: https://issues.apache.org/jira/browse/SLING-4206 Project: Sling Issue

[jira] [Resolved] (SLING-4204) Better abstraction of internal Filter handling and add filter processing timing

[ https://issues.apache.org/jira/browse/SLING-4204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4204. -- Resolution: Fixed Implemented in Rev. 1642086 > Better abstraction of internal Fil

[jira] [Created] (SLING-4204) Better abstraction of internal Filter handling and add filter processing timing

Felix Meschberger created SLING-4204: Summary: Better abstraction of internal Filter handling and add filter processing timing Key: SLING-4204 URL: https://issues.apache.org/jira/browse/SLING-4204

[jira] [Commented] (SLING-4199) Remove ProviderOutcome

[ https://issues.apache.org/jira/browse/SLING-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226268#comment-14226268 ] Felix Meschberger commented on SLING-4199: -- I think there are cases w

Re: [Sightly] API vs. Implementation

e can >> get rid of the UnitLocator interface, therefore reducing the size of the >> exported API to the bare minimum. >> >> Thanks, >> Radu >> >> On Mon, Nov 24, 2014 at 12:36 PM, Felix Meschberger >> wrote: >> >>> Hi Radu >>

[jira] [Commented] (SLING-4193) Cannot set Property type in import operation using @TypeHint suffix

[ https://issues.apache.org/jira/browse/SLING-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224294#comment-14224294 ] Felix Meschberger commented on SLING-4193: -- I have the impression that non

[jira] [Resolved] (SLING-4197) Startup fails if StartupHandler throws an exception

[ https://issues.apache.org/jira/browse/SLING-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4197. -- Resolution: Fixed I don't think we don't need to update any Java

[jira] [Updated] (SLING-4197) Startup fails if StartupHandler throws an exception

[ https://issues.apache.org/jira/browse/SLING-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4197: - Affects Version/s: (was: Launchpad API 1.1.0) > Startup fails if StartupHand

[jira] [Updated] (SLING-4197) Startup fails if StartupHandler throws an exception

[ https://issues.apache.org/jira/browse/SLING-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4197: - Fix Version/s: (was: Launchpad API 1.1.2) > Startup fails if StartupHandler throws

[jira] [Assigned] (SLING-4197) Startup fails if StartupHandler throws an exception

[ https://issues.apache.org/jira/browse/SLING-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4197: Assignee: Felix Meschberger > Startup fails if StartupHandler throws an except

[jira] [Commented] (SLING-4197) Startup fails if StartupHandler throws an exception

[ https://issues.apache.org/jira/browse/SLING-4197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224286#comment-14224286 ] Felix Meschberger commented on SLING-4197: -- Implemented catching and loggin

[jira] [Created] (SLING-4197) Startup fails if StartupHandler throws an exception

Felix Meschberger created SLING-4197: Summary: Startup fails if StartupHandler throws an exception Key: SLING-4197 URL: https://issues.apache.org/jira/browse/SLING-4197 Project: Sling

Re: Old website content on Confluence, should we remove it?

Hi I think the SLINGxSITE always only served as the source for the site. Information there is outdated. I think we can just drop the space. Regards Felix > Am 24.11.2014 um 11:27 schrieb Bertrand Delacretaz : > > Hi, > > https://cwiki.apache.org/confluence/display/SLINGxSITE/ was used to > g

[jira] [Commented] (SLING-4187) Move validation and xss projects into contrib/extensions

[ https://issues.apache.org/jira/browse/SLING-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222868#comment-14222868 ] Felix Meschberger commented on SLING-4187: -- [~rombert] Thanks alot :-) &g

Re: [Sightly] API vs. Implementation

ling of packages etc. Thanks Felix > > Cheers, > Radu > > On Thu, Nov 20, 2014 at 6:53 PM, Felix Meschberger > wrote: > >> Hi >> >> Thanks for your reply. >> >> For those interested in following, Radu and I are cooperating on these >> chan

Re: [Sightly] API vs. Implementation

> On Wed, Nov 19, 2014 at 10:49 PM, Felix Meschberger > wrote: > >> Apart from splitting the base .api package, this are further discussions: >> >> * Exceptions are forming a hierarchy with SightlyEngineException being the >> root and itself extending from SlingEx

[Sightly] API vs. Implementation

Hi TL;DR We have to cleanup APIs and exports from Sightly Engine and JS UseProvider bundles. I have been going through the Sightly Engine and JS UseProvider bundles. The JS UseProvider bundle currently exports everything at the bundle version. I would think this bundle should not be exporting

[jira] [Resolved] (SLING-4185) The org.apache.sling.xss bundle should properly export its API

[ https://issues.apache.org/jira/browse/SLING-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4185. -- Resolution: Fixed Thanks for providing the patch. I have applied it slightly modified

[jira] [Assigned] (SLING-4185) The org.apache.sling.xss bundle should properly export its API

[ https://issues.apache.org/jira/browse/SLING-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4185: Assignee: Felix Meschberger > The org.apache.sling.xss bundle should prope

[jira] [Commented] (SLING-4154) Discuss distribution components creation and configuration

[ https://issues.apache.org/jira/browse/SLING-4154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218039#comment-14218039 ] Felix Meschberger commented on SLING-4154: -- [~mpetria] Re "internal A

[jira] [Updated] (SLING-4188) EventHandlers registered for TOPIC_RESOURCE_REMOVED should get property values of deleted resource in handleEvent method.

[ https://issues.apache.org/jira/browse/SLING-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4188: - Component/s: JCR > EventHandlers registered for TOPIC_RESOURCE_REMOVED should

[jira] [Updated] (SLING-4188) EventHandlers registered for TOPIC_RESOURCE_REMOVED should get property values of deleted resource in handleEvent method.

[ https://issues.apache.org/jira/browse/SLING-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-4188: - Affects Version/s: JCR Resource 2.3.12 > EventHandlers registered

Re: XSS bundle location

Ok, moved both in Rev. 1640525 (SLING-4187) Regards Felix > Am 19.11.2014 um 12:15 schrieb Felix Meschberger : > > Hi > >> Am 19.11.2014 um 11:44 schrieb Oliver Lietz : >> >> On Wednesday 19 November 2014 09:54:05 Felix Meschberger wrote: >>> Hi all >

[jira] [Resolved] (SLING-4187) Move validation and xss projects into contrib/extensions

[ https://issues.apache.org/jira/browse/SLING-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4187. -- Resolution: Fixed Done in Rev. 1640525 > Move validation and xss projects into cont

[jira] [Created] (SLING-4187) Move validation and xss projects into contrib/extensions

Felix Meschberger created SLING-4187: Summary: Move validation and xss projects into contrib/extensions Key: SLING-4187 URL: https://issues.apache.org/jira/browse/SLING-4187 Project: Sling

Re: XSS bundle location

Hi > Am 19.11.2014 um 11:44 schrieb Oliver Lietz : > > On Wednesday 19 November 2014 09:54:05 Felix Meschberger wrote: >> Hi all >> >> The XSS bundle is currently in the contrib folder. IMHO it should be in >> contrib/extensions. >> >> Any opposi

[jira] [Resolved] (SLING-4180) Sightly Engine should properly reimport its own API export

[ https://issues.apache.org/jira/browse/SLING-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4180. -- Resolution: Fixed Thanks for providing the patch. I have applied it in Rev. 1640508

[jira] [Assigned] (SLING-4180) Sightly Engine should properly reimport its own API export

[ https://issues.apache.org/jira/browse/SLING-4180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-4180: Assignee: Felix Meschberger > Sightly Engine should properly reimport its own

[jira] [Resolved] (SLING-4167) The Sightly implementation should provide support for escaped expressions

[ https://issues.apache.org/jira/browse/SLING-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4167. -- Resolution: Fixed Fix Version/s: Scripting Sightly Engine 1.0.0 Thanks for

<    1   2   3   4   5   6   7   8   9   10   >