Re: Not-sticky sessions with Sling?
Hi Lance, On Wed, Jan 18, 2017 at 11:21 PM, lancedolan wrote: > ...Bertrand, I'd feel selfish taking you up on your offer to build this for > me. > Yet I'd be a fool to not at least partner with you to get it done. Should we > correspond outside this mail list?... I understand you're probably looking at a different solution now but just wanted to clarify this: the Sling dev list would be the place to discuss such things, no need for off-list communications. -Bertrand
Re: Sling Model and Request Parameters
Hi, I now created https://issues.apache.org/jira/browse/SLING-6478 and attached a diff with the new code. Best regards Christophe On 19/01/17 09:43, "Christophe Jelger" wrote: Hi again, Thx for your answer: I understand why we don’t want to add that request parameter injector to the list of default injectors, but I haven’t yet found in the code where and how I should prevent that. Could anybody point me to the right piece of code I should check? Thanks, Christophe On 18/01/17 18:33, "Jason Bailey" wrote: As mentioned in the original thread. I think you would just need to create a JIRA and add your patch to that. As long as it was one of those non-default injectors I would appreciate it. Original thread: http://apache-sling.73963.n3.nabble.com/Sling-Model-and-Request-Parameters-tt4065648.html#a4065663 -Original Message- From: Christophe Jelger [mailto:jel...@adobe.com] Sent: Tuesday, January 17, 2017 5:35 AM To: users@sling.apache.org Subject: Re: Sling Model and Request Parameters Hi everyone, There was a discussion back on Oct 11, 2016 about an extra injector+annotation to inject request parameters into Sling models. I couldn’t find any JIRA issue about that, and I haven’t seen anything like that in the code so I don’t think this is currently in progress. I just joined the mailing list and I started developing with AEM + Sling recently, but I have quite some experience with Spring and think this would be a useful annotation, especially to be able to handle form submits with sling models. If there is still interest to have that annotation, I would be willing to take care of that: I already wrote the missing code and could already provide a diff or pull request. Best regards, Christophe
Re: Bad asset resource resolving
Hi Stefan I've explained myself rather poorly. I've dug into this and prepared a example package - which I've logged under SLING-6476 to better illustrate the issue I'm having. 2017-01-16 22:01 GMT+01:00 Stefan Seifert : > no, the basics of resource resolution have not change recently - a > resource with multiple dots in it's resource name (like > /content/sling.logo.png) should always be resolvable by this name. and it > works as expected when i reproduce the steps you describe (copy to > /content/sling.logo.png). > > i tested it with the current sling launchpad from trunk. > > stefan > > > >-Original Message- > >From: Bart Wulteputte [mailto:bart.wultepu...@gmail.com] > >Sent: Monday, January 16, 2017 1:44 PM > >To: users@sling.apache.org > >Subject: Bad asset resource resolving > > > >Hi all, > > > >It seems that the way assets are resolved has changed a little. When an > >asset contains an additional . (dot) it can't be resolved anymore to the > >actual asset resource. e.g. /content/my.asset.pdf resolves to > >/content/my.pdf rather than the expected path. > > > >As a simple test you can copy the sling-logo.png to > >/content/sling.logo.png. When now using the Sling Resolver Test - we see > >that resolving /content/sling.logo.png results in a non-existing resource > >with path /content/sling.png instead of the expected asset url. The > section > >after the first dot is now interpreted as a selector which didn't used to > >be the case for assets in the past. > > > >Was this intentionally changed or is this an actual bug? > > > >Best regards > > > >Bart >
Re: Sling Model and Request Parameters
Hi again, Thx for your answer: I understand why we don’t want to add that request parameter injector to the list of default injectors, but I haven’t yet found in the code where and how I should prevent that. Could anybody point me to the right piece of code I should check? Thanks, Christophe On 18/01/17 18:33, "Jason Bailey" wrote: As mentioned in the original thread. I think you would just need to create a JIRA and add your patch to that. As long as it was one of those non-default injectors I would appreciate it. Original thread: http://apache-sling.73963.n3.nabble.com/Sling-Model-and-Request-Parameters-tt4065648.html#a4065663 -Original Message- From: Christophe Jelger [mailto:jel...@adobe.com] Sent: Tuesday, January 17, 2017 5:35 AM To: users@sling.apache.org Subject: Re: Sling Model and Request Parameters Hi everyone, There was a discussion back on Oct 11, 2016 about an extra injector+annotation to inject request parameters into Sling models. I couldn’t find any JIRA issue about that, and I haven’t seen anything like that in the code so I don’t think this is currently in progress. I just joined the mailing list and I started developing with AEM + Sling recently, but I have quite some experience with Spring and think this would be a useful annotation, especially to be able to handle form submits with sling models. If there is still interest to have that annotation, I would be willing to take care of that: I already wrote the missing code and could already provide a diff or pull request. Best regards, Christophe
