[
https://issues.apache.org/jira/browse/SLING-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-321:
---
Assignee: Felix Meschberger
> Log stops working after reconfiguration
> --
On Tue, Mar 11, 2008 at 7:59 PM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> ...It seems Sling attempts to register nodetypes on every startup, even
> though they're already be registered - and when registering fails,
> Sling gives up on trying to connect to the repository. This is a bit
> odd,
Hi,
Am Dienstag, den 11.03.2008, 08:24 -0700 schrieb Bertrand Delacretaz
(JIRA):
> Note that currently running these tests requires setting Allow Anonymous
> Access to false on the Sling Authentication Filter configuration page, I'll
> open another issue for that.
I am currently working on SLIN
[
https://issues.apache.org/jira/browse/SLING-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Saar closed SLING-264.
Tested and works.
> Allow sling scripts resolved by the script resolver to be executed without
> reque
On 3/11/08, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> yes. in jackrabbit 1.4 the api exposes the import nodetypes
> capabilities of the nodetype manager. this is also available in
> jackrabbit:
>
> private void initNodeTypes() throws RepositoryException {
> // check if node types
On 3/11/08, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 10, 2008 at 11:27 AM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
>
> > ...This
> > leads me to suspect that the error has to do with
> > http://issues.apache.org/jira/browse/JCR-585 - that the
> > NodeTypeRegistry is not ava
> yes. in jackrabbit 1.4 the api exposes the import nodetypes
> capabilities of the nodetype manager. this is also available in
> jackrabbit:
should read: this is also available over RMI :-)
--
-< [EMAIL PROTECTED] >---
Tobias Bocanegra, Day Management AG,
yes. in jackrabbit 1.4 the api exposes the import nodetypes
capabilities of the nodetype manager. this is also available in
jackrabbit:
private void initNodeTypes() throws RepositoryException {
// check if node types are registered
try {
session.getWorkspace().getN
On Mon, Mar 10, 2008 at 11:27 AM, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> ...This
> leads me to suspect that the error has to do with
> http://issues.apache.org/jira/browse/JCR-585 - that the
> NodeTypeRegistry is not available via the "normal" RMI interfaces
I think you're right, does a
i have 2 questions/concerns:
1) why do you need cross domain scripting at all?
2) if you use the server as proxy you need to ensure that the server
'sees' the target. which might not be the case in most of the
companies.
regards, toby
On 3/11/08, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> O
Hate to be a pain in the ***, but this issue is preventing me from
making use of Sling.
Has anyone successfully set up Sling with a remote JCR lately?
On 3/10/08, Vidar Ramdal <[EMAIL PROTECTED]> wrote:
> I'm trying to set up sling to use a remote JCR repository, by using
> the sling.repository.
> i think it is confusing to deal with all those technologies for a newbie.
> everything from jackrabbit to sling to jcr to osgi to launchpad to ujax.
> some of this complexity is not necessary and can be removed easily.
> i think the ujax / sling distinction can definitely go. i would basicall
ujax tests require Allow Anonymous Access = false
-
Key: SLING-322
URL: https://issues.apache.org/jira/browse/SLING-322
Project: Sling
Issue Type: Bug
Components: ujax
Rep
[
https://issues.apache.org/jira/browse/SLING-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz closed SLING-241.
-
Resolution: Fixed
Tests re-added to launchpad/content in revision 635973, link on
http://
[
https://issues.apache.org/jira/browse/SLING-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577477#action_12577477
]
Carsten Ziegeler commented on SLING-320:
I added the return value to eval() and adde
[
https://issues.apache.org/jira/browse/SLING-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-321:
--
Attachment: SLING-log.patch
> Log stops working after reconfiguration
>
Log stops working after reconfiguration
---
Key: SLING-321
URL: https://issues.apache.org/jira/browse/SLING-321
Project: Sling
Issue Type: Bug
Components: Core
Reporter: Bertrand Dela
On Tue, Mar 11, 2008 at 12:33 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...We will probably anyway have two classes of modules in Sling: Those with
> regular releases and those, which just sit here and may be used with
> occasional releases on demand
Agreed, hence my intention to
Hi,
Am Dienstag, den 11.03.2008, 11:44 +0100 schrieb Bertrand Delacretaz:
> On Tue, Mar 11, 2008 at 11:42 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>
> > ... I share the same concerns, in addition I think this is a more general
> > feature which *might be* of interest for any web framework
Hi,
Am Dienstag, den 11.03.2008, 11:43 +0100 schrieb Bertrand Delacretaz:
> On Tue, Mar 11, 2008 at 11:34 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ... * Sling may therefore be used for attacks where the root of the attack
> > is hidden
> >
> > * We shift the cross-domain limi
[
https://issues.apache.org/jira/browse/SLING-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577399#action_12577399
]
Felix Meschberger commented on SLING-319:
-
Implemented part (6) (503 on missing repo
[
https://issues.apache.org/jira/browse/SLING-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-214.
---
Resolution: Fixed
With making use of the new RequestLogger service in the SlingMainServlet in
[
https://issues.apache.org/jira/browse/SLING-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577395#action_12577395
]
Felix Meschberger commented on SLING-214:
-
Refactored the RequestLoggerFilter into a
Felix Meschberger wrote:
Invocable is an interface, which is generally implemented by a
ScriptEngine, so adapting a Script to Invocable is comparable to adapt
it to a ScriptEngine and I would not do that.
Yes, adapting to ScriptEngine is not a good idea, that's why I thought
of just allowing In
Extend the scripting api to allow calls of methods defined in a script
--
Key: SLING-320
URL: https://issues.apache.org/jira/browse/SLING-320
Project: Sling
Issue Type: New
On Tue, Mar 11, 2008 at 11:42 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ... I share the same concerns, in addition I think this is a more general
> feature which *might be* of interest for any web framework using ajax.
> Atm I think we should not deal with things like these unless we rea
On Tue, Mar 11, 2008 at 11:34 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ... * Sling may therefore be used for attacks where the root of the attack
> is hidden
>
> * We shift the cross-domain limitation from the client to the server
> and burden the server with protection agains
Felix Meschberger wrote:
Hi,
Am Dienstag, den 11.03.2008, 11:17 +0100 schrieb Bertrand Delacretaz:
Hi,
I'm playing with some Ajax stuff using Sling, and hitting the
cross-domain limitations. Having an optional built-in HTTP proxy in
Sling would be useful.
I could create a servlet under extens
Hi,
Am Dienstag, den 11.03.2008, 11:17 +0100 schrieb Bertrand Delacretaz:
> Hi,
>
> I'm playing with some Ajax stuff using Sling, and hitting the
> cross-domain limitations. Having an optional built-in HTTP proxy in
> Sling would be useful.
>
> I could create a servlet under extensions/http-prox
Hi,
Am Montag, den 10.03.2008, 14:55 + schrieb padraic hannon:
> The script engine merely executes some chunk of script code with a given
> context. It has access to the execution context and should be able to call
> other scripts. Thus you could have scripts which call other scripts which i
Hi all,
Am Dienstag, den 11.03.2008, 11:06 +0100 schrieb Carsten Ziegeler:
> Rethinking, I think we should make these two changes:
> a) Add the return value to the eval() method
+1
> b) Make SlingScript adaptable and allow to adapt it to
> javax.script.Invocable [1].
>
> The only (minor) drawb
Hi,
I'm playing with some Ajax stuff using Sling, and hitting the
cross-domain limitations. Having an optional built-in HTTP proxy in
Sling would be useful.
I could create a servlet under extensions/http-proxy, that uses the
httpproxy selector, handling requests like:
/foo.httpproxy.anyextensi
Carsten Ziegeler wrote:
Felix Meschberger wrote:
First, I think the SlingScript interface provides a nice abstraction to
integrate with the Servlet/Script execution mechanism and taking the
burden of acquiring a ScriptEngine off the shoulders of developers.
Having said that, lets start about a
Streamlining authentication and access control
--
Key: SLING-319
URL: https://issues.apache.org/jira/browse/SLING-319
Project: Sling
Issue Type: Improvement
Components: Core, Resource
On Tue, Mar 11, 2008 at 8:30 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ... Ah, this is the right time to throw in my "catapult" naming idea :)
> (Some day someone will pick it up, I'm 100% sure...)...
Sure. some day ;-)
-Bertrand
On Tue, Mar 11, 2008 at 8:28 AM, David Nuescheler <[EMAIL PROTECTED]> wrote:
> ...i would basically
> recommend to replace ujax with sling throughout the code, this
> particularly includes the js side, and would graduate ujax into the
> sling js library, which makes perfect sense to me
Agr
David Nuescheler wrote:
hi guys,
i think it is confusing to deal with all those technologies for a newbie.
everything from jackrabbit to sling to jcr to osgi to launchpad to ujax.
some of this complexity is not necessary and can be removed easily.
i think the ujax / sling distinction can definit
hi guys,
i think it is confusing to deal with all those technologies for a newbie.
everything from jackrabbit to sling to jcr to osgi to launchpad to ujax.
some of this complexity is not necessary and can be removed easily.
i think the ujax / sling distinction can definitely go. i would basically
38 matches
Mail list logo
