[
https://issues.apache.org/jira/browse/SLING-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572826#action_12572826
]
Bertrand Delacretaz commented on SLING-281:
---
I agree with Thierry that the current
[
https://issues.apache.org/jira/browse/SLING-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572839#action_12572839
]
Felix Meschberger commented on SLING-280:
-
Just a slight remark on the syntax: You
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572847#action_12572847
]
Bertrand Delacretaz commented on SLING-273:
---
Wouldn't it be better to fail more
[
https://issues.apache.org/jira/browse/SLING-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572843#action_12572843
]
Felix Meschberger commented on SLING-280:
-
Sounds good.
ujax post serlvet should
[
https://issues.apache.org/jira/browse/SLING-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572918#action_12572918
]
Felix Meschberger commented on SLING-278:
-
In Rev. 631604:
* Added
[
https://issues.apache.org/jira/browse/SLING-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-278.
---
Resolution: Fixed
Everything is in place and works. So I close this issue.
Add Resource
[
https://issues.apache.org/jira/browse/SLING-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572915#action_12572915
]
Felix Meschberger commented on SLING-278:
-
In Rev. 631601:
*
This functionality is now implemented as of Rev. 631604.
Have fun !
Regards
Felix
Am Donnerstag, den 07.02.2008, 09:17 +0100 schrieb Tobias Bocanegra:
sounds good!
On 2/7/08, Felix Meschberger [EMAIL PROTECTED] wrote:
Hi all,
I think this idea is certainly worth considering, though
[
https://issues.apache.org/jira/browse/SLING-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572911#action_12572911
]
Felix Meschberger commented on SLING-278:
-
Extended the Sling API with the new
[
https://issues.apache.org/jira/browse/SLING-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572936#action_12572936
]
Carsten Ziegeler commented on SLING-282:
I think we should remove resource.node
Hi,
Am Mittwoch, den 27.02.2008, 07:33 -0800 schrieb Carsten Ziegeler
(JIRA):
I think we should remove resource.node completly, it causes too many
problems.
The proper way is to use currentNode.
+1, and as this has been discussed before, I think we just should go
ahead, create an issue and
On Wed, Feb 27, 2008 at 4:46 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
... I am confused. We decided to provide JavaScript-like API, that is JCR
node properties are properties of the JavaScript Node object, thus the
sling:resourceType property would be accessed as
Remove resource.node for scripting
--
Key: SLING-283
URL: https://issues.apache.org/jira/browse/SLING-283
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Carsten
Felix Meschberger schrieb:
Hi,
Am Mittwoch, den 27.02.2008, 07:33 -0800 schrieb Carsten Ziegeler
(JIRA):
I think we should remove resource.node completly, it causes too many problems.
The proper way is to use currentNode.
+1, and as this has been discussed before, I think we just should go
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572952#action_12572952
]
Felix Meschberger commented on SLING-273:
-
I tned to agree with Bertrand that
[
https://issues.apache.org/jira/browse/SLING-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572949#action_12572949
]
Michael Marth commented on SLING-282:
-
I am not sure if (or how much of) currentNode is
[
https://issues.apache.org/jira/browse/SLING-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572958#action_12572958
]
Michael Marth commented on SLING-282:
-
this might be related (regarding collections
[
https://issues.apache.org/jira/browse/SLING-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572962#action_12572962
]
Tobias Bocanegra commented on SLING-280:
great. i will provide a patch
ujax post
[
https://issues.apache.org/jira/browse/SLING-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-279:
---
Assignee: Carsten Ziegeler
Remaining Estimate: 0h
Original Estimate: 0h
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572973#action_12572973
]
Tobias Bocanegra commented on SLING-273:
well i agree in general. but in case of the
On Wed, Feb 27, 2008 at 5:57 PM, Tobias Bocanegra (JIRA)
[EMAIL PROTECTED] wrote:
...well i agree in general. but in case of the delete, there is no error
thrown if the element does not exist.
so imo a namespace exception of a missing prefix is comparable to the item
not found.
eg:
...well i agree in general. but in case of the delete, there is no error
thrown if the element does not exist.
so imo a namespace exception of a missing prefix is comparable to the item
not found.
eg: deleting /foo/bar/not_exsiting
vs: deleting /foo/bar/my:not_existing (if
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12572992#action_12572992
]
Tobias Bocanegra commented on SLING-273:
the servlet should not swallow errors that
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-273:
---
Attachment: ujax_error_fix.r631660.patch
new patch that just swallows namespace exception on
thanks. i'll take a look at it today :-)
regards, toby
On 2/27/08, Felix Meschberger [EMAIL PROTECTED] wrote:
This functionality is now implemented as of Rev. 631604.
Have fun !
Regards
Felix
Am Donnerstag, den 07.02.2008, 09:17 +0100 schrieb Tobias Bocanegra:
sounds good!
On
[
https://issues.apache.org/jira/browse/SLING-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-279.
--
Resolution: Fixed
ServiceLocator clean up
---
Key:
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573022#action_12573022
]
Bertrand Delacretaz commented on SLING-273:
---
Ok, agree about ignoring errors for
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573035#action_12573035
]
Felix Meschberger commented on SLING-273:
-
But we should test that important errors
[
https://issues.apache.org/jira/browse/SLING-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-273.
-
Resolution: Fixed
Fix Version/s: 2.0.0
Applied second path in Rev. 631682.
Please
[
https://issues.apache.org/jira/browse/SLING-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra closed SLING-244.
--
thanks.
ujax post servlet should allow relative moves
[
https://issues.apache.org/jira/browse/SLING-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra closed SLING-195.
--
thanks.
use system view format for XML resource loader
Hi,
Am Mittwoch, den 27.02.2008, 09:31 -0800 schrieb Carsten Ziegeler
(JIRA):
A script gets a service locator in the form of the sling script helper passed
into. Currently this locator is
using the bundle context of the scripting resolver bundle to resolve services.
The bundle context of the
ujax post servlet should silently replace existing move targets
---
Key: SLING-285
URL: https://issues.apache.org/jira/browse/SLING-285
Project: Sling
Issue Type: Bug
[
https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573069#action_12573069
]
Felix Meschberger commented on SLING-285:
-
Hmm, I think failure is ok if the target
[
https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-285:
---
Attachment: ujax_move_fix.r631699.patch
fixes the replace.
ujax post servlet should
[
https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12573076#action_12573076
]
Tobias Bocanegra commented on SLING-285:
maybe this can be solved using a flag:
Hi all,
The sling/servlet-resovler module, which manages resolution of serlvets
and scripts to handle requests for resources, also contains a
DefaultServlet which partially implements the same functionality as the
default servlets in the sling/servlets-default module.
The problem is, that we
On Wed, Feb 27, 2008 at 11:06 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
... I suggest, we drop the DefaultServlet from the sling/servlet-resolver
module entirely and have requests fail, if the DefaultServlet would have
been used
+1
-Bertrand
On Wed, Feb 27, 2008 at 8:16 PM, Felix Meschberger
[EMAIL PROTECTED] wrote:
... I think, we can safely define this reference optional as in:
@scr.reference cardinality=0..1 policy=dynamic...
It's probably ok in this case, but please, if someone implements this,
make sure to add clear log
Hi,
Am Mittwoch, den 27.02.2008, 23:12 +0100 schrieb Bertrand Delacretaz:
On Wed, Feb 27, 2008 at 8:16 PM, Felix Meschberger
[EMAIL PROTECTED] wrote:
... I think, we can safely define this reference optional as in:
@scr.reference cardinality=0..1 policy=dynamic...
It's probably ok
Use ServletContext to resolve content type of uploaded file
---
Key: SLING-286
URL: https://issues.apache.org/jira/browse/SLING-286
Project: Sling
Issue Type: Bug
Reporter:
[
https://issues.apache.org/jira/browse/SLING-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-286:
Component/s: ujax
Use ServletContext to resolve content type of uploaded file
Modify DefaultServlet of the servlet resolver bundle to send failure status
---
Key: SLING-287
URL: https://issues.apache.org/jira/browse/SLING-287
Project: Sling
Issue
[
https://issues.apache.org/jira/browse/SLING-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-258:
Component/s: (was: Launchpad)
ujax
Fix Version/s: 2.0.0
[
https://issues.apache.org/jira/browse/SLING-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-241:
---
Assignee: Felix Meschberger
ujax.js and related test code missing from the launchpad
[
https://issues.apache.org/jira/browse/SLING-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-241:
Component/s: (was: Launchpad)
ujax
Fix Version/s: 2.0.0
[
https://issues.apache.org/jira/browse/SLING-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-198.
---
Resolution: Fixed
This can be closed for now.
Extend ResourceResolver to make it more
[
https://issues.apache.org/jira/browse/SLING-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-285:
---
Attachment: (was: ujax_move_fix.r631699.patch)
ujax post servlet should silently replace
[
https://issues.apache.org/jira/browse/SLING-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bocanegra updated SLING-288:
---
Attachment: content_length_fix.r631795.patch
patch provides an extension to the resource
Felix Meschberger wrote:
Hi,
Am Mittwoch, den 27.02.2008, 23:12 +0100 schrieb Bertrand Delacretaz:
On Wed, Feb 27, 2008 at 8:16 PM, Felix Meschberger
[EMAIL PROTECTED] wrote:
... I think, we can safely define this reference optional as in:
@scr.reference cardinality=0..1
Bertrand Delacretaz wrote
On Wed, Feb 27, 2008 at 11:06 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
... I suggest, we drop the DefaultServlet from the sling/servlet-resolver
module entirely and have requests fail, if the DefaultServlet would have
been used
+1
-Bertrand
+1
Felix Meschberger wrote:
Hi,
Am Mittwoch, den 27.02.2008, 09:31 -0800 schrieb Carsten Ziegeler
(JIRA):
A script gets a service locator in the form of the sling script helper passed
into. Currently this locator is
using the bundle context of the scripting resolver bundle to resolve services.
On Thu, Feb 28, 2008 at 8:23 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... I agree that we either should make the reference dynamic or use the
servlet context. I would opt for using the servlet context
+1, I didn't realize the servlet context uses the mime type service,
that's fine of
53 matches
Mail list logo
