Re: [Dev] [DEV] ERROR NullPointerException & Error occurred while running CacheCleanupTask in GREG

[Nuwan Silva]

Could this cause the issue where we can not login to GREG?


On Wed, Oct 9, 2013 at 11:39 AM, Afkham Azeez  wrote:

> The bug is in the implementation of the AuthorizationKey.equals method,
> which leads to this NPE
>
>
> On Wed, Oct 9, 2013 at 10:11 AM, Nuwan Silva  wrote:
>
>> Following occurs when running GREG cluster
>>
>> https://wso2.org/jira/browse/REGISTRY-1984
>>
>> Exception in thread "hz.greg.qa.460.domain.instance.cached.thread-3"
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
>> at
>> org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
>> at
>> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:930)
>> at
>> org.wso2.carbon.caching.impl.CacheImpl$TimestampMapEntryListenerImpl.entryUpdated(CacheImpl.java:1026)
>> at
>> org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap$1.entryUpdated(HazelcastDistributedMapProvider.java:73)
>> at com.hazelcast.map.MapService.dispatchEvent(MapService.java:698)
>> at com.hazelcast.map.MapService.dispatchEvent(MapService.java:65)
>> at
>> com.hazelcast.spi.impl.EventServiceImpl$EventPacketProcessor.process(EventServiceImpl.java:444)
>> at
>> com.hazelcast.spi.impl.EventServiceImpl$RemoteEventPacketProcessor.run(EventServiceImpl.java:470)
>> at
>> com.hazelcast.util.executor.StripedExecutor$Worker.run(StripedExecutor.java:130)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>> at java.lang.Thread.run(Thread.java:722)
>>
>>
>> [2013-10-09 10:05:32,203] ERROR
>> {org.wso2.carbon.caching.impl.CacheCleanupTask} -  Error occurred while
>> running CacheCleanupTask
>> java.lang.NullPointerException
>> at
>> org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
>> at
>> org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
>> at
>> java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:958)
>> at
>> org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:239)
>> at
>> org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>> at java.lang.Thread.run(Thread.java:722)
>>
>> >* Not sure if due to this, but can not login to the cluster setup as
>> well.*
>> [2013-10-09 09:58:05,024] ERROR
>> {org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient} -  Error
>> occurred while logging in
>> org.apache.axis2.AxisFault: Exception occurred while trying to invoke
>> service method login
>> at
>> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:367)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:413)
>> at
>> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
>> at
>> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
>> at
>> org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
>> at
>> org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
>> at
>> org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
>> at
>> org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
>> at
>> org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:77)
>> at
>> org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:358)
>> at
>> org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:246)
>> at
>> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
>> at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
>> at
>> org.eclipse.equinox.http.servlet.int

Re: [Dev] [DEV] ERROR NullPointerException & Error occurred while running CacheCleanupTask in GREG

[Afkham Azeez]

The bug is in the implementation of the AuthorizationKey.equals method,
which leads to this NPE


On Wed, Oct 9, 2013 at 10:11 AM, Nuwan Silva  wrote:

> Following occurs when running GREG cluster
>
> https://wso2.org/jira/browse/REGISTRY-1984
>
> Exception in thread "hz.greg.qa.460.domain.instance.cached.thread-3"
> java.lang.NullPointerException
> at
> org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
> at
> org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
> at
> java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:930)
> at
> org.wso2.carbon.caching.impl.CacheImpl$TimestampMapEntryListenerImpl.entryUpdated(CacheImpl.java:1026)
> at
> org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap$1.entryUpdated(HazelcastDistributedMapProvider.java:73)
> at com.hazelcast.map.MapService.dispatchEvent(MapService.java:698)
> at com.hazelcast.map.MapService.dispatchEvent(MapService.java:65)
> at
> com.hazelcast.spi.impl.EventServiceImpl$EventPacketProcessor.process(EventServiceImpl.java:444)
> at
> com.hazelcast.spi.impl.EventServiceImpl$RemoteEventPacketProcessor.run(EventServiceImpl.java:470)
> at
> com.hazelcast.util.executor.StripedExecutor$Worker.run(StripedExecutor.java:130)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
>
>
> [2013-10-09 10:05:32,203] ERROR
> {org.wso2.carbon.caching.impl.CacheCleanupTask} -  Error occurred while
> running CacheCleanupTask
> java.lang.NullPointerException
> at
> org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
> at
> org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
> at
> java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:958)
> at
> org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:239)
> at
> org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
>
> >* Not sure if due to this, but can not login to the cluster setup as
> well.*
> [2013-10-09 09:58:05,024] ERROR
> {org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient} -  Error
> occurred while logging in
> org.apache.axis2.AxisFault: Exception occurred while trying to invoke
> service method login
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:367)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:413)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
> at
> org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
> at
> org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
> at
> org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
> at
> org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
> at
> org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:77)
> at
> org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:358)
> at
> org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:246)
> at
> org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
>   

Re: [Dev] Python client for WSO2 Message Broker

[Ishara Premadasa]

Hi Dinesh,

Do you see any error log there when running the subscriber ?  Also can you
see any terminal logs saying that 'Subscriber binded successfully with
ID_XX ' etc.  ? If possible please add the MB log here after running the
sample clients.

Thanks,
Ishara


On Wed, Oct 9, 2013 at 11:00 AM, Dinesh Bandara  wrote:

> Hi,
>
> I have tried to implement a python client for WSO2 MB by using the [1]
> which supports for RabbitMQ as well as Qpid. When use it with WSO2MB,
> publisher can publish into topic but subscriber could not be able to
> consume messages from the topic.
> Can anyone help me to figure this out?
>
> [1] https://launchpad.net/txamqp
>
> --
> *Dinesh Bandara*
> Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/
*Blog   :  http://isharapremadasa.blogspot.com/
Twitter   :  https://twitter.com/ishadil
Mobile   : +94 714445832*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kernel][patch0001] Test Failure in Axiom

[Subash Chaturanga]

In clean repo in the builder machine, this test fails. JDK version in
builder is jdk1.6.0_45.  But I will continue the build with out tests in
kernel to build packs.


On Wed, Oct 9, 2013 at 10:03 AM, Subash Chaturanga  wrote:

> sure will do.
>
>
> On Wed, Oct 9, 2013 at 9:37 AM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> All the axiom tests were passed for me. Can you please check.
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Wed, Oct 9, 2013 at 9:28 AM, Manoj Kumara  wrote:
>>
>>> Hi,
>>>
>>> Yes there was no issue with the test. Will look into this.
>>>
>>> Thanks,
>>> Manoj
>>>
>>> Best Regards..
>>>
>>>
>>> Manoj Kumara
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Twitter:  http://twitter.com/ManKuma
>>> Mobile: +94713448188
>>>
>>>
>>> On Tue, Oct 8, 2013 at 11:17 PM, Subash Chaturanga wrote:
>>>
 Hi
 Following is the sure fire report for $subject ? Were we before able to
 build the kernel with all tests passing ?



 ---
 Test set: org.apache.axiom.attachments.PartOnFileTest

 ---
 Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006
 sec <<< FAILURE!
 testHeaderGetSet(org.apache.axiom.attachments.PartOnFileTest)  Time
 elapsed: 0.003 sec  <<< FAILURE!
 junit.framework.AssertionFailedError: Expected PartOnFile
 at junit.framework.Assert.fail(Assert.java:47)
 at
 org.apache.axiom.attachments.PartOnFileTest.testHeaderGetSet(PartOnFileTest.java:59)


 --
 Thanks
 /subash

 *Subash Chaturanga*
 Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

 email: sub...@wso2.com
 blog:  http://subashsdm.blogspot.com/
 twitter: @subash89
 phone: +9477 2225922
 Lean . Enterprise . Middleware

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>



-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] cmis tool scenario does not work

[Shavantha Weerasinghe]

Hi All

with the GReg pack on 8th October I was not able to login to CMIS as
per the 
http://docs.wso2.org/display/Governance460/Integrate+CMIS+Client+with+WSO2+Governance+Registry.
however, I reverted back to 3rd September pack which allowed me to
gain access to CMIS. Jira is
https://wso2.org/jira/browse/REGISTRY-2031


Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Python client for WSO2 Message Broker

[Dinesh Bandara]

Hi,

I have tried to implement a python client for WSO2 MB by using the [1]
which supports for RabbitMQ as well as Qpid. When use it with WSO2MB,
publisher can publish into topic but subscriber could not be able to
consume messages from the topic.
Can anyone help me to figure this out?

[1] https://launchpad.net/txamqp

-- 
*Dinesh Bandara*
Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Balana policy source question

[Asela Pathberiya]

Hi Scott,

If you create an account in wso2.com  [1]. Then you can login to jira
account with those credentials.

[1] https://wso2.com/user/register

Thanks,
Asela.

On Wed, Oct 9, 2013 at 6:01 AM, Scott Came  wrote:

>  Hi Asela.  I have created an InMemoryPolicyFinderModule and an
> associated unit test.  I can easily roll a patch for this and submit it.**
> **
>
> ** **
>
> I hit the link [1] you referenced, but it looks like I need a JIRA account
> in order to create a ticket and post the patch.  I looked around on the
> WSO2 site and could not see how to create an account.  What is the next
> step?
>
> ** **
>
> Thanks.
>
> --Scott
>
> ** **
>
> *From:* Asela Pathberiya [mailto:as...@wso2.com]
> *Sent:* Tuesday, October 01, 2013 10:08 AM
> *To:* Scott Came
> *Cc:* dev@wso2.org
> *Subject:* Re: [Dev] Balana policy source question
>
> ** **
>
> Hi Scott,
>
> Really welcome your ideas.  Yes. Balana only have a sample implementation
> for file system based policies.  As you know, WSO2 Identity Server uses
> Balana as XACML engine and Identity Server has own implementation for
> PolicyFinderModule. Sure... you could implement this for Balana... If
> policies are loading from different sources (file system, databases and so
> on...), it is easy to extend an in-memory finder module.  You can create a
> ticket in here [1]
>
> under Balana component and provide a patch for trunk.   ** **
>
>
> [1] https://wso2.org/jira/browse/COMMONS
>
> Thanks,
> Asela.
>
> ** **
>
> On Tue, Oct 1, 2013 at 4:06 AM, Scott Came  wrote:*
> ***
>
> Unless I’m missing something, it looks like the only way to feed policies
> into the Balana PDP is to have them in files that reside in the filesystem.
> 
>
>  
>
> I’m wondering if any thought was given to allowing (somehow) in-memory DOM
> Documents to be passed in.  I haven’t investigated in-depth yet, but I
> wonder if it would be possible to write a PolicyFinderModule implementation
> class that references an in-memory collection of policies…
>
>  
>
> If this seems like a good idea, I’d be happy to attempt it…
>
>  
>
> Thanks.
>
> --Scott
>
>  
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> -- 
>
> Thanks & Regards,
>
> Asela
>
> ** **
>
> ATL
>
> Mobile : +94 777 625 933
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Fwd: [jira] [Created] (STRATOS-95) Build failure on trunk (3.0.0-SNAPSHOT)

