Hi Eranda,

It is not an issue in the sequence, it is an issue in the code inside the
SQLQueryHandler. It should be using the Registry to do the put and not the
repository, or it will invariably fail. The use of the repository might be
correct in certain types of handlers, but definitely not in this. Please
fix, run integration tests and validate whether that solves the issue in AM
and breaks nothing in G-Reg.

Thanks,
Senaka.

On Tue, Jan 8, 2013 at 10:40 AM, Eranda Sooriyabandara <[email protected]>wrote:

> Hi all,
> This is regarding the issue [1], where the registry.put hits
> in SQLQueryHandler before MountHandler which causes the exception. Here I
> tested it by putting a resource with the mediatype
> "application/vnd.sql.query" to a mounted location. Adding the resource
> succeeded but the resource no longer listed in the respected location. Then
> I remove the mount and check the respective location where the resources
> were there.
> So here I wanted to change the sequence of hitting Handlers, give priority
> to MountHandler over SQLQueryHandler. How can I do that?
>
> thanks
> Eranda
>
> [1]. https://wso2.org/jira/browse/APIMANAGER-869
>



-- 
* <http://wso2con.com/>
*
*

Senaka Fernando*
Member - Integration Technologies Management Committee;
Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

*Lean . Enterprise . Middleware
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to