Hi Samisa, No the docs should be improved to explain how this works. Eranda, we need a high-level explanation of things like this, the low-level classloading details won't help a user who's going to deploy a handler. They are not supposed to debug the product source code to learn how to register handlers and how they are sequenced.
Thanks, Senaka. On Fri, Oct 5, 2012 at 8:44 AM, Eranda Sooriyabandara <[email protected]>wrote: > Hi Samisa, > > > >> >> Um I am confused by your statement - can you clarify further please? Or >> better yet, do we have a doc on this preference order? >> >> > > AFAIK, There is a class loader which search jars in > repository/components/lib folder if the class not found in the current > classpath. First time you added to the classpath then it will remain in the > classpath so that the modification to the same jar won't affect. > > thanks > Eranda > * > * > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *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
