[jira] Updated: (SLING-142) Compact Syntax for ESP expressions in HTML attributes

[ https://issues.apache.org/jira/browse/SLING-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Trieloff updated SLING-142: Attachment: esp-compact-dollar-syntax.patch This patch implements the ${expr} syntax. The simple

[jira] Assigned: (SLING-142) Compact Syntax for ESP expressions in HTML attributes

[ https://issues.apache.org/jira/browse/SLING-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned SLING-142: --- Assignee: Felix Meschberger Compact Syntax for ESP expressions in HTML attributes

[jira] Commented: (SLING-142) Compact Syntax for ESP expressions in HTML attributes

[ https://issues.apache.org/jira/browse/SLING-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553618 ] Felix Meschberger commented on SLING-142: - Thanks for updating the patch. Will apply it shortly. Compact

[jira] Created: (SLING-144) multipart parameter support

multipart parameter support --- Key: SLING-144 URL: https://issues.apache.org/jira/browse/SLING-144 Project: Sling Issue Type: Improvement Components: microsling Reporter: Philipp Koch the

Handling multiple servlets for a resource type?

I'm wondering if we do something about the case where more than one servlet is able to process a specific resource type? For example, you have a bundle containing standard servlets for some resource types providing a default rendering. Then you want to provider for one of the resource types a

[jira] Updated: (SLING-144) multipart parameter support

[ https://issues.apache.org/jira/browse/SLING-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philipp Koch updated SLING-144: --- Attachment: multipart_param_support.patch multipart parameter support ---

Re: Handling multiple servlets for a resource type?

Hi, Am Donnerstag, den 20.12.2007, 11:39 +0100 schrieb Carsten Ziegeler: I'm wondering if we do something about the case where more than one servlet is able to process a specific resource type? For example, you have a bundle containing standard servlets for some resource types providing a

javascript: javax.jcr.Node vs. ScriptableNode

hi, i've been playing around with the javascript impl. (by using microsling) quite a while. it works well, but stumbled over the ScriptableNode object which you get by calling: var node = request.getResource().node; the javax.jcr.Node provides lots of methods which are not wrapped in the

Re: javascript: javax.jcr.Node vs. ScriptableNode

Hi, Am Donnerstag, den 20.12.2007, 11:57 +0100 schrieb Philipp Koch: i would nevertheless propose to drop the ScriptableNode impl because the sling resource also provides a default mapping which does basically what the ScriptableNode impl does. this mapped object can be retrieved by calling

[jira] Updated: (SLING-3) Use RequestProgressTracker to log request processing steps

[ https://issues.apache.org/jira/browse/SLING-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated SLING-3: -- Component/s: ServletResolver Scripting Resource

[jira] Commented: (SLING-53) Add request filter for method overwrite

[ https://issues.apache.org/jira/browse/SLING-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553645 ] Lars Trieloff commented on SLING-53: Just a quick note: Google uses a X-HTTP-Method-Override header to specify the

[jira] Created: (SLING-145) Apply same logic to servlet resolution as is used for script resolution

Apply same logic to servlet resolution as is used for script resolution --- Key: SLING-145 URL: https://issues.apache.org/jira/browse/SLING-145 Project: Sling Issue Type:

[jira] Commented: (SLING-53) Add request filter for method overwrite

[ https://issues.apache.org/jira/browse/SLING-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553647 ] Felix Meschberger commented on SLING-53: ... X-HTTP-Method-Override ... Absolutely. In fact the Abdera

[jira] Commented: (SLING-144) multipart parameter support

[ https://issues.apache.org/jira/browse/SLING-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553667 ] Bertrand Delacretaz commented on SLING-144: --- Thanks, I'll have a look right now. With the recent decision

[jira] Resolved: (SLING-144) multipart parameter support

[ https://issues.apache.org/jira/browse/SLING-144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-144. --- Resolution: Fixed Patch applied in revisions 605921 and 605922, thanks very much!

Re: javascript: javax.jcr.Node vs. ScriptableNode

Hi Philipp, the reason I contributed the ScriptableNode interface is that the exposure as a first-class Javascript object allows us to access often- used features of a node in a way that feels natural to Javascript programmers. This is not only using node.text instead of the more Java- ish

[jira] Closed: (SLING-142) Compact Syntax for ESP expressions in HTML attributes

[ https://issues.apache.org/jira/browse/SLING-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Trieloff closed SLING-142. --- Works fine, thanks. Compact Syntax for ESP expressions in HTML attributes

Re: javascript: javax.jcr.Node vs. ScriptableNode

Hi Felix, this sounds reasonable. We should introduce a similar two-stage wrapping for the request and response: - request.attributes - request.parameters - request.cookies - request.session this way you could express the default behavior of Sling with node.properties = request.parameters

Re: [VOTE] Community Roles and Processes

Hi, Am Donnerstag, den 20.12.2007, 09:47 +0200 schrieb Jukka Zitting: PPS. For special circumstances (e.g. GSoC students, temporary cross-project integration, etc.) it is good to reserve the option of granting someone commit access without (P)PMC membership, but as a general rule the proposed

[RESULT] [VOTE] Community Roles and Processes

Hi all, It is time to tally the vote for our Community Roles and Processes [1]. The vote gathered 6 +1 votes (all binding), no 0 votes and no -1 votes from: * Bertrand Delacretaz * Carsten Ziegeler * Karl Pauls * Felix Meschberger * Juan José Vázquez Delgado * Jukka Zitting

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is comparatively easy (i.e. does not require a recompile) (I like CRX's Repository

Re: µsling 2.0 requirements (was: [RT] Shall we merge microsling into Sling?)

Hi, Am Donnerstag, den 20.12.2007, 16:48 +0100 schrieb Michael Marth: Sounds great. This WebDAV module currently supports the Jackrabbit JCR repository, but Sling is meant to run with any JCR repository. OK, but can I add: switching the repository to another JCR repository is

Re: Error Handling in Sling

Guys, you might have lost me in this discussion, but may I ask anyway: We now have three orthogonal pieces in resolving a script: http method, requested mime type and response status code (plus script language). How do they get mixed in the script resolution process? Which script will be

POSTs and microjax

Hi, this has been discussed before, but without conclusion afaik, so I would like to start this discussion again: at the moment one can only use the microjax post servlet in an all-or-nothing way. This means that my app needs to decide: I either send POSTs to the microjax servlet and that's all