[Sanjiva Weerawarana]

FYI - please fix in Carbon itself (see thread on
d...@stratos.incubator.apache.org for more info).

-- Forwarded message --
From: Hadrian Zbarcea (JIRA) 
Date: Tue, Oct 8, 2013 at 7:10 AM
Subject: [jira] [Created] (STRATOS-95) Build failure on trunk
(3.0.0-SNAPSHOT)
To: d...@stratos.incubator.apache.org


Hadrian Zbarcea created STRATOS-95:
--

 Summary: Build failure on trunk (3.0.0-SNAPSHOT)
 Key: STRATOS-95
 URL: https://issues.apache.org/jira/browse/STRATOS-95
 Project: Stratos
  Issue Type: Bug
Affects Versions: 3.0.0 RC1
Reporter: Hadrian Zbarcea
 Fix For: 3.0.0 RC1


Builds fail in org.apache.stratos.account.mgt due to a missing dependency
on javax.activation:activation:jar:1.0.2.

A quick mvn -X dependency:tree shows it as being a transitive dependency
coming from org.wso2.carbon:atlassian-jira.

{code}
[DEBUG]org.wso2.carbon:atlassian-jira:jar:1.0.0.wso2v1:compile
[...]
[DEBUG]   javax.xml:jaxrpc-api:jar:1.1:compile
[DEBUG]  javax.xml.soap:saaj-api:jar:1.3:compile
[DEBUG] javax.activation:activation:jar:1.0.2:compile
{code}

A simple excludes of the transitive dependency solves the problem (patch
attached). Ideally this would be done directly in carbon/atlassian-jira in
a future release and removed from here.

Cheers



--
This message was sent by Atlassian JIRA
(v6.1#6144)



-- 
Sanjiva Weerawarana, Ph.D.
Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
email: sanj...@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1
650 265 8311
blog: http://sanjiva.weerawarana.org/

Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [DEV] ERROR NullPointerException & Error occurred while running CacheCleanupTask in GREG

[Nuwan Silva]

Following occurs when running GREG cluster

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

Exception in thread "hz.greg.qa.460.domain.instance.cached.thread-3"
java.lang.NullPointerException
at
org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
at
org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
at
java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:930)
at
org.wso2.carbon.caching.impl.CacheImpl$TimestampMapEntryListenerImpl.entryUpdated(CacheImpl.java:1026)
at
org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap$1.entryUpdated(HazelcastDistributedMapProvider.java:73)
at com.hazelcast.map.MapService.dispatchEvent(MapService.java:698)
at com.hazelcast.map.MapService.dispatchEvent(MapService.java:65)
at
com.hazelcast.spi.impl.EventServiceImpl$EventPacketProcessor.process(EventServiceImpl.java:444)
at
com.hazelcast.spi.impl.EventServiceImpl$RemoteEventPacketProcessor.run(EventServiceImpl.java:470)
at
com.hazelcast.util.executor.StripedExecutor$Worker.run(StripedExecutor.java:130)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)


[2013-10-09 10:05:32,203] ERROR
{org.wso2.carbon.caching.impl.CacheCleanupTask} -  Error occurred while
running CacheCleanupTask
java.lang.NullPointerException
at
org.wso2.carbon.user.core.authorization.AuthorizationKey.checkAttributesAreEqual(AuthorizationKey.java:116)
at
org.wso2.carbon.user.core.authorization.AuthorizationKey.equals(AuthorizationKey.java:61)
at
java.util.concurrent.ConcurrentHashMap.containsKey(ConcurrentHashMap.java:958)
at org.wso2.carbon.caching.impl.CacheImpl.syncCaches(CacheImpl.java:239)
at
org.wso2.carbon.caching.impl.CacheCleanupTask.run(CacheCleanupTask.java:61)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)

>* Not sure if due to this, but can not login to the cluster setup as well.*
[2013-10-09 09:58:05,024] ERROR
{org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient} -  Error
occurred while logging in
org.apache.axis2.AxisFault: Exception occurred while trying to invoke
service method login
at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
at
org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:367)
at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:413)
at
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:224)
at
org.apache.axis2.client.OperationClient.execute(OperationClient.java:149)
at
org.wso2.carbon.authenticator.stub.AuthenticationAdminStub.login(AuthenticationAdminStub.java:659)
at
org.wso2.carbon.authenticator.proxy.AuthenticationAdminClient.login(AuthenticationAdminClient.java:64)
at
org.wso2.carbon.ui.DefaultCarbonAuthenticator.doAuthentication(DefaultCarbonAuthenticator.java:119)
at
org.wso2.carbon.ui.AbstractCarbonUIAuthenticator.handleSecurity(AbstractCarbonUIAuthenticator.java:218)
at
org.wso2.carbon.ui.BasicAuthUIAuthenticator.authenticate(BasicAuthUIAuthenticator.java:77)
at
org.wso2.carbon.ui.CarbonUILoginUtil.handleLogin(CarbonUILoginUtil.java:358)
at
org.wso2.carbon.ui.CarbonSecuredHttpContext.handleSecurity(CarbonSecuredHttpContext.java:246)
at
org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:60)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:128)
at
org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.service(DelegationServlet.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.wso2.carbon.tomcat.ext.filter.CharacterSetFilter.doFilter(CharacterSetFilter.java:61)
at
org.apache.catalina.core.ApplicationFilterCha

Re: [Dev] [Kernel][patch0001] Test Failure in Axiom

[Subash Chaturanga]

sure will do.


On Wed, Oct 9, 2013 at 9:37 AM, Manoj Kumara  wrote:

> Hi,
>
> All the axiom tests were passed for me. Can you please check.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Wed, Oct 9, 2013 at 9:28 AM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> Yes there was no issue with the test. Will look into this.
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Tue, Oct 8, 2013 at 11:17 PM, Subash Chaturanga wrote:
>>
>>> Hi
>>> Following is the sure fire report for $subject ? Were we before able to
>>> build the kernel with all tests passing ?
>>>
>>>
>>>
>>> ---
>>> Test set: org.apache.axiom.attachments.PartOnFileTest
>>>
>>> ---
>>> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006
>>> sec <<< FAILURE!
>>> testHeaderGetSet(org.apache.axiom.attachments.PartOnFileTest)  Time
>>> elapsed: 0.003 sec  <<< FAILURE!
>>> junit.framework.AssertionFailedError: Expected PartOnFile
>>> at junit.framework.Assert.fail(Assert.java:47)
>>> at
>>> org.apache.axiom.attachments.PartOnFileTest.testHeaderGetSet(PartOnFileTest.java:59)
>>>
>>>
>>> --
>>> Thanks
>>> /subash
>>>
>>> *Subash Chaturanga*
>>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>>>
>>> email: sub...@wso2.com
>>> blog:  http://subashsdm.blogspot.com/
>>> twitter: @subash89
>>> phone: +9477 2225922
>>> Lean . Enterprise . Middleware
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>


-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kernel][patch0001] Test Failure in Axiom

[Manoj Kumara]

Hi,

All the axiom tests were passed for me. Can you please check.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Wed, Oct 9, 2013 at 9:28 AM, Manoj Kumara  wrote:

> Hi,
>
> Yes there was no issue with the test. Will look into this.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Tue, Oct 8, 2013 at 11:17 PM, Subash Chaturanga wrote:
>
>> Hi
>> Following is the sure fire report for $subject ? Were we before able to
>> build the kernel with all tests passing ?
>>
>>
>>
>> ---
>> Test set: org.apache.axiom.attachments.PartOnFileTest
>>
>> ---
>> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
>> <<< FAILURE!
>> testHeaderGetSet(org.apache.axiom.attachments.PartOnFileTest)  Time
>> elapsed: 0.003 sec  <<< FAILURE!
>> junit.framework.AssertionFailedError: Expected PartOnFile
>> at junit.framework.Assert.fail(Assert.java:47)
>> at
>> org.apache.axiom.attachments.PartOnFileTest.testHeaderGetSet(PartOnFileTest.java:59)
>>
>>
>> --
>> Thanks
>> /subash
>>
>> *Subash Chaturanga*
>> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>>
>> email: sub...@wso2.com
>> blog:  http://subashsdm.blogspot.com/
>> twitter: @subash89
>> phone: +9477 2225922
>> Lean . Enterprise . Middleware
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Kernel][patch0001] Test Failure in Axiom

[Manoj Kumara]

Hi,

Yes there was no issue with the test. Will look into this.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Tue, Oct 8, 2013 at 11:17 PM, Subash Chaturanga  wrote:

> Hi
> Following is the sure fire report for $subject ? Were we before able to
> build the kernel with all tests passing ?
>
>
>
> ---
> Test set: org.apache.axiom.attachments.PartOnFileTest
>
> ---
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
> <<< FAILURE!
> testHeaderGetSet(org.apache.axiom.attachments.PartOnFileTest)  Time
> elapsed: 0.003 sec  <<< FAILURE!
> junit.framework.AssertionFailedError: Expected PartOnFile
> at junit.framework.Assert.fail(Assert.java:47)
> at
> org.apache.axiom.attachments.PartOnFileTest.testHeaderGetSet(PartOnFileTest.java:59)
>
>
> --
> Thanks
> /subash
>
> *Subash Chaturanga*
> Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com
>
> email: sub...@wso2.com
> blog:  http://subashsdm.blogspot.com/
> twitter: @subash89
> phone: +9477 2225922
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Balana policy source question

[Scott Came]

Hi Asela.  I have created an InMemoryPolicyFinderModule and an associated unit 
test.  I can easily roll a patch for this and submit it.

I hit the link [1] you referenced, but it looks like I need a JIRA account in 
order to create a ticket and post the patch.  I looked around on the WSO2 site 
and could not see how to create an account.  What is the next step?

Thanks.
--Scott

From: Asela Pathberiya [mailto:as...@wso2.com]
Sent: Tuesday, October 01, 2013 10:08 AM
To: Scott Came
Cc: dev@wso2.org
Subject: Re: [Dev] Balana policy source question

Hi Scott,
Really welcome your ideas.  Yes. Balana only have a sample implementation for 
file system based policies.  As you know, WSO2 Identity Server uses Balana as 
XACML engine and Identity Server has own implementation for PolicyFinderModule. 
Sure... you could implement this for Balana... If policies are loading from 
different sources (file system, databases and so on...), it is easy to extend 
an in-memory finder module.  You can create a ticket in here [1]
under Balana component and provide a patch for trunk.

[1] https://wso2.org/jira/browse/COMMONS
Thanks,
Asela.

On Tue, Oct 1, 2013 at 4:06 AM, Scott Came 
mailto:scott.c...@search.org>> wrote:
Unless I'm missing something, it looks like the only way to feed policies into 
the Balana PDP is to have them in files that reside in the filesystem.

I'm wondering if any thought was given to allowing (somehow) in-memory DOM 
Documents to be passed in.  I haven't investigated in-depth yet, but I wonder 
if it would be possible to write a PolicyFinderModule implementation class that 
references an in-memory collection of policies...

