: Philipp Koch
Priority: Blocker
We already had this problem for pretty big event/job queues once (a month ago
or so. could not find a jira issue) that the job in the queue got purged
because the "job acknowledge" timed out for that job (by default the job/event
is purg
are you using https connection?
regards,
philipp
On Thu, Apr 16, 2009 at 2:31 PM, Vidar Ramdal wrote:
> 2009/4/6 Bertrand Delacretaz :
>> Vidar's account has been created, used vramdal should have commit
>> access on Sling now.
>>
>> Vidar, note that your first commit message needs to be moderat
[
https://issues.apache.org/jira/browse/SLING-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch updated SLING-661:
---
Attachment: SLING-661.patch
> vanityPath nodetype should be defined as mi
Reporter: Philipp Koch
the vanityPath nodetype definition is wrong (the description right...)
instead of:
//-
// Mixin node type for defining vanity resource path.
[sling:VanityPath]
- sling:vanityPath (string
[
https://issues.apache.org/jira/browse/SLING-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch closed SLING-423.
--
Resolution: Fixed
works fine. thanks!
> TimedJobHandler: error is thrown while executing timed
[
https://issues.apache.org/jira/browse/SLING-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch updated SLING-423:
---
Attachment: event.patch
Attached a patch that solves the above described problem.
> TimedJobHand
: Event
Reporter: Philipp Koch
the eventing resp. event processing works but the post processing (cleaning up)
the persisted event (node) fails:
1. the timedjobhandler creates a node of type slingevent:TimedEvent. the node
name got created by cancatenating the topicId and the jobid.
2
[
https://issues.apache.org/jira/browse/SLING-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589457#action_12589457
]
Philipp Koch commented on SLING-311:
the update functionality is very importan
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 a
i would opt for Option 1: /libs/dojo
regards,
philipp
On Fri, Mar 14, 2008 at 2:34 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> As of SLING-302 I created an extensions/dojo bundle which provides the
> Dojo Toolkit. Currently the dojo, dojox and dijit hierarchies are at the
>
hi,
this is something i already missed and i think could be useful in apps
that use the script support for executing kind of business logic (e.g.
workflow, forms validation, rules engine) which of course would expect
a return value.
regards,
philipp
On 3/5/08, Carsten Ziegeler <[EMAIL PROTECTED]>
[
https://issues.apache.org/jira/browse/SLING-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch updated SLING-307:
---
Attachment: queryservlet.patch
> QueryServlet
>
>
> Ke
QueryServlet
Key: SLING-307
URL: https://issues.apache.org/jira/browse/SLING-307
Project: Sling
Issue Type: New Feature
Components: Default Servlets
Reporter: Philipp Koch
it would be nice to have a way
> just keep in mind, that the scripts must be executed with the correct
> (jcr) session. the jobs that are executed by the event handling might
> to all run as 'admin'.
where is the difference? you have to pass the correct session in both
usecases, or did i miss something?
regards,
philipp
On 2/1
> (2) I would really like to table the sling API discussions for a while
> and let us all gather some experience with what we have before we
> we start modifying the API. From my personal perspective the
> constant change in the sling API is the biggest problem for the
> few early adopters we
[
https://issues.apache.org/jira/browse/SLING-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567021#action_12567021
]
Philipp Koch commented on SLING-239:
theh post url looks like this:
http://10.0.
[
https://issues.apache.org/jira/browse/SLING-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567013#action_12567013
]
Philipp Koch commented on SLING-239:
>I don't think, that this fix i
[
https://issues.apache.org/jira/browse/SLING-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch updated SLING-239:
---
Attachment: ujax_delete.patch
attached patch which solves the problem.
btw. all tests passed after
Affects Versions: 2.0.0
Reporter: Philipp Koch
ujax:delete /a/b/c
deletes /a/b/c
creates /a/b/c again
because the changelog is not respected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
that means that the PathResolver.pathToURL(Resource res) will be
replaced by ResourceResolver.map(String path)?
the current pathToUrl method is currently useless because the path to
url resolving only works for a given resource eg. /a/b/c but not for a
path like /a/b/c.gif (also addresses /a/b/c bu
i agree with tobi and still wonder why there are still two code bases
(sling and launchpad) for many servlets which do almost the same...
regards,
philipp
On 1/23/08, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> hi,
> there is a o.a.s.launchpad.LaunchpadDefaultServlet and a
> o.a.s.servlet.resolv
hi,
i like the current "json node export" format since it seems to me more
natural (in respect to jcr).
regards,
philipp
On 1/22/08, Peter Svensson <[EMAIL PROTECTED]> wrote:
> On Jan 22, 2008 10:08 AM, Bertrand Delacretaz <[EMAIL PROTECTED]>
> wrote:
>
> > Hi,
> >
> > (renaming the thread to att
: Sling
Issue Type: Bug
Components: Resource
Reporter: Philipp Koch
Priority: Critical
the adaptTo method returns currently the value set in the objectContentManager
field. this field might not be initialized (in most cases) resp. set to null.
the below
> /mynode.0.json -> returns the node and its properties
> /mynode.1.json -> returns the node, it properties and the child nodes
> and their properties
> ...
> /mynode.infinity.json -> returns the entire subtree.
>
> and i suggest to treat the '0' case as default.
finally convinced ;-). this all mak
i completely agree with carsten (as i have already written in an earlier post).
regards,
philipp
On 1/9/08, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Felix Meschberger wrote:
> > The problem with defaulting to full recursive export (which is what you
> > propose by omitting the selector), is
you have an url "/a/b/c.-1.json" ? Not sure, whether is nice :-)
>
> Regards
> Felix
>
> Am Mittwoch, den 09.01.2008, 15:45 +0100 schrieb Philipp Koch:
> > >...requesting /a/b/c.all.json would return the subtree rooted at
> > > node c to be dumped as JSON.
elix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Am Mittwoch, den 09.01.2008, 11:03 +0100 schrieb Carsten Ziegeler:
> > Bertrand Delacretaz wrote:
> > > On Jan 9, 2008 10:42 AM, Philipp Koch <[EMAIL PROTECTED]> wrote:
> > >
> > >> ...my pro
wrote:
> On Jan 9, 2008 10:42 AM, Philipp Koch <[EMAIL PROTECTED]> wrote:
>
> > ...my proposal:
> > full recursive mode should be default. if you would like to specify
> > the recursion depth one could e.g. specify a request parameter that
> > specifies the dept
hi,
currently the DefaultServlet handles the json content "export". it
exports only the current node and its properties. i am not sure if
this default behaviour is desirable and would expect that the default
behaviour would be so that the json exporter would recursively export
the current node and
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 Scriptabl
[
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 supp
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
> request.getServiceLocator().getService(ServletContext.class);
and what about microsling?
regards, philipp
On 12/12/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Felix Meschberger wrote:
> > Hi Betrand,
> >
> > Am Mittwoch, den 12.12.2007, 13:49 +0100 schrieb Bertrand Delacretaz:
> >> Hi,
[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540201
]
Philipp Koch commented on SLING-96:
---
well i missed to update the modified node types in my repo. this was the reason
[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540199
]
Philipp Koch commented on SLING-96:
---
even if i create anew timed event i get following exception which is thrown
[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540198
]
Philipp Koch commented on SLING-96:
---
i created a new timed event. then i updated the timed event. following error
[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540171
]
Philipp Koch commented on SLING-96:
---
>I guess that your use case is to have timed events that are not schedu
[
https://issues.apache.org/jira/browse/SLING-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540161
]
Philipp Koch commented on SLING-96:
---
when fireing an event with the same id (previous event got processed) i get
[
https://issues.apache.org/jira/browse/SLING-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch closed SLING-95.
-
works. thanks for fixing the issues!
> timed events by date do not w
Project: Sling
Issue Type: Bug
Components: Event
Reporter: Philipp Koch
Priority: Minor
the persisted timed events keep staying in the repository also after being
executed/fired successfully. this is from my point of view not correct. the
[
https://issues.apache.org/jira/browse/SLING-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Koch updated SLING-95:
--
Attachment: SLING-95.patch
patch that solves the issue (at least for my use case)
> timed events
timed events by date do not work
Key: SLING-95
URL: https://issues.apache.org/jira/browse/SLING-95
Project: Sling
Issue Type: Bug
Components: Event
Reporter: Philipp Koch
there are 3
is another story and if we could use the webdav stuff
(jackrabbit) for that which works really well and supports all the
http 1.1 stuff, so why don't we use that?
regards, philipp
On 10/19/07, Philipp Koch <[EMAIL PROTECTED]> wrote:
> the way how the current "big" sling does s
the way how the current "big" sling does spool static resources out of
the repository is very nice and should somehow (as suggested by felix
(kind of spool servlet) added to the micro sling "product" as well.
regards,
philipp
On 10/19/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi,
>
> At
> So I really think we need a comfortable way to include content in
> microsling scripts.
this makes sense since we could support for different scripting languages.
regards,
philipp
On 10/19/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> On 10/19/07, Felix Meschberger <[EMAIL PROTECTED]> wr
: Content
Reporter: Philipp Koch
the mappings cannot be resolved bacause of the wrong ocm mapping nodetype
configuration.
change:
@ocm.mapped jcrNodeType="sling:Content" .
to
@ocm.mapped jcrType="sling:Content" .
the wrong mapping configuration is applie
46 matches
Mail list logo
