Carsten Ziegeler created SLING-2999:
---
Summary: JMX Resource Provider
Key: SLING-2999
URL: https://issues.apache.org/jira/browse/SLING-2999
Project: Sling
Issue Type: New Feature
Hi
Am 06.08.2013 um 20:26 schrieb Justin Edelson:
Hi Carsten,
I can't speak for exactly what Bertrand is thinking, but when I was
thinking about it, the scope/usage was an orthogonal concern to which
engine is selected.
Whereas today you do:
ScriptEngineManager.getEngineByExtension(ecma)
Hi
Am 07.08.2013 um 07:46 schrieb Carsten Ziegeler:
I'm not totally against this, but just adhoc adding this property without a
complete concept seems wrong to me. Defining the technical selection
process (e.g. as you describe it) is one part, but the other equally
important part, how to
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731716#comment-13731716
]
Felix Meschberger commented on SLING-2999:
--
I like this.
But why introduce a new
On Wed, Aug 7, 2013 at 9:04 AM, Felix Meschberger fmesc...@adobe.com wrote:
...But there is not currently a way that a script could declare I am an HC
script or
I am a Request Processing script...
The missing piece here is that the HC scripts that I'm talking about
(and probably the workflow
Hi Bertrand
We don't really disagree at all ;-)
In fact having written my previous messages, I wonder, whether our default
values we provide to scripts (request, response, etc.) should not really be
provided by a BVP in the request (or such) scope/context/usage ;-)
Somehow I tend to get to
I assume you are talking of Sling 7 ?
If so, I agree ;-)
Regards
Felix
Am 07.08.2013 um 07:52 schrieb Carsten Ziegeler:
I definitely agree that we should try to get Sling 6 out asap - and I think
we're pretty close to that. Apart maybe from a release of one or two
additional bundles, we
On Wed, Aug 7, 2013 at 9:43 AM, Felix Meschberger fmesc...@adobe.com wrote:
...In fact having written my previous messages, I wonder, whether our default
values we provide
to scripts (request, response, etc.) should not really be provided by a BVP
in the request (or such)
Here's my revised proposal based on this thread's discussions:
1. Add a context service property to our existing
BindingValuesProvider (BVP) implementations, value=request. The
context property can have multiple values.
2. Modify the scripting setup in DefaultSlingScript so that any BVP
which
On Wed, Aug 7, 2013 at 9:47 AM, Felix Meschberger fmesc...@adobe.com wrote:
I assume you are talking of Sling 7 ?
If so, I agree ;-)
Me too.
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731747#comment-13731747
]
Bertrand Delacretaz commented on SLING-2999:
Looks good to me, this will be
Hi
Basically sounds good.
Am 07.08.2013 um 09:55 schrieb Bertrand Delacretaz:
Here's my revised proposal based on this thread's discussions:
1. Add a context service property to our existing
BindingValuesProvider (BVP) implementations, value=request. The
context property can have multiple
On Wed, Aug 7, 2013 at 10:09 AM, Felix Meschberger fmesc...@adobe.com wrote:
...In fact I would say, that BVPs without the property should just be used
anywhere
that might work - I was going to say that [1] for example makes no
sense in my health check context, but that provider is being
2013/8/7 Felix Meschberger fmesc...@adobe.com
A script, at the end of the day, executes some action and might or might
not expect some bindings (global variables in some languages). The script
would have to cope with them missing or of the wrong type or such... But
there is not currently a
Again, I'm still missing a suggestion on how to mark a script to run in a
given context.
Carsten
2013/8/7 Bertrand Delacretaz bdelacre...@apache.org
On Wed, Aug 7, 2013 at 10:09 AM, Felix Meschberger fmesc...@adobe.com
wrote:
...In fact I would say, that BVPs without the property should
On Wed, Aug 7, 2013 at 8:52 AM, Carsten Ziegeler cziege...@apache.org wrote:
I definitely agree that we should try to get Sling 6 out asap - and I think
we're pretty close to that. Apart maybe from a release of one or two
additional bundles, we need to release the discovery stuff (I plan to do
[
https://issues.apache.org/jira/browse/SLING-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731771#comment-13731771
]
Carsten Ziegeler commented on SLING-2999:
-
Yes, the namespace is there do avoid
[
https://issues.apache.org/jira/browse/SLING-2997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731801#comment-13731801
]
Felix Meschberger commented on SLING-2997:
--
I agree. Java 5 is dead and new code
On Wed, Aug 7, 2013 at 10:26 AM, Carsten Ziegeler cziege...@apache.org wrote:
Again, I'm still missing a suggestion on how to mark a script to run in a
given context...
You don't.
There are request processing scripts, the ones we have and always had
- there's no change for those, except that
On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote:
...I can take care of setting up the .travis.yml file to make sure that
Sling builds on Travis. Then we need to find out how to authorize
Travis to build apache/sling ; OAK did it so it's possible
Sounds good to me!
Hmm, this doesn't really convince me. So this means there is no way to set
the context apart from creating/retrieving a script engine by hand (java
code)?
So scripts run with the usual Sling script resolution will always just use
BVPs not marked for any context and BVPs marked for the context
Yepp, let's give it a try - we don't need to publish the artifacts, just
getting a success/fail mail is enough
Carsten
2013/8/7 Bertrand Delacretaz bdelacre...@apache.org
On Wed, Aug 7, 2013 at 10:35 AM, Robert Munteanu rob...@lmn.ro wrote:
...I can take care of setting up the .travis.yml
On Wed, Aug 7, 2013 at 11:47 AM, Carsten Ziegeler cziege...@apache.org wrote:
...scripts run with the usual Sling script resolution will always just use
BVPs not marked for any context and BVPs marked for the context request...
That's exactly the idea - no change for existing request processing
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731864#comment-13731864
]
Robert Munteanu commented on SLING-920:
---
Added .travis.yml file in
On Wed, Aug 7, 2013 at 12:49 PM, Carsten Ziegeler cziege...@apache.org wrote:
Yepp, let's give it a try - we don't need to publish the artifacts, just
getting a success/fail mail is enough
Added .travis.yml file in
http://svn.apache.org/viewvc?view=revisionrevision=1511240 and also
filed
[
https://issues.apache.org/jira/browse/SLING-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2972.
-
Resolution: Fixed
Direct processing of local events has been added in rev 1504035
[
https://issues.apache.org/jira/browse/SLING-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2971.
-
Resolution: Fixed
I think we can close this now - as the underlying problem is due to
[
https://issues.apache.org/jira/browse/SLING-2950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2950.
-
Resolution: Fixed
This has been changed in rev 1501098
Disabling the
[
https://issues.apache.org/jira/browse/SLING-2724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2724.
-
Resolution: Fixed
Error handling doesn't respect servlet spec
On Tue, Aug 6, 2013 at 3:18 PM, Ian Boston i...@tfd.co.uk wrote:
Hi,
On 6 August 2013 10:24, Robert Munteanu rob...@lmn.ro wrote:
On Tue, Aug 6, 2013 at 12:10 PM, Dishara Wijewardana
ddwijeward...@gmail.com wrote:
com.google.common.base -- Cannot be resolved
com.google.common.collect
Hi Carsten
I started hacking around to this avail -- but I am nowhere near completion ...
I committed my current (incomplete) work to
https://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/logback
Regards
Felix
Am 06.08.2013 um 13:30 schrieb Carsten Ziegeler:
Hi,
i've the need for a
[
https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731910#comment-13731910
]
Felix Meschberger commented on SLING-2944:
--
Hmm, excellent point.
The goal of
[
https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731925#comment-13731925
]
Carsten Ziegeler commented on SLING-2944:
-
Right - I think the point is to be able
[
https://issues.apache.org/jira/browse/SLING-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13731932#comment-13731932
]
Felix Meschberger commented on SLING-2944:
--
Right using a service does not work:
See https://builds.apache.org/job/sling-trunk-1.7/166/changes
Changes:
[cziegeler] Correct license header
[rombert] SLING-920 - Jenkins continuous integration setup
Added .travis.yml file for travis-ci integration.
--
[...truncated 24472 lines...]
Aug
On 7 August 2013 12:49, Dishara Wijewardana ddwijeward...@gmail.com wrote:
@Dishara
Will be better to just add Guava as a bundle rathe than embed it since
it uses threads to reap weak references and do clean up.
I manually Added Guva OSGI bundle. It worked as mentioned. Is that what you
See https://builds.apache.org/job/sling-trunk-1.6/1794/changes
Changes:
[cziegeler] Add missing licence header
[cziegeler] Correct license header
[rombert] SLING-920 - Jenkins continuous integration setup
Added .travis.yml file for travis-ci integration.
See https://builds.apache.org/job/sling-trunk-1.7/167/changes
Changes:
[cziegeler] Add missing licence header
--
[...truncated 24508 lines...]
Aug 07, 2013 3:51:41 PM org.apache.maven.cli.event.ExecutionEventLogger
logReactorSummary
INFO: Sling Adapter
See https://builds.apache.org/job/sling-trunk-1.6/1795/changes
Changes:
[stefanegli] SLING-2985 : tooling : show content of .content.xml in project
explorer
- WIP/Work in progress : adding prototype of content[-package][.content.xml]
browsing. 'mounts' the syncDir as a new toplevel node to a
See https://builds.apache.org/job/sling-trunk-1.7/168/changes
Changes:
[stefanegli] SLING-2985 : tooling : show content of .content.xml in project
explorer
- WIP/Work in progress : adding prototype of content[-package][.content.xml]
browsing. 'mounts' the syncDir as a new toplevel node to a
All,
I am attempting to complete the release for Sling JSP TagLib 2.2.0, however
it seems I don't have commit access to the repository for the Sling
project's folder on dist.apache.org (
https://dist.apache.org/repos/dist/release/sling/).
When I checked with the infrastructure team, they said
See https://builds.apache.org/job/sling-trunk-1.7/169/changes
Changes:
[fmeschbe] SLING-2944 Prevent NPE if there is no authenticationInfo
is null.
--
[...truncated 23478 lines...]
Aug 07, 2013 10:45:23 PM
See https://builds.apache.org/job/sling-trunk-1.6/1796/changes
Changes:
[fmeschbe] SLING-2944 Prevent NPE if there is no authenticationInfo
is null.
--
[...truncated 26729 lines...]
Aug 7, 2013 11:07:22 PM
On Wed, Aug 7, 2013 at 6:48 PM, Ian Boston i...@tfd.co.uk wrote:
On 7 August 2013 12:49, Dishara Wijewardana ddwijeward...@gmail.com
wrote:
@Dishara
Will be better to just add Guava as a bundle rathe than embed it since
it uses threads to reap weak references and do clean up.
I
On Mon, Aug 5, 2013 at 5:50 AM, Dishara Wijewardana ddwijeward...@gmail.com
wrote:
On Tue, Jul 23, 2013 at 5:32 PM, Dishara Wijewardana
ddwijeward...@gmail.com wrote:
On Mon, Jul 22, 2013 at 1:56 PM, Ian Boston i...@tfd.co.uk wrote:
Hi Dishara,
The Unit test coverage sounds great. I
45 matches
Mail list logo