If this seems like a good idea, I'd be happy to attempt it...

Thanks.
--Scott


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev



--
Thanks & Regards,
Asela

ATL
Mobile : +94 777 625 933
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [Kernel][patch0001] Test Failure in Axiom

[Subash Chaturanga]

Hi
Following is the sure fire report for $subject ? Were we before able to
build the kernel with all tests passing ?


---
Test set: org.apache.axiom.attachments.PartOnFileTest
---
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec
<<< FAILURE!
testHeaderGetSet(org.apache.axiom.attachments.PartOnFileTest)  Time
elapsed: 0.003 sec  <<< FAILURE!
junit.framework.AssertionFailedError: Expected PartOnFile
at junit.framework.Assert.fail(Assert.java:47)
at
org.apache.axiom.attachments.PartOnFileTest.testHeaderGetSet(PartOnFileTest.java:59)


-- 
Thanks
/subash

*Subash Chaturanga*
Senior Software Engineer :Integration TG; WSO2 Inc. http://wso2.com

email: sub...@wso2.com
blog:  http://subashsdm.blogspot.com/
twitter: @subash89
phone: +9477 2225922
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] WSO2 Enterprise Store 1.0.0 ALPHA-3 Released

[Nuwan Bandara]

*WSO2 Enterprise Store 1.0.0 ALPHA-3 Released !*

This is the ALPHA-3 release of WSO2 Enterprise Store, which will create a
marketplace for your enterprise assets. You can download the Alpha-3 at
[1]. This release specifically contains following tasks, improvements and
bug fixes towards 1.0.0 GA.

*Bugs*

   - [STORE-69 ] - Mark Required
   Fields in add asset form
   - [STORE-70 ] - Publisher
   breadcrumb should be updated automatically with newly added RXTs
   - [STORE-84 ] - Cleanup all debug
   logs at startup
   - [STORE-121 ] - Upload option
   not there in create gadget
   - [STORE-139 ] - Better keep the
   field blank, if no value is provided while creating the assets
   - [STORE-144 ] - Error at
   startup when openldap is configured as external read/write user store
   - [STORE-150 ] - Proper
   warning/error message should be given if user name/password is incorrect
   - [STORE-153 ] - 404 returned if
   you click on table headings on asset list
   - [STORE-160 ] - Every page in
   publisher need to check for a logged in session like in the store
   - [STORE-165 ] - Get permissions
   should not be removed the scxml
   - [STORE-167 ] - It's better if
   non-editable fields can be made read only
   - [STORE-169 ] - Books, category
   is not a dropdown
   - [STORE-170 ] - Gadget not
   created when adding the for the first time after server restart
   - [STORE-171 ] - Edit asset page
   need more UI work
   - [STORE-172 ] - Asset rating
   doesn't work
   - [STORE-175 ] - Rating not
   shown in gadget list
   - [STORE-179 ] - Issues in
   single log out
   - [STORE-181 ] - Remove
   individual logs when adding default assets
   - [STORE-182 ] - New Gadgets
   need banners/thumbnails
   - [STORE-187 ] - Cannot add new
   tags, only existing tags can be selected
   - [STORE-188 ] - Asset
   description need to be a textbox
   - [STORE-189 ] - footer wso2
   link has to be http://wso2.com not http://www.wso2.com
   - [STORE-190 ] - Charts has non
   functional right hand side controllers, lets remove them if not needed
   - [STORE-194 ] - 1px shift in
   publisher list view
   - [STORE-195 ] - Need pagination
   in store and page loading is really slow when there are large number of
   assets
   - [STORE-196 ] - Sites hover
   label says "Go To Microsite"
   - [STORE-197 ] - My Items page
   doesn't have the header texture
   - [STORE-198 ] - Re-factor RXT
   Managers in Store
   - [STORE-199 ] - adjust date
   range for asset stats
   - [STORE-202 ] - Ratings shown
   in My Gadgets are wrong
   - [STORE-203 ] - [Store] Get 404
   when viewing the gadget if it's created by a non-admin user and published
   by admin
   - [STORE-204 ] - A user
   belonging to Internal/reviewer role not allowed to publish an asset in
   in-review state
   - [STORE-205 ] - invalid asset
   URL appears while infinite scrolling
   - [STORE-206 ] - Do we need
   "Portal" role in ES?
   - [STORE-207 ] - ES admin
   console need to have the Store logo not UES logo
   - [STORE-208 ] - [Store] Wrong
   version information
   - [STORE-209 ] - version display
   issue after asset thumbs generated with infinite scrolling
   - [STORE-215 ] - Publisher:
   Asset title jump up/down based on the thumb image size
   - [STORE-217 ] - Adding MT
   features to RXTManager in publisher and store


*Improvements*

   - [STORE-186 ] - Publisher list
   view can only have the

Re: [Dev] SSO issue for tenant users

[Amila De Silva]

Hi,
Can't we take out the registry loading out of the sso hostobject and do it
from the acs.jag ? The thing is when populating the store/publisher for a
tenant we somehow have to load the tenant registry and doing it in the sso
hostobject would only incur an additional cost. When loading tenant
registries in store/publisher, we keep track of which registries have been
already loaded so when a different user from the same tenant logs in, we
can avoid loading it for a second time.

AmilaD


On Tue, Oct 8, 2013 at 7:35 PM, Sumedha Rubasinghe  wrote:

> How this is working for two web apps (store , publisher) in API Manager?
>
>
> On Tue, Oct 8, 2013 at 5:57 PM, Ranga Siriwardena  wrote:
>
>> Hi devs,
>>
>> We are using sso hostobject  for appfactory sso purpose. We encountered
>> $Subject when login as a tenant user. Following are the issues encountered.
>>
>> - tenant registry is not loaded during the signature validation phase
>> - decode method is not compatible  with encode mechanism
>>
>> We were able to get rid of this issue by loading tenant registry inside
>> hostobject (here we load tenant registry before signature validation) and
>> fixing decode method. Hope this issue will effect anyone who use sso
>> hostobject hence we need to commit this fix to current branch. Could some
>> one from IS team please review and commit this fix in[1].  Please let us
>> know if there is better ways to get rid of these issues as well.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-1858
>>
>> Thank You.
>> Ranga.
>> --
>> Ranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Amila De Silva*
*
*
*Software Engineer*
WSO2 Inc.*
*
mobile :(+94) 775119302
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Axiom test failure {axiom-osgi-run-1.2.11-wso2v4.jar is not a valid bundle}

[Eranda Sooriyabandara]

This was due to using JDK 7. These tests passed with JDK 6.

thanks
Eranda


On Tue, Oct 8, 2013 at 3:08 PM, Eranda Sooriyabandara wrote:

> Hi All,
> I am getting following failure when build kernel with tests on clean repo.
>
> thanks
> Eranda
>
> ---
>  T E S T S
> ---
> The current artifact axiom-osgi-run-1.2.11-wso2v4.jar is not a valid bundle
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/apache/servicemix/specs/org.apache.servicemix.specs.stax-api-1.0/1.1.1/org.apache.servicemix.specs.stax-api-1.0-1.1.1.jar
> (org.osgi.framewor
> dleException: Unresolved constraint in bundle 6: package;
> (package=javax.xml.transform))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 6:
> package; (package=javax.xml.transform)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.11-wso2v4/axiom-api-1.2.11-wso2v4.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bu
> 7: package; (package=org.w3c.dom))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
> package; (package=org.w3c.dom)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-impl/1.2.11-wso2v4/axiom-impl-1.2.11-wso2v4.jar
> (org.osgi.framework.BundleException: Unresolved constraint in
> e 7: package; (package=org.w3c.dom))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
> package; (package=org.w3c.dom)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-osgi-build/1.2.11-wso2v4/axiom-osgi-build-1.2.11-wso2v4.jar
> (org.osgi.framework.BundleException: Unresolved co
> int in bundle 7: package; (package=org.w3c.dom))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
> package; (package=org.w3c.dom)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-dom/1.2.11-wso2v4/axiom-dom-1.2.11-wso2v4.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bu
> 7: package; (package=org.w3c.dom))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
> package; (package=org.w3c.dom)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/codehaus/woodstox/stax2-api/3.0.1/stax2-api-3.0.1.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle 11:
> package; (pac
> javax.xml.transform.dom))
> org.osgi.framework.BundleException: Unresolved constraint in bundle 11:
> package; (package=javax.xml.transform.dom)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
> at
> org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
> at java.lang.Thread.run(Thread.java:722)
> ERROR: Error starting
> file:/D:/repo/.m2/repository/org/codehaus/woodstox/woodstox-core-asl/4.0.1/woodstox-core-asl-4.0.1.jar
> (org.osgi.framework.

Re: [Dev] org.wso2.carbon.application.deployer build failure in carbon kernel

[Eranda Sooriyabandara]

Hi Kicha,
Yeah, figured out. It worked with JDK 6.

thanks
Eranda


On Tue, Oct 8, 2013 at 8:50 PM, Kishanthan Thangarajah
wrote:

> Are you building with jdk 7?
>
>
>
> On Tue, Oct 8, 2013 at 6:35 PM, Eranda Sooriyabandara wrote:
>
>> Hi Sameera,
>> Any idea of the following compilation failure?
>>
>> thanks
>> Eranda
>>
>>
>> [ERROR] COMPILATION ERROR :
>> [INFO] -
>> [ERROR]
>> \carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
>> error: type IQ
>> uery does not take parameters
>> [INFO] 1 error
>> [INFO] -
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 3.096s
>> [INFO] Finished at: Tue Oct 08 18:28:52 IST 2013
>> [INFO] Final Memory: 22M/215M
>> [INFO]
>> 
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
>> (default-compile) on project org.wso2.carbon.application.deployer:
>> Compilation failure
>> [ERROR]
>> \carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
>> error: type IQ
>> uery does not take parameters
>> [ERROR] -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>>
>> --
>> *Eranda Sooriyabandara
>> *Senior Software Engineer;
>> Integration Technologies Team;
>> WSO2 Inc.; http://wso2.com
>> Lean . Enterprise . Middleware
>>
>> E-mail: eranda AT wso2.com
>> Mobile: +94 716 472 816
>> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
>> Blog: http://emsooriyabandara.blogspot.com/
>>
>>
>>
>> *
>> *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Kishanthan Thangarajah*
> Senior Software Engineer,
> Platform Technologies Team,
> WSO2, Inc.
> lean.enterprise.middleware
>
> Mobile - +94773426635
> Blog - *http://kishanthan.wordpress.com*
> Twitter - *http://twitter.com/kishanthan*
>



-- 
*Eranda Sooriyabandara
*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/



*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] org.wso2.carbon.application.deployer build failure in carbon kernel

[Kishanthan Thangarajah]

Are you building with jdk 7?



On Tue, Oct 8, 2013 at 6:35 PM, Eranda Sooriyabandara wrote:

> Hi Sameera,
> Any idea of the following compilation failure?
>
> thanks
> Eranda
>
>
> [ERROR] COMPILATION ERROR :
> [INFO] -
> [ERROR]
> \carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
> error: type IQ
> uery does not take parameters
> [INFO] 1 error
> [INFO] -
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 3.096s
> [INFO] Finished at: Tue Oct 08 18:28:52 IST 2013
> [INFO] Final Memory: 22M/215M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.application.deployer:
> Compilation failure
> [ERROR]
> \carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
> error: type IQ
> uery does not take parameters
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
>
> --
> *Eranda Sooriyabandara
> *Senior Software Engineer;
> Integration Technologies Team;
> WSO2 Inc.; http://wso2.com
> Lean . Enterprise . Middleware
>
> E-mail: eranda AT wso2.com
> Mobile: +94 716 472 816
> Linked-In: http://www.linkedin.com/in/erandasooriyabandara
> Blog: http://emsooriyabandara.blogspot.com/
>
>
>
> *
> *
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Kishanthan Thangarajah*
Senior Software Engineer,
Platform Technologies Team,
WSO2, Inc.
lean.enterprise.middleware

Mobile - +94773426635
Blog - *http://kishanthan.wordpress.com*
Twitter - *http://twitter.com/kishanthan*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SSO issue for tenant users

[Ranga Siriwardena]

On Tue, Oct 8, 2013 at 7:35 PM, Sumedha Rubasinghe  wrote:

> How this is working for two web apps (store , publisher) in API Manager?
>

This need to be tested. Since AM also depend on hostobject, store and
publisher also may fail with SSO.


>
>
> On Tue, Oct 8, 2013 at 5:57 PM, Ranga Siriwardena  wrote:
>
>> Hi devs,
>>
>> We are using sso hostobject  for appfactory sso purpose. We encountered
>> $Subject when login as a tenant user. Following are the issues encountered.
>>
>> - tenant registry is not loaded during the signature validation phase
>> - decode method is not compatible  with encode mechanism
>>
>> We were able to get rid of this issue by loading tenant registry inside
>> hostobject (here we load tenant registry before signature validation) and
>> fixing decode method. Hope this issue will effect anyone who use sso
>> hostobject hence we need to commit this fix to current branch. Could some
>> one from IS team please review and commit this fix in[1].  Please let us
>> know if there is better ways to get rid of these issues as well.
>>
>> [1] https://wso2.org/jira/browse/IDENTITY-1858
>>
>> Thank You.
>> Ranga.
>> --
>> Ranga Siriwardena
>> Software Engineer
>> WSO2 Inc.
>>
>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



Thank You.
Ranga.
-- 
Ranga Siriwardena
Software Engineer
Mobile: +94779808031
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server takes about 1 min to bootup

[Sumedha Rubasinghe]

On Tue, Oct 8, 2013 at 5:50 PM, Prabath Siriwardena wrote:

> Looks like someone has introduced Shiro ?
>

How could she do something bad as this? !!!


> Thanks & regards,
> -Prabath
>
>
> On Tue, Oct 8, 2013 at 4:28 PM, Nuwan Bandara  wrote:
>
>> Seems
>>
>> [2013-10-08 16:17:39,518]  INFO
>> {org.apache.shiro.config.IniSecurityManagerFactory} -  Realms have been
>> explicitly set on the SecurityManager instance - auto-setting of realms
>> will not occur.
>> [2013-10-08 16:17:39,964]  INFO {org.apache.shiro.realm.AuthorizingRealm}
>> -  No cache or cacheManager properties have been set.  Authorization cache
>> cannot be obtained.
>>
>> Above tasks seems to be the culprit. any idea ?
>>
>>
>> --
>> *Thanks & Regards,
>>
>> Nuwan Bandara
>> Technical Lead; **WSO2 Inc. *
>> *lean . enterprise . middleware |  http://wso2.com *
>> *blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 214
>> 5345
>> *
>> 
>>
>
>
>
> --
> Thanks & Regards,
> Prabath
>
> Mobile : +94 71 809 6732
>
> http://blog.facilelogin.com
> http://RampartFAQ.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] SSO issue for tenant users

[Sumedha Rubasinghe]

How this is working for two web apps (store , publisher) in API Manager?


On Tue, Oct 8, 2013 at 5:57 PM, Ranga Siriwardena  wrote:

> Hi devs,
>
> We are using sso hostobject  for appfactory sso purpose. We encountered
> $Subject when login as a tenant user. Following are the issues encountered.
>
> - tenant registry is not loaded during the signature validation phase
> - decode method is not compatible  with encode mechanism
>
> We were able to get rid of this issue by loading tenant registry inside
> hostobject (here we load tenant registry before signature validation) and
> fixing decode method. Hope this issue will effect anyone who use sso
> hostobject hence we need to commit this fix to current branch. Could some
> one from IS team please review and commit this fix in[1].  Please let us
> know if there is better ways to get rid of these issues as well.
>
> [1] https://wso2.org/jira/browse/IDENTITY-1858
>
> Thank You.
> Ranga.
> --
> Ranga Siriwardena
> Software Engineer
> WSO2 Inc.
>



-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [Build] Integration test failure in API Manager

[Krishantha Samaraweera]

Hi Sanjeewa,

Is this issue still there. it seems like server hasn't got started
within 18ms.
Did you try to manually start the server ?

Thanks,


On Sat, Oct 5, 2013 at 6:11 AM, Sanjeewa Malalgoda wrote:

> I ran user creation and server start up manually and everything works fine
> in last pack. Following content was there in  userList.csv file. I guess
> we need to debug and see what went wrong. Thanks for your input.
>
> "0","admin","admin"
> "1","adminuser","adminuser"
> "2","testuser2","testuser2"
> "3","testuser3","testuser3"
> "4","testuser4","testuser4"
> "5","testuser5","testuser5"
> "6","testuser6","testuser6"
> "7","testuser7","testuser7"
> "8","testuser8","testuser8"
> "9","testuser9","testuser9"
> "10","testuser10","testuser10"
> "11","testuser11","testuser12"
> "12","testuser12","testuser12"
> "13","testuser13","testuser13"
> "14","testuser14","testuser14"
> "15","testuser15","testuser15"
>
>
> Thanks,
> sanjeewa.
>
>
> On Sat, Oct 5, 2013 at 10:51 AM, Nuwan Wimalasekara wrote:
>
>> This is because of Login request  from test framework failed. Can you
>> please check the server startup and login manually. and also please check
>> the username and password in userList.csv in tests directory.  if those are
>> correct we need to debug the authentication service call in Test framework.
>>
>> Thanks,
>> Nuwanw
>>
>>
>> On Sat, Oct 5, 2013 at 10:26 AM, Sanjeewa Malalgoda wrote:
>>
>>> Getting same in ESB 4.8.0 as well.
>>>
>>> Thanks,
>>> sanjeewa.
>>>
>>>
>>> On Sat, Oct 5, 2013 at 9:57 AM, Sanjeewa Malalgoda wrote:
>>>
 Hi,
 Following error is getting when we build api manager with tests we are
 seeing similar issue in CEP as well. Any idea about this issue?

 Thanks,
 sanjeewa.


 [2013-10-05 04:19:19,456]  INFO
 {org.wso2.carbon.automation.core.utils.ClientConnectionUtil} -
  Successfully connected to the server on port 9443
 org.apache.maven.surefire.util.SurefireReflectionException:
 java.lang.reflect.InvocationTargetException; nested exception is
 java.lang.reflect.InvocationTargetException: null
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
  at
 org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
 at
 org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
  at
 org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
 at
 org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
  at
 org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
 Caused by: java.lang.RuntimeException: Could not login to Carbon server
 within 18ms. port=9443
  at
 org.wso2.carbon.automation.core.utils.ClientConnectionUtil.waitForLogin(ClientConnectionUtil.java:66)
 at
 org.wso2.carbon.automation.core.utils.serverutils.ServerUtils.startServerUsingCarbonHome(ServerUtils.java:143)
  at
 org.wso2.carbon.automation.core.ServerGroupManager.startServer(ServerGroupManager.java:92)
 at
 org.wso2.carbon.automation.core.ServerGroupManager.startServersForBuilder(ServerGroupManager.java:98)
  at
 org.wso2.carbon.automation.core.PlatformExecutionManager.startSevers(PlatformExecutionManager.java:187)
 at
 org.wso2.carbon.automation.core.PlatformExecutionManager.onExecutionStart(PlatformExecutionManager.java:76)
  at org.testng.TestNG.runExecutionListeners(TestNG.java:1032)
 at org.testng.TestNG.run(TestNG.java:983)
  at
 org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:178)
 at
 org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
  at
 org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:96)
 ... 9 more
 [2013-10-05 04:19:21,501]  INFO
 {org.wso2.carbon.automation.core.utils.serverutils.ServerUtils} -  Shutting
 down server..

 Results :

 Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

 [INFO]
 
 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 API Manager - Styles . SUCCESS
 [2.582s]
 [INFO] WSO2 Stratos  API Manager - UI styles . SUCCESS
 [1.817s]
 [INFO] WSO2 API Manager - Styles Parent .. SUCCESS
 [0.108s]
 [INFO] WSO2 Stratos  API Manager - Dashboard UI .. SUCCESS
 [2.424s]
 [INFO] WSO2 AM - Login User Interface  SUCCESS
 [1.000s]
 [INFO]

[Dev] org.wso2.carbon.application.deployer build failure in carbon kernel

[Eranda Sooriyabandara]

Hi Sameera,
Any idea of the following compilation failure?

thanks
Eranda


[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
\carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
error: type IQ
uery does not take parameters
[INFO] 1 error
[INFO] -
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 3.096s
[INFO] Finished at: Tue Oct 08 18:28:52 IST 2013
[INFO] Final Memory: 22M/215M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.application.deployer:
Compilation failure
[ERROR]
\carbon\kernel\branches\4.2.0\patches\patch0001\core\org.wso2.carbon.application.deployer\4.2.0\src\main\java\org\wso2\carbon\application\deployer\AppDeployerUtils.java:[558,14]
error: type IQ
uery does not take parameters
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]

-- 
*Eranda Sooriyabandara
*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/



*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] SSO issue for tenant users

[Ranga Siriwardena]

Hi devs,

We are using sso hostobject  for appfactory sso purpose. We encountered
$Subject when login as a tenant user. Following are the issues encountered.

- tenant registry is not loaded during the signature validation phase
- decode method is not compatible  with encode mechanism

We were able to get rid of this issue by loading tenant registry inside
hostobject (here we load tenant registry before signature validation) and
fixing decode method. Hope this issue will effect anyone who use sso
hostobject hence we need to commit this fix to current branch. Could some
one from IS team please review and commit this fix in[1].  Please let us
know if there is better ways to get rid of these issues as well.

[1] https://wso2.org/jira/browse/IDENTITY-1858

Thank You.
Ranga.
-- 
Ranga Siriwardena
Software Engineer
WSO2 Inc.


