[jira] [Commented] (SLING-6511) SlingTemplateResource unable to handle missing localization for a language

2017-02-09 Thread Oliver Lietz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15860686#comment-15860686
 ] 

Oliver Lietz commented on SLING-6511:
-

bq. Now what might be missing is the content node called `test` in the 
`/content/geometrixx/en/jcr:content/par`.

Right, that's what I tried to say.

bq. Were you able to upload & install the Test.zip in the package manager, 
http://localhost:4502/crx/packmgr/index.jsp?

Yes, installed without errors. Can you check the package?

> SlingTemplateResource unable to handle missing localization for a language
> --
>
> Key: SLING-6511
> URL: https://issues.apache.org/jira/browse/SLING-6511
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Scripting Thymeleaf 1.0.0
>Reporter: Sajid Momin
>Assignee: Oliver Lietz
> Attachments: error.log, javassist-3.20.0-GA.jar, 
> org.apache.sling.scripting.thymeleaf-1.0.0.jar, Test.zip, 
> thymeleaf-i18n-error.log
>
>
> I am currently deploying Sling Thymeleaf HTML template processor to AEM 6.2.  
> In my attempt to use i18n in my template, I am receiving a null pointer 
> exception.  When the message resolver is looping through the localization of 
> the language, it's unable to skip the processing of the missing localization 
> file resulting in a null pointer.  The only way to fix the issue is to define 
> all localization resource bundle for the language in order to process the 
> template.  It would be nice for the message resolver to ignore the missing 
> localized language resource bundle and continue to the next.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Servlets Get version 2.1.22

2017-02-09 Thread Carsten Ziegeler 
+1

 

-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Sling is disregarding changes in filters

2017-02-09 Thread Andreas Schaefer Sr. 
Hi

I am working at a project (AEM 6.2) where the customer is used Portlets.

These are legacy portlets and have very long query strings. The previous
deployment used some features of the web server that hide that query string.

In AEM 6.0 I created a link rewriter / filter that took the query string, 
placed it
into the session and returned a query string with a reference to the session 
cache.
On the returning call (action / render) the query string was the re-applied to 
the
Servlet Request by wrapping the request and returning the new / old query 
string.

Now In AEM 6.2 that fails and I figured out that:

1) The ParameterSupport class is obtaining the values from the request in this 
method:

private ParameterMap getRequestParameterMapInternal() {
if (this.postParameterMap == null) {

(line 221 in org.apache.sling.engine 2.4.6)

2) AEM 6.2 does obtain the first parameter from the request on the 
HTTPAuthHandler.forceAuthentication()
and therefore fixes all the variables. This handler is called way before my 
filter and so any changes made
by this filter is disregarded.

I could circumvent that by intercepting the request for the 
“org.apache.sling.engine.impl.parameters.ParameterSupport”
attribute with which I was finally able to call the portlet.

From what I see the code is fine but the method:

public static ParameterSupport getInstance(HttpServletRequest request) {
Object instance = request.getAttribute(ATTR_NAME);
if (!(instance instanceof ParameterSupport)) {
instance = new ParameterSupport(request);
request.setAttribute(ATTR_NAME, instance);
}
return (ParameterSupport) instance;
}

Should also check if the Parameter Support instance is based off the same 
request and recreated it. Something like
this:

public static ParameterSupport getInstance(HttpServletRequest request) {
Object instance = request.getAttribute(ATTR_NAME);
if (!(instance instanceof ParameterSupport)) {
instance = new ParameterSupport(request);
request.setAttribute(ATTR_NAME, instance);
} else {
ParameterSupport found = (ParameterSupport) instance;
if(request != found.getServletRequest) {
instance = new ParameterSupport(request);
request.setAttribute(ATTR_NAME, instance);
}
return (ParameterSupport) instance;
}

Cheers - Andy Schaefer

[jira] [Assigned] (SLING-6506) Sling Log Tracer queries reports Plan that does not match Query statement

2017-02-09 Thread Chetan Mehrotra (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra reassigned SLING-6506:
--

Assignee: Chetan Mehrotra

> Sling Log Tracer queries reports Plan that does not match Query statement
> -
>
> Key: SLING-6506
> URL: https://issues.apache.org/jira/browse/SLING-6506
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Log Tracer 0.0.2
>Reporter: David Gonzalez
>Assignee: Chetan Mehrotra
> Fix For: Log Tracer 1.0.2
>
> Attachments: tracer-error-output.txt, tracer-error-screencap.png
>
>
> The Queries data set from Sling Log Tracer (1.0.2) may report the wrong Query 
> plan for the query.  
> {noformat}
> "query": "//*[jcr:contains(., 
> '\"/content/dam/we-retail/en/people/mens/men_1.jpg\"')]",
> "plan": "[nt:unstructured] as [a] /* 
> lucene:ntBaseLucene(/oak:index/ntBaseLucene) 
> dam:resolvedPath:/content/dam/we-retail/en/people/mens/men_1.jpg where 
> [a].[dam:resolvedPath] = '/content/dam/we-retail/en/people/mens/men_1.jpg' */"
> {noformat}
> Attached raw tracer output from Felix console.
> Explaining the query statement via Oak gives a different (and correct) plan.
> /cc [~chetanm]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6506) Sling Log Tracer queries reports Plan that does not match Query statement

