Tobias Bocanegra wrote:
so a 'special' parameter would for example be:
sling:postMoveSrc ?
or sling:post:MoveSrc ?
sling:post:MoveSrc
this sounds weird, but ok for me :-)
Yepp, but it helps to avoid name clashes :)
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
> * The Ujax* classes in the sling/ujax module are renamed to Sling*
so your saying:
o.a.s.ujax.impl.UjaxPostServlet -> o.a.s.servlets.post.SlingPostServlet
o.a.s.ujax.impl.UjaxPostProcesser -> o.a.s.servlets.post.SlingPostProcessor
...
could this not be moved to the org.apache.sling.servlets.d
Hi,
Just want to note this in case it rings a bell with someone, haven't
investigated yet.
Sometimes, when installing a new bundle, either using the maven plugin
or via the html console, the bundle is not installed properly.
When that happens, the bundle is listed at the end of list at
http://lo
> > ... In addition, I also suggest to not limit this special casing to the GET
>
> > method. This would just create such a SyntheticStarResource for any
> > request ...
>
>
> We don't want a SyntheticStarResource for POST, do we? That might
> interfere with the way we handle POST to *, see S
[
https://issues.apache.org/jira/browse/SLING-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582722#action_12582722
]
Bertrand Delacretaz commented on SLING-344:
---
Implemented in revision 641876, leavi
Hi,
Am Donnerstag, den 27.03.2008, 16:35 +0100 schrieb Carsten Ziegeler:
> Hi,
>
> it seems to be that the HtmlResponse in the current ujax module is
> of use for implementing a html response in a servlet in general.
> As we have the Sling*Servlets in the api, what about moving this class
> ther
On Thu, Mar 27, 2008 at 4:35 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ... As we have the Sling*Servlets in the api, what about moving this class
> there as well?...
+1
-Bertrand
Hi,
it seems to be that the HtmlResponse in the current ujax module is
of use for implementing a html response in a servlet in general.
As we have the Sling*Servlets in the api, what about moving this class
there as well?
For now I have to add a dependency to ujax just to use this class which
s
On Thu, Mar 27, 2008 at 3:52 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ... The Sling Client Library is just a single file - ujax.js (or now
> sling.js). Of course we may create single module for that, but I am not
> sure, whether this is worth it
I agree that this doesn't require a
Felix Meschberger wrote:
Hi,
Am Donnerstag, den 27.03.2008, 15:35 +0100 schrieb Carsten Ziegeler:
Bertrand Delacretaz wrote:
On Thu, Mar 27, 2008 at 3:18 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
+1
+1 to the proposed changes as well, and I'd suggest using "sling
client library" as the
Hi,
Am Donnerstag, den 27.03.2008, 15:35 +0100 schrieb Carsten Ziegeler:
> Bertrand Delacretaz wrote:
> > On Thu, Mar 27, 2008 at 3:18 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> >> +1
> >
> > +1 to the proposed changes as well, and I'd suggest using "sling
> > client library" as the name f
Hi Felix,
On Thu, Mar 27, 2008 at 2:39 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> (1) The EmptyRangeIterator.next() method in the patch should throw
> a NoSuchElementException instead of returning null...
ok, I'll change that.
> (2) special casing issues...
I agree with the sugges
[
https://issues.apache.org/jira/browse/SLING-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-340.
---
Resolution: Fixed
Implemented in revision 641828.
The new jcr/default-rtp module prov
Bertrand Delacretaz wrote:
On Thu, Mar 27, 2008 at 3:18 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
+1
+1 to the proposed changes as well, and I'd suggest using "sling
client library" as the name for what was ujax, for use in docs, etc.
Hmm, I think if we use this in the docs, the module n
On Thu, Mar 27, 2008 at 3:18 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> +1
+1 to the proposed changes as well, and I'd suggest using "sling
client library" as the name for what was ujax, for use in docs, etc.
> ... And also I really would like to see the name "Catapult" being used
> somew
+1
And also I really would like to see the name "Catapult" being used
somewhere in Sling, I don't think it makes sense to use it here. So lets
keep it for something better...
Carsten
Felix Meschberger wrote:
Hi all,
Am Montag, den 10.03.2008, 15:51 +0100 schrieb Felix Meschberger:
Current
Hi all,
Am Montag, den 10.03.2008, 15:51 +0100 schrieb Felix Meschberger:
> Currently names used by Sling are prefixed with sling: with the
> exception of well known parameters of the ujax servlets. To get all
> these prefixes in line I suggest we change the prefix used by ujax
> parameters to sli
Hi Bertrand,
This basically makes sense. Yet, I have some comments:
(1) The EmptyRangeIterator.next() method in the patch should throw
a NoSuchElementException instead of returning null
(2) special casing issues...
Regarding the special casing: Your patch adds a check for GET method and
"/*.
Hi,
I am pleased to officially announce the first JCR community gathering
in Amsterdam on April 8th. This JCR meetup event is targeted to
everyone interested in the JCR standard and applications built using
JCR. All JCR users and developers are welcome to participate.
What: JCR community gath
19 matches
Mail list logo