Re: Issues that block our release

Hi, Am Donnerstag, den 03.04.2008, 09:37 +0200 schrieb Bertrand Delacretaz: Hi, Do we agree on using https://issues.apache.org/jira/browse/SLING/fixforversion/12312765 to define what's preventing us from making a first release? This definitely helps. Up to now, I just scanned the list of

Re: Servlet registration acrobatics

On Wed, Apr 2, 2008 at 4:57 PM, Vidar Ramdal [EMAIL PROTECTED] wrote: Created https://issues.apache.org/jira/browse/SLING-352 Any possibility for incorporating this in 1.0? -- Vidar S. Ramdal [EMAIL PROTECTED] - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway

Clustering Sling

We're building a large-scale web CMS, so scalability will be important. Does anyone have any thoughts on how to cluster Sling instances? -- Vidar S. Ramdal [EMAIL PROTECTED] - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway

[jira] Created: (SLING-354) Better way to define the node name for a newly created node

Better way to define the node name for a newly created node --- Key: SLING-354 URL: https://issues.apache.org/jira/browse/SLING-354 Project: Sling Issue Type: Improvement

[jira] Created: (SLING-356) Create separate project for the BundleResourceProvider

Create separate project for the BundleResourceProvider -- Key: SLING-356 URL: https://issues.apache.org/jira/browse/SLING-356 Project: Sling Issue Type: Bug Components: Resource

[jira] Created: (SLING-357) Support simple path mappings for bundle provided resources

Support simple path mappings for bundle provided resources -- Key: SLING-357 URL: https://issues.apache.org/jira/browse/SLING-357 Project: Sling Issue Type: Improvement

Updates to the post servlet

Hi, I would like to fix SLING-354 and SLING-355 asap. What do you think about the proposed changes? Carsten -- Carsten Ziegeler [EMAIL PROTECTED]

Re: Clustering Sling

Hi Vidar, Am Freitag, den 04.04.2008, 11:25 +0200 schrieb Vidar Ramdal: We're building a large-scale web CMS, so scalability will be important. Does anyone have any thoughts on how to cluster Sling instances? While I am not a specialist in Clustering, here are my thoughts. The basis is that

Re: Eclipse Plugin

It works! Thanks, Juanjo On Fri, Apr 4, 2008 at 12:30 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Hi Juanjo, This problem is caused by the jackrabbit-jcr-rmi version 1.4 library not being complete. This issue will be fixed in the upcoming (vote under way) version 1.4.1 library. As

Re: Eclipse Plugin

Hi Juanjo, This problem is caused by the jackrabbit-jcr-rmi version 1.4 library not being complete. This issue will be fixed in the upcoming (vote under way) version 1.4.1 library. As soon as this vote has passed and the release published, I will update the respective Jackrabbit 1.4 Eclipse

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585484#action_12585484 ] Carsten Ziegeler commented on SLING-355: Yes, I mean the case where a request

Re: Updates to the post servlet

Hi, ... I would like to fix SLING-354 and SLING-355 asap. What do you think about the proposed changes?... Ok with both changes (assuming you include/update the tests ;-), see my comment in SLING-355. -Bertrand

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585479#action_12585479 ] Bertrand Delacretaz commented on SLING-355: --- I assume by empty value you mean a

Re: Eclipse Plugin

