On Wed, Jun 6, 2018 at 7:23 PM, Jörg Hoh wrote:
> ...Streamer stream = resource.adaptTo(Streamer.class);
> could do the trick. Then you can have everything in a dedicated bundle and
> there is no need to change any of the sling core APIs or bundles
+1
-Bertrand
On Wed, 2018-06-06 at 13:17 -0700, Eric Norman wrote:
> Keep in mind that an in memory cache wont work so well in a cluster
> unless
> you can guarantee sticky sessions from your load balancer.
That's a good point. Hasini, can you make a note of that for
improvements?
But let's start simple
Keep in mind that an in memory cache wont work so well in a cluster unless
you can guarantee sticky sessions from your load balancer.
On Wed, Jun 6, 2018, 1:11 PM Robert Munteanu wrote:
> On Wed, 2018-06-06 at 21:37 +0300, Ioan Eugen Stan wrote:
> > Hi,
> >
> > I think you should store it in
On Wed, 2018-06-06 at 21:37 +0300, Ioan Eugen Stan wrote:
> Hi,
>
> I think you should store it in memory. Use a hashmap or something.
>
> Make it work and then optimize. The check should be very fast so
> don't worry about it.
+1
Robert
[
https://issues.apache.org/jira/browse/SLING-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-7684:
Attachment: project-readme.png
modules-page.png
features-page.png
> Add
Hello Apache Supporters and Enthusiasts
This is a final reminder that our Apache EU Roadshow will be held in
Berlin next week on 13th and 14th June 2018. We will have 28 different
sessions running over 2 days that cover some great topics. So if you are
interested in Microservices, Internet of
A while back, I had implemented an oauth2 sling authentication handler for
a private project. If you have interest in seeing the code I could
probably find it again.
I used the scribejava library from [1] to do most of the oauth2 heavy
lifting and it seemed to work pretty well for hooking into
Hi,
I think you should store it in memory. Use a hashmap or something.
Make it work and then optimize. The check should be very fast so don't worry
about it.
In case you do need to store it, use jcr.
Always delay optimisations. Caching is an optimization.
Eugen Stan
Netdava
Hi all,
I am implementing OpenID Connect protocol for Sling. First, Sling is
sending an authorization request to Google( OpenID Connect Provider - OP).
This request contains an attribute call state. State is a string object.
If the authorization is successful Google will send a response with an
Hi
2018-06-06 17:01 GMT+02:00 Jason E Bailey :
> This started out as a separate Object which was part of a bigger set of
> code, from which the feedback eventually had it end up as a single method
> in the Resource interface.
>
Resource implements the very flexible Adapter interface, so I
Chris Millar created SLING-7711:
---
Summary: [JIRA] Access to assign tickets / sub-tasks
Key: SLING-7711
URL: https://issues.apache.org/jira/browse/SLING-7711
Project: Sling
Issue Type:
On Wed, Jun 6, 2018 at 3:53 PM, Carsten Ziegeler wrote:
> ...I see the value of having this as a library
> everyone can use. But I think we usually should keep library code
> separate from the pure (in lack of a better word) api like the resource
> api...
I agree with that.
IIUC the current
Because the resource resolver bundle is a provider (not consumer) of the
resource package and therefore has a narrow version import range,
basically limited to a specific minor version. It implements a couple of
interfaces from that package.
So adding anything to that package comes with this
1. good to know.
2. why?
- Jason
On Wed, Jun 6, 2018, at 9:54 AM, Carsten Ziegeler wrote:
> Forgot one thing: each time we change the resource api package, we need
> to re-release the resource resolver (although we might not need to
> implement anything there) - which is another indicator
This started out as a separate Object which was part of a bigger set of code,
from which the feedback eventually had it end up as a single method in the
Resource interface.
The libraries I mentioned would be entirely separate, all of this came from
here:
dulvac closed pull request #3: SLING-7669 StartupManager overwrites the
frameworkstartlevel property…
URL: https://github.com/apache/sling-org-apache-sling-launchpad-base/pull/3
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed
[
https://issues.apache.org/jira/browse/SLING-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503334#comment-16503334
]
Radu Cotescu commented on SLING-7710:
-
Implemented in [commit
Forgot one thing: each time we change the resource api package, we need
to re-release the resource resolver (although we might not need to
implement anything there) - which is another indicator whether the
resource api package is a good candidate or not
Regards
Carsten
Carsten Ziegeler wrote
>
Radu Cotescu created SLING-7710:
---
Summary: [HTL] Enhance error reporting for plugin errors
Key: SLING-7710
URL: https://issues.apache.org/jira/browse/SLING-7710
Project: Sling
Issue Type:
I haven't really followed the whole discussion but the keyword in your a
response to me is "library". I see the value of having this as a library
everyone can use. But I think we usually should keep library code
separate from the pure (in lack of a better word) api like the resource
api. There are
[
https://issues.apache.org/jira/browse/SLING-7709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503302#comment-16503302
]
Radu Cotescu commented on SLING-7709:
-
Implemented in:
* [commit
Radu Cotescu created SLING-7709:
---
Summary: [HTL] Implement the data-sly-set block element
Key: SLING-7709
URL: https://issues.apache.org/jira/browse/SLING-7709
Project: Sling
Issue Type:
Hi Jörg,
I think this is, in part, a matter of personal experience. My team and I have
found traversing a sub tree traversal so useful that I've created libraries of
predicates and an expression language to ease the creation of predicates for
those traversals. I would estimate that we use a
[
https://issues.apache.org/jira/browse/SLING-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Peltier resolved SLING-7692.
Resolution: Fixed
> MockSession.revert(false) support should be clearer
>
npeltier closed pull request #1: Revert "SLING-7692 implement refresh(false)"
URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/1
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of
Hi everyone,
we are happy to present to you the official adaptTo() 2018 agenda:
http://adapt.to/schedule
If you were waiting for the agenda to book your ticket you can get it here:
http://adapt.to/tickets
This year we have a special for you! We are happy to offer you two free
Hands-On Labs.
26 matches
Mail list logo
