[jira] Resolved: (SLING-1483) SlingPostServlet saves operations that throw an error in the log but return 200 responses

2010-08-04 Thread Eric Norman (JIRA)

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

Eric Norman resolved SLING-1483.


Fix Version/s: API 2.1.0
   Resolution: Fixed

This is probably a duplicate of SLING-1628.   Please verify.

 SlingPostServlet saves operations that throw an error in the log but return 
 200 responses
 -

 Key: SLING-1483
 URL: https://issues.apache.org/jira/browse/SLING-1483
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Reporter: Michael Yin
Assignee: Eric Norman
Priority: Minor
 Fix For: API 2.1.0


 I'm on a fairly recent trunk build, and when I do save operations with the 
 sling post servlet, I'm  getting OK responses back from the servlet but I see 
 errors in the sling log, and trying to retrieve the node again shows that the 
 changes did not happen. 
 Here is one of the stack traces in the log
 org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception 
 during response processing. javax.jcr.nodetype.ConstraintViolationException: 
 Unable to perform operation. Node is protected.
   at 
 org.apache.jackrabbit.core.ItemValidator.checkCondition(ItemValidator.java:303)
   at 
 org.apache.jackrabbit.core.ItemValidator.checkModify(ItemValidator.java:277)
   at 
 org.apache.jackrabbit.core.PropertyImpl.checkSetValue(PropertyImpl.java:235)
   at 
 org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:690)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2418)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:1560)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2139)
   at 
 org.apache.sling.servlets.post.impl.helper.SlingPropertyValueHandler.setPropertyAsIs(SlingPropertyValueHandler.java:278)
   at 
 org.apache.sling.servlets.post.impl.helper.SlingPropertyValueHandler.setProperty(SlingPropertyValueHandler.java:106)
   at 
 org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:432)
   at 
 org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:100)
   at 
 org.apache.sling.servlets.post.AbstractSlingPostOperation.run(AbstractSlingPostOperation.java:87)
   at 
 org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:178)
 The node is not saved yet the http client is given a status of 200 which 
 communicates that the request has succeeded. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Resolved: (SLING-1483) SlingPostServlet saves operations that throw an error in the log but return 200 responses

2010-04-12 Thread Justin Edelson (JIRA)

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

Justin Edelson resolved SLING-1483.
---

Resolution: Fixed

 SlingPostServlet saves operations that throw an error in the log but return 
 200 responses
 -

 Key: SLING-1483
 URL: https://issues.apache.org/jira/browse/SLING-1483
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Reporter: Michael Yin
Priority: Minor

 I'm on a fairly recent trunk build, and when I do save operations with the 
 sling post servlet, I'm  getting OK responses back from the servlet but I see 
 errors in the sling log, and trying to retrieve the node again shows that the 
 changes did not happen. 
 Here is one of the stack traces in the log
 org.apache.sling.servlets.post.impl.operations.ModifyOperation Exception 
 during response processing. javax.jcr.nodetype.ConstraintViolationException: 
 Unable to perform operation. Node is protected.
   at 
 org.apache.jackrabbit.core.ItemValidator.checkCondition(ItemValidator.java:303)
   at 
 org.apache.jackrabbit.core.ItemValidator.checkModify(ItemValidator.java:277)
   at 
 org.apache.jackrabbit.core.PropertyImpl.checkSetValue(PropertyImpl.java:235)
   at 
 org.apache.jackrabbit.core.PropertyImpl.setValue(PropertyImpl.java:690)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2418)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:1560)
   at org.apache.jackrabbit.core.NodeImpl.setProperty(NodeImpl.java:2139)
   at 
 org.apache.sling.servlets.post.impl.helper.SlingPropertyValueHandler.setPropertyAsIs(SlingPropertyValueHandler.java:278)
   at 
 org.apache.sling.servlets.post.impl.helper.SlingPropertyValueHandler.setProperty(SlingPropertyValueHandler.java:106)
   at 
 org.apache.sling.servlets.post.impl.operations.ModifyOperation.writeContent(ModifyOperation.java:432)
   at 
 org.apache.sling.servlets.post.impl.operations.ModifyOperation.doRun(ModifyOperation.java:100)
   at 
 org.apache.sling.servlets.post.AbstractSlingPostOperation.run(AbstractSlingPostOperation.java:87)
   at 
 org.apache.sling.servlets.post.impl.SlingPostServlet.doPost(SlingPostServlet.java:178)
 The node is not saved yet the http client is given a status of 200 which 
 communicates that the request has succeeded. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira