Hi Sagara.

Done.

https://wso2.org/jira/browse/REGISTRY-2624

Thanks.

On Mon, Jun 29, 2015 at 2:59 PM, Sagara Gunathunga <[email protected]> wrote:

>
>
> Can you please create an issue in Registry project ?
>
> Thanks !
>
> On Fri, Jun 26, 2015 at 3:23 PM, KasunG Gajasinghe <[email protected]>
> wrote:
>
>>
>> It is wrong to package ECJ bundles inside reporting ui feature. This
>> bundle is already coming from kernel.
>>
>> The jasper-jdt is a wso2 orbit of ECJ, but there was no need to create an
>> orbit in the first place since the original jar itself is an osgi bundle.
>>
>> I believe we can remove this from the reporting ui feature. But can you
>> verify that with the maintainers of the reporting component?
>>
>>
>> On Fri, Jun 26, 2015 at 2:16 PM, Prabath Ariyarathna <[email protected]>
>> wrote:
>>
>>> Hi Kasun G.
>>>
>>> Reason seems to be exposed same ECJ packages from
>>> the jasper-jdt_6.0.18.wso2v1 bundle and it has exposed from the
>>> carbon-commons (org.wso2.carbon.reporting.ui.feature). After removing
>>> this bundle JSP exceptions has not occurred.
>>>
>>>
>>> Thanks.
>>>
>>> On Fri, Jun 26, 2015 at 6:27 AM, Prabath Ariyarathna <[email protected]
>>> > wrote:
>>>
>>>> Hi KasunG.
>>>>
>>>> I tested scenario with the set carbon-kernel  ECJ version to
>>>> 4.4.2 but same  exceptions can see in the console however if we place the
>>>> ECJ jar into the lib directory, it is working perfectly even for the old
>>>> ECJ 4.3.1.
>>>>
>>>>
>>>> Thanks.
>>>>
>>>> On Thu, Jun 25, 2015 at 6:39 PM, KasunG Gajasinghe <[email protected]>
>>>> wrote:
>>>>
>>>>> Raised a jira - https://wso2.org/jira/browse/WSAS-1993
>>>>>
>>>>> On Thu, Jun 25, 2015 at 6:38 PM, KasunG Gajasinghe <[email protected]>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> The ECJ bundle is not packed into the Tomcat orbit. Rather, it is
>>>>>> included in kernel o.w.c.core.common feature. We have tested with ECJ
>>>>>> 4.4.2, and it worked.
>>>>>>
>>>>>> PrabathAR is testing this further.
>>>>>>
>>>>>> On Thu, Jun 25, 2015 at 6:28 AM, Prabath Ariyarathna <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> Hi KasunG.
>>>>>>>
>>>>>>> I tried with change ECJ version to 4.4.2 but same error has
>>>>>>> occurred. Do I need to change anything other than the ECJ version?
>>>>>>>
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> On Wed, Jun 24, 2015 at 5:28 PM, KasunG Gajasinghe <[email protected]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> We are using Eclipse ECJ for JSP compilation which is packed into
>>>>>>>> the Tomcat orbit bundle. We are currently using ECJ 4.3.1. To support 
>>>>>>>> JDK
>>>>>>>> 8, we will need to update it to ECJ 4.4.x as per this Tomcat bug [1].
>>>>>>>>
>>>>>>>> To verify, can you guys try your scenario by updating the ecj
>>>>>>>> version of tomcat orbit [2] to 4.4.2?
>>>>>>>>
>>>>>>>>
>>>>>>>> [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=56283
>>>>>>>> [2]
>>>>>>>> https://github.com/wso2/orbit/blob/master/tomcat/7.0.59.wso2v3/pom.xml
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> KasunG
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> *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
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> *Prabath Ariyarathna*
>>>>>>>
>>>>>>> *Associate Technical Lead*
>>>>>>>
>>>>>>> *WSO2, Inc. *
>>>>>>>
>>>>>>> *lean . enterprise . middleware *
>>>>>>>
>>>>>>>
>>>>>>> *Email: [email protected] <[email protected]>*
>>>>>>>
>>>>>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*
>>>>>>>
>>>>>>> *Flicker : https://www.flickr.com/photos/47759189@N08
>>>>>>> <https://www.flickr.com/photos/47759189@N08>*
>>>>>>>
>>>>>>> *Mobile: +94 77 699 4730 *
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> *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
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> *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
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Prabath Ariyarathna*
>>>>
>>>> *Associate Technical Lead*
>>>>
>>>> *WSO2, Inc. *
>>>>
>>>> *lean . enterprise . middleware *
>>>>
>>>>
>>>> *Email: [email protected] <[email protected]>*
>>>>
>>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*
>>>>
>>>> *Flicker : https://www.flickr.com/photos/47759189@N08
>>>> <https://www.flickr.com/photos/47759189@N08>*
>>>>
>>>> *Mobile: +94 77 699 4730 *
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> *Prabath Ariyarathna*
>>>
>>> *Associate Technical Lead*
>>>
>>> *WSO2, Inc. *
>>>
>>> *lean . enterprise . middleware *
>>>
>>>
>>> *Email: [email protected] <[email protected]>*
>>>
>>> *Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*
>>>
>>> *Flicker : https://www.flickr.com/photos/47759189@N08
>>> <https://www.flickr.com/photos/47759189@N08>*
>>>
>>> *Mobile: +94 77 699 4730 *
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> *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
>>
>>
>>
>
>
>
> --
> Sagara Gunathunga
>
> Architect; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;    http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 

*Prabath Ariyarathna*

*Associate Technical Lead*

*WSO2, Inc. *

*lean . enterprise . middleware *


*Email: [email protected] <[email protected]>*

*Blog: http://prabu-lk.blogspot.com <http://prabu-lk.blogspot.com>*

*Flicker : https://www.flickr.com/photos/47759189@N08
<https://www.flickr.com/photos/47759189@N08>*

*Mobile: +94 77 699 4730 *
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to