hi *,
the current Sling Servlet Filter Support [0] allows to have scope dependent
filter (e.g. REQUEST, INCLUDE, FORWARD, ERROR, COMPONENT).
It would be nice to extend this support to have a specific filter being taken
in consideration only for specific path (adding sling.filter.pattern) a bit
hi *,
the current Sling Servlet Filter Support [0] allows to have scope dependent
filter (e.g. REQUEST, INCLUDE, FORWARD, ERROR, COMPONENT).
It would be nice to extend this support to have a specific filter being taken
in consideration only for specific path (adding sling.filter.pattern) a bit
See https://builds.apache.org/job/sling-healthcheck-1.6/563/
--
[...truncated 212 lines...]
Caused by: svn: E175002: timed out waiting for server
at
org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208)
at
Hi,
One ongoing problem (which has been a bit exacerbated by Sling Models)
is when code depends upon the AdapterManager being able to handle a
particular adaptation. Right now, the only way to deal with this is by
listening for the AdapterManager events. But these events aren't
particularly easy
Hi Antonio,
I'd suggest starting with support for resource type and *then* add path support.
Justin
On Thu, Dec 4, 2014 at 5:46 AM, Antonio Sanso asa...@adobe.com wrote:
hi *,
the current Sling Servlet Filter Support [0] allows to have scope dependent
filter (e.g. REQUEST, INCLUDE, FORWARD,
Hi Antonio,
I'd suggest starting with support for resource type and *then* add
path support if it was still necessary.
Regards,
Justin
On Thu, Dec 4, 2014 at 5:46 AM, Antonio Sanso asa...@adobe.com wrote:
hi *,
the current Sling Servlet Filter Support [0] allows to have scope dependent
Hi,
I thought I sent this earlier, but it appears not to have gotten
through (at least not according to markmail). Weird...
--
Hi,
One ongoing problem (which has been a bit exacerbated by Sling Models)
is when code depends upon the AdapterManager being able to handle a
particular adaptation.
Hi Justin,
On Wed, Dec 3, 2014 at 10:19 PM, Justin Edelson
jus...@justinedelson.com wrote:
Hi,
I thought I sent this earlier, but it appears not to have gotten
through (at least not according to markmail). Weird...
It came through as a separate email with a new subject. Anyway ...
--
On Wed, Dec 3, 2014 at 9:11 PM, Robert Munteanu romb...@apache.org 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 required
adapters are available before starting bundle
Hi
Am 04.12.2014 um 15:00 schrieb Bertrand Delacretaz bdelacre...@apache.org:
On Wed, Dec 3, 2014 at 9:11 PM, Robert Munteanu romb...@apache.org wrote:
...When Sling starts up, it's perfectly legal for Bundle B to be STARTED
while Bundle A is just RESOLVED
Would the OSGi
thanks Justin for your feedback,
if you would not mind I would try to do the opposite :)
The only reason is that I have already a Pocs for this that it actually
requires really few modifications.. (Felix gave me some good hints on how to
implement it :))
It would probably be the same for
Hi,
On Thursday, December 4, 2014, Robert Munteanu rob...@lmn.ro wrote:
...
@RequiresAdapter(adaptable=Resource.class, adapter=MyClass.class)
...
This looks good to me, although it would be even more obvious as
@RequiresAdapter(from=Resource.class, to=MyClass.class)
The adaptable/adapter
On Thu, Dec 4, 2014 at 5:25 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
Hi,
On Thursday, December 4, 2014, Robert Munteanu rob...@lmn.ro wrote:
...
@RequiresAdapter(adaptable=Resource.class, adapter=MyClass.class)
...
This looks good to me, although it would be even more obvious
Antonio Sanso created SLING-4216:
Summary: Limit the number of MapEntry
Key: SLING-4216
URL: https://issues.apache.org/jira/browse/SLING-4216
Project: Sling
Issue Type: Improvement
On Wed, 2014-12-03 at 15:19 -0500, Justin Edelson wrote:
@Component
@Service
@Reference(referenceInterface=Adaptation.class,
target=((adaptable=com.myco.MyClass)(adaptable=org.apache.sling.api.Resource)))
public class Foo {
public void doSomething(Resource resource) {
MyClass cfgMan =
[
https://issues.apache.org/jira/browse/SLING-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Sanso updated SLING-4216:
-
Summary: Limit the number of vanityPath MapEntry (was: Limit the number
of MapEntry )
Limit
See https://builds.apache.org/job/sling-healthcheck-1.6/564/
--
[...truncated 226 lines...]
at
org.tmatesoft.svn.core.internal.util.SVNSocketFactory.createPlainSocket(SVNSocketFactory.java:73)
at
Robert Munteanu created SLING-4217:
--
Summary: Register OSGi services corresponding to available adapter
factories
Key: SLING-4217
URL: https://issues.apache.org/jira/browse/SLING-4217
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4217:
---
Attachment: SLING-4217-1.diff
Register OSGi services corresponding to available adapter
I took a quick stab at a patch ( org.apache.sling.adapter only, no SCR
annotations for now),
https://issues.apache.org/jira/browse/SLING-4217
Patch attached, a review would be appreciated. It works for my
specific scenario, but might not be 100% correct.
Thanks,
Robert
[
https://issues.apache.org/jira/browse/SLING-4212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14234789#comment-14234789
]
Stefan Seifert commented on SLING-4212:
---
the patch looks fine for me.
(two really
See
https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/2830/
See https://builds.apache.org/job/sling-trunk-1.6/2830/changes
23 matches
Mail list logo