Hi, I´m using CRX Eclipse Plugin (http://www.day.com/eclipse/) with Jackrabbit version 1.4 and RMI protocol. I´m getting this error when trying to connect to the repository: org.apache.jackrabbit.rmi.client.RemoteRepositoryException: error unmarshalling return; nested exception is:

[jira] Created: (SLING-358) Webloader sample mini-application

Webloader sample mini-application - Key: SLING-358 URL: https://issues.apache.org/jira/browse/SLING-358 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Bertrand

[jira] Resolved: (SLING-358) Webloader sample mini-application

[ https://issues.apache.org/jira/browse/SLING-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-358. --- Resolution: Fixed Committed in revision 644707, see the README.txt files under

[jira] Assigned: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-354: -- Assignee: Carsten Ziegeler Better way to define the node name for a newly created node

[jira] Closed: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-354. -- Resolution: Fixed Fix Version/s: 2.0.0 Better way to define the node name for a newly

[jira] Assigned: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-355: -- Assignee: Carsten Ziegeler Empty Request Parameters should be handled as not present

[jira] Created: (SLING-359) sling/sling.js path hidden by Sling console

sling/sling.js path hidden by Sling console --- Key: SLING-359 URL: https://issues.apache.org/jira/browse/SLING-359 Project: Sling Issue Type: Bug Reporter: Bertrand Delacretaz

Re: svn commit: r644699 - /incubator/sling/trunk/scripting/jst/src/main/java/org/apache/sling/scripting/jst/JstScriptEngine.java

On Fri, Apr 4, 2008 at 3:03 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 04.04.2008, 12:51 + schrieb [EMAIL PROTECTED]: +public final static String SLING_JS_PATH = /bundles/sling/sling.js; Didn't we say /system/sling.js or something like that instead of

[jira] Resolved: (SLING-359) sling/sling.js path hidden by Sling console

[ https://issues.apache.org/jira/browse/SLING-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-359. --- Resolution: Fixed In revision 644731, sling.js is served as /system/sling.js

Re: svn commit: r644699 - /incubator/sling/trunk/scripting/jst/src/main/java/org/apache/sling/scripting/jst/JstScriptEngine.java

Hi Bertrand, Am Freitag, den 04.04.2008, 16:36 +0200 schrieb Bertrand Delacretaz: On Fri, Apr 4, 2008 at 3:03 PM, Felix Meschberger [EMAIL PROTECTED] wrote: Am Freitag, den 04.04.2008, 12:51 + schrieb [EMAIL PROTECTED]: +public final static String SLING_JS_PATH =

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585597#action_12585597 ] Tobias Bocanegra commented on SLING-354: if you 'know' the node name, you can

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585598#action_12585598 ] Tobias Bocanegra commented on SLING-355: it depends on the use case. sometimes a

Re: Updates to the post servlet

I would like to fix SLING-354 and SLING-355 asap. What do you think about the proposed changes? see my comments in the issues. btw: i have another issue for the post servlet. i want to introduce the possibility to copy nodes. i'll come up with a jira issue later. -- toby

[jira] Commented: (SLING-354) Better way to define the node name for a newly created node

[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585608#action_12585608 ] Carsten Ziegeler commented on SLING-354: Sometimes, you can't make up the post url

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585611#action_12585611 ] Felix Meschberger commented on SLING-355: - I agree with you Tobias, yet what is the

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585618#action_12585618 ] Tobias Bocanegra commented on SLING-355: well, an empty string can also mean i see

Re: svn commit: r644750 - /incubator/sling/trunk/commons/json/src/main/java/org/apache/sling/commons/json/jcr/JsonItemWriter.java

why did you change this without a proper jira issue? i think that all clients that rely on this need to be informed. regards, toby On 4/4/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Author: cziegeler Date: Fri Apr 4 09:05:04 2008 New Revision: 644750 URL:

[jira] Commented: (SLING-359) sling/sling.js path hidden by Sling console

[ https://issues.apache.org/jira/browse/SLING-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585632#action_12585632 ] Tobias Bocanegra commented on SLING-359: the consensus seems to be to address this

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585638#action_12585638 ] Felix Meschberger commented on SLING-355: - what was the resolution on this? why is

[jira] Commented: (SLING-355) Empty Request Parameters should be handled as not present

[ https://issues.apache.org/jira/browse/SLING-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585645#action_12585645 ] Tobias Bocanegra commented on SLING-355: ok. consistency is better :-) removing all

Re: Checkin versionable nodes

so, why don't you introduce some kind of flag that will specify the required behaviour: checkin or not? regards, philipp On Fri, Apr 4, 2008 at 7:17 PM, Tobias Bocanegra [EMAIL PROTECTED] wrote: while working with Sing I noticed that nodes declaring mixin node type mix:versionable are not

Re: Checkin versionable nodes

Hi, Am Freitag, den 04.04.2008, 20:36 +0200 schrieb Philipp Koch: so, why don't you introduce some kind of flag that will specify the required behaviour: checkin or not? Same time - same thinking ;-) Regards Felix regards, philipp On Fri, Apr 4, 2008 at 7:17 PM, Tobias Bocanegra

Re: Checkin versionable nodes

Hi, Am Freitag, den 04.04.2008, 10:17 -0700 schrieb Tobias Bocanegra: while working with Sing I noticed that nodes declaring mixin node type mix:versionable are not checked in when the initial content is loaded. This is somehow unexpected to me and can lead to some trouble if you rely

Re: Clustering Sling

Hi, Am Freitag, den 04.04.2008, 11:53 -0700 schrieb Tobias Bocanegra: unless the bundles are not stored in the repository as well (which is not possible in the current version), you also need to deploy them on each instance, of course. There are two cases of bundles stored in the repository:

Re: Checkin versionable nodes

so, why don't you introduce some kind of flag that will specify the required behaviour: checkin or not? Same time - same thinking ;-) well, there is already such a flag: the jcr:isCheckedOut' property. so if the content has a 'jcr:isCheckedOut == true', then it should

Re: Checkin versionable nodes

Hi, Am Freitag, den 04.04.2008, 12:11 -0700 schrieb Tobias Bocanegra: so, why don't you introduce some kind of flag that will specify the required behaviour: checkin or not? Same time - same thinking ;-) well, there is already such a flag: the jcr:isCheckedOut'

[jira] Commented: (SLING-351) Use uppercase Sling in sling.js

[ https://issues.apache.org/jira/browse/SLING-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585716#action_12585716 ] Felix Meschberger commented on SLING-351: - Apart from a minor error:

Re: /sling/sling.js path hidden by OSGi management console

Hi, Am Donnerstag, den 03.04.2008, 12:00 +0200 schrieb Alexander Klimetschek: Am 03.04.2008 um 10:06 schrieb Bertrand Delacretaz: My larger concern is that those resources, served by bundles, are not discoverable. What I love when working with a JCR repository (like on a unixish system)

Re: Servlet registration acrobatics

Hi Vidal, Am Freitag, den 04.04.2008, 11:26 +0200 schrieb Vidar Ramdal: On Wed, Apr 2, 2008 at 4:57 PM, Vidar Ramdal [EMAIL PROTECTED] wrote: Created https://issues.apache.org/jira/browse/SLING-352 Any possibility for incorporating this in 1.0? Sorry for not answering earlier, I was

Re: Servlet registration acrobatics

Hi Betrand Am Mittwoch, den 02.04.2008, 09:47 +0200 schrieb Bertrand Delacretaz: On Tue, Apr 1, 2008 at 9:23 PM, Felix Meschberger [EMAIL PROTECTED] wrote: ...maybe an API call such as boolean canHandle(SlingHttpServletRequest) in an interface, which a servlet may implement.

[jira] Commented: (SLING-359) sling/sling.js path hidden by Sling console

[ https://issues.apache.org/jira/browse/SLING-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585730#action_12585730 ] Felix Meschberger commented on SLING-359: - Currently the docroot mapping is not

[jira] Created: (SLING-360) Relocate Sling Console

Relocate Sling Console -- Key: SLING-360 URL: https://issues.apache.org/jira/browse/SLING-360 Project: Sling Issue Type: Improvement Components: Console Reporter: Felix Meschberger

[jira] Issue Comment Edited: (SLING-359) sling/sling.js path hidden by Sling console

[ https://issues.apache.org/jira/browse/SLING-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585730#action_12585730 ] fmeschbe edited comment on SLING-359 at 4/4/08 1:13 PM: -

[jira] Commented: (SLING-356) Create separate project for the BundleResourceProvider

[ https://issues.apache.org/jira/browse/SLING-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585765#action_12585765 ] Felix Meschberger commented on SLING-356: - Removed BundleResourceProvider from

[jira] Commented: (SLING-356) Create separate project for the BundleResourceProvider

[ https://issues.apache.org/jira/browse/SLING-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585766#action_12585766 ] Felix Meschberger commented on SLING-356: - Keeping this issue open until the new

[jira] Created: (SLING-361) The sling/sample module fails to compile JSP scripts when run in a reactor build

The sling/sample module fails to compile JSP scripts when run in a reactor build Key: SLING-361 URL: https://issues.apache.org/jira/browse/SLING-361 Project: Sling

[jira] Commented: (SLING-361) The sling/sample module fails to compile JSP scripts when run in a reactor build

[ https://issues.apache.org/jira/browse/SLING-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585777#action_12585777 ] Felix Meschberger commented on SLING-361: - For the moment I comment the sling/sample

[jira] Closed: (SLING-362) JspC plugin should fail on error and support overwriting the output

[ https://issues.apache.org/jira/browse/SLING-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-362. --- Resolution: Fixed Fixed in Rev. 644941 JspC plugin should fail on error and support

[jira] Commented: (SLING-357) Support simple path mappings for bundle provided resources

[ https://issues.apache.org/jira/browse/SLING-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585792#action_12585792 ] Felix Meschberger commented on SLING-357: - Implemented first step (bang separator)

[jira] Created: (SLING-363) Add support for ResourceBundle base names

Add support for ResourceBundle base names - Key: SLING-363 URL: https://issues.apache.org/jira/browse/SLING-363 Project: Sling Issue Type: New Feature Components: Core Reporter:

[jira] Created: (SLING-364) I18N: Apply ResourceResolver.getSearchPath() to prioritized messages with the same key

I18N: Apply ResourceResolver.getSearchPath() to prioritized messages with the same key -- Key: SLING-364 URL: https://issues.apache.org/jira/browse/SLING-364

[jira] Closed: (SLING-364) I18N: Apply ResourceResolver.getSearchPath() to prioritized messages with the same key

[ https://issues.apache.org/jira/browse/SLING-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-364. --- Resolution: Fixed Closing this issue after committing the fix. See Subversion Commits for

[jira] Commented: (SLING-363) Add support for ResourceBundle base names

[ https://issues.apache.org/jira/browse/SLING-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12585815#action_12585815 ] Felix Meschberger commented on SLING-363: - Committed the extensions. See Subversion

[jira] Closed: (SLING-363) Add support for ResourceBundle base names

[ https://issues.apache.org/jira/browse/SLING-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger closed SLING-363. --- Resolution: Fixed Updated the documentation on the site. Thus closing this issue. Add