patch.diff
Description: Binary data
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Server takes about 1 min to bootup

[Prabath Siriwardena]

Looks like someone has introduced Shiro ?

Thanks & regards,
-Prabath


On Tue, Oct 8, 2013 at 4:28 PM, Nuwan Bandara  wrote:

> Seems
>
> [2013-10-08 16:17:39,518]  INFO
> {org.apache.shiro.config.IniSecurityManagerFactory} -  Realms have been
> explicitly set on the SecurityManager instance - auto-setting of realms
> will not occur.
> [2013-10-08 16:17:39,964]  INFO {org.apache.shiro.realm.AuthorizingRealm}
> -  No cache or cacheManager properties have been set.  Authorization cache
> cannot be obtained.
>
> Above tasks seems to be the culprit. any idea ?
>
>
> --
> *Thanks & Regards,
>
> Nuwan Bandara
> Technical Lead; **WSO2 Inc. *
> *lean . enterprise . middleware |  http://wso2.com *
> *blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 214
> 5345
> *
> 
>



-- 
Thanks & Regards,
Prabath

Mobile : +94 71 809 6732

http://blog.facilelogin.com
http://RampartFAQ.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Developer Studio 3.3.0 Alpha Released!

[Asanka Sanjeewa]

Hi All,

We have WSO2 Developer Studio 3.3.0 Alpha version  ready to be downloaded
at [1]. Installed eclipse distributions available at [2].

This release includes following improvement and bug fixes.

Improvement

   - [TOOLS-2017 ] -
   Deserialization logic for cloud connectors.\


Bug Fixes

   - [TOOLS-1608 ] - Entitlement
   Mediator has been changed those new changes does not available in DevS
   - [TOOLS-1717 ] - [Dev
   Studio-3.2] - REST API Resources Medaitor cannot be added to design view
   - [TOOLS-1720 ] - Developer
   Studio erases outSequence from Proxy Service
   - [TOOLS-1739 ] - Unable to
   refer endpoint template from proxy service
   - [TOOLS-1758 ] - Template Name
   does not appear in the config when creating an address endpoint template
   - [TOOLS-1764 ] - Typos in
   AppFactory tooling
   - [TOOLS-1852 ] - Cannot give
   xml body for Header Mediator
   - [TOOLS-1873 ] -
   markforsuspension property is missing
   - [TOOLS-1874 ] - Mediator flow
   break when it has dynamic or registry refer sequence
   - [TOOLS-1911 ] - Defined
   Endpoints do not appear in Sequence Creation
   - [TOOLS-1937 ] - Dev Studio
   does not support "returnRequestStatus" DSS param with REST resource
   - [TOOLS-1963 ] - ESB graphical
   editor doesn't allow to add a drop mediator
   - [TOOLS-1964 ] - Scroll bars
   appear when a Switch mediator is added
   - [TOOLS-1965 ] - ESB graphical
   editor allows to move first Drop mediator added
   - [TOOLS-1967 ] - Entitlement
   mediator serialization fails
   - [TOOLS-1971 ] - Http Endpoint
   - leaving URI Template null, returns a meaningless error message
   - [TOOLS-1982 ] - Location of
   the Send Mediator is incorrect
   - [TOOLS-1985 ] - Imported
   LoadBalancing-EP fails to open
   - [TOOLS-1987 ] - Serialization
   issue in Recipient List
   - [TOOLS-1990 ] -
   [Connector-Tool] Twitter connector source rendering invalid
   - [TOOLS-1991 ] - Exception on
   Scheduled Task property change
   - [TOOLS-1993 ] - Issue in
   rearranging the mediators in ESB Graphical Editor
   - [TOOLS-1994 ] - Exception
   occurs when adding a Drop Mediator
   - [TOOLS-1995 ] -
   [Connector-Tool] Default Configuration created in local entry
   - [TOOLS-1998 ] - An exception
   occurs when trying to undo the changes made in the ESB Graphical Editor
   - [TOOLS-1999 ] - Source is
   missing after importing a synapse configuration and exception occurs while
   trying to modify the source
   - [TOOLS-2000 ] - Issue in
   resizing the Iterator Mediator when importing a synapse configuration
   - [TOOLS-2001 ] - Import
   Mediator Issue from Developer Studio 3.2
   - [TOOLS-2002 ] - Warning is
   not displaying when trying to add a Log after the Send Mediator
   - [TOOLS-2004 ] - ESB editor
   fails to display a Switch mediator which has a bigger number of cases.
   - [TOOLS-2007 ] - When
   deserializing, the Class Mediator is not connnecting properly
   - [TOOLS-2008 ] - An already
   existing sequence is emptied in Design view when the corresponding Sequence
   mediator is double clicked
   - [TOOLS-2010 ] - Filter
   Mediator cannot vertically resize
   - [TOOLS-2011 ] - Scroll bars
   in REST API Resource
   - [TOOLS-2012 ] - ESB graphical
   editor fails to arrange mediators properly in a Template
   - [TOOLS-2014 ] - Respond
   mediator: Reverse property doesn't get serialized
   - [TOOLS-2018 ] -
   IndexOutOfBoundsException thrown when op

Re: [Dev] [GReg] Server Startup Error in todays packs

[Shavantha Weerasinghe]

hi

yes saw this issue coming on startup
regards,
Shavantha Weerasinghe
Senior Software Engineer QA
WSO2, Inc.
lean.enterprise.middleware.
http://wso2.com
http://wso2.org
Tel : 94 11 214 5345
Fax :94 11 2145300



On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga  wrote:
> Hi all,
> I am seeing this in the today's packs. Have anybody else seeing this in
> today's packs.
>
>
> 2013-10-08 09:49:41,888]  INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
> service: WorkListService {super-tenant}
> [2013-10-08 09:49:42,407]  INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
> service: DiscoveryProxy {super-tenant}
> [2013-10-08 09:49:45,106] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
> Version: 4.2.1, ID: 384
> java.lang.IllegalStateException
> at
> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
> at org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
> at
> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
> at
> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
> at
> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
> at
> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
> at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at
> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at
> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at
> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
> at
> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
> at
> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
> at
> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
> at
> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServlet.java:38)
> at
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1267)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(S

Re: [Dev] [GReg] Server Startup Error in todays packs

[Subash Chaturanga]

OK, Sure will do in the next build.


On Tue, Oct 8, 2013 at 4:36 PM, Kishanthan Thangarajah
wrote:

> Subash,
>
> Please start a fresh build updating kernel as-well.
>
> Thanks,
> Kishanthan.
>
>
> On Tue, Oct 8, 2013 at 3:45 PM, Manoj Kumara  wrote:
>
>> Change is reverted with r187598 form patch0001.
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Tue, Oct 8, 2013 at 3:40 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>>
>>>
>>>
>>> On Tue, Oct 8, 2013 at 3:28 PM, Nandika Jayawardana wrote:
>>>
 Previosly, In Axis2ServiceRegistry.processWSDL method, its was
 calculating the wsdl path incorrectly and hence was not processing wsdls
 packed in the bundles. A fix was done for this since BPS uses some wsdls
 with useOriginalwsdl=true option.

 The actual problem is these error producing bundles are packing wsdls
 which throw exception when being processed by axiom. They were
 working because, those wsdl's were not processed previously due to
 incorrect path.

>>>
>>> Yes. But, since this may break some other bundles which contain wsdl's,
>>> we will have to skip this fix for chunk-02 and fix it for chunk-03
>>> properly. We will revert this fix for now.
>>>
>>>
>>>
 Regards
 Nandika


 On Tue, Oct 8, 2013 at 3:13 PM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> Found the issue. We have added a fix (correct) to read the wsdl files
> from bundles. This causes the above error. We will have to properly fix
> this.
>
>
> On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> I'll have a look.
>>
>> Kishanthan.
>>
>>
>> On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga 
>> wrote:
>>
>>> Hi all,
>>> I am seeing this in the today's packs. Have anybody else seeing this
>>> in today's packs.
>>>
>>>
>>> 2013-10-08 09:49:41,888]  INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying 
>>> Axis2
>>> service: WorkListService {super-tenant}
>>> [2013-10-08 09:49:42,407]  INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying 
>>> Axis2
>>> service: DiscoveryProxy {super-tenant}
>>> [2013-10-08 09:49:45,106] ERROR
>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error 
>>> building
>>> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
>>> Version: 4.2.1, ID: 384
>>> java.lang.IllegalStateException
>>> at
>>> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
>>>  at
>>> org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
>>> at
>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
>>>  at
>>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
>>> at
>>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
>>>  at
>>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
>>> at
>>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
>>>  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
>>> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
>>>  at
>>> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
>>>  at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>  at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>  at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.ecl

Re: [Dev] [GReg] Server Startup Error in todays packs

[Kishanthan Thangarajah]

Subash,

Please start a fresh build updating kernel as-well.

Thanks,
Kishanthan.


On Tue, Oct 8, 2013 at 3:45 PM, Manoj Kumara  wrote:

> Change is reverted with r187598 form patch0001.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Tue, Oct 8, 2013 at 3:40 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>>
>>
>>
>> On Tue, Oct 8, 2013 at 3:28 PM, Nandika Jayawardana wrote:
>>
>>> Previosly, In Axis2ServiceRegistry.processWSDL method, its was
>>> calculating the wsdl path incorrectly and hence was not processing wsdls
>>> packed in the bundles. A fix was done for this since BPS uses some wsdls
>>> with useOriginalwsdl=true option.
>>>
>>> The actual problem is these error producing bundles are packing wsdls
>>> which throw exception when being processed by axiom. They were
>>> working because, those wsdl's were not processed previously due to
>>> incorrect path.
>>>
>>
>> Yes. But, since this may break some other bundles which contain wsdl's,
>> we will have to skip this fix for chunk-02 and fix it for chunk-03
>> properly. We will revert this fix for now.
>>
>>
>>
>>> Regards
>>> Nandika
>>>
>>>
>>> On Tue, Oct 8, 2013 at 3:13 PM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 Found the issue. We have added a fix (correct) to read the wsdl files
 from bundles. This causes the above error. We will have to properly fix
 this.


 On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah <
 kishant...@wso2.com> wrote:

> I'll have a look.
>
> Kishanthan.
>
>
> On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga wrote:
>
>> Hi all,
>> I am seeing this in the today's packs. Have anybody else seeing this
>> in today's packs.
>>
>>
>> 2013-10-08 09:49:41,888]  INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying 
>> Axis2
>> service: WorkListService {super-tenant}
>> [2013-10-08 09:49:42,407]  INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying 
>> Axis2
>> service: DiscoveryProxy {super-tenant}
>> [2013-10-08 09:49:45,106] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
>> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
>> Version: 4.2.1, ID: 384
>> java.lang.IllegalStateException
>> at
>> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
>>  at
>> org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
>> at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
>>  at
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
>> at
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
>>  at
>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
>> at
>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
>>  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
>> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
>>  at
>> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
>>  at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>  at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.I

[Dev] Server takes about 1 min to bootup

