Hi, As per offline chat with supun malinga best way to expose classes to internals package is to make the utils package private. Since ' org.wso2.carbon.andes.utils' won't be used by any other class it's better not to export this package as well.
Regards, On Tue, Feb 17, 2015 at 10:20 AM, Pumudu Ruhunage <pum...@wso2.com> wrote: > Hi, > > I'm getting class not found error when instantiate classes > inside 'org.wso2.carbon.andes' in ''org.wso2.carbon.andes.internals'' > package. > > I have created a package named 'utils' inside 'org.wso2.carbon.andes' and > added some utility classes which needs to be call > from ''org.wso2.carbon.andes.internals'' startAndesBroker method. these > 'utils' are not used in any other bundle except for > 'org.wso2.carbon.andes'. Therefore these 'utils' classes should exposed to > classes inside 'org.wso2.carbon.andes' without exporting in pom since it's > in the same bundle. But instead i'm getting class not found error when > trying to instantiate a utils class in internals package. > > As a work around, if i export utils package in pom these classes will be > exposed to ''org.wso2.carbon.andes.internals'' package. what can be the > cause for this issue ? > Any help/advice will be much appreciated. > > -- > Pumudu Ruhunage > Associate Software Engineer | WSO2 Inc > M: +94 779 664493 | http://wso2.com > -- Pumudu Ruhunage Associate Software Engineer | WSO2 Inc M: +94 779 664493 | http://wso2.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
