[
https://issues.apache.org/jira/browse/SLING-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1266.
-
Resolution: Fixed
Fixed in revision: 896348
Init parameters from servlet config are
[
https://issues.apache.org/jira/browse/SLING-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1267.
-
Resolution: Fixed
Fixed in revision: 896348 and revision: 896349
Get metadata of
[
https://issues.apache.org/jira/browse/SLING-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797030#action_12797030
]
Felix Meschberger commented on SLING-966:
-
Deployed SNAPSHOT version
[
https://issues.apache.org/jira/browse/SLING-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797033#action_12797033
]
Felix Meschberger commented on SLING-966:
-
Removed old authentication code from the
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/293/
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/224/
[
https://issues.apache.org/jira/browse/SLING-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-1265:
-
Fix Version/s: Extensions OpenID Authentication 1.0.0
Adapt OpenID Authentication
[
https://issues.apache.org/jira/browse/SLING-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-1265.
--
Resolution: Fixed
Rev. 896366: Adapt to new AuthenticationHandler API and replace
Replace Session.logout from SlingMainServlet
Key: SLING-1270
URL: https://issues.apache.org/jira/browse/SLING-1270
Project: Sling
Issue Type: Task
Components: Engine
Affects
[
https://issues.apache.org/jira/browse/SLING-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797059#action_12797059
]
Felix Meschberger commented on SLING-966:
-
Updated the bundle list in the Launchpad
Hi all,
I have now committed the changes required for SLING-966 [1].
So, if you upgrade the Sling Engine to the latest trunk, you should also
install the new Commons Auth bundle.
Your existing AuthenticationHandler implementations will still be
working. I have upgraded our own HTTP Basic and
Felix,
I agree that we should use the ServletRequestListener support, but I continue
to wonder if there isnt a need for a request lifecycle to be exposed by the
sling main servlet which would avoid having to a) create a stack of
ServletFilters b) bind the SlingMainServlet to other apis' c)
Felix,
Were there recent releases of the bundles in question before this change was
made. I am 1 week away from cutting a release and we have some major bits of
work in the AuthN area, including container and CAS authn modules. I suspect
that the porting effort is going to be minimal but the
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/460/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/460/changes
See
http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/org.apache.sling$org.apache.sling.launchpad.contrib-testing/294/
See http://hudson.zones.apache.org/hudson/job/sling-contrib-1.5/294/
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/225/
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/461/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/461/changes
Hi Ian,
There was an Engine 2.0.6 release, which still contains the old
authentication API.
The combo Engine trunk plus Commons Auth trunk is basically an extended
situation of the Engine 2.0.6 release and all the 2.0.6 authentication
functionality still works.
Hope this helps.
Regards
Felix
Hi Ian,
On 06.01.2010 11:57, Ian Boston wrote:
I agree that we should use the ServletRequestListener support, but I continue
to wonder if there isnt a need for a request lifecycle to be exposed by the
sling main servlet which would avoid having to a) create a stack of
ServletFilters b)
The maven-sling-plugin has the very useful feature mountByFS, which
automatically sets up FsResourceProviders for the initial-content in
the bundle.
This is great for development, as you can work directly on the files
in the bundle, without having to re-deploy the bundle for each change.
However,
On 6 Jan 2010, at 13:01, Felix Meschberger wrote:
Hi Ian,
On 06.01.2010 11:57, Ian Boston wrote:
I agree that we should use the ServletRequestListener support, but I
continue to wonder if there isnt a need for a request lifecycle to be
exposed by the sling main servlet which would avoid
Hi,
Vidar Ramdal wrote:
The maven-sling-plugin has the very useful feature mountByFS, which
automatically sets up FsResourceProviders for the initial-content in
the bundle.
This is great for development, as you can work directly on the files
in the bundle, without having to re-deploy the
Hi,
On 06.01.2010 14:30, Ian Boston wrote:
On 6 Jan 2010, at 12:51, Felix Meschberger wrote:
Hi Ian,
There was an Engine 2.0.6 release, which still contains the old
authentication API.
Ok cool, thanks we will give that a go.
The combo Engine trunk plus Commons Auth trunk is
Support mounting FsResourceProviders while avoiding loading content to JCR
--
Key: SLING-1271
URL: https://issues.apache.org/jira/browse/SLING-1271
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vidar S. Ramdal updated SLING-1271:
---
Description:
As described at [1], the mountByFS [2] flag allows you to have
Intermittent integration test failures
--
Key: SLING-1272
URL: https://issues.apache.org/jira/browse/SLING-1272
Project: Sling
Issue Type: Bug
Reporter: Felix Meschberger
Assignee:
On Wed, Jan 6, 2010 at 8:53 AM, Vidar Ramdal vi...@idium.no wrote:
Vidar Ramdal wrote:
However, the mountByFS feature relies on the Sling-Initial-Content
header to decide which paths should be mapped. This crashes with the
Sling Content Loader bundle, which also looks for that header. So,
Make Scala Scripting JSR 223 compliant
--
Key: SLING-1274
URL: https://issues.apache.org/jira/browse/SLING-1274
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter:
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/462/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/462/changes
[
https://issues.apache.org/jira/browse/SLING-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1268.
-
Resolution: Fixed
Fix Version/s: Scripting Core 2.0.10
Assignee: Carsten
Hi,
currently our scripting core depends on the jcr api. This is an old
relict to support the optional binding for currentNode. If the current
resource is adaptable to a jcr node, then this binding is set to this node.
This binding is not officially supported :)
We should definitly either remove
[
https://issues.apache.org/jira/browse/SLING-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797306#action_12797306
]
Felix Meschberger commented on SLING-1272:
--
It looks like the version dependency
A few comments on this:
1) It seems like this would impact every scripting language *except* JSPs.
For example, I reference it on the page which describes the new
JSONGroovyBuilder (
http://cwiki.apache.org/confluence/display/SLING/Using+the+JSONGroovyBuilder
).
2) Removing without deprecation
Hi,
On 06.01.2010 21:14, Carsten Ziegeler wrote:
Hi,
currently our scripting core depends on the jcr api. This is an old
relict to support the optional binding for currentNode. If the current
resource is adaptable to a jcr node, then this binding is set to this node.
This binding is not
Hi,
On 06.01.2010 22:16, Justin Edelson wrote:
A few comments on this:
1) It seems like this would impact every scripting language *except* JSPs.
For example, I reference it on the page which describes the new
JSONGroovyBuilder (
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/463/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/463/changes
Hi all,
Today I stumbled upon a potential problem with the JCR Session Pooling
we have in the JCR Base bundle.
Some time ago, we disabled session pooling by default. Only today I
actually set this default for the Embedded Jackrabbit bundle (see
SLING-1272).
The problems with session pooling are
+1
Session pooling is part of Jackrabbit 2 (which is where it belongs)
anyway. IIRC, you removed it in your JR 2 branch.
On Jan 6, 2010, at 5:11 PM, Felix Meschberger fmesc...@gmail.com
wrote:
Hi all,
Today I stumbled upon a potential problem with the JCR Session Pooling
we have in the
Hi,
On 06.01.2010 23:20, Justin Edelson wrote:
+1
Session pooling is part of Jackrabbit 2 (which is where it belongs)
anyway. IIRC, you removed it in your JR 2 branch.
I actually removed it in that branch exactly for the reasons outlined
below ;-)
Regards
Felix
On Jan 6, 2010, at 5:11
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/226/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/226/changes
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing/227/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.6/227/
On Jan 6, 2010, at 5:26 PM, Felix Meschberger fmesc...@gmail.com
wrote:
Hi,
On 06.01.2010 23:20, Justin Edelson wrote:
+1
Session pooling is part of Jackrabbit 2 (which is where it belongs)
anyway. IIRC, you removed it in your JR 2 branch.
I actually removed it in that branch exactly
Hi,
On 07.01.2010 03:59, Justin Edelson wrote:
On 1/6/10 4:33 PM, Felix Meschberger wrote:
Hi,
On 06.01.2010 22:16, Justin Edelson wrote:
3) I've been kicking around the idea that it would be nice for the
scripting
binding to be expandable. Given a service interface like this:
public
Hi,
On Wed, Jan 6, 2010 at 9:14 PM, Carsten Ziegeler cziege...@apache.org wrote:
...currently our scripting core depends on the jcr api. This is an old
relict to support the optional binding for currentNode. If the current
resource is adaptable to a jcr node, then this binding is set to this
51 matches
Mail list logo