[Nuwan Bandara]

Seems

[2013-10-08 16:17:39,518]  INFO
{org.apache.shiro.config.IniSecurityManagerFactory} -  Realms have been
explicitly set on the SecurityManager instance - auto-setting of realms
will not occur.
[2013-10-08 16:17:39,964]  INFO {org.apache.shiro.realm.AuthorizingRealm} -
 No cache or cacheManager properties have been set.  Authorization cache
cannot be obtained.

Above tasks seems to be the culprit. any idea ?


-- 
*Thanks & Regards,

Nuwan Bandara
Technical Lead; **WSO2 Inc. *
*lean . enterprise . middleware |  http://wso2.com *
*blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 214 5345
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [GReg] Server Startup Error in todays packs

[Manoj Kumara]

Change is reverted with r187598 form patch0001.

Thanks,
Manoj

Best Regards..


Manoj Kumara
Software Engineer
WSO2, Inc.; http://wso2.com

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188


On Tue, Oct 8, 2013 at 3:40 PM, Kishanthan Thangarajah
wrote:

>
>
>
> On Tue, Oct 8, 2013 at 3:28 PM, Nandika Jayawardana wrote:
>
>> Previosly, In Axis2ServiceRegistry.processWSDL method, its was
>> calculating the wsdl path incorrectly and hence was not processing wsdls
>> packed in the bundles. A fix was done for this since BPS uses some wsdls
>> with useOriginalwsdl=true option.
>>
>> The actual problem is these error producing bundles are packing wsdls
>> which throw exception when being processed by axiom. They were
>> working because, those wsdl's were not processed previously due to
>> incorrect path.
>>
>
> Yes. But, since this may break some other bundles which contain wsdl's, we
> will have to skip this fix for chunk-02 and fix it for chunk-03 properly.
> We will revert this fix for now.
>
>
>
>> Regards
>> Nandika
>>
>>
>> On Tue, Oct 8, 2013 at 3:13 PM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> Found the issue. We have added a fix (correct) to read the wsdl files
>>> from bundles. This causes the above error. We will have to properly fix
>>> this.
>>>
>>>
>>> On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah <
>>> kishant...@wso2.com> wrote:
>>>
 I'll have a look.

 Kishanthan.


 On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga wrote:

> Hi all,
> I am seeing this in the today's packs. Have anybody else seeing this
> in today's packs.
>
>
> 2013-10-08 09:49:41,888]  INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
> service: WorkListService {super-tenant}
> [2013-10-08 09:49:42,407]  INFO
> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
> service: DiscoveryProxy {super-tenant}
> [2013-10-08 09:49:45,106] ERROR
> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
> Version: 4.2.1, ID: 384
> java.lang.IllegalStateException
> at
> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
>  at
> org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
>  at
> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
> at
> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
>  at
> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
> at
> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
>  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
>  at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
>  at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
> at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>  at
> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
> at
> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
> at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>  at
> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
> at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>  at
> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at
> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>  at
> org.eclipse.equinox.internal.ds.SCRManager.servi

Re: [Dev] [GReg] Server Startup Error in todays packs

[Kishanthan Thangarajah]

On Tue, Oct 8, 2013 at 3:28 PM, Nandika Jayawardana wrote:

> Previosly, In Axis2ServiceRegistry.processWSDL method, its was calculating
> the wsdl path incorrectly and hence was not processing wsdls packed in the
> bundles. A fix was done for this since BPS uses some wsdls with
> useOriginalwsdl=true option.
>
> The actual problem is these error producing bundles are packing wsdls
> which throw exception when being processed by axiom. They were
> working because, those wsdl's were not processed previously due to
> incorrect path.
>

Yes. But, since this may break some other bundles which contain wsdl's, we
will have to skip this fix for chunk-02 and fix it for chunk-03 properly.
We will revert this fix for now.



