ResourceProvider registration issues: better info on duplicate, prevent loss on
registration
Key: SLING-911
URL: https://issues.apache.org/jira/browse/SLING-911
[
https://issues.apache.org/jira/browse/SLING-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-911.
-
Resolution: Fixed
In Rev. 761559 applied a synchronization fix to solve this issue:
* reg
On a fresh checkout, I currently get integration test failures
(org.apache.sling.launchpad.webapp.integrationtest.*):
Server does not seem to be ready, after 6 msec, got the following
119
Exceptions:org.apache.sling.commons.testing.integration.HttpStatusCodeException:
Expected status code 302
Hi Vidar,
this is related to a property change shortly before the Felix Framework
1.6 release candidate was cut. IIRC the latest Framework 1.5.0-SNAPSHOT
already supports this new property.
The result is, that the framework remains in start level 1 and no Sling
bundles are started and hence the t
Hi Daniel,
Posting to a resource with a trailing /* yields a StarResource of
default resource type "sling:syntheticStarResource". If you post to a
non-existing resource with a trailing slash / (which is recommended
here), a NonExistingResource with resource type "sling:nonexisting" is
assumed.
So
On Fri, Apr 3, 2009 at 10:35 AM, Felix Meschberger wrote:
> See also SLING-905 [1].
Ah, thanks, I had missed that issue. A Felix upgrade did the trick.
--
Vidar S. Ramdal - http://www.idium.no
Akersgata 16, N-0158 Oslo, Norway
+47 21 531941, ext 2070
Hi all,
I am running Sling under jBoss and I am not able to keep the server
alive for more than 10mn (30s when using a webdav client) because I
get "OutOfMemoryError: PermGen space" errors, even tho the max heap
size is set to be at 2Go.
I searched through the mailing-list archives but the only r
Hi Mike,
Mike Müller schrieb:
> Hi all,
>
> First of all, I would like to thank all of you for the big efforts to enhance
> and refine sling step by step. I'm watching the project since a few months
> for now and tested sling in a few simple projects - and it really is very
> easy to use it ri
Hi Claude,
raising the heap size does not help here, since this does not
(generally) enlarge the PermGen space. The PermGen space is used amongst
other things (very old objects) to store the class objects. If this
space fills up, the VM has lost ...
So, provided you are running a Sun VM, you migh
Hi,
> Exciting stuff for an old xslt head like myself.
Yeap, XST is still the best option in a lot of situations.
> Just wondering, if the xpl
> file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
> the .html extension in this example to the script?
> I would have guessed /
[
https://issues.apache.org/jira/browse/SLING-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695312#action_12695312
]
Alexander Klimetschek commented on SLING-909:
-
But at least the javadoc has to b
>> > Just wondering, if the xpl
>> > file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
>> > the .html extension in this example to the script?
>> > I would have guessed /apps/xproc/sling/servlet/default/html.xpl ..
>>
>> Because of resource type is "xproc", you have:
>>
>> /
Hi
2009/4/3 Juan José Vázquez Delgado
> > Just wondering, if the xpl
> > file is at /apps/xproc/xproc.xpl, what tells sling that it should resolve
> > the .html extension in this example to the script?
> > I would have guessed /apps/xproc/sling/servlet/default/html.xpl ..
>
> Because of resource
On Fri, Apr 3, 2009 at 8:20 AM, Felix Meschberger wrote:
> Do we want to keep the ResourceResolver.resolve(String path) method
> return null if the reource cannot be found (backwards compatible case)
> or do we want to have the method return NonExistingResource (consistency
> case).
As mentioned
On Fri, Apr 3, 2009 at 8:20 AM, Felix Meschberger wrote:
> [...]
> Do we want to keep the ResourceResolver.resolve(String path) method
> return null if the reource cannot be found (backwards compatible case)
> or do we want to have the method return NonExistingResource (consistency
> case).
If I
On Fri, Apr 3, 2009 at 1:34 PM, Vidar Ramdal wrote:
> If I can disregard the points of backwards compatibility and
> documentation for a second, I'd say: I've allways regarded
> NonExistingResource as something of a hack, so I wouldn't mind trying
> to avoid it as much as possible. A null returned
Hi Max,
This option does not appear in my VM's help (java -X) but I will give it a try!
By the way, do you know where I can find what is the available context
in a script, beyond "currentNode"?
Thx,
Claude
On Fri, Apr 3, 2009 at 11:22 AM, Felix Meschberger wrote:
> Hi Claude,
>
> raising the
Hi,
Bertrand Delacretaz schrieb:
> Hi,
>
> 2009/4/1 Juan José Vázquez Delgado :
>> Bertrand said:
>>> SLING-893 Pipeline support - still in the whiteboard, right? I'm going
>>> to test it today.
>> As discussed in [1], pipeline support stuff has been already saved in
>> contrib [2]. I´m going to
Hi Claude,
Claude Vedovini schrieb:
> This option does not appear in my VM's help (java -X) but I will give it a
> try!
Its an extended option, which is so extended, that it does not even
appear on -X ;-)
> By the way, do you know where I can find what is the available context
> in a script, be
Hi,
Alexander Klimetschek schrieb:
> On Fri, Apr 3, 2009 at 1:34 PM, Vidar Ramdal wrote:
>> If I can disregard the points of backwards compatibility and
>> documentation for a second, I'd say: I've allways regarded
>> NonExistingResource as something of a hack, so I wouldn't mind trying
>> to avo
[
https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-736.
---
Looks good, I think we can close this again, right ?
> Ensure getPathInfo returns correct (expect
[
https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695357#action_12695357
]
Felix Meschberger edited comment on SLING-736 at 4/3/09 5:11 AM:
-
[
https://issues.apache.org/jira/browse/SLING-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695361#action_12695361
]
Juan Jose Vazquez Delgado commented on SLING-736:
-
Right, I think it´s fixed
On Fri, Apr 3, 2009 at 1:53 PM, Felix Meschberger wrote:
> I have created a documentation page at [1] which should shortly appear
> on our site (follow Development -> Integrating Scripting Languages ->
> XSLT ...)
Thanks! Just added a note that the xproc module uses the Cocoon 3
pipeline engine.
> I have created a documentation page at [1] which should shortly appear
> on our site (follow Development -> Integrating Scripting Languages ->
> XSLT ...)
>
> This page may be edited directly in the SLINGxSITE wiki to update the site.
Thanks Felix. I´ll work at it soon.
Juanjo.
> Claude Vedovini schrieb:
>> This option does not appear in my VM's help (java -X) but I will give it a
>> try!
>
> Its an extended option, which is so extended, that it does not even
> appear on -X ;-)
Hence the double X I guess...
It seems to be working fine now (no failure since 30min) but I
>> On Fri, Apr 3, 2009 at 1:34 PM, Vidar Ramdal wrote:
>>> If I can disregard the points of backwards compatibility and
>>> documentation for a second, I'd say: I've allways regarded
>>> NonExistingResource as something of a hack, so I wouldn't mind trying
>>> to avoid it as much as possible. A nu
Hi Felix
> First of all: We are perfectly aware of this situation, but fail to be
> able to really cope with it in the sense of updating all docs, due to
> overfilled time tables (you know the problem ;-) ).
yes, you're totally right, I know exactly the problem :-)
> One thing you could do, exce
28 matches
Mail list logo
