You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by Robert Munteanu <rm...@adobe.com> on 2012/11/12 18:48:10 UTC

[slingclipse] Checking out resources fails if the DefaultGetServlet does not serve the content

Hi,

By trying out Slingclipse on a larger project I found out that checking out a resource fails if the DefaultGetServlet does not serve calls for a specific resource, e.g.

- content ( nt:folder ) 
\- child ( my:resource )

where my:resource is served by a servlet which returns 404 on JSON calls. The importer correctly discovers that /content/child exists since it is listed at /content.1.json but then retrieval fails for /content/child.json .

What would be the best approach to handle this scenario?

Thanks,

Robert

RE: [slingclipse] Checking out resources fails if the DefaultGetServlet does not serve the content

Posted by Robert Munteanu <rm...@adobe.com>.

Hi Antonio,

> Hi Robert,
> 
> thanks for reporting this.
> It would be something to investigate for sure.
> Would also be interesting to know the current behavior. What's happening in
> this failure situation?
> Does the import stops completely or it just doesn't import a part of the
> repository?

Well, it depends. I encountered two situations in my testing:

1. The repository returns a 4xx status, which means that the command fails and the import continues, but the user is not notified
2. The repository returns invalid JSON due to a sloppy script/servlet mapping which breaks the import since the JSON error is propagated.

Robert

> 
> Regards
> 
> Antonio
> 
> On Nov 12, 2012, at 6:48 PM, Robert Munteanu wrote:
> 
> > Hi,
> >
> > By trying out Slingclipse on a larger project I found out that checking out
> a resource fails if the DefaultGetServlet does not serve calls for a specific
> resource, e.g.
> >
> > - content ( nt:folder )
> > \- child ( my:resource )
> >
> > where my:resource is served by a servlet which returns 404 on JSON calls.
> The importer correctly discovers that /content/child exists since it is
> listed at /content.1.json but then retrieval fails for /content/child.json .
> >
> > What would be the best approach to handle this scenario?
> >
> > Thanks,
> >
> > Robert

Re: [slingclipse] Checking out resources fails if the DefaultGetServlet does not serve the content

Posted by Antonio Sanso <as...@adobe.com>.

Hi Robert,

thanks for reporting this.
It would be something to investigate for sure.
Would also be interesting to know the current behavior. What's happening in this failure situation?
Does the import stops completely or it just doesn't import a part of the repository?

Regards

Antonio

On Nov 12, 2012, at 6:48 PM, Robert Munteanu wrote:

> Hi,
> 
> By trying out Slingclipse on a larger project I found out that checking out a resource fails if the DefaultGetServlet does not serve calls for a specific resource, e.g.
> 
> - content ( nt:folder ) 
> \- child ( my:resource )
> 
> where my:resource is served by a servlet which returns 404 on JSON calls. The importer correctly discovers that /content/child exists since it is listed at /content.1.json but then retrieval fails for /content/child.json .
> 
> What would be the best approach to handle this scenario?
> 
> Thanks,
> 
> Robert