> Regards
> Nandika
>
>
> On Tue, Oct 8, 2013 at 3:13 PM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> Found the issue. We have added a fix (correct) to read the wsdl files
>> from bundles. This causes the above error. We will have to properly fix
>> this.
>>
>>
>> On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah <
>> kishant...@wso2.com> wrote:
>>
>>> I'll have a look.
>>>
>>> Kishanthan.
>>>
>>>
>>> On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga wrote:
>>>
 Hi all,
 I am seeing this in the today's packs. Have anybody else seeing this in
 today's packs.


 2013-10-08 09:49:41,888]  INFO
 {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
 service: WorkListService {super-tenant}
 [2013-10-08 09:49:42,407]  INFO
 {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
 service: DiscoveryProxy {super-tenant}
 [2013-10-08 09:49:45,106] ERROR
 {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
 service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
 Version: 4.2.1, ID: 384
 java.lang.IllegalStateException
 at
 org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
  at
 org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
 at
 org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
  at
 org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
 at
 org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
  at
 org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
 at
 org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
 at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
  at
 org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
 at
 org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
  at
 org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
 at
 org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
  at
 org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
 at
 org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
  at
 org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
 at
 org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
 at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
  at
 org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
 at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
  at
 org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
 at
 org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
  at
 org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
 at
 org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
  at
 org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
 at
 org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
  at
>

Re: [Dev] [GReg] Server Startup Error in todays packs

[Nandika Jayawardana]

Previosly, In Axis2ServiceRegistry.processWSDL method, its was calculating
the wsdl path incorrectly and hence was not processing wsdls packed in the
bundles. A fix was done for this since BPS uses some wsdls with
useOriginalwsdl=true option.

The actual problem is these error producing bundles are packing wsdls which
throw exception when being processed by axiom. They were working because,
those wsdl's were not processed previously due to incorrect path.

Regards
Nandika


On Tue, Oct 8, 2013 at 3:13 PM, Kishanthan Thangarajah
wrote:

> Found the issue. We have added a fix (correct) to read the wsdl files from
> bundles. This causes the above error. We will have to properly fix this.
>
>
> On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah <
> kishant...@wso2.com> wrote:
>
>> I'll have a look.
>>
>> Kishanthan.
>>
>>
>> On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga wrote:
>>
>>> Hi all,
>>> I am seeing this in the today's packs. Have anybody else seeing this in
>>> today's packs.
>>>
>>>
>>> 2013-10-08 09:49:41,888]  INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
>>> service: WorkListService {super-tenant}
>>> [2013-10-08 09:49:42,407]  INFO
>>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
>>> service: DiscoveryProxy {super-tenant}
>>> [2013-10-08 09:49:45,106] ERROR
>>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
>>> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
>>> Version: 4.2.1, ID: 384
>>> java.lang.IllegalStateException
>>> at
>>> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
>>>  at
>>> org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
>>> at
>>> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
>>>  at
>>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
>>> at
>>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
>>>  at
>>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
>>> at
>>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
>>>  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
>>> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
>>>  at
>>> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
>>>  at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
>>> at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>>  at
>>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>>> at
>>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>>  at
>>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>>> at
>>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>> at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>  at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>>> at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>>  at
>>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>>> at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>>  at
>>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>>> at
>>> org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>>  at
>>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>>  at
>>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>>> at
>>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>>  at
>>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>>> at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>>  at
>>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>>> at
>>> org.eclipse.osgi.internal.servicereg

Re: [Dev] [GReg] Server Startup Error in todays packs

[Kishanthan Thangarajah]

Found the issue. We have added a fix (correct) to read the wsdl files from
bundles. This causes the above error. We will have to properly fix this.


On Tue, Oct 8, 2013 at 11:30 AM, Kishanthan Thangarajah  wrote:

> I'll have a look.
>
> Kishanthan.
>
>
> On Tue, Oct 8, 2013 at 10:05 AM, Subash Chaturanga wrote:
>
>> Hi all,
>> I am seeing this in the today's packs. Have anybody else seeing this in
>> today's packs.
>>
>>
>> 2013-10-08 09:49:41,888]  INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
>> service: WorkListService {super-tenant}
>> [2013-10-08 09:49:42,407]  INFO
>> {org.wso2.carbon.core.deployment.DeploymentInterceptor} -  Deploying Axis2
>> service: DiscoveryProxy {super-tenant}
>> [2013-10-08 09:49:45,106] ERROR
>> {org.wso2.carbon.utils.deployment.Axis2ServiceRegistry} -  Error building
>> service from bundle : Symbolic Name: org.wso2.carbon.statistics,Bundle
>> Version: 4.2.1, ID: 384
>> java.lang.IllegalStateException
>> at
>> org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.getCharacterEncodingScheme(SJSXPStreamReaderWrapper.java:39)
>>  at
>> org.apache.axiom.om.impl.builder.StAXBuilder.(StAXBuilder.java:126)
>> at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.(StAXOMBuilder.java:104)
>>  at
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createStAXOMBuilder(AbstractOMMetaFactory.java:59)
>> at
>> org.apache.axiom.om.impl.AbstractOMMetaFactory.createOMBuilder(AbstractOMMetaFactory.java:69)
>>  at
>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:88)
>> at
>> org.apache.axiom.om.OMXMLBuilderFactory.createOMBuilder(OMXMLBuilderFactory.java:73)
>>  at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:590)
>> at org.apache.axis2.util.XMLUtils.toOM(XMLUtils.java:575)
>>  at
>> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(ArchiveReader.java:337)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.processWSDL(Axis2ServiceRegistry.java:302)
>>  at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.addServices(Axis2ServiceRegistry.java:184)
>> at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:102)
>>  at
>> org.wso2.carbon.utils.deployment.Axis2ServiceRegistry.register(Axis2ServiceRegistry.java:89)
>> at
>> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:473)
>>  at
>> org.wso2.carbon.core.init.CarbonServerManager.start(CarbonServerManager.java:219)
>> at
>> org.wso2.carbon.core.internal.CarbonCoreServiceComponent.activate(CarbonCoreServiceComponent.java:74)
>>  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>  at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponent.activate(ServiceComponent.java:260)
>> at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.activate(ServiceComponentProp.java:146)
>>  at
>> org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:347)
>> at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
>>  at
>> org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
>> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
>>  at
>> org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
>> at
>> org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:107)
>>  at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:861)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>>  at
>> org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:819)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:771)
>> at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:130)
>>  at
>> org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:214)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.registerService(BundleContextImpl.java:433)
>>  at
>> org.eclipse.equinox.http.servlet.internal.Activator.registerHttpService(Activator.java:81)
>> at
>> org.eclipse.equinox.http.servlet.internal.Activator.addProxyServlet(Activator.java:60)
>>  at
>> org.eclipse.equinox.http.servlet.internal.ProxyServlet.init(ProxyServlet.java:40)
>> at
>> org.wso2.carbon.tomcat.ext.servlet.DelegationServlet.init(DelegationServle

[Dev] Axiom test failure {axiom-osgi-run-1.2.11-wso2v4.jar is not a valid bundle}

[Eranda Sooriyabandara]

Hi All,
I am getting following failure when build kernel with tests on clean repo.

thanks
Eranda

---
 T E S T S
---
The current artifact axiom-osgi-run-1.2.11-wso2v4.jar is not a valid bundle
ERROR: Error starting
file:/D:/repo/.m2/repository/org/apache/servicemix/specs/org.apache.servicemix.specs.stax-api-1.0/1.1.1/org.apache.servicemix.specs.stax-api-1.0-1.1.1.jar
(org.osgi.framewor
dleException: Unresolved constraint in bundle 6: package;
(package=javax.xml.transform))
org.osgi.framework.BundleException: Unresolved constraint in bundle 6:
package; (package=javax.xml.transform)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-api/1.2.11-wso2v4/axiom-api-1.2.11-wso2v4.jar
(org.osgi.framework.BundleException: Unresolved constraint in bu
7: package; (package=org.w3c.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
package; (package=org.w3c.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-impl/1.2.11-wso2v4/axiom-impl-1.2.11-wso2v4.jar
(org.osgi.framework.BundleException: Unresolved constraint in
e 7: package; (package=org.w3c.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
package; (package=org.w3c.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-osgi-build/1.2.11-wso2v4/axiom-osgi-build-1.2.11-wso2v4.jar
(org.osgi.framework.BundleException: Unresolved co
int in bundle 7: package; (package=org.w3c.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
package; (package=org.w3c.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/apache/ws/commons/axiom/axiom-dom/1.2.11-wso2v4/axiom-dom-1.2.11-wso2v4.jar
(org.osgi.framework.BundleException: Unresolved constraint in bu
7: package; (package=org.w3c.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 7:
package; (package=org.w3c.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/codehaus/woodstox/stax2-api/3.0.1/stax2-api-3.0.1.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle 11:
package; (pac
javax.xml.transform.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 11:
package; (package=javax.xml.transform.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:984)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:263)
at java.lang.Thread.run(Thread.java:722)
ERROR: Error starting
file:/D:/repo/.m2/repository/org/codehaus/woodstox/woodstox-core-asl/4.0.1/woodstox-core-asl-4.0.1.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle 1
ckage; (package=javax.xml.transform.dom))
org.osgi.framework.BundleException: Unresolved constraint in bundle 11:
package; (package=javax.xml.transform.dom)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3090)
at org.apache.felix.framework.Fe

Re: [Dev] InitialContext.lookup failed to find an already created topic, if it isn't specified in the jndi.properties file

[Shammi Jayasinghe]

Hi Nirmal,

Thank you for the explanation. I think you are doing the same thing which
we have done in our JMS transport. How ever , if would be great if you can
attach your client in this case, because i need to verify that , entries in
your jndi.properties file is getting loaded in to the initial context.

Thanks
Shammi


On Tue, Oct 8, 2013 at 2:05 PM, Nirmal Fernando  wrote:

> Hi Shammi,
>
> * I'm using MB 2.1.0 and I've created a topic X there.
> * I've written a small JMS client to subscribe to a topic (same as MB's
> sample topic subscriber).
> * JMS client creates initial context after reading jndi.properties file.
> * In my jndi.properties file, I have;
>
> java.naming.factory.initial =
> org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>
> # use the following property to configure the default connector
> connectionfactory.topicConnectionfactory = amqp://admin:admin@clientID
> /carbon?brokerlist='tcp://10.100.1.154:5677'&reconnect='true'
>
> # use the following property to specify the JNDI name the connection
> factory
> # should appear as.
> connectionFactoryNames = connectionfactory, topicConnectionfactory
>
>
> * My subscriber lookup the initial context for this topic X. But it cannot
> be found (i.e. ctx.lookup(topicName) gives null).
> * Then, if I add my topic name to jndi.properties file;
>
> topic.X = X
>
> * ctx.lookup(topicName) correctly finds the topic.
>
> Am I doing something wrong?
>
>
> On Tue, Oct 8, 2013 at 11:32 AM, Shammi Jayasinghe wrote:
>
>> Hi Nirmal,
>>
>> Thanks for reporting this . Could you please send us more information on
>> this.
>>
>> Thanks
>> Shammi
>>
>>
>> On Tue, Oct 8, 2013 at 11:06 AM, Nirmal Fernando  wrote:
>>
>>> Hi All,
>>>
>>> Noticed $Subject when subscribing to a topic via a client.
>>>
>>> --
>>>
>>> Thanks & regards,
>>> Nirmal
>>>
>>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> Mobile: +94715779733
>>> Blog: http://nirmalfdo.blogspot.com/
>>>
>>>
>>
>>
>> --
>> Best Regards,*
>>
>> Shammi Jayasinghe*
>> Associate Tech Lead
>> WSO2, Inc.; http://wso2.com,
>> mobile: +94 71 4493085
>>
>>
>
>
> --
>
> Thanks & regards,
> Nirmal
>
> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
> Mobile: +94715779733
> Blog: http://nirmalfdo.blogspot.com/
>
>


-- 
Best Regards,*

Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +94 71 4493085
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] getContent in Jaggery doesn't return Base64 encoded data

[Dilshan Edirisuriya]

Hi,

Looked into the code. I believe if its application/json or
aplication/json/badgerfish the code looks ok. If the data is a stream IMO
this needs to be a Base64 encoded string rather than making it a string
using UTF-8.

Regards,

Dilshan


-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2Mobile
Mob: + 94 772245502
http://wso2mobile.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Hadoop 0.20.203.1-wso2v5 on 4.1.0 branch

[Malith Dhanushka]

Hi Maninda,

Thanks for the verification , will proceed with v6.


On Tue, Oct 8, 2013 at 2:17 PM, Maninda Edirisooriya wrote:

> Hi Malith,
>
> AFAIK v5 is a mistake. The correct one which is shipped with BAM is v4. v4
> has all the fixes in the v5. So neglect v5 and if you want to create a new
> version you need to create v6 which should be the modified version of v4.
>
> *
> Maninda Edirisooriya*
> Software Engineer
> *WSO2, Inc.
> *lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *Phone* : +94 777603226
>
>
> On Tue, Oct 8, 2013 at 2:04 PM, Malith Dhanushka  wrote:
>
>> Hi folks,
>>
>> I am going to add Hadoop dependency to 4.2.0 branch. As it seems
>> only 0.20.203.1-wso2v4 has been released with 4.1.0. But there is already a
>> 0.20.203.1-wso2v5 in 4.1.0 branch. Is there any special reason to
>> have 0.20.203.1-wso2v5 in 4.1.0 branch?
>>
>> Thanks,
>> Malith
>> --
>> Malith Dhanushka
>>
>> Engineer - Data Technologies
>> *WSO2, Inc. : wso2.com*
>>
>> *Mobile*  : +94 716 506 693
>>
>
>


-- 
Malith Dhanushka

Engineer - Data Technologies
*WSO2, Inc. : wso2.com*

*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is there an already available Email Executor for Greg?

[Chan]

We will have to write a custom executor to send an email- to trigger from
the lifecycle state change. Also we will have to send the dynamic email
parameters from promote method with a ThreadLocal. Also the promote method
is invoked via a jaggery code so we'll have to utilize the thread local in
jaggery. @Nuwan - is it possible to access ThreadLocal from jaggery?

Cheers


On Tue, Oct 8, 2013 at 11:35 AM, Shazni Nazeer  wrote:

> Hi Dulitha,
>
> Currently we don't have an email executor for asset life cycle change. But
> as far as I know there is way to invoke a particular service when a state
> change occurs.
>
> Shazni Nazeer
> Senior Software Engineer
>
> Mob: +94 715 440 607
>
>
> On Tue, Oct 8, 2013 at 11:07 AM, Chan  wrote:
>
>> Hi Nuwan,
>> The change LC state is triggered when ever a Life Cycle state is changed
>> - we can't capture per life cycle state change. Let me revise the
>> requirement - I want to fire off an email when an asset's life cycle state
>> change to X state.
>>
>> Cheers
>>
>>
>> On Tue, Oct 8, 2013 at 9:28 AM, Nuwan Silva  wrote:
>>
>>> Is this [1] what your looking for?
>>>
>>> *Change LC State* - Represents the event of changing a lifecycle state
>>>
>>> [1]
>>> http://docs.wso2.org/display/Governance460/Adding+a+Subscription#AddingaSubscription-AddSubscriptionOptions%C2%A0
>>>
>>>
>>> On Mon, Oct 7, 2013 at 10:40 PM, Chan  wrote:
>>>
 $subject? The requirement is to fire off an email when a state
 transition happens in asset in the Enterprise-Store.

 Cheers!
 --
 Chan (Dulitha Wijewantha)
 Software Engineer - Mobile Development
 WSO2Mobile
 Lean.Enterprise.Mobileware
  * ~Email   duli...@wso2mobile.com*
 *  ~Mobile +94712112165*
 *  ~Website   dulithawijewantha.com
 *
 *  ~Blog 
 blog.dulithawijewantha.com
 *
 *  ~Twitter @dulitharw *

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev


>>>
>>>
>>> --
>>> *
>>> *
>>> *Nuwan Silva
>>> *
>>> *Senior Software Engineer - QA*
>>> Mobile: +94779804543
>>>
>>> WSO2 Inc.
>>> lean . enterprise . middlewear.
>>> http://www.wso2.com
>>>
>>
>>
>>
>> --
>> Chan (Dulitha Wijewantha)
>> Software Engineer - Mobile Development
>> WSO2Mobile
>> Lean.Enterprise.Mobileware
>>  * ~Email   duli...@wso2mobile.com*
>> *  ~Mobile +94712112165*
>> *  ~Website   dulithawijewantha.com
>> *
>> *  ~Blog blog.dulithawijewantha.com
>> *
>> *  ~Twitter @dulitharw *
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>


-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2mobile.com*
*  ~Mobile +94712112165*
*  ~Website   dulithawijewantha.com
*
*  ~Blog blog.dulithawijewantha.com
*
*  ~Twitter @dulitharw *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Hadoop 0.20.203.1-wso2v5 on 4.1.0 branch

[Maninda Edirisooriya]

Hi Malith,

AFAIK v5 is a mistake. The correct one which is shipped with BAM is v4. v4
has all the fixes in the v5. So neglect v5 and if you want to create a new
version you need to create v6 which should be the modified version of v4.

*
Maninda Edirisooriya*
Software Engineer
*WSO2, Inc.
*lean.enterprise.middleware.

*Blog* : http://maninda.blogspot.com/
*Phone* : +94 777603226


On Tue, Oct 8, 2013 at 2:04 PM, Malith Dhanushka  wrote:

> Hi folks,
>
> I am going to add Hadoop dependency to 4.2.0 branch. As it seems
> only 0.20.203.1-wso2v4 has been released with 4.1.0. But there is already a
> 0.20.203.1-wso2v5 in 4.1.0 branch. Is there any special reason to
> have 0.20.203.1-wso2v5 in 4.1.0 branch?
>
> Thanks,
> Malith
> --
> Malith Dhanushka
>
> Engineer - Data Technologies
> *WSO2, Inc. : wso2.com*
>
> *Mobile*  : +94 716 506 693
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] require_once() function for Jaggery

[Dulitha Wijewantha]

+1 for the require_once method. The best example for this (since we are in
the javascript world) is requirejs. http://requirejs.org/. They have
mentioned that they support rhino runtime as well. Also I don't think it's
a bad design considering the fact that we are talking about scripting.
Scripting always has scenarios where you need to run a particular script
only once.

Cheers!


On Tue, Oct 8, 2013 at 1:18 PM, Dilshan Edirisuriya wrote:

> Hi,
>
> Is there anything similar to subject? Looked into the docs and could not
> find any.
>
> Above function is needed for cyclic module dependencies. I know its a bad
> design to implement such way but there are few scenarios this will be
> needed.
>
> 1) If there is cyclic dependencies we may have to come up with a common
> module. But if there lot of modules, the number of common modules can
> increase and it will end up being hard to manage.
>
> 2) We may have to add a function level module injection. Again this will
> have module inter-dependencies.
>
> PHP itself has this capability. Also NodeJS uses a cache in such a
> scenario when there is a dependency it will retrieved the previous object.
>
> Can we have such a function under Jaggery?
>
> Regards,
>
> Dilshan
>
>
> --
> Dilshan Edirisuriya
> Senior Software Engineer - WSO2Mobile
> Mob: + 94 772245502
> http://wso2mobile.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chan (Dulitha Wijewantha)
Software Engineer - Mobile Development
WSO2Mobile
Lean.Enterprise.Mobileware
 * ~Email   duli...@wso2.com *
*  ~Mobile +94712112165*
*  ~Website   dulithawijewantha.com
*
*  ~Blog blog.dulithawijewantha.com
*
*  ~Twitter @dulitharw *
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] InitialContext.lookup failed to find an already created topic, if it isn't specified in the jndi.properties file

[Nirmal Fernando]

Hi Shammi,

* I'm using MB 2.1.0 and I've created a topic X there.
* I've written a small JMS client to subscribe to a topic (same as MB's
sample topic subscriber).
* JMS client creates initial context after reading jndi.properties file.
* In my jndi.properties file, I have;

java.naming.factory.initial =
org.wso2.andes.jndi.PropertiesFileInitialContextFactory

# use the following property to configure the default connector
connectionfactory.topicConnectionfactory = amqp://admin:admin@clientID
/carbon?brokerlist='tcp://10.100.1.154:5677'&reconnect='true'

# use the following property to specify the JNDI name the connection factory
# should appear as.
connectionFactoryNames = connectionfactory, topicConnectionfactory


* My subscriber lookup the initial context for this topic X. But it cannot
be found (i.e. ctx.lookup(topicName) gives null).
* Then, if I add my topic name to jndi.properties file;

topic.X = X

* ctx.lookup(topicName) correctly finds the topic.

Am I doing something wrong?


On Tue, Oct 8, 2013 at 11:32 AM, Shammi Jayasinghe  wrote:

> Hi Nirmal,
>
> Thanks for reporting this . Could you please send us more information on
> this.
>
> Thanks
> Shammi
>
>
> On Tue, Oct 8, 2013 at 11:06 AM, Nirmal Fernando  wrote:
>
>> Hi All,
>>
>> Noticed $Subject when subscribing to a topic via a client.
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
> Best Regards,*
>
> Shammi Jayasinghe*
> Associate Tech Lead
> WSO2, Inc.; http://wso2.com,
> mobile: +94 71 4493085
>
>


-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Hadoop 0.20.203.1-wso2v5 on 4.1.0 branch

[Malith Dhanushka]

Hi folks,

I am going to add Hadoop dependency to 4.2.0 branch. As it seems
only 0.20.203.1-wso2v4 has been released with 4.1.0. But there is already a
0.20.203.1-wso2v5 in 4.1.0 branch. Is there any special reason to
have 0.20.203.1-wso2v5 in 4.1.0 branch?

Thanks,
Malith
-- 
Malith Dhanushka

Engineer - Data Technologies
*WSO2, Inc. : wso2.com*

*Mobile*  : +94 716 506 693
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Where can I find the documentation on available functions of a CEP window?

[Nirmal Fernando]

On Tue, Oct 8, 2013 at 11:40 AM, Rajeev Sampath  wrote:

> Hi Nirmal,
>
> Some suggestions for your use case:
> 1. use time windows with current-events and expired-events (expired event
> is the one that's get emitted at the end of the time - i.e the oldest,
> current event is the incoming one - i.e. the latest)
>
This won't work since there can be multiple expired events.


>  2. or use output rate limiting [1], you can extract first and last event
> in a given time period
>
> I don't think I can get both first and last events at the same time?!

>
>
> [1] http://docs.wso2.org/display/CEP300/Output+Rate+Limiting
>
> Thanks
>
>
> On Tue, Oct 8, 2013 at 11:20 AM, Nirmal Fernando  wrote:
>
>> Shavantha,
>>
>> Thanks for the reply.
>>
>> But what I want to get is the first and the last event within a period
>> of time. Counting would not help me.
>>
>>
>> On Tue, Oct 8, 2013 at 11:18 AM, Shavantha Weerasinghe <
>> shavan...@wso2.com> wrote:
>>
>>> Hi Nimal
>>>
>>>
>>>
>>> is it the time batch window concept [1] to identify the events that
>>> occur within a given time. Also counting patterns section on [2] which
>>> says "You can count the number of event occurrences of the same event
>>> stream with the minimum and maximum limits. "
>>>
>>> [1] http://docs.wso2.org/display/CEP210/Windows
>>> [2 ]http://docs.wso2.org/display/CEP210/Patterns
>>>
>>> Would these be useful
>>> regards,
>>> Shavantha Weerasinghe
>>> Senior Software Engineer QA
>>> WSO2, Inc.
>>> lean.enterprise.middleware.
>>> http://wso2.com
>>> http://wso2.org
>>> Tel : 94 11 214 5345
>>> Fax :94 11 2145300
>>>
>>>
>>>
>>> On Tue, Oct 8, 2013 at 10:52 AM, Nirmal Fernando 
>>> wrote:
>>> > $Subject please. I'd like to get the first and last event of a window.
>>> >
>>> > --
>>> >
>>> > Thanks & regards,
>>> > Nirmal
>>> >
>>> > Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>>> > Mobile: +94715779733
>>> > Blog: http://nirmalfdo.blogspot.com/
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google
>>> Groups
>>> > "WSO2 Documentation" group.
>>> > To unsubscribe from this group and stop receiving emails from it, send
>>> an
>>> > email to documentation+unsubscr...@wso2.com.
>>> > For more options, visit
>>> https://groups.google.com/a/wso2.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>>
>> Thanks & regards,
>> Nirmal
>>
>> Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
>> Mobile: +94715779733
>> Blog: http://nirmalfdo.blogspot.com/
>>
>>
>
>
> --
> Rajeev Sampath
> Senior Software Engineer
> WSO2, Inc.; http://www.wso2.com.
>
> Mobile:* +94716265766
> *
>



-- 

Thanks & regards,
Nirmal

Senior Software Engineer- Platform Technologies Team, WSO2 Inc.
Mobile: +94715779733
Blog: http://nirmalfdo.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Are we running integration tests against nightly builds

[Krishantha Samaraweera]

I believe human builders are not the solution for this. However RMs should
take the responsibility of building with integration tests until proper CI
server with smooth build process is available. I think most product teams
have dedicated machine for building, so how about scheduling a build at
night locally.

To have a better build process all should comply to follow the engineering
best practices. Most of the time build remain on broken state until hard
code freeze being done so it will never come up to product integration
level. I think we are already having some discussions on build
stabilization.

Thanks,


On Mon, Oct 7, 2013 at 9:44 PM, Shelan Perera  wrote:

> Hi,
>
> Are we running integration tests against new builds ? I am not up to date
> with new Carbon Context changes how it went. Do we have a process in place
> to keep the things monitored. I am bit worried since we realized the pain
> of rectifying things after went wrong :)
>
> Thanks
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* :   blog.shelan.org
> *Linked-i*n  :   http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* :https://twitter.com/#!/shelan
>
> *Mobile*  : +94 772 604 402
>
>


-- 
Krishantha Samaraweera
Senior Technical Lead - Test Automation
Mobile: +94 77 7759918
WSO2, Inc.; http://wso2.com/
lean . enterprise . middlewear.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] require_once() function for Jaggery

[Dilshan Edirisuriya]

Hi,

Is there anything similar to subject? Looked into the docs and could not
find any.

Above function is needed for cyclic module dependencies. I know its a bad
design to implement such way but there are few scenarios this will be
needed.

1) If there is cyclic dependencies we may have to come up with a common
module. But if there lot of modules, the number of common modules can
increase and it will end up being hard to manage.

2) We may have to add a function level module injection. Again this will
have module inter-dependencies.

