Hi Manjula,

Can you drop by and help us to debug the issue, IMO, its a falut in the
executed code, which is mentioned in the stacktrace with a line number.
Lets dig in to it.

Regards,
/Nuwan

On Fri, Feb 17, 2012 at 6:19 AM, Samisa Abeysinghe <[email protected]> wrote:

>
>
> On Thu, Feb 16, 2012 at 6:39 PM, Manjula Rathnayake <[email protected]>wrote:
>
>>
>>
>> On Thu, Feb 16, 2012 at 6:28 PM, Ruchira Wageesha <[email protected]>wrote:
>>
>>> How did you deploy the jaggery app? Is it using web console?
>>>
>>> In Jaggery M2, there is an issue when apps are uploaded or redeployed
>>> using web console. i.e. Jaggery deployer isn't being hit for those apps and
>>> get deployed as normal JSP web apps. Try manually copying *.war to
>>> repository/deployment/server/jaggeryapps dir and check whether the issue is
>>> still there?
>>>
>>>
>> Yes, That is how we deployed the jaggery app. It seems to me that the
>> behavior got changed from machine to machine. Any idea what goes wrong
>> here?
>>
>
> Seems to be an issue in the Host Objects code.
>
> Have we done a review as of late on this code?
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
>
> _______________________________________________
> Carbon-dev mailing list
> [email protected]
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>


-- 
*Thanks & Regards,

Nuwan Bandara
Senior Software Engineer
WSO2 Inc. | http://wso2.com
lean . enterprise . middleware

http://nuwan.bandara.co
*
<http://www.nuwanbando.com/>
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev

Reply via email to