On Thu, Jan 26, 2012 at 6:13 AM, Afkham Azeez wrote:
> Yeah, there is no need to add redundant jars into the AAR. Perhaps we can
> exclude these jars during AAR creation.
>
Yes, if the AAR generation is done by axis2-aar-maven-plugin, this can be
configured. For that, just
set false inside
of th
Hi,
On Wed, Jan 25, 2012 at 3:57 PM, Senaka Fernando wrote:
>
>
> On Wed, Jan 25, 2012 at 10:30 PM, Subash Chaturanga wrote:
>
>>
>>
>> On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez wrote:
>>>
It is very strange that
On Thu, Jan 26, 2012 at 6:13 AM, Afkham Azeez wrote:
> Yeah, there is no need to add redundant jars into the AAR. Perhaps we can
> exclude these jars during AAR creation.
>
+1
> --
> Afkham Azeez
> Sent from my phone
> On Jan 25, 2012 10:30 PM, "Subash Chaturanga" wrote:
>
>>
>>
>> On Wed, Jan
Yeah, there is no need to add redundant jars into the AAR. Perhaps we can
exclude these jars during AAR creation.
--
Afkham Azeez
Sent from my phone
On Jan 25, 2012 10:30 PM, "Subash Chaturanga" wrote:
>
>
> On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi wrote:
>
>>
>>
>> On Fri, Jan 20, 20
On Wed, Jan 25, 2012 at 10:30 PM, Subash Chaturanga wrote:
>
>
> On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi wrote:
>
>>
>>
>> On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez wrote:
>>
>>> It is very strange that MessageContext.getCurrentContext returns null
>>> only in G-Reg.
>>>
>>
>> th
On Wed, Jan 25, 2012 at 7:02 PM, Amila Suriarachchi wrote:
>
>
> On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez wrote:
>
>> It is very strange that MessageContext.getCurrentContext returns null
>> only in G-Reg.
>>
>
> this is a classloading issue. this .aar file contains an axis2 jar in the
> li
On Fri, Jan 20, 2012 at 2:09 PM, Afkham Azeez wrote:
> It is very strange that MessageContext.getCurrentContext returns null only
> in G-Reg.
>
this is a classloading issue. this .aar file contains an axis2 jar in the
lib folder and GReg has set child first class loading true.
thanks,
Amila.
>
Did we able to fix this?
On Fri, Jan 20, 2012 at 4:39 PM, Subash Chaturanga wrote:
> Hi
>
> I debug in axis2 level and the reason for this issue is;
>
> The thread which set the axis2 message context to the ThreadLocal, cannot
> acquire it in the service. Its a null. When debugging I kept tracki
Hi
I debug in axis2 level and the reason for this issue is;
The thread which set the axis2 message context to the ThreadLocal, cannot
acquire it in the service. Its a null. When debugging I kept tracking on
the thread ids and the thread which set the message context to its thread
local get remov
It is very strange that MessageContext.getCurrentContext returns null only
in G-Reg.
On Fri, Jan 20, 2012 at 12:44 PM, Subash Chaturanga wrote:
> Hi all,
>
> I came across with this issue when running the GReg testng
> SecurityVetification test case as it invokes
> the org.wso2.carbon.integratio
Hi all,
I came across with this issue when running the GReg testng
SecurityVetification test case as it invokes
the org.wso2.carbon.integration.secverifier.SecurityVerifierService.
There was a NPE as axis2 MessageContext gets null.
This can be reproduced when you manually drop a service aar to
G
11 matches
Mail list logo