PHP itself has this capability. Also NodeJS uses a cache in such a scenario
when there is a dependency it will retrieved the previous object.

Can we have such a function under Jaggery?

Regards,

Dilshan


-- 
Dilshan Edirisuriya
Senior Software Engineer - WSO2Mobile
Mob: + 94 772245502
http://wso2mobile.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Does Conditional Router Mediator allow child mediators?

[Asanka Sanjeewa]

Hi,

Clarified the $subject with ESB team. Since Conditional Router Mediator
doesn't allow child mediators inside, the graphical representation of the
mediator will be modified accordingly in Developer Studio ESB Graphical
Editor.

Thanks and Regards,
AsankaS.


On Thu, Oct 3, 2013 at 12:00 PM, Asanka Sanjeewa  wrote:

> Hi,
>
> ESB management console allows to add child mediators to the Conditional
> Router Mediator, but after the artifact is saved and come back child
> mediators of the Conditional Router Mediator will be disappeared.
>
> Developer Studio ESB Graphical Editor also allows to add child mediators
> to the Conditional Router Mediator, but synapse api doesn't support for
> child mediators in Conditional Router Mediator. Therefore it is not
> possible to serialize them under Conditional Router Mediator.
>
> Are we allow $subject?
>
> Thanks and Regards,
> AsankaS.
>
> --
> *Asanka Sanjeewa*
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
> Blog: http://asanka-tech-blog.blogspot.com/
>
>


-- 
*Asanka Sanjeewa*
Senior Software Engineer
Mobile: +94772532924
WSO2 Inc. http://wso2.com/
Blog: http://asanka-tech-blog.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Install features for ESB 4.6.0

[Udara Liyanage]

Hi,

As release matrix [1] suggest, the carbon version of the ESB 4.6.0 is
carbon 4.0.6. But I could not find a feature repository location for 4.0.6
in [2] .
What is the correct feature repository location ?

[1] http://wso2.com/products/carbon/release-matrix/
[2] http://dist.wso2.org/p2/carbon/releases/

-- 
Udara Liyanage
Software Engineer
WSO2, Inc.: http://wso2.com
lean. enterprise. middleware

web: http://udaraliyanage.wordpress.com
phone: +94 71 443 6897
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev