[
https://issues.apache.org/jira/browse/SLING-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-199:
Fix Version/s: (was: 2.0.0)
Descheduling from initial release.
Implement Request
[
https://issues.apache.org/jira/browse/SLING-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-3:
--
Fix Version/s: (was: 2.0.0)
Descheduling from initial release.
This may be worked on as an
[
https://issues.apache.org/jira/browse/SLING-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-258:
Fix Version/s: (was: 2.0.0)
Descheduling from initial release.
This is not required
[
https://issues.apache.org/jira/browse/SLING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-154:
Priority: Blocker (was: Minor)
Raising priority to blocker, because IMHO we should be API
[
https://issues.apache.org/jira/browse/SLING-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-190:
---
Fix Version/s: (was: 2.0.1)
The Sling class of the launcher should verify minimum JDK
Provide properties of JCR Nodes underlying Resources as Map
---
Key: SLING-395
URL: https://issues.apache.org/jira/browse/SLING-395
Project: Sling
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/SLING-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12592967#action_12592967
]
Felix Meschberger commented on SLING-298:
-
I think it is worth it using a special
Hi,
On Mon, Apr 28, 2008 at 5:33 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...After re-reading this proposal and discussing it with David, also
considering any consequences with respect to backwards compatibility,
performance and usability, I would like to summarize, what we came up
Hi all,
I tried to create nodes with random names using Sling Post Servlet and
XHR, but I always receive responses with status code 200 and not 201
as expected. Also the Location header is missing in the response. Lars
pointed me to the discussion around this issues in [1]. But I'm
RepositoryAccessor cannot cast to Repository anymore
Key: SLING-396
URL: https://issues.apache.org/jira/browse/SLING-396
Project: Sling
Issue Type: Bug
Components: Repository
On Mon, Apr 28, 2008 at 5:25 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... I'm not 100% sure, but I don't think that this is caused by a change in
Sling. It might be caused by changes in the repository implementation you
use? Perhaps some other classes are missing in the global class
Hi all,
I tried to create nodes with random names using Sling Post Servlet and
XHR, but I always receive responses with status code 200 and not 201
as expected.
Yes, because currently the SlingPostServlet calls the HtmlResponse.send
method with a setStatus flag of false, thus the
[
https://issues.apache.org/jira/browse/SLING-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz closed SLING-282.
-
Resolution: Fixed
Works, closing
missing node functions in node wrapper
[
https://issues.apache.org/jira/browse/SLING-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593006#action_12593006
]
Tobias Bocanegra commented on SLING-298:
agreed.
+1 for using _charset_ and
Generate javascript wrapper methods from specific interfaces automatically
--
Key: SLING-397
URL: https://issues.apache.org/jira/browse/SLING-397
Project: Sling
Issue
Hi Felix,
Am 29.04.2008 um 10:55 schrieb Felix Meschberger:
Am Dienstag, den 29.04.2008, 10:17 +0200 schrieb Alexander Saar:
Hi all,
I tried to create nodes with random names using Sling Post Servlet
and
XHR, but I always receive responses with status code 200 and not 201
as expected.
Hi,
Am 29.04.2008 um 13:41 schrieb Tobias Bocanegra:
and there will be another request parameter
which allows to override the response code for special case handling
like hidden iframes in forms. This parameter could be named
sling:post:responseCodeOverride and the value could be the response
On Tue, Apr 29, 2008 at 3:47 PM, Alexander Saar
[EMAIL PROTECTED] wrote:
This could look as follows:
POST to /foo- 200 OK and a XHTML representation
POST to /foo.html - 200 OK and a XHTML representation
POST to /foo.xml- correct response codes
and there will be another request parameter
which allows to override the response code for special case handling
like hidden iframes in forms. This parameter could be named
sling:post:responseCodeOverride and the value could be the response
code that should be used. If the
[Patch] Separate bundle details page in sling web console
-
Key: SLING-398
URL: https://issues.apache.org/jira/browse/SLING-398
Project: Sling
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/SLING-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593022#action_12593022
]
Alexander Klimetschek commented on SLING-398:
-
And I forgot: to get the bundle
Hi,
I think we should move the default-rtp bundle from the jcr dir to the
samples. It's a nice little module which more servers as a sample.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
I'm wondering why we export the jackrabbit-api in our jcr.api?
The jcr api should imho not be tied to any jcr implementation.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
On Tue, Apr 29, 2008 at 4:47 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... I think we should move the default-rtp bundle from the jcr dir to the
samples. It's a nice little module which more servers as a sample
Agreed, but note that it is used by launchpad/app (which is itself
also kind
Bertrand Delacretaz wrote:
On Tue, Apr 29, 2008 at 4:47 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... I think we should move the default-rtp bundle from the jcr dir to the
samples. It's a nice little module which more servers as a sample
Agreed, but note that it is used by
[
https://issues.apache.org/jira/browse/SLING-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-397:
--
Attachment: SLING-397.patch
Patch that uses a different mechanism than initially
On Tue, Apr 29, 2008 at 4:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... For what is it used there?...
Integration tests only at the moment, which verify that the mechanism works.
But I suspect we'll use it for examples as well, once we finally create them ;-)
-Bertrand
Bertrand Delacretaz wrote:
On Tue, Apr 29, 2008 at 4:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
... For what is it used there?...
Integration tests only at the moment, which verify that the mechanism works.
:) Ok - I think we should move the integration tests to a separate
module as
On Tue, Apr 29, 2008 at 5:11 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...I think we should move the integration tests to a separate module
as ewll
As long as they run automatically and can also be run against a
separate Sling instance, I'm fine.
We'll have to find a way for bundles
Bertrand Delacretaz wrote:
On Tue, Apr 29, 2008 at 5:11 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...I think we should move the integration tests to a separate module
as ewll
As long as they run automatically and can also be run against a
separate Sling instance, I'm fine.
We'll
Hi,
I think our current directory is a little bit confusing for new users,
We have several top level dirs (like commons, extensions, osgi, sling)
which do not clearly indicate what they might contain.
I know this is a hot topic :) and we could debate for ages about it. I
think we should just
Remove useless launchpad.app bundle from launchpad.webapp
-
Key: SLING-399
URL: https://issues.apache.org/jira/browse/SLING-399
Project: Sling
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/SLING-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-399:
--
Attachment: SLING-399.patch
Will apply this patch when SVN write access is back
Carsten Ziegeler wrote:
So, wrapping up:
a) commons is a place for common code/bundles which is not directly
tied to Sling (but used by Sling)
I forgot to mention that all modules in commons use o.a.s.commons.* as
package names.
b) We move the stuff from the osgi dir to better places
c)
[
https://issues.apache.org/jira/browse/SLING-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12593043#action_12593043
]
Carsten Ziegeler commented on SLING-399:
I have a patch for this on my machine as
What about using extensions to specify the desired behaviour?
This could look as follows:
POST to /foo- 200 OK and a XHTML representation
POST to /foo.html - 200 OK and a XHTML representation
POST to /foo.xml- correct response codes and a
XML
Hi,
Am Dienstag, den 29.04.2008, 13:41 +0200 schrieb Tobias Bocanegra:
The Location header seems to in fact not be set for a content creation
request. I agree, that this is a bug in the SlingPostServlet. Could you
please create an issue for that one ? Thanks.
the location header is only
[
https://issues.apache.org/jira/browse/SLING-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-396.
---
Resolution: Fixed
Patch applied in revision 652267
RepositoryAccessor cannot cast
Hi,
Am Dienstag, den 29.04.2008, 15:47 +0200 schrieb Alexander Saar:
and there will be another request parameter
which allows to override the response code for special case handling
like hidden iframes in forms. This parameter could be named
sling:post:responseCodeOverride and the value
[
https://issues.apache.org/jira/browse/SLING-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-397.
---
Resolution: Fixed
Patch committed in revision 652268
Generate javascript wrapper
[
https://issues.apache.org/jira/browse/SLING-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-399.
---
Resolution: Fixed
Patch committed in revision 652270
Remove useless launchpad.app
[
https://issues.apache.org/jira/browse/SLING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-154.
---
Resolution: Fixed
SLING-397 should give access to all Node and Property methods, and
[
https://issues.apache.org/jira/browse/SLING-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reassigned SLING-383:
-
Assignee: Bertrand Delacretaz
Add simple JavaScript (Rhino) Wrappers for Version
43 matches
Mail list logo