2017-02-09 Thread Chetan Mehrotra (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chetan Mehrotra updated SLING-6506:
---
Fix Version/s: Log Tracer 1.0.2

> Sling Log Tracer queries reports Plan that does not match Query statement
> -
>
> Key: SLING-6506
> URL: https://issues.apache.org/jira/browse/SLING-6506
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Log Tracer 0.0.2
>Reporter: David Gonzalez
> Fix For: Log Tracer 1.0.2
>
> Attachments: tracer-error-output.txt, tracer-error-screencap.png
>
>
> The Queries data set from Sling Log Tracer (1.0.2) may report the wrong Query 
> plan for the query.  
> {noformat}
> "query": "//*[jcr:contains(., 
> '\"/content/dam/we-retail/en/people/mens/men_1.jpg\"')]",
> "plan": "[nt:unstructured] as [a] /* 
> lucene:ntBaseLucene(/oak:index/ntBaseLucene) 
> dam:resolvedPath:/content/dam/we-retail/en/people/mens/men_1.jpg where 
> [a].[dam:resolvedPath] = '/content/dam/we-retail/en/people/mens/men_1.jpg' */"
> {noformat}
> Attached raw tracer output from Felix console.
> Explaining the query statement via Oak gives a different (and correct) plan.
> /cc [~chetanm]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6511) SlingTemplateResource unable to handle missing localization for a language

2017-02-09 Thread Sajid Momin (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859989#comment-15859989
 ] 

Sajid Momin commented on SLING-6511:


Hey Oliver,

Test.html is in the `/apps/audi/test/test.html` which is provided in the 
test.zip.  Now what might be missing is the content node called `test` in the 
`/content/geometrixx/en/jcr:content/par`.  I retried the Test.zip on my local 
and I didn't have any issues.  Were you able to upload & install the Test.zip 
in the package manager, http://localhost:4502/crx/packmgr/index.jsp?

Sajid

> SlingTemplateResource unable to handle missing localization for a language
> --
>
> Key: SLING-6511
> URL: https://issues.apache.org/jira/browse/SLING-6511
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Scripting Thymeleaf 1.0.0
>Reporter: Sajid Momin
>Assignee: Oliver Lietz
> Attachments: error.log, javassist-3.20.0-GA.jar, 
> org.apache.sling.scripting.thymeleaf-1.0.0.jar, Test.zip, 
> thymeleaf-i18n-error.log
>
>
> I am currently deploying Sling Thymeleaf HTML template processor to AEM 6.2.  
> In my attempt to use i18n in my template, I am receiving a null pointer 
> exception.  When the message resolver is looping through the localization of 
> the language, it's unable to skip the processing of the missing localization 
> file resulting in a null pointer.  The only way to fix the issue is to define 
> all localization resource bundle for the language in order to process the 
> template.  It would be nice for the message resolver to ignore the missing 
> localized language resource bundle and continue to the next.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SLING-6511) SlingTemplateResource unable to handle missing localization for a language

