HI Kasun, Yes. That's get resolved once the jasper jdt is removed. I think the fix to not ship the jasper jdt is merged in carbon-commons and this will be fixed when we upgrade to latest carbon-commons once it's released.
Shazni Nazeer Mob : +94 777737331 LinkedIn : http://lk.linkedin.com/in/shazninazeer Blog : http://shazninazeer.blogspot.com On Tue, Aug 4, 2015 at 5:02 PM, KasunG Gajasinghe <[email protected]> wrote: > Hi Shazni, > > This looks like the issue with jasper-jdt. Can you make sure jasper-jdt is > removed and you are using latest ecj? > > On Tue, Aug 4, 2015 at 5:00 PM, Shazni Nazeer <[email protected]> wrote: > >> Hi all, >> >> I tried creating a tenant in a latest G-Reg pack built with kernel 4.4.1 >> and multi-tenancy 4.4.1 with Java 8. Tenant creation failed with following >> error. >> >> [2015-08-04 16:29:29,890] ERROR >> {org.apache.catalina.core.StandardWrapperValve} - Servlet.service() for >> servlet [bridgeservlet] in context with path [/] threw exception [Unable to >> compile class for JSP: >> >> An error occurred at line: 12 in the jsp file: >> /tenant-mgt/check_domain_availability_ajaxprocessor.jsp >> The type java.lang.CharSequence cannot be resolved. It is indirectly >> referenced from required .class files >> 9: JSONObject jsonObject = new JSONObject(); >> 10: >> 11: if (isDomainAvailable) { >> 12: jsonObject.put("available", "true"); >> 13: >> 14: } else { >> 15: jsonObject.put("available", "false"); >> >> >> Stacktrace:] with root cause >> org.apache.jasper.JasperException: Unable to compile class for JSP: >> >> An error occurred at line: 12 in the jsp file: >> /tenant-mgt/check_domain_availability_ajaxprocessor.jsp >> The type java.lang.CharSequence cannot be resolved. It is indirectly >> referenced from required .class files >> 9: JSONObject jsonObject = new JSONObject(); >> 10: >> 11: if (isDomainAvailable) { >> 12: jsonObject.put("available", "true"); >> 13: >> 14: } else { >> 15: jsonObject.put("available", "false"); >> >> >> The same error could be observed in packs built with kernel 4.4.0 as >> well. Hence, the issue probably exist in older multi-tenancy 4.4.1. Created >> the following jiira [1] to track this. >> >> [1] https://wso2.org/jira/browse/CARBON-15348 >> >> Shazni Nazeer >> Mob : +94 777737331 >> LinkedIn : http://lk.linkedin.com/in/shazninazeer >> Blog : http://shazninazeer.blogspot.com >> > > > > -- > > *Kasun Gajasinghe*Senior Software Engineer, WSO2 Inc. > email: kasung AT spamfree wso2.com > linked-in: http://lk.linkedin.com/in/gajasinghe > blog: http://kasunbg.org > > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