2017-02-09 Thread Oliver Lietz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859381#comment-15859381
 ] 

Oliver Lietz edited comment on SLING-6511 at 2/9/17 5:26 PM:
-

{{test.html}} is missing:

{noformat}
Not Found

Cannot serve request to /content/geometrixx/en/jcr:content/par/test.html in 
org.apache.sling.servlets.get.DefaultGetServlet

Request Progress:

  0 TIMER_START{Request Processing}
  0 COMMENT timer_end format is {,} 
  0 LOG Method=GET, 
PathInfo=/content/geometrixx/en/jcr:content/par/test.html
  0 TIMER_START{ResourceResolution}
  0 TIMER_END{0,ResourceResolution} 
URI=/content/geometrixx/en/jcr:content/par/test.html resolves to 
Resource=JcrNodeResource, type=audi/test, superType=null, 
path=/content/geometrixx/en/jcr:content/par/test
  0 LOG Resource Path Info: SlingRequestPathInfo: 
path='/content/geometrixx/en/jcr:content/par/test', selectorString='null', 
extension='html', suffix='null'
  0 TIMER_START{ServletResolution}
  0 TIMER_START{resolveServlet(/content/geometrixx/en/jcr:content/par/test)}
  0 
TIMER_END{0,resolveServlet(/content/geometrixx/en/jcr:content/par/test)} Using 
servlet org.apache.sling.servlets.get.DefaultGetServlet
  0 TIMER_END{0,ServletResolution} 
URI=/content/geometrixx/en/jcr:content/par/test.html handled by 
Servlet=org.apache.sling.servlets.get.DefaultGetServlet
  0 LOG Applying Requestfilters
  0 LOG Calling filter: 
com.adobe.granite.resourceresolverhelper.impl.ResourceResolverHelperImpl
  0 LOG Calling filter: 
org.apache.sling.bgservlets.impl.BackgroundServletStarterFilter
  0 LOG Calling filter: 
com.adobe.granite.rest.impl.servlet.ApiResourceFilter
  0 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
  0 LOG Calling filter: com.adobe.granite.httpcache.impl.InnerCacheFilter
  0 LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter
  0 LOG Calling filter: 
com.adobe.cq.mcm.campaign.servlets.CampaignCopyTracker
  0 LOG Calling filter: com.day.cq.wcm.core.impl.WCMRequestFilter
  0 LOG Calling filter: com.adobe.cq.history.impl.HistoryRequestFilter
  0 LOG Calling filter: com.adobe.granite.optout.impl.OptOutFilter
  0 LOG Calling filter: 
com.day.cq.wcm.foundation.forms.impl.FormsHandlingServlet
  0 LOG Calling filter: 
com.adobe.cq.social.commons.cors.CORSAuthenticationFilter
  0 LOG Calling filter: 
com.day.cq.analytics.provisioning.impl.UserAuthenticationRequestFilter
  0 LOG Calling filter: 
org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter
  0 LOG Calling filter: 
com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter
  0 LOG RedirectFilter did not redirect (not redirecting in author mode)
  0 LOG Calling filter: com.day.cq.wcm.core.impl.warp.TimeWarpFilter
  0 LOG Calling filter: com.day.cq.wcm.core.impl.AuthoringUIModeServiceImpl
  0 LOG Calling filter: 
org.apache.sling.security.impl.ContentDispositionFilter
  0 LOG Calling filter: com.adobe.granite.csrf.impl.CSRFFilter
  0 LOG Calling filter: 
com.adobe.granite.requests.logging.impl.RequestLoggerImpl
  0 LOG Calling filter: 
com.day.cq.dam.core.impl.servlet.ActivityRecordHandler
  0 LOG Calling filter: 
com.day.cq.dam.core.impl.assetlinkshare.AdhocAssetShareAuthHandler
  0 LOG Calling filter: 
com.adobe.cq.social.ugcbase.security.impl.SaferSlingPostServlet
  0 LOG Applying Componentfilters
  0 LOG Calling filter: com.day.cq.wcm.core.impl.WCMComponentFilter
  0 LOG Calling filter: com.day.cq.wcm.core.impl.WCMDebugFilter
  0 LOG Calling filter: 
com.day.cq.personalization.impl.TargetComponentFilter
  0 TIMER_START{org.apache.sling.servlets.get.DefaultGetServlet#0}
  0 LOG No renderer for extension html
  0 LOG Applying Error filters
  0 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
  0 LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter
  0 TIMER_START{handleError:status=404}
  0 TIMER_END{0,handleError:status=404} Using handler 
/libs/sling/servlet/errorhandler/404.jsp
  1 LOG Found processor for post processing ProcessorConfiguration: 
{contentTypes=[text/html], order=-1, active=true, valid=true, 
processErrorResponse=true, pipeline=(generator=Config(type=htmlparser, 
config={}), transformers=(Config(type=linkchecker, config={}), 
Config(type=mobile, config=JcrPropertyMap 
[node=Node[NodeDelegate{tree=/libs/cq/config/rewriter/default/transformer-mobile:
 { jcr:primaryType = nt:unstructured, component-optional = true}}], 
values={jcr:primaryType=nt:unstructured, component-optional=true}]), 
Config(type=mobiledebug, config=JcrPropertyMap 
[node=Node[NodeDelegate{tree=/libs/cq/config/rewriter/default/transformer-mobiledebug:
 { jcr:primaryType = nt:unstructured, component-optional = true}}], 
values={jcr:primaryType=nt:unstructured,

Re: [VOTE] Release Apache Servlets Get version 2.1.22

2017-02-09 Thread Ian Boston 
+1
Ian

On 9 February 2017 at 12:33, Robert Munteanu  wrote:

> On Thu, 2017-02-09 at 00:32 +0100, Karl Pauls wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
>

[jira] [Commented] (SLING-6515) Sling Post Processor considering validation model as well

2017-02-09 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859566#comment-15859566
 ] 

Konrad Windszus commented on SLING-6515:


It is not clear whether the response format 
(https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#response-format)
 can be influenced by Sling Post Processor at all?

> Sling Post Processor considering validation model as well
> -
>
> Key: SLING-6515
> URL: https://issues.apache.org/jira/browse/SLING-6515
> Project: Sling
>  Issue Type: Improvement
>  Components: Validation
>Reporter: Konrad Windszus
>
> It should be possible to optionally enable a Sling Post Processor which 
> validates the incoming parameters against a validation model. In case the 
> incoming parameters are not valid, there must be an error response. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (SLING-6515) Sling Post Processor considering validation model as well

2017-02-09 Thread Konrad Windszus (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859566#comment-15859566
 ] 

Konrad Windszus edited comment on SLING-6515 at 2/9/17 2:10 PM:


It is not clear whether the response format 
(https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#response-format)
 can be influenced by Sling Post Processor at all.


was (Author: kwin):
It is not clear whether the response format 
(https://sling.apache.org/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html#response-format)
 can be influenced by Sling Post Processor at all?

> Sling Post Processor considering validation model as well
> -
>
> Key: SLING-6515
> URL: https://issues.apache.org/jira/browse/SLING-6515
> Project: Sling
>  Issue Type: Improvement
>  Components: Validation
>Reporter: Konrad Windszus
>
> It should be possible to optionally enable a Sling Post Processor which 
> validates the incoming parameters against a validation model. In case the 
> incoming parameters are not valid, there must be an error response. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6516) ValidationModelProvider for annotation based Sling Model

2017-02-09 Thread Konrad Windszus (JIRA) 
Konrad Windszus created SLING-6516:
--

 Summary: ValidationModelProvider for annotation based Sling Model
 Key: SLING-6516
 URL: https://issues.apache.org/jira/browse/SLING-6516
 Project: Sling
  Issue Type: Improvement
  Components: Validation
Reporter: Konrad Windszus


Instead of providing a validation model through a dedicated sling resource with 
specific properties, it is often more handy to rely on annotations. A new 
ValidationModelProvider should support additional annotations on SlingModels 
defining a validation model for the underlying resource type of that SlingModel.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (SLING-6516) ValidationModelProvider evaluating additional annotations on a Sling Model bound to a specific resource type

2017-02-09 Thread Konrad Windszus (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Konrad Windszus updated SLING-6516:
---
Summary: ValidationModelProvider evaluating additional annotations on a 
Sling Model bound to a specific resource type  (was: ValidationModelProvider 
for annotation based Sling Model)

> ValidationModelProvider evaluating additional annotations on a Sling Model 
> bound to a specific resource type
> 
>
> Key: SLING-6516
> URL: https://issues.apache.org/jira/browse/SLING-6516
> Project: Sling
>  Issue Type: Improvement
>  Components: Validation
>Reporter: Konrad Windszus
>
> Instead of providing a validation model through a dedicated sling resource 
> with specific properties, it is often more handy to rely on annotations. A 
> new ValidationModelProvider should support additional annotations on 
> SlingModels defining a validation model for the underlying resource type of 
> that SlingModel.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6515) Sling Post Processor considering validation model as well

2017-02-09 Thread Konrad Windszus (JIRA) 
Konrad Windszus created SLING-6515:
--

 Summary: Sling Post Processor considering validation model as well
 Key: SLING-6515
 URL: https://issues.apache.org/jira/browse/SLING-6515
 Project: Sling
  Issue Type: Improvement
  Components: Validation
Reporter: Konrad Windszus


It should be possible to optionally enable a Sling Post Processor which 
validates the incoming parameters against a validation model. In case the 
incoming parameters are not valid, there must be an error response. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [VOTE] Release Apache Servlets Get version 2.1.22

2017-02-09 Thread Robert Munteanu 
On Thu, 2017-02-09 at 00:32 +0100, Karl Pauls wrote:
> Please vote to approve this release:

+1

Robert

[jira] [Commented] (SLING-6511) SlingTemplateResource unable to handle missing localization for a language

2017-02-09 Thread Oliver Lietz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859381#comment-15859381
 ] 

Oliver Lietz commented on SLING-6511:
-

{{test.html}} is missing.

> SlingTemplateResource unable to handle missing localization for a language
> --
>
> Key: SLING-6511
> URL: https://issues.apache.org/jira/browse/SLING-6511
> Project: Sling
>  Issue Type: Bug
>  Components: Engine
>Affects Versions: Scripting Thymeleaf 1.0.0
>Reporter: Sajid Momin
>Assignee: Oliver Lietz
> Attachments: error.log, javassist-3.20.0-GA.jar, 
> org.apache.sling.scripting.thymeleaf-1.0.0.jar, Test.zip, 
> thymeleaf-i18n-error.log
>
>
> I am currently deploying Sling Thymeleaf HTML template processor to AEM 6.2.  
> In my attempt to use i18n in my template, I am receiving a null pointer 
> exception.  When the message resolver is looping through the localization of 
> the language, it's unable to skip the processing of the missing localization 
> file resulting in a null pointer.  The only way to fix the issue is to define 
> all localization resource bundle for the language in order to process the 
> template.  It would be nice for the message resolver to ignore the missing 
> localized language resource bundle and continue to the next.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6448) Not able to upload file when sling running as war file using curl

2017-02-09 Thread Oliver Lietz (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Oliver Lietz resolved SLING-6448.
-
Resolution: Not A Problem

> Not able to upload file when sling running as war file using curl
> -
>
> Key: SLING-6448
> URL: https://issues.apache.org/jira/browse/SLING-6448
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 9
> Environment: Windows, Apache 
>Reporter: Ravi Singareddy
>
> Here are steps followed
> 1) Checked out code from svn
> svn co http://svn.apache.org/repos/asf/sling/trunk sling
> 2) cd sling
> 3) cd launchpad/builder
> 4) mvn --update-snapshots clean install
> 5) mvn jetty:run-war
> (please note I have add jetty dependency in pom.xml to run above command)
> I have used curl to upload file
> >> curl -u admin:admin http://localhost:8080/content/test.html --upload-file 
> >> test.html
> is giving following error: PUT 405 Error
> d:\curl-7.52.1-win64-mingw\bin\curl.exe -u admin:admin 
> http://localhost:8080/content/test.html --upload-file test.html
> 
> 
> 
> 405 Method PUT not supported
> 
> 
> Method PUT not supported (405)
> The requested URL /content/test.html resulted in an error in Apache Sling
>  Core Default Servlet.
> Request Progress:
> 
>   0 TIMER_START{Request Processing}
>   2 COMMENT timer_end format is {elapsed microseconds,timer 
> name
> } optional message
>  10 LOG Method=PUT, PathInfo=null
>  21 TIMER_START{handleSecurity}
>2418 TIMER_END{2395,handleSecurity} authenticator 
> org.apache.sling.auth.core.
> impl.SlingAuthenticator@68556f8e returns true
>3517 TIMER_START{ResourceResolution}
>3925 TIMER_END{406,ResourceResolution} URI=/content/test.html resolves to
>  Resource=NonExistingResource, path=/content/test.html
>3936 LOG Resource Path Info: SlingRequestPathInfo: 
> path=/content/landin
> g.html, selectorString=null, extension=html, suf
> fix=null
>3936 TIMER_START{ServletResolution}
>3941 TIMER_START{resolveServlet(/content/test.html)}
>4367 TIMER_END{423,resolveServlet(/content/test.html)} Using servlet Apac
> he Sling Core Default Servlet
>4371 TIMER_END{434,ServletResolution} URI=/content/test.html handled by S
> ervlet=Apache Sling Core Default Servlet
>4378 LOG Applying Requestfilters
>4385 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>4392 LOG Calling filter: 
> org.apache.sling.engine.impl.debug.RequestProgressTr
> ackerLogFilter
>4397 LOG Applying Componentfilters
>4409 TIMER_START{Apache Sling Core Default Servlet#0}
>4425 LOG Applying Error filters
>4428 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>4433 TIMER_START{handleError:status=405}
>4577 TIMER_END{143,handleError:status=405} Using handler 
> org.apache.sling.ser
> vlets.resolver.internal.defaults.DefaultErrorHandlerServlet
>5111 TIMER_END{5109,Request Processing} Dumping 
> SlingRequestProgressTracker E
> ntries
> 
> 
> ApacheSling/2.6 (jetty/9.3.12.v20160915, Java HotSpot(TM) 64-Bit 
> Server
>  VM 1.8.0_102, Windows 8 6.2 amd64)
> 
> 
> ___
> But If start sling using executable jar able to upload the file using curl.
> java -Xmx4g -Xms4g -Dsling.home=\var\sling -Dsling.run.modes=oak -jar 
> target\org.apache.sling.launchpad-9-SNAPSHOT.jar start
> Thanks
> Ravi



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SLING-6448) Not able to upload file when sling running as war file using curl

2017-02-09 Thread Oliver Lietz (JIRA) 

[ 
https://issues.apache.org/jira/browse/SLING-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15859368#comment-15859368
 ] 

Oliver Lietz commented on SLING-6448:
-

You should use the WAR from {{launchpad/builder}} or build a custom one with 
{{slingstart}}.

> Not able to upload file when sling running as war file using curl
> -
>
> Key: SLING-6448
> URL: https://issues.apache.org/jira/browse/SLING-6448
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad
>Affects Versions: Launchpad Builder 9
> Environment: Windows, Apache 
>Reporter: Ravi Singareddy
>
> Here are steps followed
> 1) Checked out code from svn
> svn co http://svn.apache.org/repos/asf/sling/trunk sling
> 2) cd sling
> 3) cd launchpad/builder
> 4) mvn --update-snapshots clean install
> 5) mvn jetty:run-war
> (please note I have add jetty dependency in pom.xml to run above command)
> I have used curl to upload file
> >> curl -u admin:admin http://localhost:8080/content/test.html --upload-file 
> >> test.html
> is giving following error: PUT 405 Error
> d:\curl-7.52.1-win64-mingw\bin\curl.exe -u admin:admin 
> http://localhost:8080/content/test.html --upload-file test.html
> 
> 
> 
> 405 Method PUT not supported
> 
> 
> Method PUT not supported (405)
> The requested URL /content/test.html resulted in an error in Apache Sling
>  Core Default Servlet.
> Request Progress:
> 
>   0 TIMER_START{Request Processing}
>   2 COMMENT timer_end format is {elapsed microseconds,timer 
> name
> } optional message
>  10 LOG Method=PUT, PathInfo=null
>  21 TIMER_START{handleSecurity}
>2418 TIMER_END{2395,handleSecurity} authenticator 
> org.apache.sling.auth.core.
> impl.SlingAuthenticator@68556f8e returns true
>3517 TIMER_START{ResourceResolution}
>3925 TIMER_END{406,ResourceResolution} URI=/content/test.html resolves to
>  Resource=NonExistingResource, path=/content/test.html
>3936 LOG Resource Path Info: SlingRequestPathInfo: 
> path=/content/landin
> g.html, selectorString=null, extension=html, suf
> fix=null
>3936 TIMER_START{ServletResolution}
>3941 TIMER_START{resolveServlet(/content/test.html)}
>4367 TIMER_END{423,resolveServlet(/content/test.html)} Using servlet Apac
> he Sling Core Default Servlet
>4371 TIMER_END{434,ServletResolution} URI=/content/test.html handled by S
> ervlet=Apache Sling Core Default Servlet
>4378 LOG Applying Requestfilters
>4385 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>4392 LOG Calling filter: 
> org.apache.sling.engine.impl.debug.RequestProgressTr
> ackerLogFilter
>4397 LOG Applying Componentfilters
>4409 TIMER_START{Apache Sling Core Default Servlet#0}
>4425 LOG Applying Error filters
>4428 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter
>4433 TIMER_START{handleError:status=405}
>4577 TIMER_END{143,handleError:status=405} Using handler 
> org.apache.sling.ser
> vlets.resolver.internal.defaults.DefaultErrorHandlerServlet
>5111 TIMER_END{5109,Request Processing} Dumping 
> SlingRequestProgressTracker E
> ntries
> 
> 
> ApacheSling/2.6 (jetty/9.3.12.v20160915, Java HotSpot(TM) 64-Bit 
> Server
>  VM 1.8.0_102, Windows 8 6.2 amd64)
> 
> 
> ___
> But If start sling using executable jar able to upload the file using curl.
> java -Xmx4g -Xms4g -Dsling.home=\var\sling -Dsling.run.modes=oak -jar 
> target\org.apache.sling.launchpad-9-SNAPSHOT.jar start
> Thanks
> Ravi



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (SLING-6514) Test distributions should not go through the queues

2017-02-09 Thread Tommaso Teofili (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SLING-6514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommaso Teofili resolved SLING-6514.

Resolution: Fixed

fixed in r1782306.


> Test distributions should not go through the queues
> ---
>
> Key: SLING-6514
> URL: https://issues.apache.org/jira/browse/SLING-6514
> Project: Sling
>  Issue Type: Bug
>  Components: Content Distribution
>Affects Versions: Content Distribution Core 0.1.18
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: Content Distribution Core 0.2.2
>
>
> When performing distributions of type TEST the test package goes through the 
> packages like any other package, this should not be the case as TEST 
> distributions are usually meant to check that the agent can deliver 
> (permissions and network / disk IO are fine) and therefore they should be 
> delivered without going through the queues.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (SLING-6514) Test distributions should not go through the queues

2017-02-09 Thread Tommaso Teofili (JIRA) 
Tommaso Teofili created SLING-6514:
--

 Summary: Test distributions should not go through the queues
 Key: SLING-6514
 URL: https://issues.apache.org/jira/browse/SLING-6514
 Project: Sling
  Issue Type: Bug
  Components: Content Distribution
Affects Versions: Content Distribution Core 0.1.18
Reporter: Tommaso Teofili
Assignee: Tommaso Teofili
 Fix For: Content Distribution Core 0.2.2


When performing distributions of type TEST the test package goes through the 
packages like any other package, this should not be the case as TEST 
distributions are usually meant to check that the agent can deliver 
(permissions and network / disk IO are fine) and therefore they should be 
delivered without going through the queues.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: [VOTE] Release Apache Servlets Get version 2.1.22

2017-02-09 Thread Stefan Seifert 
+1

Re: Managing the version order in JIRA

2017-02-09 Thread Julian Sedding 
That's handy Carsten. I didn't know it was possible with multi-touch
to drag with one hand and scroll with the other (even works on a
single touch-pad for me).

Regards
Julian

On Wed, Feb 8, 2017 at 3:40 PM, Carsten Ziegeler  wrote:
> Konrad Windszus wrote
>> I also really think sorting will help a lot. Unfortunately if you rely on 
>> drag and drop only it takes much more than 15 seconds (at least for me).
>> @Carsten: Do you know a shortcut?
>
> Not really a short cut, but this is how I do it:
> I search for the place were the version should go to and remember the
> position of the page slider.
> I started dragging with one hand, use the other hand on the touch pad to
> quickly scroll approximately to the remembered position. Then its just a
> little bit up or down scrolling and done.
> I really does not take more than 15 secs :)
>
> Carsten
>
>>
>>> On 8 Feb 2017, at 14:06, Carsten Ziegeler  wrote:
>>>
>>> Robert Munteanu wrote
 Hi Konrad,

 On Wed, 2017-02-08 at 09:26 +0100, Konrad Windszus wrote:
> Currently the list of versions which is supposed to be kept in order
> (http://sling.staging.apache.org/documentation/development/release-ma
> nagement.html#update-jira) is already pretty long. This makes adding
> a new version tedious and time-consuming work because you basically
> need to drag the new version to the right position in the list.
> Anyone came up with a script to automate that somehow? It seems that
> there is some javascript at https://jira.atlassian.com/browse/JRA-
> 32156?focusedCommentId=674689=com.atlassian.jira.plugin.system.i
> ssuetabpanels:comment-tabpanel#comment-674689 which automatically
> sorts via JavaScript. This seems to sort only by the release dates,
> which is not intended for Sling (since we want to group by bundle).
> So one would need to adjust the script.
> Thanks for your inputs on how you do that currently.

 I simply don't sort the versions anymore :-)

 It might be worth discussion why we are sorting them and if it makes
 sense to keep doing it, since it's quite a hassle with such a large
 number of versions.

>>> Sorting helps to jump from one version to another of that module. If you
>>> look at all issues of a version you have links to the next and the prev
>>> version, which is really very handy.
>>>
>>> And sorting is really not a major task, if you release you have to sort
>>> in a single version which takes like 15 seconds. So if everyone who does
>>> a release/adds a version does this, its really not a big deal.
>>>
>>> Carsten
>>>
>>>
>>>
>>>
>>> --
>>> Carsten Ziegeler
>>> Adobe Research Switzerland
>>> cziege...@apache.org
>>
>>
>
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org