Re: [Dev] ESB 4.7.0 payloadFactory -- Some problems - Needs clarification

2013-07-16 Thread Susinda Perera
Hi Nalin
Thanks for the explanatory answer.

rdgs
susinda

On Wed, Jul 17, 2013 at 12:07 PM, Nalin Chandraratne  wrote:

> Hi Susinda,
>
> Please find comment inline.
>
>>
>>> Suppose we have a sample payloadFactory configuration as follows
>>>
>>> 
>>> json body
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>
>>>
>>> 1. Is there any use cases such that *media-type="json"* and <*arg
>>> evaluator="xml"*  will be used
>>>
>> "media-type" is to specify the type which will be used to compose the
> outgoing payload (json/xml) and "evaluator" is used to specify the type of
> the expression (JsonPath/Xpath) used. UseCase : Incoming XML and need to
> send a Different Json payload to BE which consist of some values extracted
> from the incoming XML.
>
>  2. Possible use case of *media-type="xml"* and <*arg 
> evaluator="json"*(opposite of the question one)
>>>
>>
> UseCase: when incoming payload is json and Steam Builders and Formatters
> are used, we use evaluator=json. The reason is, when the stream builders
> are enabled, content is set to a property JSON_STREAM and we have to
> extract the payload from that instead of taking it from the soap body.
> There we are using JsonPath to traverse the json object.
>
>>
>>> And some synapse code problems
>>> payloadFactoryMediator has has methods called getJsonPathArgumentList()
>>> and getXPathArgumentList(). I used these methods to access arguments, issue
>>> was the value type argument () is returned from both
>>> methods.
>>>
>>> 3. Is this a bug or intended behavior.
>>>
>>
> This is an intended behavior. We only read the arguments in the synapse
> config once, when the PF initialize. Then keep the two argument types
> separately in two Lists and use the appropriate one for the scenarios
> accordingly.
> Eg: if xml -> PF -> xml, we use getXpath..
>   if json -> PF -> json and stream BnF are enabled, we use
> getJsonPath..
> Values has to be there in both lists since it's common for both.
>
>
>>> And a suggestion
>>> 4 .How about giving the config something like follows (omitting the
>>> evaluator because in code level it is handled in that way). Hope this
>>> simplifies coding and understandability.
>>> 
>>> 
>>> 
>>> 
>>> 
>>
>>
> "evaluator" is used to distinguish different expression types. suppose we
> add more expression types in future, what makes more sense is keeping the
> arg type as expression and keep adding the different evaluator types.
>
>
> Thanks.
>
> --
> Nalin Chamara
> Software Engineer
> na...@wso2.com
> +94715614756
>



-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

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


Re: [Dev] ESB 4.7.0 payloadFactory -- Some problems - Needs clarification

2013-07-16 Thread Nalin Chandraratne
Hi Susinda,

Please find comment inline.

>
>> Suppose we have a sample payloadFactory configuration as follows
>>
>> 
>> json body
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>
>> 1. Is there any use cases such that *media-type="json"* and <*arg
>> evaluator="xml"*  will be used
>>
> "media-type" is to specify the type which will be used to compose the
outgoing payload (json/xml) and "evaluator" is used to specify the type of
the expression (JsonPath/Xpath) used. UseCase : Incoming XML and need to
send a Different Json payload to BE which consist of some values extracted
from the incoming XML.

2. Possible use case of *media-type="xml"* and <*arg
evaluator="json"*(opposite of the question one)
>>
>
UseCase: when incoming payload is json and Steam Builders and Formatters
are used, we use evaluator=json. The reason is, when the stream builders
are enabled, content is set to a property JSON_STREAM and we have to
extract the payload from that instead of taking it from the soap body.
There we are using JsonPath to traverse the json object.

>
>> And some synapse code problems
>> payloadFactoryMediator has has methods called getJsonPathArgumentList()
>> and getXPathArgumentList(). I used these methods to access arguments, issue
>> was the value type argument () is returned from both
>> methods.
>>
>> 3. Is this a bug or intended behavior.
>>
>
This is an intended behavior. We only read the arguments in the synapse
config once, when the PF initialize. Then keep the two argument types
separately in two Lists and use the appropriate one for the scenarios
accordingly.
Eg: if xml -> PF -> xml, we use getXpath..
  if json -> PF -> json and stream BnF are enabled, we use getJsonPath..
Values has to be there in both lists since it's common for both.


>> And a suggestion
>> 4 .How about giving the config something like follows (omitting the
>> evaluator because in code level it is handled in that way). Hope this
>> simplifies coding and understandability.
>> 
>> 
>> 
>> 
>> 
>
>
"evaluator" is used to distinguish different expression types. suppose we
add more expression types in future, what makes more sense is keeping the
arg type as expression and keep adding the different evaluator types.


Thanks.

-- 
Nalin Chamara
Software Engineer
na...@wso2.com
+94715614756
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.1.x > Platform 4.1.5 > #3 has FAILED. Change made by Ranga Siriwardena.

2013-07-16 Thread Deependra Ariyadewa
On Wed, Jul 17, 2013 at 11:37 AM, Ranga Siriwardena  wrote:

> Hi,
>
> Bamboo build failing on Storage Server p2 profile. Please have a look.
>

We need to deploy org.wso2.carbon:cassandra-explorer-feature:pom:4.1.0 to
Maven repository to solve this issue.

Shall I deploy this pom to nexus.

Thanks,

Deependra.

>
>
> 16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Features Parent
> . SUCCESS [0.003s]
> 16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - P2 Profile Generation
> ... FAILURE [0.951s]
> 16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Distribution
>  FAILURE [15.309s]
> 16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Aggregator Module
> ... SUCCESS [0.004s]
> 16-Jul-2013 22:42:29 [INFO] WSO2 Carbon - Patch releases - products -
> Aggregator Module  SUCCESS [0.003s]
> 16-Jul-2013 22:42:29 [INFO] WSO2 Carbon - Patch releases - Platform
> Automated Test Suite  SUCCESS [0.003s]
> 16-Jul-2013 22:42:29 [INFO]
> 
> 16-Jul-2013 22:42:29 [INFO] BUILD FAILURE
> 16-Jul-2013 22:42:29 [INFO]
> 
> 16-Jul-2013 22:42:29 [INFO] Total time: 1:15.418s
> 16-Jul-2013 22:42:29 [INFO] Finished at: Tue Jul 16 22:42:29 PDT 2013
> 16-Jul-2013 22:42:30 [INFO] Final Memory: 270M/1677M
> 16-Jul-2013 22:42:30 [INFO]
> 
> 16-Jul-2013 22:42:30 [ERROR] Failed to execute goal on project
> org.wso2.carbon.cassandra.explorer.feature: Could not resolve dependencies
> for project
> org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:pom:4.1.5:
> Failed to collect dependencies for
> [org.wso2.carbon:org.wso2.carbon.cassandra.explorer.server.feature:zip:4.1.5
> (compile),
> org.wso2.carbon:org.wso2.carbon.cassandra.explorer.ui.feature:zip:4.1.2
> (compile)]: Failed to read artifact descriptor for
> org.wso2.carbon:org.wso2.carbon.cassandra.explorer.ui.feature:zip:4.1.2:
> Failure to find org.wso2.carbon:cassandra-explorer-feature:pom:4.1.0 in
> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
> 16-Jul-2013 22:42:30 [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.2:p2-repo-gen (2-p2-repo-generation) on
> project wso2ss-p2-profile: Error occured when processing the Feature
> Artifact: org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:4.1.5:
> ERROR: Failure to find
> org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:zip:4.1.5 in
> http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
> local repository, resolution will not be reattempted until the update
> interval of wso2-nexus has elapsed or updates are forced
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] Try downloading the file manually from the
> project website.
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] Then, install it using the command:
> 16-Jul-2013 22:42:30 [ERROR] mvn install:install-file
> -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.cassandra.explorer.feature -Dversion=4.1.5
> -Dpackaging=zip -Dfile=/path/to/file
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] Alternatively, if you host your own
> repository you can deploy the file there:
> 16-Jul-2013 22:42:30 [ERROR] mvn deploy:deploy-file
> -DgroupId=org.wso2.carbon
> -DartifactId=org.wso2.carbon.cassandra.explorer.feature -Dversion=4.1.5
> -Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR]
> org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:zip:4.1.5
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] from the specified remote repositories:
> 16-Jul-2013 22:42:30 [ERROR] wso2-nexus (
> http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true,
> snapshots=true),
> 16-Jul-2013 22:42:30 [ERROR] central (http://repo1.maven.org/maven2,
> releases=true, snapshots=false)
> 16-Jul-2013 22:42:30 [ERROR] -> [Help 2]
> 16-Jul-2013 22:42:30 [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
> on project wso2ss: Failed to create assembly: Error adding file to archive:
> /home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB003-PLA006-JOB1/products/ss/1.0.3/modules/distribution/../p2-profile/target/wso2carbon-core-4.1.0/repository/conf/etc/logging-config.xml
> isn't a file. -> [Help 2]
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] To see the full stack trace of the errors,
> re-run Maven with the -e switch.
> 16-Jul-2013 22:42:30 [ERROR] Re-run Maven using the -X switch to enable
> full debug logging.
> 16-Jul-2013 22:42:30 [ERROR]
> 16-Jul-2013 22:42:30 [ERROR] For more in

Re: [Dev] [IS] Server doesn't start up.

2013-07-16 Thread Asela Pathberiya
fixed this.. for now, please edit identity.xml

Thanks,
Asela.

On Wed, Jul 17, 2013 at 11:13 AM, Thilini Ishaka  wrote:

>
> On Wed, Jul 17, 2013 at 11:04 AM, Sameera Jayasoma wrote:
>
>> Seems like someone has committed a XML configuration file with invalid
>> syntax. Please have a look.
>>
>> Issue in the following line with r 178396.
>
> <*Skipe*UserConsent>false
>
> -Thilini
>
>>
>> [2013-07-17 05:32:26,350]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon...
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Linux 2.6.32-5-xen-amd64, amd64
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> /build/software/dist/jdk1.6.0_45/jre
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.6.0_45
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 20.45-b01,Sun Microsystems Inc.
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT
>> [2013-07-17 05:32:26,353]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT/tmp
>> [2013-07-17 05:32:26,354]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> wso2, en-US, Etc/UTC
>> [2013-07-17 05:32:26,421]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Open files limit :1024 of the system is below the recommended minimum
>> count :4096
>> [2013-07-17 05:32:26,421]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Maximum free Disk Space (MB): 247 of the system is below the recommended
>> minimum size :1024
>> [2013-07-17 05:32:26,422]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Default wso2carbon keystore is being used...
>> [2013-07-17 05:32:26,422]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Swap Memory size (MB): 0 of the system is below the recommended minimum
>> size :2048
>> [2013-07-17 05:32:26,431]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>> [2013-07-17 05:32:26,456]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
>> deployed Agent Client
>> [2013-07-17 05:32:26,878]  INFO
>> {org.wso2.carbon.identity.authenticator.iwa.ui.internal.Activator} -
>>  Integrated Windows Authenticator enabled in the system
>> [2013-07-17 05:32:26,911] ERROR
>> {org.wso2.carbon.identity.core.util.IdentityConfigParser} -  Error while
>> loading Identity Configurations
>> org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException:
>> Unexpected close tag ; expected .
>>  at [row,col {unknown-source}]: [138,65]
>> at
>> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
>> at
>> org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
>>  at
>> org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
>> at
>> org.wso2.carbon.identity.core.util.IdentityConfigParser.readChildElements(IdentityConfigParser.java:165)
>>  at
>> org.wso2.carbon.identity.core.util.IdentityConfigParser.buildConfiguration(IdentityConfigParser.java:150)
>> at
>> org.wso2.carbon.identity.core.util.IdentityConfigParser.(IdentityConfigParser.java:62)
>>  at
>> org.wso2.carbon.identity.core.util.IdentityConfigParser.getInstance(IdentityConfigParser.java:73)
>> at
>> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.buildOAuthServerConfiguration(OAuthServerConfiguration.java:256)
>>  at
>> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.(OAuthServerConfiguration.java:238)
>> at
>> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getInstance(OAuthServerConfiguration.java:246)
>>  at
>> org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent.activate(OAuth2ServiceComponent.java:41)
>> 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.Instan

Re: [Dev] Exception during tenant cleanup

2013-07-16 Thread Anjana Fernando
Hi,

Thanks Chanika, the patch is applied.

Cheers,
Anjana.


On Wed, Jul 17, 2013 at 10:42 AM, Chanika Geeganage wrote:

> Hi,
>
> I tested it and works fine. The modified svn diff of the ndatasource core
> is attached in the JIRA [1]
>
> [1] https://wso2.org/jira/browse/DS-740
>
> Thanks
>
>
> On Wed, Jul 17, 2013 at 10:01 AM, Sameera Jayasoma wrote:
>
>> I've populated CarbonContext objects for the threads which terminates the
>> idle tenant config contexts. Fix is committed to the trunk. Test and let me
>> know.
>>
>> Thanks,
>> Sameera.
>>
>>
>> On Tue, Jul 16, 2013 at 9:07 PM, Chanika Geeganage wrote:
>>
>>> Hi,
>>>
>>> Had an offline chat with Sameera and figured out that this should be
>>> handled in the carbon core level and the ndatasource core should be changed
>>> accordingly.
>>>
>>> Thanks
>>>
>>>
>>> On Tue, Jul 16, 2013 at 3:00 PM, Chanika Geeganage wrote:
>>>
 Hi,

 This was because of the latest changes for the new caching model. I
 have attached the patch to [1].

 [1] https://wso2.org/jira/browse/DS-740

 Thanks


 On Mon, Jul 15, 2013 at 12:48 PM, Kasun Gajasinghe wrote:

> Hi Chanika,
>
> Please try this in a latest pack from trunk.
>
>
> On Mon, Jul 15, 2013 at 11:47 AM, Chanika Geeganage 
> wrote:
>
>> Hi Azeez,
>>
>> I couldn't reproduce this error. I used DSS 3.0.1 and here are the
>> steps I followed.
>>
>> 1. Created a tenant.
>> 2. Sign in as the tenant admin.
>> 2. Added a data source
>> 3. Deployed a dataservice
>> 4. Sign out and wait for the tenant cleanup.
>>
>> Then tenant is cleaned up without any exceptions. Is there any other
>> steps to follow to reproduce the error?
>>
>> Thanks
>>
>>
>> On Mon, Jul 15, 2013 at 10:39 AM, Chanika Geeganage > > wrote:
>>
>>> I will check on this.
>>>
>>> Thanks
>>>
>>>
>>> On Sat, Jul 13, 2013 at 7:24 PM, Afkham Azeez wrote:
>>>
 [2013-07-13 17:09:15,544]  INFO
 {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Starting 
 to
 clean tenant : azeez.org
 [2013-07-13 17:09:15,966]  INFO
 {org.wso2.carbon.webapp.mgt.WebApplication} -  Unloaded webapp:
 StandardEngine[Catalina].StandardHost[localhost].StandardContext[/t/
 azeez.org/webapps/Calendar]
 [2013-07-13 17:09:15,970] ERROR
 {org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver}
 -  Error in initializing data sources for tenant: 1 - Error in getting 
 all
 data sources from repository: null
 org.wso2.carbon.ndatasource.common.DataSourceException: Error in
 getting all data sources from repository: null
 at
 org.wso2.carbon.ndatasource.core.DataSourceRepository.updateAllUserDataSource(DataSourceRepository.java:143)
  at
 org.wso2.carbon.ndatasource.core.DataSourceRepository.unregisterAllUserDataSources(DataSourceRepository.java:123)
 at
 org.wso2.carbon.ndatasource.core.DataSourceManager.unloadTenant(DataSourceManager.java:108)
  at
 org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver.terminatingConfigurationContext(DataSourceAxis2ConfigurationContextObserver.java:49)
  at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:515)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:477)
  at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:429)
 at
 org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
  at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
  at
 java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
  at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
  at java.lang.Thread.run(Thread.java:680)
 Caused by: java.lang.NullPointerException

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.co

Re: [Dev] [ELB] Server does startup at all.

2013-07-16 Thread Afkham Azeez
What if a ST CC is created before calling createConfigurationContext in
Carbon kernel/core.

Azeez


On Wed, Jul 17, 2013 at 11:16 AM, Sameera Jayasoma  wrote:

> ELB still uses the tribes clustering. We need to change it use HZ.  Looks
> like there are more caching changes to be done.
>
> [2013-07-17 05:27:10,337]  WARN - DefaultRealm You cannot disable the
> primary user store.
> [2013-07-17 05:27:10,526]  INFO - EmbeddedRegistryService Configured
> Registry in 60ms
> [2013-07-17 05:27:10,732]  INFO - RegistryCoreServiceComponent Registry
> Mode: READ-WRITE
> [2013-07-17 05:27:11,575]  INFO - UserStoreManagerRegistry 4
> UserStoreManagers registered.
> [2013-07-17 05:27:11,575]  INFO - UserStoreMgtDSComponent Carbon
> UserStoreMgtDSComponent activated successfully.
> [2013-07-17 05:27:11,700] FATAL - UserRegistry Failed to add the root
> collection to the coreRegistry.
> java.lang.NullPointerException: Tenant domain has not been set in
> CarbonContext
> at
> org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79)
>  at
> org.wso2.carbon.registry.core.utils.RegistryUtils.getCacheManager(RegistryUtils.java:289)
> at
> org.wso2.carbon.registry.core.utils.RegistryUtils.getResourcePathCache(RegistryUtils.java:283)
>  at
> org.wso2.carbon.registry.core.caching.PathCache.getCache(PathCache.java:35)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache.getPathID(JDBCPathCache.java:298)
>  at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResourceID(JDBCResourceDAO.java:67)
> at
> org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.resourceExists(JDBCResourceDAO.java:151)
>  at
> org.wso2.carbon.registry.core.utils.RegistryUtils.systemResourceShouldBeAdded(RegistryUtils.java:630)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:374)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:481)
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:477)
> at
> org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:294)
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:188)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
>  at
> org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
> at
> org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
>  at
> org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
> at
> org.wso2.carbon.core.init.OSGiAxis2ServicesListener.bundleChanged(OSGiAxis2ServicesListener.java:84)
>  at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>  at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> [2013-07-17 05:27:11,703] ERROR - CarbonAxisConfigurator Error occurred
> while populating the CarbonContext on the AxisConfiguration
> org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to add
> the root collection to the coreRegistry.
> at
> org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:399)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
> at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
>  at
> org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
> at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:481)
>  at
> org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:477)
> at
> org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:294)
>  at
> org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:188)
> at
> org.apache.ax

Re: [Dev] Error Log in AS pack startup

2013-07-16 Thread Isuru Haththotuwa
I had a look at the carbon.xml with Manoj. Even though the
DeploymentSynchronizer is disabled, this error is occurring, which is
strange. I'm looking in to this more.


On Wed, Jul 17, 2013 at 10:49 AM, Isuru Haththotuwa  wrote:

> Hi Manoj,
>
> Can you please share the the DeploymentSynchronizer section of the
> carbon.xml.
>
>
> On Wed, Jul 17, 2013 at 10:39 AM, Manoj Kumara  wrote:
>
>> Hi,
>>
>> No. Just extract and started the sever.
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Wed, Jul 17, 2013 at 10:36 AM, Kasun Gajasinghe wrote:
>>
>>> Hi Ananda, did you enable DepSync git feature?
>>> On Jul 17, 2013 10:27 AM, "Manoj Kumara"  wrote:
>>>
 Hi,

 I faced a error log when starting the fresh pack build from trunk.
 Please have a look.


 [2013-07-17 10:23:40,847]  INFO
 {org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
  Coordination service disabled.
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
 Carbon...
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
 Linux 3.2.0-45-generic, amd64
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
 /home/manoj/installation/jdk1.6.0_39/jre
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
 1.6.0_39
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
 Java HotSpot(TM) 64-Bit Server VM 20.14-b01,Sun Microsystems Inc.
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
 /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT
 [2013-07-17 10:23:40,870]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
 /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT/tmp
 [2013-07-17 10:23:40,871]  INFO
 {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
 manoj, en-US, Asia/Colombo
 [2013-07-17 10:23:40,906]  WARN
 {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
  Default wso2carbon keystore is being used...
 [2013-07-17 10:23:40,922]  INFO
 {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
 [2013-07-17 10:23:40,937]  INFO
 {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
 deployed Agent Client
 [2013-07-17 10:23:40,954] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:40,962] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,055] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,061] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,064] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,067] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,072] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,077] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,085] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,090] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,108] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
 [2013-07-17 10:23:41,110] ERROR
 {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>

Re: [Dev] [Bamboo-Build] WSO2 Carbon 4.1.x > Platform 4.1.5 > #3 has FAILED. Change made by Ranga Siriwardena.

2013-07-16 Thread Ranga Siriwardena
Hi,

Bamboo build failing on Storage Server p2 profile. Please have a look.


16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Features Parent
. SUCCESS [0.003s]
16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - P2 Profile Generation
... FAILURE [0.951s]
16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Distribution
 FAILURE [15.309s]
16-Jul-2013 22:42:29 [INFO] WSO2 Storage Server - Aggregator Module
... SUCCESS [0.004s]
16-Jul-2013 22:42:29 [INFO] WSO2 Carbon - Patch releases - products -
Aggregator Module  SUCCESS [0.003s]
16-Jul-2013 22:42:29 [INFO] WSO2 Carbon - Patch releases - Platform
Automated Test Suite  SUCCESS [0.003s]
16-Jul-2013 22:42:29 [INFO]

16-Jul-2013 22:42:29 [INFO] BUILD FAILURE
16-Jul-2013 22:42:29 [INFO]

16-Jul-2013 22:42:29 [INFO] Total time: 1:15.418s
16-Jul-2013 22:42:29 [INFO] Finished at: Tue Jul 16 22:42:29 PDT 2013
16-Jul-2013 22:42:30 [INFO] Final Memory: 270M/1677M
16-Jul-2013 22:42:30 [INFO]

16-Jul-2013 22:42:30 [ERROR] Failed to execute goal on project
org.wso2.carbon.cassandra.explorer.feature: Could not resolve dependencies
for project
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:pom:4.1.5:
Failed to collect dependencies for
[org.wso2.carbon:org.wso2.carbon.cassandra.explorer.server.feature:zip:4.1.5
(compile),
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.ui.feature:zip:4.1.2
(compile)]: Failed to read artifact descriptor for
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.ui.feature:zip:4.1.2:
Failure to find org.wso2.carbon:cassandra-explorer-feature:pom:4.1.0 in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of wso2-nexus has elapsed or updates are forced -> [Help 1]
16-Jul-2013 22:42:30 [ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.2:p2-repo-gen (2-p2-repo-generation) on
project wso2ss-p2-profile: Error occured when processing the Feature
Artifact: org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:4.1.5:
ERROR: Failure to find
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:zip:4.1.5 in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of wso2-nexus has elapsed or updates are forced
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] Try downloading the file manually from the
project website.
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] Then, install it using the command:
16-Jul-2013 22:42:30 [ERROR] mvn install:install-file
-DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.cassandra.explorer.feature -Dversion=4.1.5
-Dpackaging=zip -Dfile=/path/to/file
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] Alternatively, if you host your own repository
you can deploy the file there:
16-Jul-2013 22:42:30 [ERROR] mvn deploy:deploy-file
-DgroupId=org.wso2.carbon
-DartifactId=org.wso2.carbon.cassandra.explorer.feature -Dversion=4.1.5
-Dpackaging=zip -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR]
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.feature:zip:4.1.5
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] from the specified remote repositories:
16-Jul-2013 22:42:30 [ERROR] wso2-nexus (
http://maven.wso2.org/nexus/content/groups/wso2-public/, releases=true,
snapshots=true),
16-Jul-2013 22:42:30 [ERROR] central (http://repo1.maven.org/maven2,
releases=true, snapshots=false)
16-Jul-2013 22:42:30 [ERROR] -> [Help 2]
16-Jul-2013 22:42:30 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-2:attached (dist)
on project wso2ss: Failed to create assembly: Error adding file to archive:
/home/bamboo/Bamboo-3.4/source-repository/build-dir/WCB003-PLA006-JOB1/products/ss/1.0.3/modules/distribution/../p2-profile/target/wso2carbon-core-4.1.0/repository/conf/etc/logging-config.xml
isn't a file. -> [Help 2]
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.
16-Jul-2013 22:42:30 [ERROR] Re-run Maven using the -X switch to enable
full debug logging.
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] For more information about the errors and
possible solutions, please read the following articles:
16-Jul-2013 22:42:30 [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
16-Jul-2013 22:42:30 [ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
16-Jul-2013 22:42:30 [ERROR]
16-Jul-2013 22:42:30 [ERROR] After correcting the problems, you can

[Dev] [ELB] Server does startup at all.

2013-07-16 Thread Sameera Jayasoma
ELB still uses the tribes clustering. We need to change it use HZ.  Looks
like there are more caching changes to be done.

[2013-07-17 05:27:10,337]  WARN - DefaultRealm You cannot disable the
primary user store.
[2013-07-17 05:27:10,526]  INFO - EmbeddedRegistryService Configured
Registry in 60ms
[2013-07-17 05:27:10,732]  INFO - RegistryCoreServiceComponent Registry
Mode: READ-WRITE
[2013-07-17 05:27:11,575]  INFO - UserStoreManagerRegistry 4
UserStoreManagers registered.
[2013-07-17 05:27:11,575]  INFO - UserStoreMgtDSComponent Carbon
UserStoreMgtDSComponent activated successfully.
[2013-07-17 05:27:11,700] FATAL - UserRegistry Failed to add the root
collection to the coreRegistry.
java.lang.NullPointerException: Tenant domain has not been set in
CarbonContext
at
org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:79)
 at
org.wso2.carbon.registry.core.utils.RegistryUtils.getCacheManager(RegistryUtils.java:289)
at
org.wso2.carbon.registry.core.utils.RegistryUtils.getResourcePathCache(RegistryUtils.java:283)
 at
org.wso2.carbon.registry.core.caching.PathCache.getCache(PathCache.java:35)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCPathCache.getPathID(JDBCPathCache.java:298)
 at
org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.getResourceID(JDBCResourceDAO.java:67)
at
org.wso2.carbon.registry.core.jdbc.dao.JDBCResourceDAO.resourceExists(JDBCResourceDAO.java:151)
 at
org.wso2.carbon.registry.core.utils.RegistryUtils.systemResourceShouldBeAdded(RegistryUtils.java:630)
at
org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:374)
 at
org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
 at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
 at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:481)
 at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:477)
at
org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:294)
 at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:188)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
 at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
 at
org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:290)
at
org.wso2.carbon.core.init.OSGiAxis2ServicesListener.bundleChanged(OSGiAxis2ServicesListener.java:84)
 at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:847)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
 at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
[2013-07-17 05:27:11,703] ERROR - CarbonAxisConfigurator Error occurred
while populating the CarbonContext on the AxisConfiguration
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to add
the root collection to the coreRegistry.
at
org.wso2.carbon.registry.core.session.UserRegistry.addRootCollection(UserRegistry.java:399)
 at
org.wso2.carbon.registry.core.session.UserRegistry.init(UserRegistry.java:299)
at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:226)
 at
org.wso2.carbon.registry.core.session.UserRegistry.(UserRegistry.java:205)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getUserRegistry(EmbeddedRegistryService.java:427)
 at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getSystemRegistry(EmbeddedRegistryService.java:292)
at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:481)
 at
org.wso2.carbon.registry.core.jdbc.EmbeddedRegistryService.getLocalRepository(EmbeddedRegistryService.java:477)
at
org.wso2.carbon.core.CarbonAxisConfigurator.populateAxisConfiguration(CarbonAxisConfigurator.java:294)
 at
org.wso2.carbon.core.CarbonAxisConfigurator.getAxisConfiguration(CarbonAxisConfigurator.java:188)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:64)
 at
org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
at
org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:398)
 at
org.wso2.carbo

Re: [Dev] [IS] Server doesn't start up.

2013-07-16 Thread Thilini Ishaka
On Wed, Jul 17, 2013 at 11:04 AM, Sameera Jayasoma  wrote:

> Seems like someone has committed a XML configuration file with invalid
> syntax. Please have a look.
>
> Issue in the following line with r 178396.

<*Skipe*UserConsent>false

-Thilini

>
> [2013-07-17 05:32:26,350]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-5-xen-amd64, amd64
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /build/software/dist/jdk1.6.0_45/jre
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_45
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 20.45-b01,Sun Microsystems Inc.
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT/tmp
> [2013-07-17 05:32:26,354]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> wso2, en-US, Etc/UTC
> [2013-07-17 05:32:26,421]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Open files limit :1024 of the system is below the recommended minimum
> count :4096
> [2013-07-17 05:32:26,421]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Maximum free Disk Space (MB): 247 of the system is below the recommended
> minimum size :1024
> [2013-07-17 05:32:26,422]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Default wso2carbon keystore is being used...
> [2013-07-17 05:32:26,422]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Swap Memory size (MB): 0 of the system is below the recommended minimum
> size :2048
> [2013-07-17 05:32:26,431]  INFO
> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
> [2013-07-17 05:32:26,456]  INFO
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
> deployed Agent Client
> [2013-07-17 05:32:26,878]  INFO
> {org.wso2.carbon.identity.authenticator.iwa.ui.internal.Activator} -
>  Integrated Windows Authenticator enabled in the system
> [2013-07-17 05:32:26,911] ERROR
> {org.wso2.carbon.identity.core.util.IdentityConfigParser} -  Error while
> loading Identity Configurations
> org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException:
> Unexpected close tag ; expected .
>  at [row,col {unknown-source}]: [138,65]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
>  at
> org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
> at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.readChildElements(IdentityConfigParser.java:165)
>  at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.buildConfiguration(IdentityConfigParser.java:150)
> at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.(IdentityConfigParser.java:62)
>  at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.getInstance(IdentityConfigParser.java:73)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.buildOAuthServerConfiguration(OAuthServerConfiguration.java:256)
>  at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.(OAuthServerConfiguration.java:238)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getInstance(OAuthServerConfiguration.java:246)
>  at
> org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent.activate(OAuth2ServiceComponent.java:41)
> 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.buildNewlySatisfied(Resolver.java:

Re: [Dev] [Architecture] WSO2 CEP 3.0.0 Milestone 2 Released!

2013-07-16 Thread Sriskandarajah Suhothayan
On Wed, Jul 17, 2013 at 8:15 AM, Samisa Abeysinghe  wrote:

>
>
>
> On Tue, Jul 16, 2013 at 10:02 AM, Sriskandarajah Suhothayan  > wrote:
>
>>
>>
>>
>> On Tue, Jul 16, 2013 at 5:40 AM, Samisa Abeysinghe wrote:
>>
>>>
>>>
>>>
>>> On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam <
>>> mo...@wso2.com> wrote:
>>>
 Hi Cyril,

 We are on the way of creating the documentation for CEP 3.0.0...

>>>
>>> If there are no docs on the features shipped with the milestone, who can
>>> we consider those to be "done-done"?
>>>
>>
>> CEP 3.0.0 M2 is just an incremental release and it does not have any
>> features in done-done state.
>>
>
> This does not sound right. If a single feature is not done, what are we
> shipping in the milestone, only bug fixes?
> And the CEP Jira dashboard does not shoe any significant fixes either.
> https://wso2.org/jira/secure/Dashboard.jspa?selectPageId=10406
>
> I am confused.
>
>

Its a valid question.
CEP 3.0.0 is a complete rewrite on the carbon server side. On CEP 2.1.0 we
had three components broker, broker-manager and cep, but in CEP 3.0.0 we
changed the fundamental architecture according the architecture mail thread
"CEP 3.0 towards a Complete eventing solution to the platform" and because
of that now we have five components input transport adaptor, output
transport adaptor, event builder, event formatter and event processor.

Since we were writing all features in parallel and since this is a complete
rewrite, we had trouble delivering working milestones having features at
done-done level. On CEP 3.0.0 M2 we were able to make all the core features
work together, therefore no the next release "CEP 3.0.0 alpha" we will be
able to deliver all the features in done-done level.

Thanks
Suho

 Both documentation and integration tests are still pending.
>> Currently it has almost all the features with their core functionality
>> implemented and a simple ReadMe on how to run the samples using its
>> available functionality.
>>
>> In future releases we will be focusing more on brining these features to
>> the done-done state.
>>
>> Thanks
>> Suho
>>
>>
>>>
>>>
 We'll share the documentation with the CEP 3.0.0 release soon...

 Yes, 'non occurrence' of events is already implemented and can be
 achieved using the event tables in CEP 3.0.0..

 We'll update when CEP 3.0.0 released... Thanks for your interest on
 CEP...

 Regards,
 Mohan





 On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon wrote:

> Hello cep team,
>
> thank you for this new milestone. I am wondering if there is any
> documentation link for  the upcoming 3.0.0 version.
>
> As far as I know, there is still no logical 'not' operator that we
> could use to filter the 'non occurrence' of events
>
> in siddhi language there is
>
> * **::=  *
>
> it would be nice to be able to say*
> *
>
> * **::= not  *
> I reckon I have not looked into the code to evaluate the cost of this
> requirement, so feel free to turn it down if it is prohibitive.
>
> Maybe eventTables will allow one to simulate this ?
>
> thanks,
> Cyril
>
>
> On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam <
> mo...@wso2.com> wrote:
>
>> *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!*
>>
>> Date :5th July 2013
>>
>> This milestone is available at :
>> https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip
>>
>> To run the samples please follow the read-me,
>> wso2cep-3.0.0/samples/cep-samples/ReadMe.txt
>>
>>
>> Following are the bug fixes, improvements and the new features
>>
>> Bug
>>
>>- [CEP-258 ] - When trying
>>to deploy the multiple configuration files, File reference is missing
>>- [CEP-261 ] - Table is not
>>properly generated when creating WSO2 Event mapping and Map mapping
>>
>> Improvement
>>
>>- [CEP-179 ] - It is better
>>if the UI supports to check the validity of "Event Sink URL" when
>>subscribing to a topic
>>- [CEP-243 ] - Separate
>>implementation classes & UI for handing in/out sequences of transport
>>adapators
>>- [CEP-247 ] - Making
>>Coalesce as a ExecutorFunction
>>- [CEP-248 ] - Removing
>>conversion types from output attribute processor
>>- [CEP-249 ] - Replacing
>>Condition Extentions using bool returning Expression Extentions
>>- [CEP-251 ] - White-board
>>pattern for Transport A

Re: [Dev] [IS] Server doesn't start up.

2013-07-16 Thread Sameera Jayasoma
Even G-Reg has the same error.


On Wed, Jul 17, 2013 at 11:04 AM, Sameera Jayasoma  wrote:

> Seems like someone has committed a XML configuration file with invalid
> syntax. Please have a look.
>
>
> [2013-07-17 05:32:26,350]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 2.6.32-5-xen-amd64, amd64
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /build/software/dist/jdk1.6.0_45/jre
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_45
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 20.45-b01,Sun Microsystems Inc.
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT
> [2013-07-17 05:32:26,353]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT/tmp
> [2013-07-17 05:32:26,354]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> wso2, en-US, Etc/UTC
> [2013-07-17 05:32:26,421]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Open files limit :1024 of the system is below the recommended minimum
> count :4096
> [2013-07-17 05:32:26,421]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Maximum free Disk Space (MB): 247 of the system is below the recommended
> minimum size :1024
> [2013-07-17 05:32:26,422]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Default wso2carbon keystore is being used...
> [2013-07-17 05:32:26,422]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Swap Memory size (MB): 0 of the system is below the recommended minimum
> size :2048
> [2013-07-17 05:32:26,431]  INFO
> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
> [2013-07-17 05:32:26,456]  INFO
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
> deployed Agent Client
> [2013-07-17 05:32:26,878]  INFO
> {org.wso2.carbon.identity.authenticator.iwa.ui.internal.Activator} -
>  Integrated Windows Authenticator enabled in the system
> [2013-07-17 05:32:26,911] ERROR
> {org.wso2.carbon.identity.core.util.IdentityConfigParser} -  Error while
> loading Identity Configurations
> org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException:
> Unexpected close tag ; expected .
>  at [row,col {unknown-source}]: [138,65]
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
> at
> org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
>  at
> org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
> at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.readChildElements(IdentityConfigParser.java:165)
>  at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.buildConfiguration(IdentityConfigParser.java:150)
> at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.(IdentityConfigParser.java:62)
>  at
> org.wso2.carbon.identity.core.util.IdentityConfigParser.getInstance(IdentityConfigParser.java:73)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.buildOAuthServerConfiguration(OAuthServerConfiguration.java:256)
>  at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.(OAuthServerConfiguration.java:238)
> at
> org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getInstance(OAuthServerConfiguration.java:246)
>  at
> org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent.activate(OAuth2ServiceComponent.java:41)
> 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.buildNewlySatisfied(Resolver.java:473)
> at
> org.eclipse.equinox.internal.ds.Resolv

[Dev] [IS] Server doesn't start up.

2013-07-16 Thread Sameera Jayasoma
Seems like someone has committed a XML configuration file with invalid
syntax. Please have a look.


[2013-07-17 05:32:26,350]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Linux 2.6.32-5-xen-amd64, amd64
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/build/software/dist/jdk1.6.0_45/jre
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.6.0_45
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 20.45-b01,Sun Microsystems Inc.
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
/build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT
[2013-07-17 05:32:26,353]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
/build/trunk/platform/products/is/modules/distribution/target/wso2is-4.5.0-SNAPSHOT/tmp
[2013-07-17 05:32:26,354]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
wso2, en-US, Etc/UTC
[2013-07-17 05:32:26,421]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Open files limit :1024 of the system is below the recommended minimum
count :4096
[2013-07-17 05:32:26,421]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Maximum free Disk Space (MB): 247 of the system is below the recommended
minimum size :1024
[2013-07-17 05:32:26,422]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Default wso2carbon keystore is being used...
[2013-07-17 05:32:26,422]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Swap Memory size (MB): 0 of the system is below the recommended minimum
size :2048
[2013-07-17 05:32:26,431]  INFO
{org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
[2013-07-17 05:32:26,456]  INFO
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
deployed Agent Client
[2013-07-17 05:32:26,878]  INFO
{org.wso2.carbon.identity.authenticator.iwa.ui.internal.Activator} -
 Integrated Windows Authenticator enabled in the system
[2013-07-17 05:32:26,911] ERROR
{org.wso2.carbon.identity.core.util.IdentityConfigParser} -  Error while
loading Identity Configurations
org.apache.axiom.om.OMException: com.ctc.wstx.exc.WstxParsingException:
Unexpected close tag ; expected .
 at [row,col {unknown-source}]: [138,65]
at
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)
at
org.apache.axiom.om.impl.llom.OMElementImpl.getNextOMSibling(OMElementImpl.java:336)
 at
org.apache.axiom.om.impl.traverse.OMChildElementIterator.next(OMChildElementIterator.java:104)
at
org.wso2.carbon.identity.core.util.IdentityConfigParser.readChildElements(IdentityConfigParser.java:165)
 at
org.wso2.carbon.identity.core.util.IdentityConfigParser.buildConfiguration(IdentityConfigParser.java:150)
at
org.wso2.carbon.identity.core.util.IdentityConfigParser.(IdentityConfigParser.java:62)
 at
org.wso2.carbon.identity.core.util.IdentityConfigParser.getInstance(IdentityConfigParser.java:73)
at
org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.buildOAuthServerConfiguration(OAuthServerConfiguration.java:256)
 at
org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.(OAuthServerConfiguration.java:238)
at
org.wso2.carbon.identity.oauth.config.OAuthServerConfiguration.getInstance(OAuthServerConfiguration.java:246)
 at
org.wso2.carbon.identity.oauth2.internal.OAuth2ServiceComponent.activate(OAuth2ServiceComponent.java:41)
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.buildNewlySatisfied(Resolver.java:473)
at
org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
 at
org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
at
org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
 at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
at java.lang.

Re: [Dev] Bringing back "carbon.registry.root" carbon property

2013-07-16 Thread Senaka Fernando
Hi Azeez,

Adding you to this discussion.

The particular system property being referred to here, was removed with the
introducing of the multiple instance feature back then. The reason being
that this system property being a node specific thing could have an impact
where two nodes wanted to have their own registry roots. What Suho is
proposing is a little different to how it was used back then, where the
system property does not become something mandatory but an override to the
one defined in the registry.xml. This will make it convenient for those
running samples etc. While discussing we didn't find this to create any
issues, so I am in favor of making the change.

WDYT?

Thanks,
Senaka.


On Tue, Jul 16, 2013 at 7:50 PM, Sriskandarajah Suhothayan wrote:

>
> Hi,
>
> With CEP 3.0.0 effort we are building ESB like samples for CEP where we
> can up CEP with the sample numbers and run the samples.
>
> Here since CEP stores stream definitions (DataBridge Streams) in the
> governance registry space we are currently having issues isolating a test
> space from the registry.
>
> We can achieve this functionality if we can specify the
> carbon.registry.root as system property.
> But according to the "[Carbon-dev] Getting rid of Carbon System
> properties" discussion made on 22/7/2009 this system property was removed
> and now we can only change the registry root via the registry.xml
>
> Please do raise your concern if you have issues in bringing back this
> system property
>
> Thanks
> Suho
>
>
> --
> *S. Suhothayan
> *
> Associate Technical Lead,
>  *WSO2 Inc. *http://wso2.com *
>  *
> lean . enterprise . middleware
>
> *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
> twitter: http://twitter.com/suhothayan | linked-in:
> http://lk.linkedin.com/in/suhothayan*
> *
> *
>



-- 
* 
*
*
*
*Senaka Fernando*
Senior Technical Lead; WSO2 Inc.; http://wso2.com*
Member; Apache Software Foundation; http://apache.org

E-mail: senaka AT wso2.com
**P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
Linked-In: http://linkedin.com/in/senakafernando

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


Re: [Dev] Error Log in AS pack startup

2013-07-16 Thread Isuru Haththotuwa
Hi Manoj,

Can you please share the the DeploymentSynchronizer section of the
carbon.xml.


On Wed, Jul 17, 2013 at 10:39 AM, Manoj Kumara  wrote:

> Hi,
>
> No. Just extract and started the sever.
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
>
> On Wed, Jul 17, 2013 at 10:36 AM, Kasun Gajasinghe wrote:
>
>> Hi Ananda, did you enable DepSync git feature?
>> On Jul 17, 2013 10:27 AM, "Manoj Kumara"  wrote:
>>
>>> Hi,
>>>
>>> I faced a error log when starting the fresh pack build from trunk.
>>> Please have a look.
>>>
>>>
>>> [2013-07-17 10:23:40,847]  INFO
>>> {org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
>>>  Coordination service disabled.
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>>> Carbon...
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>>> Linux 3.2.0-45-generic, amd64
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>>> /home/manoj/installation/jdk1.6.0_39/jre
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>>> 1.6.0_39
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>>> Java HotSpot(TM) 64-Bit Server VM 20.14-b01,Sun Microsystems Inc.
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>>> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT
>>> [2013-07-17 10:23:40,870]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>>> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT/tmp
>>> [2013-07-17 10:23:40,871]  INFO
>>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>>> manoj, en-US, Asia/Colombo
>>> [2013-07-17 10:23:40,906]  WARN
>>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>>  Default wso2carbon keystore is being used...
>>> [2013-07-17 10:23:40,922]  INFO
>>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>>> [2013-07-17 10:23:40,937]  INFO
>>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
>>> deployed Agent Client
>>> [2013-07-17 10:23:40,954] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:40,962] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,055] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,061] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,064] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,067] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,072] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,077] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,085] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,090] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,108] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,110] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,132] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>> [2013-07-17 10:23:41,134] ERROR
>>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>>  Required parameter DeploymentSynchroniz

Re: [Dev] Exception during tenant cleanup

2013-07-16 Thread Chanika Geeganage
Hi,

I tested it and works fine. The modified svn diff of the ndatasource core
is attached in the JIRA [1]

[1] https://wso2.org/jira/browse/DS-740

Thanks


On Wed, Jul 17, 2013 at 10:01 AM, Sameera Jayasoma  wrote:

> I've populated CarbonContext objects for the threads which terminates the
> idle tenant config contexts. Fix is committed to the trunk. Test and let me
> know.
>
> Thanks,
> Sameera.
>
>
> On Tue, Jul 16, 2013 at 9:07 PM, Chanika Geeganage wrote:
>
>> Hi,
>>
>> Had an offline chat with Sameera and figured out that this should be
>> handled in the carbon core level and the ndatasource core should be changed
>> accordingly.
>>
>> Thanks
>>
>>
>> On Tue, Jul 16, 2013 at 3:00 PM, Chanika Geeganage wrote:
>>
>>> Hi,
>>>
>>> This was because of the latest changes for the new caching model. I have
>>> attached the patch to [1].
>>>
>>> [1] https://wso2.org/jira/browse/DS-740
>>>
>>> Thanks
>>>
>>>
>>> On Mon, Jul 15, 2013 at 12:48 PM, Kasun Gajasinghe wrote:
>>>
 Hi Chanika,

 Please try this in a latest pack from trunk.


 On Mon, Jul 15, 2013 at 11:47 AM, Chanika Geeganage 
 wrote:

> Hi Azeez,
>
> I couldn't reproduce this error. I used DSS 3.0.1 and here are the
> steps I followed.
>
> 1. Created a tenant.
> 2. Sign in as the tenant admin.
> 2. Added a data source
> 3. Deployed a dataservice
> 4. Sign out and wait for the tenant cleanup.
>
> Then tenant is cleaned up without any exceptions. Is there any other
> steps to follow to reproduce the error?
>
> Thanks
>
>
> On Mon, Jul 15, 2013 at 10:39 AM, Chanika Geeganage 
> wrote:
>
>> I will check on this.
>>
>> Thanks
>>
>>
>> On Sat, Jul 13, 2013 at 7:24 PM, Afkham Azeez  wrote:
>>
>>> [2013-07-13 17:09:15,544]  INFO
>>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Starting to
>>> clean tenant : azeez.org
>>> [2013-07-13 17:09:15,966]  INFO
>>> {org.wso2.carbon.webapp.mgt.WebApplication} -  Unloaded webapp:
>>> StandardEngine[Catalina].StandardHost[localhost].StandardContext[/t/
>>> azeez.org/webapps/Calendar]
>>> [2013-07-13 17:09:15,970] ERROR
>>> {org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver}
>>> -  Error in initializing data sources for tenant: 1 - Error in getting 
>>> all
>>> data sources from repository: null
>>> org.wso2.carbon.ndatasource.common.DataSourceException: Error in
>>> getting all data sources from repository: null
>>> at
>>> org.wso2.carbon.ndatasource.core.DataSourceRepository.updateAllUserDataSource(DataSourceRepository.java:143)
>>>  at
>>> org.wso2.carbon.ndatasource.core.DataSourceRepository.unregisterAllUserDataSources(DataSourceRepository.java:123)
>>> at
>>> org.wso2.carbon.ndatasource.core.DataSourceManager.unloadTenant(DataSourceManager.java:108)
>>>  at
>>> org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver.terminatingConfigurationContext(DataSourceAxis2ConfigurationContextObserver.java:49)
>>>  at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:515)
>>> at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:477)
>>>  at
>>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:429)
>>> at
>>> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
>>>  at
>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>>> at
>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>>  at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>> at
>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>>  at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>>> at
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>>  at java.lang.Thread.run(Thread.java:680)
>>> Caused by: java.lang.NullPointerException
>>>
>>> --
>>> *Afkham Azeez*
>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>> Member; Apache Software Foundation; http://www.apache.org/
>>> * **
>>> email: **az...@wso2.com* * cell: +94 77 3320919
>>> blog: **http://blog.afkham.org* *
>>> twitter: 
>>> **http://twitter.com/a

Re: [Dev] Error Log in AS pack startup

2013-07-16 Thread Manoj Kumara
Hi,

No. Just extract and started the sever.

Thanks,
Manoj

Best Regards..


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

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


On Wed, Jul 17, 2013 at 10:36 AM, Kasun Gajasinghe  wrote:

> Hi Ananda, did you enable DepSync git feature?
> On Jul 17, 2013 10:27 AM, "Manoj Kumara"  wrote:
>
>> Hi,
>>
>> I faced a error log when starting the fresh pack build from trunk. Please
>> have a look.
>>
>>
>> [2013-07-17 10:23:40,847]  INFO
>> {org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
>>  Coordination service disabled.
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
>> Carbon...
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
>> Linux 3.2.0-45-generic, amd64
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
>> /home/manoj/installation/jdk1.6.0_39/jre
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
>> 1.6.0_39
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
>> Java HotSpot(TM) 64-Bit Server VM 20.14-b01,Sun Microsystems Inc.
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
>> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT
>> [2013-07-17 10:23:40,870]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
>> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT/tmp
>> [2013-07-17 10:23:40,871]  INFO
>> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
>> manoj, en-US, Asia/Colombo
>> [2013-07-17 10:23:40,906]  WARN
>> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>>  Default wso2carbon keystore is being used...
>> [2013-07-17 10:23:40,922]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
>> [2013-07-17 10:23:40,937]  INFO
>> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
>> deployed Agent Client
>> [2013-07-17 10:23:40,954] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:40,962] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,055] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,061] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,064] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,067] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,072] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,077] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,085] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,090] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,108] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,110] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,132] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>> [2013-07-17 10:23:41,134] ERROR
>> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>>
>>
>> Thanks,
>> Manoj
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>
___

Re: [Dev] Error Log in AS pack startup

2013-07-16 Thread Kasun Gajasinghe
Hi Ananda, did you enable DepSync git feature?
On Jul 17, 2013 10:27 AM, "Manoj Kumara"  wrote:

> Hi,
>
> I faced a error log when starting the fresh pack build from trunk. Please
> have a look.
>
>
> [2013-07-17 10:23:40,847]  INFO
> {org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
>  Coordination service disabled.
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
> Carbon...
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
> Linux 3.2.0-45-generic, amd64
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
> /home/manoj/installation/jdk1.6.0_39/jre
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
> 1.6.0_39
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
> Java HotSpot(TM) 64-Bit Server VM 20.14-b01,Sun Microsystems Inc.
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT
> [2013-07-17 10:23:40,870]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
> /home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT/tmp
> [2013-07-17 10:23:40,871]  INFO
> {org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
> manoj, en-US, Asia/Colombo
> [2013-07-17 10:23:40,906]  WARN
> {org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
>  Default wso2carbon keystore is being used...
> [2013-07-17 10:23:40,922]  INFO
> {org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
> [2013-07-17 10:23:40,937]  INFO
> {org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
> deployed Agent Client
> [2013-07-17 10:23:40,954] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:40,962] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,055] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,061] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,064] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,067] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,072] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,077] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,085] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,090] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,108] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,110] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,132] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
> [2013-07-17 10:23:41,134] ERROR
> {org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
>  Required parameter DeploymentSynchronizer.GitBaseUrl not found
>
>
> Thanks,
> Manoj
>
> Best Regards..
>
>
> Manoj Kumara
> Software Engineer
> WSO2, Inc.; http://wso2.com
>
> Twitter:  http://twitter.com/ManKuma
> Mobile: +94713448188
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Error Log in AS pack startup

2013-07-16 Thread Manoj Kumara
Hi,

I faced a error log when starting the fresh pack build from trunk. Please
have a look.


[2013-07-17 10:23:40,847]  INFO
{org.wso2.carbon.coordination.core.services.impl.ZKCoordinationService} -
 Coordination service disabled.
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Starting WSO2
Carbon...
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Operating System :
Linux 3.2.0-45-generic, amd64
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Home:
/home/manoj/installation/jdk1.6.0_39/jre
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Version :
1.6.0_39
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java VM  :
Java HotSpot(TM) 64-Bit Server VM 20.14-b01,Sun Microsystems Inc.
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Carbon Home  :
/home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT
[2013-07-17 10:23:40,870]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  Java Temp Dir:
/home/manoj/Desktop/Cluster/wso2as-5.2.0-SNAPSHOT/tmp
[2013-07-17 10:23:40,871]  INFO
{org.wso2.carbon.core.internal.CarbonCoreActivator} -  User :
manoj, en-US, Asia/Colombo
[2013-07-17 10:23:40,906]  WARN
{org.wso2.carbon.core.bootup.validator.util.ValidationResultPrinter} -
 Default wso2carbon keystore is being used...
[2013-07-17 10:23:40,922]  INFO
{org.wso2.carbon.databridge.agent.thrift.AgentHolder} -  Agent created !
[2013-07-17 10:23:40,937]  INFO
{org.wso2.carbon.databridge.agent.thrift.internal.AgentDS} -  Successfully
deployed Agent Client
[2013-07-17 10:23:40,954] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:40,962] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,055] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,061] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,064] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,067] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,072] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,077] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,085] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,090] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,108] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,110] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,132] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found
[2013-07-17 10:23:41,134] ERROR
{org.wso2.carbon.deployment.synchronizer.git.DefaultGitRepositoryManager} -
 Required parameter DeploymentSynchronizer.GitBaseUrl not found


Thanks,
Manoj

Best Regards..


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

Twitter:  http://twitter.com/ManKuma
Mobile: +94713448188
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Exception during tenant cleanup

2013-07-16 Thread Sameera Jayasoma
I've populated CarbonContext objects for the threads which terminates the
idle tenant config contexts. Fix is committed to the trunk. Test and let me
know.

Thanks,
Sameera.


On Tue, Jul 16, 2013 at 9:07 PM, Chanika Geeganage  wrote:

> Hi,
>
> Had an offline chat with Sameera and figured out that this should be
> handled in the carbon core level and the ndatasource core should be changed
> accordingly.
>
> Thanks
>
>
> On Tue, Jul 16, 2013 at 3:00 PM, Chanika Geeganage wrote:
>
>> Hi,
>>
>> This was because of the latest changes for the new caching model. I have
>> attached the patch to [1].
>>
>> [1] https://wso2.org/jira/browse/DS-740
>>
>> Thanks
>>
>>
>> On Mon, Jul 15, 2013 at 12:48 PM, Kasun Gajasinghe wrote:
>>
>>> Hi Chanika,
>>>
>>> Please try this in a latest pack from trunk.
>>>
>>>
>>> On Mon, Jul 15, 2013 at 11:47 AM, Chanika Geeganage wrote:
>>>
 Hi Azeez,

 I couldn't reproduce this error. I used DSS 3.0.1 and here are the
 steps I followed.

 1. Created a tenant.
 2. Sign in as the tenant admin.
 2. Added a data source
 3. Deployed a dataservice
 4. Sign out and wait for the tenant cleanup.

 Then tenant is cleaned up without any exceptions. Is there any other
 steps to follow to reproduce the error?

 Thanks


 On Mon, Jul 15, 2013 at 10:39 AM, Chanika Geeganage 
 wrote:

> I will check on this.
>
> Thanks
>
>
> On Sat, Jul 13, 2013 at 7:24 PM, Afkham Azeez  wrote:
>
>> [2013-07-13 17:09:15,544]  INFO
>> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Starting to
>> clean tenant : azeez.org
>> [2013-07-13 17:09:15,966]  INFO
>> {org.wso2.carbon.webapp.mgt.WebApplication} -  Unloaded webapp:
>> StandardEngine[Catalina].StandardHost[localhost].StandardContext[/t/
>> azeez.org/webapps/Calendar]
>> [2013-07-13 17:09:15,970] ERROR
>> {org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver}
>> -  Error in initializing data sources for tenant: 1 - Error in getting 
>> all
>> data sources from repository: null
>> org.wso2.carbon.ndatasource.common.DataSourceException: Error in
>> getting all data sources from repository: null
>> at
>> org.wso2.carbon.ndatasource.core.DataSourceRepository.updateAllUserDataSource(DataSourceRepository.java:143)
>>  at
>> org.wso2.carbon.ndatasource.core.DataSourceRepository.unregisterAllUserDataSources(DataSourceRepository.java:123)
>> at
>> org.wso2.carbon.ndatasource.core.DataSourceManager.unloadTenant(DataSourceManager.java:108)
>>  at
>> org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver.terminatingConfigurationContext(DataSourceAxis2ConfigurationContextObserver.java:49)
>>  at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:515)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:477)
>>  at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:429)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
>>  at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>>  at java.lang.Thread.run(Thread.java:680)
>> Caused by: java.lang.NullPointerException
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: 
>> **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>>>

Re: [Dev] ESB 4.7.0 payloadFactory -- Some problems - Needs clarification

2013-07-16 Thread Susinda Perera
adding Kasun Indrasiri


On Tue, Jul 16, 2013 at 6:50 PM, Susinda Perera  wrote:

> Hi ESB team
>
> Suppose we have a sample payloadFactory configuration as follows
>
> 
> json body
> 
> 
> 
> 
> 
> 
>
>
> 1. Is there any use cases such that *media-type="json"* and <*arg
> evaluator="xml"*  will be used
> 2. Possible use case of *media-type="xml"* and <*arg 
> evaluator="json"*(opposite of the question one)
>
> And some synapse code problems
> payloadFactoryMediator has has methods called getJsonPathArgumentList()
> and getXPathArgumentList(). I used these methods to access arguments, issue
> was the value type argument () is returned from both
> methods.
>
> 3. Is this a bug or intended behavior.
>
> And a suggestion
> 4 .How about giving the config something like follows (omitting the
> evaluator because in code level it is handled in that way). Hope this
> simplifies coding and understandability.
> 
> 
> 
> 
> 
>
>
>
> --
> *Susinda Perera*
> Software Engineer
> Mobile:(+94)716049075
>
> WSO2 Inc. http://wso2.com/
>



-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

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


Re: [Dev] Content Negociation Samples - JAX-RS/REST

2013-07-16 Thread Supun Malinga
Hi Samisa,

Pls find the doc at,
http://docs.wso2.org/wiki/display/AS510/JAX-RS+Sample+on+Content+Negotiation

thanks,


On Wed, Jul 17, 2013 at 6:40 AM, Samisa Abeysinghe  wrote:

> This has an associated doc?
>
>
> On Tue, Jul 16, 2013 at 7:01 PM, Sagara Gunathunga wrote:
>
>>
>>
>>
>> On Tue, Jul 16, 2013 at 6:55 PM, Samisa Abeysinghe wrote:
>>
>>> Do we have $subject?
>>>
>>
>> Yes we have one sample please refer "jaxrs_content_negotiation" sample on
>> AS distro.
>>
>> Thanks !
>>
>>>
>>> --
>>>
>>> Thanks,
>>> Samisa...
>>>
>>> Samisa Abeysinghe
>>> VP Engineering
>>> WSO2 Inc.
>>> http://wso2.com
>>> http://wso2.org
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Sagara Gunathunga
>>
>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>> V.P Apache Web Services;http://ws.apache.org/
>> Linkedin; http://www.linkedin.com/in/ssagara
>> Blog ;  http://ssagara.blogspot.com
>>
>>
>
>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Supun Malinga,

Senior Software Engineer,
WSO2 Inc.
http://wso2.com
http://wso2.org
email - sup...@wso2.com 
mobile - 071 56 91 321
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Thilini Ishaka
On Wed, Jul 17, 2013 at 9:02 AM, Asanka Sanjeewa  wrote:

> Hi,
>
>
> On Tue, Jul 16, 2013 at 2:19 PM, Janaka Ranabahu  wrote:
>
>>
>>
>> +1 for the idea. Do we know why we have forked the earlier version? Was
>> it due to some missing features? Please make sure that we do not loose any
>> of the existing functionality when we move to the newer version.
>>
>
> Actually it is not forking the old version. The thing is that we are still
> using the initially forked version. So we have to upgrade to the new
> version of BPEL editor as it support with the Eclipse Juno. Eclipse Juno
> compatible BPEL editor comes with more enhancements.
>

Created a task for this [1] https://redmine.wso2.com/issues/1688


> Therefore there won't be any lose of existing features and
> functionalities, but we better make sure that after we successfully migrate
> to the new version.
>
Yes, once [1] is completed, BPS team can help with the test effort to make
sure everything is working as expected.

Thanks
Thilini


> Thanks and Regards,
> AsankaS.
>
> --
> *Asanka Sanjeewa*
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thilini Ishaka
Senior Software Engineer**
WSO2 Inc. http://wso2.com*
*bolg: thiliniishaka.blogspot.com*
*linkedin: http://lk.linkedin.com/in/thiliniishaka*
*twitter: https://twitter.com/#!/ThiliniIsh*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Asanka Sanjeewa
Hi,

On Tue, Jul 16, 2013 at 2:19 PM, Janaka Ranabahu  wrote:

>
>
> +1 for the idea. Do we know why we have forked the earlier version? Was it
> due to some missing features? Please make sure that we do not loose any of
> the existing functionality when we move to the newer version.
>

Actually it is not forking the old version. The thing is that we are still
using the initially forked version. So we have to upgrade to the new
version of BPEL editor as it support with the Eclipse Juno. Eclipse Juno
compatible BPEL editor comes with more enhancements. Therefore there won't
be any lose of existing features and functionalities, but we better make
sure that after we successfully migrate to the new version.

Thanks and Regards,
AsankaS.

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


Re: [Dev] [Architecture] WSO2 CEP 3.0.0 Milestone 2 Released!

2013-07-16 Thread Samisa Abeysinghe
On Tue, Jul 16, 2013 at 10:02 AM, Sriskandarajah Suhothayan
wrote:

>
>
>
> On Tue, Jul 16, 2013 at 5:40 AM, Samisa Abeysinghe wrote:
>
>>
>>
>>
>> On Wed, Jul 10, 2013 at 6:31 PM, Mohanadarshan Vivekanandalingam <
>> mo...@wso2.com> wrote:
>>
>>> Hi Cyril,
>>>
>>> We are on the way of creating the documentation for CEP 3.0.0...
>>>
>>
>> If there are no docs on the features shipped with the milestone, who can
>> we consider those to be "done-done"?
>>
>
> CEP 3.0.0 M2 is just an incremental release and it does not have any
> features in done-done state.
>

This does not sound right. If a single feature is not done, what are we
shipping in the milestone, only bug fixes?
And the CEP Jira dashboard does not shoe any significant fixes either.
https://wso2.org/jira/secure/Dashboard.jspa?selectPageId=10406

I am confused.


> Both documentation and integration tests are still pending.
> Currently it has almost all the features with their core functionality
> implemented and a simple ReadMe on how to run the samples using its
> available functionality.
>
> In future releases we will be focusing more on brining these features to
> the done-done state.
>
> Thanks
> Suho
>
>
>>
>>
>>> We'll share the documentation with the CEP 3.0.0 release soon...
>>>
>>> Yes, 'non occurrence' of events is already implemented and can be
>>> achieved using the event tables in CEP 3.0.0..
>>>
>>> We'll update when CEP 3.0.0 released... Thanks for your interest on
>>> CEP...
>>>
>>> Regards,
>>> Mohan
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jul 10, 2013 at 1:47 PM, Cyril Rognon  wrote:
>>>
 Hello cep team,

 thank you for this new milestone. I am wondering if there is any
 documentation link for  the upcoming 3.0.0 version.

 As far as I know, there is still no logical 'not' operator that we
 could use to filter the 'non occurrence' of events

 in siddhi language there is

 * **::=  *

 it would be nice to be able to say*
 *

 * **::= not  *
 I reckon I have not looked into the code to evaluate the cost of this
 requirement, so feel free to turn it down if it is prohibitive.

 Maybe eventTables will allow one to simulate this ?

 thanks,
 Cyril


 On Fri, Jul 5, 2013 at 10:47 PM, Mohanadarshan Vivekanandalingam <
 mo...@wso2.com> wrote:

> *WSO2 Complex Event Processor 3.0.0 Milestone 2 Released!*
>
> Date :5th July 2013
>
> This milestone is available at :
> https://svn.wso2.org/repos/wso2/people/suho/packs/cep/3.0.0/wso2cep-3.0.0-M2.zip
>
> To run the samples please follow the read-me,
> wso2cep-3.0.0/samples/cep-samples/ReadMe.txt
>
>
> Following are the bug fixes, improvements and the new features
>
> Bug
>
>- [CEP-258 ] - When trying
>to deploy the multiple configuration files, File reference is missing
>- [CEP-261 ] - Table is not
>properly generated when creating WSO2 Event mapping and Map mapping
>
> Improvement
>
>- [CEP-179 ] - It is better
>if the UI supports to check the validity of "Event Sink URL" when
>subscribing to a topic
>- [CEP-243 ] - Separate
>implementation classes & UI for handing in/out sequences of transport
>adapators
>- [CEP-247 ] - Making
>Coalesce as a ExecutorFunction
>- [CEP-248 ] - Removing
>conversion types from output attribute processor
>- [CEP-249 ] - Replacing
>Condition Extentions using bool returning Expression Extentions
>- [CEP-251 ] - White-board
>pattern for Transport Adaptors and Event sources
>- [CEP-257 ] - Event Tracer
>output in UI need to be formatted
>- [CEP-260 ] - UI to
>retrieve the deployed Event Formatter configuration details
>- [CEP-262 ] -
>EventFormatter to receive WSO2Event and format it to other different
>types.. For products like BAM
>- [CEP-267 ] -
>Listing/editing undeployed event builders
>- [CEP-268 ] - Handing
>dependency between the components when removing the configuration files
>
> New Feature
>
>- [CEP-156 ] - Add a default
>timeStamp convertor
>- [CEP-162 ] - Add Attribute
>Type Convetors to Siddhi
>- [CEP-215 ] 

Re: [Dev] Content Negociation Samples - JAX-RS/REST

2013-07-16 Thread Samisa Abeysinghe
This has an associated doc?


On Tue, Jul 16, 2013 at 7:01 PM, Sagara Gunathunga  wrote:

>
>
>
> On Tue, Jul 16, 2013 at 6:55 PM, Samisa Abeysinghe wrote:
>
>> Do we have $subject?
>>
>
> Yes we have one sample please refer "jaxrs_content_negotiation" sample on
> AS distro.
>
> Thanks !
>
>>
>> --
>>
>> Thanks,
>> Samisa...
>>
>> Samisa Abeysinghe
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com
>> http://wso2.org
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Sagara Gunathunga
>
> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
> V.P Apache Web Services;http://ws.apache.org/
> Linkedin; http://www.linkedin.com/in/ssagara
> Blog ;  http://ssagara.blogspot.com
>
>


-- 

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] [Architecture] Current Status of The Registry REST API and Issues I face when Integrate with APIM

2013-07-16 Thread Dinusha Senanayaka
Hi Vijitha,

On Tue, Jul 16, 2013 at 8:08 AM, Vijitha Kumara  wrote:

> Had a chat with Lakmali about this.
>
> As of now this requires a manual publishing of the REST API, but since
> this is a feature of the registry itself it would be good to ship it
> published OOTB?
>

+1. AFAIK there will be few admin services as well that need to do the API
Management in this release of GReg. Since all together there are only few
APIs that required API Management, it's good to ship them published OOTB.

>
> As we are not letting the REST API to be accessed without going through
> APIM component, the EnableAPIManagement property should be set to true by
> default as well or it can be ignored altogether? Or we can have a different
> property to denote any other aspect to be enabled//disabled other than
> default ones here?
>

The EnableAPIManagement property is a global one, that can be used by other
products as well. So, if GReg need this only for REST API and it need not
be accessed without API Management, you can set the default value of this
property to 'true' in GReg and override the carbon.xml at the product level.

Regards,
Dinusha.

>
>
>
> Regards,
> Vijitha.
>
>
>
> On Sun, Jul 14, 2013 at 9:09 PM, Dinusha Senanayaka wrote:
>
>> Hi Vijitha,
>>
>> On Sun, Jul 14, 2013 at 11:13 AM, Vijitha Kumara wrote:
>>
>>> Hi All,
>>>
>>> What's the status of this now? Do we have a working use case to be
>>> reviewed? We might need to finalize & test within next few days.
>>>
>> We have committed changes to trunk and have completed basic testing.  You
>> can use trunk GReg pack for testing..
>>
>> Regards,
>> Dinusha.
>>
>>>
>>>
>>>
>>> Regards,
>>> Vijitha.
>>>
>>>
>>>
>>> On Thu, Jun 20, 2013 at 11:20 AM, Dinusha Senanayaka 
>>> wrote:
>>>
 Hi Ragu,

 On Thu, Jun 20, 2013 at 10:52 AM, Sriragu Arudsothy 
 wrote:

> Hi Lakmali and Dinusha,
>
>
>As you have been completed the tomcat valve, shall I use the
> tomcat valve ( kind of interceptor) to test the Registry REST API with the
> externally running API Manager instance ?
>

 We are still working on supporting externally running API Manager
 instance. Will try to finish this by EOT.. But you can use inbuilt api-mgt
 support to test registry REST API.
 We have some concerns regarding the registry REST API;
 1. We need to have versioning support there. In the current API does
 not have the versions support..
 2. We need to pass both userName and tenantId as query params, if some
 user need to use the registry REST API. Having the user name is fine, but
 tenantId is something external users don't know. So having to pass tenantId
 to invoke rest API is not correct as we see.
 eg :
 http://localhost:9763/resource/comments?path=/_system/governance/apimgt/apiconf.xml&;
 *username=admin&tenantid=-1234 *

 Regards,
 Dinusha.

>
>  Thanks,
>  Ragu
>
>
>
> On Tue, Jun 18, 2013 at 1:20 PM, Dinusha Senanayaka 
> wrote:
>
>>
>>
>> On Tue, Jun 18, 2013 at 12:59 PM, Sriragu Arudsothy > > wrote:
>>
>>> Hai Dinusha,
>>>
>>>   At the later part of your answer, you mentioned
>>> the how to send the request. Do we have a use case where "without API
>>> manager". AFAIR, It has been clearly said during the final discussion ,
>>> request will be given inbuilt or external APIM. But you mention about
>>> without APIM.
>>>
>>
>> But, when it comes to services like DSS, AS etc, we need to have this
>> capability. Services, should be able to invoke with api management or
>> without api management. yes, for the GRreg (in built apis), manageAPIs 
>> will
>> be always true.
>>
>> Regards,
>> Dinusha.
>>
>>>
>>> Thanks!
>>> Ragu
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Jun 18, 2013 at 12:31 PM, Dinusha Senanayaka <
>>> dinu...@wso2.com> wrote:
>>>
 Hi Ragu,

 We have wrote a Tomcat Valve which will be act as interceptor for
 all incoming requests. There was a need of using
 Axis2ConfigurationContextObserver to get the throttling related 
 properties,
 which cannot be done through the CXF hander in GREG REST API. This 
 tomcat
 valve can be used not only by the GReg, also from any other product 
 like
 AS, DSS when it comes to manage APIs.

 Also we have been working on, getting publisher and store jaggery
 apps into Greg. It was not straight forward because just putting these 
 apps
 into GReg wont work. We had do some code changes in apimgt side to 
 avoid
 synapse dependencies. As an example, api-store and publisher need to 
 have
 apimgt-impl component been activated and while this module getting
 activated we are creating the 

[Dev] Any particular reason for datareceiver.war being committed?

2013-07-16 Thread Sumedha Rubasinghe
While taking a svn up, I noticed datareceiver.war is committed to

features/data-bridge/org.wso2.carbon.databridge.receiver.restapi.server.feature/src/main/resources/datareceiver.war

This will make a conflict every time a new checkout is made.


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


Re: [Dev] Exception during tenant cleanup

2013-07-16 Thread Chanika Geeganage
Hi,

Had an offline chat with Sameera and figured out that this should be
handled in the carbon core level and the ndatasource core should be changed
accordingly.

Thanks


On Tue, Jul 16, 2013 at 3:00 PM, Chanika Geeganage  wrote:

> Hi,
>
> This was because of the latest changes for the new caching model. I have
> attached the patch to [1].
>
> [1] https://wso2.org/jira/browse/DS-740
>
> Thanks
>
>
> On Mon, Jul 15, 2013 at 12:48 PM, Kasun Gajasinghe wrote:
>
>> Hi Chanika,
>>
>> Please try this in a latest pack from trunk.
>>
>>
>> On Mon, Jul 15, 2013 at 11:47 AM, Chanika Geeganage wrote:
>>
>>> Hi Azeez,
>>>
>>> I couldn't reproduce this error. I used DSS 3.0.1 and here are the steps
>>> I followed.
>>>
>>> 1. Created a tenant.
>>> 2. Sign in as the tenant admin.
>>> 2. Added a data source
>>> 3. Deployed a dataservice
>>> 4. Sign out and wait for the tenant cleanup.
>>>
>>> Then tenant is cleaned up without any exceptions. Is there any other
>>> steps to follow to reproduce the error?
>>>
>>> Thanks
>>>
>>>
>>> On Mon, Jul 15, 2013 at 10:39 AM, Chanika Geeganage wrote:
>>>
 I will check on this.

 Thanks


 On Sat, Jul 13, 2013 at 7:24 PM, Afkham Azeez  wrote:

> [2013-07-13 17:09:15,544]  INFO
> {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Starting to
> clean tenant : azeez.org
> [2013-07-13 17:09:15,966]  INFO
> {org.wso2.carbon.webapp.mgt.WebApplication} -  Unloaded webapp:
> StandardEngine[Catalina].StandardHost[localhost].StandardContext[/t/
> azeez.org/webapps/Calendar]
> [2013-07-13 17:09:15,970] ERROR
> {org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver}
> -  Error in initializing data sources for tenant: 1 - Error in getting all
> data sources from repository: null
> org.wso2.carbon.ndatasource.common.DataSourceException: Error in
> getting all data sources from repository: null
> at
> org.wso2.carbon.ndatasource.core.DataSourceRepository.updateAllUserDataSource(DataSourceRepository.java:143)
>  at
> org.wso2.carbon.ndatasource.core.DataSourceRepository.unregisterAllUserDataSources(DataSourceRepository.java:123)
> at
> org.wso2.carbon.ndatasource.core.DataSourceManager.unloadTenant(DataSourceManager.java:108)
>  at
> org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver.terminatingConfigurationContext(DataSourceAxis2ConfigurationContextObserver.java:49)
>  at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:515)
> at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:477)
>  at
> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:429)
> at
> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
>  at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>  at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>  at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>  at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.NullPointerException
>
> --
> *Afkham Azeez*
> Director of Architecture; WSO2, Inc.; http://wso2.com
> Member; Apache Software Foundation; http://www.apache.org/
> * **
> email: **az...@wso2.com* * cell: +94 77 3320919
> blog: **http://blog.afkham.org* *
> twitter: 
> **http://twitter.com/afkham_azeez*
> *
> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
> *
> *
> *Lean . Enterprise . Middleware*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 Best Regards..

 Chanika Geeganage
 Software Engineer
 WSO2, Inc.; http://wso2.com

 Mobile: +94773522586

>>>
>>>
>>>
>>> --
>>> Best Regards..
>>>
>>> Chanika Geeganage
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Mobile: +94773522586
>>>
>>
>>
>>
>> --
>> *Kasun Gajasinghe*
>> Software Engineer;
>> Development Techn

Re: [Dev] Why we need following methods in UserStoreManager API

2013-07-16 Thread Prabath Siriwardena
Also I found that someone had added this to ldapuserstoremanager only in 4.1.0 
- Asela will move that to the API

Sent from my mobile device

On Jul 16, 2013, at 9:05 PM, Prabath Siriwardena  wrote:

> This was added with the new API...
> 
> Sent from my mobile device
> 
> On Jul 16, 2013, at 8:53 PM, Amila Suriarachchi  wrote:
> 
>> 
>> 
>> 
>> On Mon, Jul 15, 2013 at 10:49 AM, Prabath Siriwardena  
>> wrote:
>>> 
>>> 
>>> On Mon, Jul 15, 2013 at 10:38 AM, Amila Suriarachchi  wrote:
 
 
 
 Here is another example. Registry has following method. This method is 
 used to check whether a given user in admin role and allow some 
 permissions (see the usage of this method) to user. If we have an hasRole 
 method as in here[1] we shall not require this method and code would have 
 written as 
 
 userRealm.hasRole(userName, "admin");
>>> 
>>> 
>>> We have the method, isUserHasRole(User, Role)  in UserStoreManager. Having 
>>> this in UserRealm is not that meaningful.
>> 
>> Seems like this method now not available in trunk :)
>> 
>> thanks,
>> Amila. 
>>> 
>>> Thanks & regards,
>>> -Prabath
>>>  
 
 public static boolean hasAdminAuthorizations(String userName, UserRealm 
 userRealm)
 throws RegistryException {
 
 try {
 UserStoreManager userStoreReader = 
 userRealm.getUserStoreManager();
 
 RealmConfiguration realmConfig;
 try {
 realmConfig = userRealm.getRealmConfiguration();
 } catch (UserStoreException e) {
 String msg = "Failed to retrieve realm configuration.";
 log.error(msg, e);
 throw new RegistryException(msg, e);
 }
 String systemUser = CarbonConstants.REGISTRY_SYSTEM_USERNAME;
 
 if (systemUser.equals(userName)) {
 return true;
 }
 
 String adminUser = realmConfig.getAdminUserName();
 if (adminUser.equals(userName)) {
 return true;
 }
 
 String[] roles = userStoreReader.getRoleListOfUser(userName);
 String adminRoleName = realmConfig.getAdminRoleName();
 if (containsString(adminRoleName, roles)) {
 return true;
 }
 
 } catch (UserStoreException e) {
 
 String msg = "Failed to check authorization level of user " +
 userName + ". Caused by: " + e.getMessage();
 log.error(msg, e);
 throw new RegistryException(msg, e);
 }
 
 return false;
 } 
 
 thanks,
 Amila.
 
 
 [1] 
 http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
> 
> With C5 we can keep such a simple API at core level and put admin 
> functionality to carbon components.
> 
> thanks,
> Amila. 
> 
> 
> [1] 
> http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
>> 
>> Thanks & regards,
>> -Prabath
>> 
>> 
>> On Thu, Jul 11, 2013 at 12:42 PM, Amila Suriarachchi  
>> wrote:
>>> 
>>> 
>>> 
>>> On Thu, Jul 11, 2013 at 10:21 AM, Prabath Siriwardena 
>>>  wrote:
 UserStoreManager API is not clean at all.. There so many stuff can 
 remove... Also maintain two interfaces one in the core and another in 
 API. We need to get rid of the interface in core..
 
 On Thu, Jul 11, 2013 at 10:06 AM, Asela Pathberiya  
 wrote:
> Hi All,
> 
> I am not sure why we are keeping following method in the API... 
> Sorry, if i have missed any thing  If there are on any usage, we 
> can remove them...
> 
> 1. String[] getAllSecondaryRoles() 
> 
> Why we need only the roles of secondary user store? 
 
 This is useful.. In a multi-tenanted environment - primary user store 
 is governed by the super tenant.. It's also better to have a method 
 getRoles(String userStoreDomain).
>>> 
>>> This is wrong. You should not try to get the roles from the UserStore. 
>>> Roles has to come from the Authorization manager.
>>> 
>>> thanks,
>>> Amila. 
 
 Thanks & regards,
 -Prabath
  
> 
> 2.  int getTenantId(String username)
> 
> Once user is authenticated, we knows the tenant Id.  Else why we need 
> to get the tenant id of a user who is not in its tenant space ?
>  
> 3. int getUserId(String username) 
> 
> What is the use of user id?  It seems to this is auto increment value 
> of UM_USER table
> 
>>

Re: [Dev] Why we need following methods in UserStoreManager API

2013-07-16 Thread Prabath Siriwardena
This was added with the new API...

Sent from my mobile device

On Jul 16, 2013, at 8:53 PM, Amila Suriarachchi  wrote:

> 
> 
> 
> On Mon, Jul 15, 2013 at 10:49 AM, Prabath Siriwardena  
> wrote:
>> 
>> 
>> On Mon, Jul 15, 2013 at 10:38 AM, Amila Suriarachchi  wrote:
>>> 
>>> 
>>> 
>>> Here is another example. Registry has following method. This method is used 
>>> to check whether a given user in admin role and allow some permissions (see 
>>> the usage of this method) to user. If we have an hasRole method as in 
>>> here[1] we shall not require this method and code would have written as 
>>> 
>>> userRealm.hasRole(userName, "admin");
>> 
>> 
>> We have the method, isUserHasRole(User, Role)  in UserStoreManager. Having 
>> this in UserRealm is not that meaningful.
> 
> Seems like this method now not available in trunk :)
> 
> thanks,
> Amila. 
>> 
>> Thanks & regards,
>> -Prabath
>>  
>>> 
>>> public static boolean hasAdminAuthorizations(String userName, UserRealm 
>>> userRealm)
>>> throws RegistryException {
>>> 
>>> try {
>>> UserStoreManager userStoreReader = 
>>> userRealm.getUserStoreManager();
>>> 
>>> RealmConfiguration realmConfig;
>>> try {
>>> realmConfig = userRealm.getRealmConfiguration();
>>> } catch (UserStoreException e) {
>>> String msg = "Failed to retrieve realm configuration.";
>>> log.error(msg, e);
>>> throw new RegistryException(msg, e);
>>> }
>>> String systemUser = CarbonConstants.REGISTRY_SYSTEM_USERNAME;
>>> 
>>> if (systemUser.equals(userName)) {
>>> return true;
>>> }
>>> 
>>> String adminUser = realmConfig.getAdminUserName();
>>> if (adminUser.equals(userName)) {
>>> return true;
>>> }
>>> 
>>> String[] roles = userStoreReader.getRoleListOfUser(userName);
>>> String adminRoleName = realmConfig.getAdminRoleName();
>>> if (containsString(adminRoleName, roles)) {
>>> return true;
>>> }
>>> 
>>> } catch (UserStoreException e) {
>>> 
>>> String msg = "Failed to check authorization level of user " +
>>> userName + ". Caused by: " + e.getMessage();
>>> log.error(msg, e);
>>> throw new RegistryException(msg, e);
>>> }
>>> 
>>> return false;
>>> } 
>>> 
>>> thanks,
>>> Amila.
>>> 
>>> 
>>> [1] 
>>> http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
 
 With C5 we can keep such a simple API at core level and put admin 
 functionality to carbon components.
 
 thanks,
 Amila. 
 
 
 [1] 
 http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
> 
> Thanks & regards,
> -Prabath
> 
> 
> On Thu, Jul 11, 2013 at 12:42 PM, Amila Suriarachchi  
> wrote:
>> 
>> 
>> 
>> On Thu, Jul 11, 2013 at 10:21 AM, Prabath Siriwardena  
>> wrote:
>>> UserStoreManager API is not clean at all.. There so many stuff can 
>>> remove... Also maintain two interfaces one in the core and another in 
>>> API. We need to get rid of the interface in core..
>>> 
>>> On Thu, Jul 11, 2013 at 10:06 AM, Asela Pathberiya  
>>> wrote:
 Hi All,
 
 I am not sure why we are keeping following method in the API... Sorry, 
 if i have missed any thing  If there are on any usage, we can 
 remove them...
 
 1. String[] getAllSecondaryRoles() 
 
 Why we need only the roles of secondary user store? 
>>> 
>>> This is useful.. In a multi-tenanted environment - primary user store 
>>> is governed by the super tenant.. It's also better to have a method 
>>> getRoles(String userStoreDomain).
>> 
>> This is wrong. You should not try to get the roles from the UserStore. 
>> Roles has to come from the Authorization manager.
>> 
>> thanks,
>> Amila. 
>>> 
>>> Thanks & regards,
>>> -Prabath
>>>  
 
 2.  int getTenantId(String username)
 
 Once user is authenticated, we knows the tenant Id.  Else why we need 
 to get the tenant id of a user who is not in its tenant space ?
  
 3. int getUserId(String username) 
 
 What is the use of user id?  It seems to this is auto increment value 
 of UM_USER table
 
 4.  int getTenantId()
 
 I guess,  tenant Id is not need to expose via user store manager API, 
 it is available with carbon context
 
 Thanks,
 Asela.
 
 -- 
 Thanks & Regards,
 Asela
 
 Mobile : +94 777 625 933
>>> 
>>> 
>>> 
>>> -- 
>>> Tha

Re: [Dev] Why we need following methods in UserStoreManager API

2013-07-16 Thread Amila Suriarachchi
On Mon, Jul 15, 2013 at 10:49 AM, Prabath Siriwardena wrote:

>
>
> On Mon, Jul 15, 2013 at 10:38 AM, Amila Suriarachchi wrote:
>
>>
>>
>>
>> Here is another example. Registry has following method. This method is
>> used to check whether a given user in admin role and allow some permissions
>> (see the usage of this method) to user. If we have an hasRole method as in
>> here[1] we shall not require this method and code would have written as
>>
>> userRealm.hasRole(userName, "admin");
>>
>
>
> We have the method, isUserHasRole(User, Role)  in UserStoreManager. Having
> this in UserRealm is not that meaningful.
>

Seems like this method now not available in trunk :)

thanks,
Amila.

>
> Thanks & regards,
> -Prabath
>
>
>>
>> public static boolean hasAdminAuthorizations(String userName, UserRealm
>> userRealm)
>> throws RegistryException {
>>
>> try {
>> UserStoreManager userStoreReader =
>> userRealm.getUserStoreManager();
>>
>> RealmConfiguration realmConfig;
>> try {
>> realmConfig = userRealm.getRealmConfiguration();
>> } catch (UserStoreException e) {
>> String msg = "Failed to retrieve realm configuration.";
>> log.error(msg, e);
>> throw new RegistryException(msg, e);
>> }
>> String systemUser = CarbonConstants.REGISTRY_SYSTEM_USERNAME;
>>
>> if (systemUser.equals(userName)) {
>> return true;
>> }
>>
>> String adminUser = realmConfig.getAdminUserName();
>> if (adminUser.equals(userName)) {
>> return true;
>> }
>>
>> String[] roles = userStoreReader.getRoleListOfUser(userName);
>> String adminRoleName = realmConfig.getAdminRoleName();
>> if (containsString(adminRoleName, roles)) {
>> return true;
>> }
>>
>> } catch (UserStoreException e) {
>>
>> String msg = "Failed to check authorization level of user " +
>> userName + ". Caused by: " + e.getMessage();
>> log.error(msg, e);
>> throw new RegistryException(msg, e);
>> }
>>
>> return false;
>> }
>>
>>  thanks,
>> Amila.
>>
>>
>> [1]
>> http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
>>
>>>
>>> With C5 we can keep such a simple API at core level and put admin
>>> functionality to carbon components.
>>>
>>> thanks,
>>> Amila.
>>>
>>>
>>> [1]
>>> http://tomcat.apache.org/tomcat-5.5-doc/catalina/docs/api/org/apache/catalina/Realm.html
>>>

 Thanks & regards,
 -Prabath


 On Thu, Jul 11, 2013 at 12:42 PM, Amila Suriarachchi wrote:

>
>
>
> On Thu, Jul 11, 2013 at 10:21 AM, Prabath Siriwardena <
> prab...@wso2.com> wrote:
>
>> UserStoreManager API is not clean at all.. There so many stuff can
>> remove... Also maintain two interfaces one in the core and another in 
>> API.
>> We need to get rid of the interface in core..
>>
>> On Thu, Jul 11, 2013 at 10:06 AM, Asela Pathberiya wrote:
>>
>>> Hi All,
>>>
>>> I am not sure why we are keeping following method in the API...
>>> Sorry, if i have missed any thing  If there are on any usage, we can
>>> remove them...
>>>
>>> 1. String[] getAllSecondaryRoles()
>>>
>>> Why we need only the roles of secondary user store?
>>>
>>
>> This is useful.. In a multi-tenanted environment - primary user store
>> is governed by the super tenant.. It's also better to have a method
>> getRoles(String userStoreDomain).
>>
>
> This is wrong. You should not try to get the roles from the UserStore.
> Roles has to come from the Authorization manager.
>
> thanks,
> Amila.
>
>>
>> Thanks & regards,
>> -Prabath
>>
>>
>>>
>>> 2.  int getTenantId(String username)
>>>
>>> Once user is authenticated, we knows the tenant Id.  Else why we
>>> need to get the tenant id of a user who is not in its tenant space ?
>>>
>>> 3. int getUserId(String username)
>>>
>>> What is the use of user id?  It seems to this is
>>> auto increment value of UM_USER table
>>>
>>> 4.  int getTenantId()
>>>
>>> I guess,  tenant Id is not need to expose via user store manager
>>> API, it is available with carbon context
>>>
>>> Thanks,
>>> Asela.
>>>
>>> --
>>> Thanks & Regards,
>>> Asela
>>>
>>> Mobile : +94 777 625 933
>>>
>>
>>
>>
>> --
>> 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
>>

Re: [Dev] [Build Failure] RSS-Manager

2013-07-16 Thread Prabath Abeysekera
Looks like I've dropped dev@ by mistake. :)

On Tue, Jul 16, 2013 at 8:06 PM, Pradeep Fernando  wrote:

> yes, getting an svn up in the component solved it..
>

Cool. Sorry for the inconvenience caused.


Cheers,
Prabath



>
>
> On Tue, Jul 16, 2013 at 8:04 PM, Prabath Abeysekera wrote:
>
>> Hi Pradeep,
>>
>> Do you have a latest up? I missed a commit in the evening but fixed it a
>> few minutes later.
>>
>>
>> Cheers,
>> Prabath
>>
>>
>> On Tue, Jul 16, 2013 at 7:46 PM, Pradeep Fernando wrote:
>>
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[26,50]
>>> package org.wso2.carbon.rssmanager.common.exception does not exist
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[65,56]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>> [ERROR] location: class
>>> org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[84,75]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>> [ERROR] location: class
>>> org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[23,50]
>>> package org.wso2.carbon.rssmanager.common.exception does not exist
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseDAOImpl.java:[23,50]
>>> package org.wso2.carbon.rssmanager.common.exception does not exist
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[77,26]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>> [ERROR] location: class
>>> org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[91,26]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>> [ERROR] location: class
>>> org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[55,17]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>> [ERROR] location: class
>>> org.wso2.carbon.rssmanager.core.dao.impl.DatabaseUserDAOImpl
>>> [ERROR]
>>> /home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[111,21]
>>> cannot find symbol
>>> [ERROR] symbol  : class RSSManagerCommonException
>>>
>>>
>>>
>>
>>
>> --
>> Prabath Abeysekara
>> Associate Technical Lead, Data TG.
>> WSO2 Inc.
>> Email: praba...@wso2.com 
>> Mobile: +94774171471
>>
>> 
>>
>
>
>
> --
> *Pradeep Fernando*
> Associate Technical Lead;WSO2 Inc.; http://wso2.com
>
> blog: http://pradeepfernando.blogspot.com
> m: +94776603662
>



-- 
Prabath Abeysekara
Associate Technical Lead, Data TG.
WSO2 Inc.
Email: praba...@wso2.com 
Mobile: +94774171471


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


Re: [Dev] Fwd: Platform trunk broken when building in a clean local repository

2013-07-16 Thread Johann Nallathamby
This is fixed with r178413.

Thanks,
Johann.


On Tue, Jul 16, 2013 at 10:51 AM, Randika Ratnayake wrote:

>
>
> -- Forwarded message --
> From: Randika Ratnayake 
> Date: Mon, Jul 15, 2013 at 8:47 PM
> Subject: Platform trunk broken when building in a clean local repository
> To: support-dev-group 
>
>
>
> hi all ,
> when i try to build the platform trunk in a clean local repository it
> gives the follwing error ,
>
>  The project
> org.wso2.carbon:org.wso2.carbon.identity.provider.mgt.ui:4.2.0-SNAPSHOT
> (/home/randika/svn/carbon/platform/branches/trunk/components/identity/org.wso2.carbon.identity.provider.mgt.ui/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> org.wso2.carbon:security:pom:4.2.0-SNAPSHOT and 'parent.relativePath'
> points at wrong local POM @ line 19, column 13 -> [Help 2]
> [ERROR]
> [ERROR]   The project
> org.wso2.carbon:org.wso2.carbon.identity.provider.mgt.ui.feature:4.2.0-SNAPSHOT
> (/home/randika/svn/carbon/platform/branches/trunk/features/identity/identity-provider-mgt/org.wso2.carbon.identity.provider.mgt.ui.feature/pom.xml)
> has 1 error
> [ERROR] Non-resolvable parent POM: Could not find artifact
> org.wso2.carbon:identity-provider-feature:pom:4.2.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM @ line 21, column 10 ->
> [Help 2]
> [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]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> please look into this .
>
> Thanks
> Randika
>
>
> --
> Randika Ratnayake,
> Mobile : +94773-440677 
>
>
>
> --
> Randika Ratnayake,
> Mobile : +94773-440677 
>
> ___
> 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


[Dev] Bringing back "carbon.registry.root" carbon property

2013-07-16 Thread Sriskandarajah Suhothayan
Hi,

With CEP 3.0.0 effort we are building ESB like samples for CEP where we can
up CEP with the sample numbers and run the samples.

Here since CEP stores stream definitions (DataBridge Streams) in the
governance registry space we are currently having issues isolating a test
space from the registry.

We can achieve this functionality if we can specify the
carbon.registry.root as system property.
But according to the "[Carbon-dev] Getting rid of Carbon System properties"
discussion made on 22/7/2009 this system property was removed and now we
can only change the registry root via the registry.xml

Please do raise your concern if you have issues in bringing back this
system property

Thanks
Suho


-- 
*S. Suhothayan
*
Associate Technical Lead,
 *WSO2 Inc. *http://wso2.com *
 *
lean . enterprise . middleware

*cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/
twitter: http://twitter.com/suhothayan | linked-in:
http://lk.linkedin.com/in/suhothayan*
*
*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [Build Failure] RSS-Manager

2013-07-16 Thread Pradeep Fernando
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[26,50]
package org.wso2.carbon.rssmanager.common.exception does not exist
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[65,56]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
[ERROR] location: class org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[84,75]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
[ERROR] location: class org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[23,50]
package org.wso2.carbon.rssmanager.common.exception does not exist
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseDAOImpl.java:[23,50]
package org.wso2.carbon.rssmanager.common.exception does not exist
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[77,26]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
[ERROR] location: class org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/util/RSSDAOUtil.java:[91,26]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
[ERROR] location: class org.wso2.carbon.rssmanager.core.dao.util.RSSDAOUtil
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[55,17]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
[ERROR] location: class
org.wso2.carbon.rssmanager.core.dao.impl.DatabaseUserDAOImpl
[ERROR]
/home/pradeep/checkout/carbon-trunk/platform/components/rss-manager/org.wso2.carbon.rssmanager.core/src/main/java/org/wso2/carbon/rssmanager/core/dao/impl/DatabaseUserDAOImpl.java:[111,21]
cannot find symbol
[ERROR] symbol  : class RSSManagerCommonException
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Decoupling webapp-mgt component and bam.webapp.statistic publisher

2013-07-16 Thread Sameera Jayasoma
On Tue, Jul 16, 2013 at 6:18 PM, Geeth Munasinghe  wrote:

> Hi
>
> For next AS release we have implemented a data-agent to publish web
> applications statistics to BAM. In AS user can enable or disable statistics
> publishing functionality for each web applications separately from using
> either of following methods.
>
>
>1. Webapp developers can  add a  context-param called 'enable.
>statistics' to the web.xml in webapps
>
>
IMO, we should stick only to adding a context parameter to enable
statistics. We can update the Developer studio  to support this feature.

As you've explained to its bit complex to implement the management UI
support for this. Why do we wanna introduce such a complexity to implement
a simple UI feature? Anyway we are getting rid of these sort of
UI functionalities from our management consoles. Once such example would
be, securing a web service using our management console. We are getting rid
of this feature and moving this to the Developer studio.

Thanks,
Sameera.


>1. In webapp-mgt console we have given a check box for user to enable
>or disable web app statistics for each web application.
>
> User can user either one of them.
>
> For the second scenario we maintain a hash map and registry resource in
> bam.webapp.statistic.publisher component. When user click the check box in
> webapp-mgt.ui to enable or disable statistic, bam.webapp.statistic
> publisher component updates registry and hashmap. when a request comes to
> tomcat valve implemented in bam.webapp.statistic publisher component, it
> check in the hashmap to verify statistic publishing enabled or disabled. if
> the value does not exist in hashmap, it reads from the registry and
> update the hashmap.
>
> To give statistics enable and disable  function from webapp-mgt ui for
> webapps, we have to add  bam.webapp.statistic.publisher.stub as a
> dependency to webapp-mgt.ui. This causes a problem when GREG product
> building, because it has a dependency of webapp-mgt.ui and webapp-mgt.ui
> has bam.webapp.statistic.publisher.stub dependency.
>
> One way to resolve this issue is add bam.webapp.statistic.publisher.stub
> to webapp-mgt.ui as a optional dependency and check in osgi level weather
> that dependency exists.
> WDYT?
>
> *G. K. S. Munasinghe
> *
> *Software Engineer,*
> *WSO2, Inc. http://wso2.com *
> *lean.enterprise.middleware.*
> *
> *
> email: ge...@wso2.com
> phone:(+94) 777911226
>



-- 
Sameera Jayasoma,
Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections

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


Re: [Dev] UI integration test failure in Greg in tests-ui

2013-07-16 Thread Krishantha Samaraweera
Please ignore the last mail.

Thanks,
Krishatntha.

On Tue, Jul 16, 2013 at 7:14 PM, Krishantha Samaraweera  wrote:

>  Hi G-Reg team,
>
> Please fix all the
>
>
> On Tue, Jul 16, 2013 at 5:30 PM, Randika Ratnayake wrote:
>
>> executed all the test cases ,
>> here are the test failiurs
>>
>> SearchActivityTestCase- Due to search activity functionality issue
>> ApiTestCase - Due to API list doesn't display the added API
>> WsPolicyTestCase- Due to policies doesn't display in the policy list page
>> UriTestCase- added URI doesn't display in the URI list Page
>> WsdlTestCase - Added WSDL doesn't display in the WSDL LIST Page
>>
>> Thanks
>> Randika.
>>
>>
>>
>>
>>
>>
>> On Tue, Jul 16, 2013 at 2:42 PM, Randika Ratnayake wrote:
>>
>>> hi all ,
>>> I m currently executing the selenium test cases for the governance
>>> registry the. found 2 bugs causing the test failurs please refer below jira
>>> for the further information of the issues.
>>>
>>>   REGISTRY-1674 
>>>
>>>1. REGISTRY-1675 
>>>
>>>
>>> Thanks
>>> Randika
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Jul 8, 2013 at 10:14 AM, Randika Ratnayake wrote:
>>>
 ill execute the Greg selenium tests  against the new release most of
 the ui elements have changed ill inform once its fixed

 Regards
 Randika


 On Fri, Jul 5, 2013 at 11:08 AM, Krishantha Samaraweera <
 krishan...@wso2.com> wrote:

> Most probably those selenium locators have changed in this release.
>
> Thanks,
> Krishantha.
>
>
> On Fri, Jul 5, 2013 at 10:59 AM, Pulasthi Supun wrote:
>
>> Hi QAA team
>>
>> There are several integration test failures in the UI automation
>> tests in greg [1]. It seems that some xpaths and id's defined in the
>> properties file are incorrect. can someone from the automaton team take a
>> look at this and fix them. i have attached the surefire reports.
>>
>> Thanks,
>> Pulasthi
>>
>> [1]
>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/greg/modules/integration/registry/tests-ui/
>> --
>> --
>> Pulasthi Supun
>> Software Engineer; WSO2 Inc.; http://wso2.com,
>> Email: pulas...@wso2.com
>> Mobile: +94 (71) 9258281
>> Blog : http://pulasthisupun.blogspot.com/
>> Git hub profile: https://github.com/pulasthi
>>
>
>


 --
 Randika Ratnayake,
 Mobile : +94773-440677 

>>>
>>>
>>>
>>> --
>>> Randika Ratnayake,
>>> Mobile : +94773-440677 
>>>
>>
>>
>>
>> --
>> Randika Ratnayake,
>> Mobile : +94773-440677 
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] UI integration test failure in Greg in tests-ui

2013-07-16 Thread Krishantha Samaraweera
 Hi G-Reg team,

Please fix all the

On Tue, Jul 16, 2013 at 5:30 PM, Randika Ratnayake  wrote:

> executed all the test cases ,
> here are the test failiurs
>
> SearchActivityTestCase- Due to search activity functionality issue
> ApiTestCase - Due to API list doesn't display the added API
> WsPolicyTestCase- Due to policies doesn't display in the policy list page
> UriTestCase- added URI doesn't display in the URI list Page
> WsdlTestCase - Added WSDL doesn't display in the WSDL LIST Page
>
> Thanks
> Randika.
>
>
>
>
>
>
> On Tue, Jul 16, 2013 at 2:42 PM, Randika Ratnayake wrote:
>
>> hi all ,
>> I m currently executing the selenium test cases for the governance
>> registry the. found 2 bugs causing the test failurs please refer below jira
>> for the further information of the issues.
>>
>>   REGISTRY-1674 
>>
>>1. REGISTRY-1675 
>>
>>
>> Thanks
>> Randika
>>
>>
>>
>>
>>
>> On Mon, Jul 8, 2013 at 10:14 AM, Randika Ratnayake wrote:
>>
>>> ill execute the Greg selenium tests  against the new release most of the
>>> ui elements have changed ill inform once its fixed
>>>
>>> Regards
>>> Randika
>>>
>>>
>>> On Fri, Jul 5, 2013 at 11:08 AM, Krishantha Samaraweera <
>>> krishan...@wso2.com> wrote:
>>>
 Most probably those selenium locators have changed in this release.

 Thanks,
 Krishantha.


 On Fri, Jul 5, 2013 at 10:59 AM, Pulasthi Supun wrote:

> Hi QAA team
>
> There are several integration test failures in the UI automation tests
> in greg [1]. It seems that some xpaths and id's defined in the properties
> file are incorrect. can someone from the automaton team take a look at 
> this
> and fix them. i have attached the surefire reports.
>
> Thanks,
> Pulasthi
>
> [1]
> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/greg/modules/integration/registry/tests-ui/
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>


>>>
>>>
>>> --
>>> Randika Ratnayake,
>>> Mobile : +94773-440677 
>>>
>>
>>
>>
>> --
>> Randika Ratnayake,
>> Mobile : +94773-440677 
>>
>
>
>
> --
> Randika Ratnayake,
> Mobile : +94773-440677 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] NEP at org.wso2.carbon.caching.impl.CacheManagerFactoryImpl.getCacheManager(CacheManagerFactoryImpl.java:78)

2013-07-16 Thread Sameera Jayasoma
I've committed this CarbonContexCreator class.  Miyuru and Sanjeewa test
your cases and let me know if there any change to be done.

Thanks,
Sameera.


On Tue, Jul 16, 2013 at 12:10 PM, Miyuru Wanninayaka wrote:

> We will move this hander kernel as this handler is required for all
> products in non-http transport scenarios too.
>
>
> On Tue, Jul 16, 2013 at 11:25 AM, Miyuru Wanninayaka wrote:
>
>> Hi all,
>>
>> I was able to get this working with axis2 handler and small change to
>> synapse-greg registry bridge.
>> Now both GReg integration and security scenarios working fine.
>>
>> Still we need to assess overhead of setting thread local in every message.
>>
>>
>> On Fri, Jul 12, 2013 at 11:40 AM, Amila Suriarachchi wrote:
>>
>>>
>>>
>>>
>>> On Fri, Jul 12, 2013 at 11:33 AM, Miyuru Wanninayaka wrote:
>>>
 Hi Amila,

 On Fri, Jul 12, 2013 at 11:27 AM, Amila Suriarachchi wrote:

>
>
>
> On Fri, Jul 12, 2013 at 11:17 AM, Miyuru Wanninayaka 
> wrote:
>
>> Hi Dushan,
>>
>> Dispatcher/Handler will only help in cases where message come to
>> synapse from outside.
>>
>> For other cases, we need to develop a extension point in synapse
>> which invokes after a thread spawn to set CC as thread local.
>>
>> Seems we can get AxisConfiguration in any place which synapse create
>> a new thread. So we can develop a handler API which has something like
>>
>> public void populateThreadLocal(AxisConfiguration) or something
>>
>> which figure out tenant information and  polulate CC.
>>
>> @Azeez, can we figure out tenant information by looking at
>> AxisConfiguration?
>> Using something like AxisConfiguration.getRepository()
>
>
> In here you need to think about how to get the tenant information from
> the request message. Always we need to get the tenant information from the
> request message and set to thread local. There are two ways
>
> 1. From the request URI
> 2. user name - user can have tenant qualified name
>

 both these are not available for pooling/non-http transports

>>>
>>> We don't support those transports for MT. Those transports only for ST.
>>> So we can assume always ST for those transports.
>>>
>>> thanks,
>>> Amila.
>>>


> thanks,
> Amila.
>
>>
>>
>> On Fri, Jul 12, 2013 at 10:19 AM, Dushan Abeyruwan 
>> wrote:
>>
>>> Hi Miyru,
>>>I think we can intercept the Carbon context by writing a dispatch
>>> in DispatchPhase this can be a component whose suppose to resides 
>>> outside
>>> synapse.
>>>
>>>
>>> Cheers
>>> Dushan
>>>
>>>
>>> On Fri, Jul 12, 2013 at 9:58 AM, Afkham Azeez wrote:
>>>



 On Fri, Jul 12, 2013 at 9:54 AM, Miyuru Wanninayaka <
 miy...@wso2.com> wrote:

>
>
> On Fri, Jul 12, 2013 at 9:36 AM, Afkham Azeez wrote:
>
>>
>>
>>
>> On Fri, Jul 12, 2013 at 7:28 AM, Miyuru Wanninayaka <
>> miy...@wso2.com> wrote:
>>
>>> Hi Azeez,
>>>
>>> Sorry, we were not properly following dev@ discussions recently
>>> as team was very busy with ESB 4.7 release.
>>>
>>> Yes we can set proper CC as thread local in request path via
>>> handler for NIO transports by looking at To address. But how this 
>>> can
>>> implement in generic manner for other transport ( JMS, VFS). 
>>> May be
>>> since other transports does not support MT anyway, we can always 
>>> set ST CC
>>> for non http transports?
>>>
>>> Also how we can handle thread switching in response path of NIO?
>>> Handler will not help in response path.
>>>
>>> Also there are some mediation threads spawns within synapse
>>> without going through axis2 flow such as
>>> * Synapse tasks
>>> * Message processors
>>> * Priority executors
>>> * Clone and iterate mediators
>>>
>>> How can we set CC in these cases?
>>
>>
>> Any bit of execution has to to be associated with some tenant. It
>> is true for everything listed above. We need to track things like 
>> how much
>> CPU time each tenant consumed and so on. So you need to identify the
>> relevant plug points, and inject the proper CC.
>>
>
> Only problem is above mentioned flows cannot intercept from
> outside of synapse. In such case do we have alternative than writing 
> carbon
> specific code inside synapse?
>


 No. This is why interfaces are needed. We have done this enough &
 more time for Axis2, without writing WSO2 specific code in Axis2.


>
>>

Re: [Dev] Content Negociation Samples - JAX-RS/REST

2013-07-16 Thread Sagara Gunathunga
On Tue, Jul 16, 2013 at 6:55 PM, Samisa Abeysinghe  wrote:

> Do we have $subject?
>

Yes we have one sample please refer "jaxrs_content_negotiation" sample on
AS distro.

Thanks !

>
> --
>
> Thanks,
> Samisa...
>
> Samisa Abeysinghe
> VP Engineering
> WSO2 Inc.
> http://wso2.com
> http://wso2.org
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Sagara Gunathunga

Senior Technical Lead; WSO2, Inc.;  http://wso2.com
V.P Apache Web Services;http://ws.apache.org/
Linkedin; http://www.linkedin.com/in/ssagara
Blog ;  http://ssagara.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Content Negociation Samples - JAX-RS/REST

2013-07-16 Thread Samisa Abeysinghe
Do we have $subject?

-- 

Thanks,
Samisa...

Samisa Abeysinghe
VP Engineering
WSO2 Inc.
http://wso2.com
http://wso2.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] ESB 4.7.0 payloadFactory -- Some problems - Needs clarification

2013-07-16 Thread Susinda Perera
Hi ESB team

Suppose we have a sample payloadFactory configuration as follows


json body








1. Is there any use cases such that *media-type="json"* and <*arg
evaluator="xml"*  will be used
2. Possible use case of *media-type="xml"* and <*arg
evaluator="json"*(opposite of the question one)

And some synapse code problems
payloadFactoryMediator has has methods called getJsonPathArgumentList() and
getXPathArgumentList(). I used these methods to access arguments, issue was
the value type argument () is returned from both methods.

3. Is this a bug or intended behavior.

And a suggestion
4 .How about giving the config something like follows (omitting the
evaluator because in code level it is handled in that way). Hope this
simplifies coding and understandability.








-- 
*Susinda Perera*
Software Engineer
Mobile:(+94)716049075

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


Re: [Dev] [Build Failure] [AS] Product profile-gen build fails

2013-07-16 Thread Piyum Fernando
Hi,

This is because dep-sync git.feature is not included in the dep-sync
composite feature. So we missed the featureArtifactDef for git in AS
product profile-gen.

Fixed the issue.

Thanks.


On Tue, Jul 16, 2013 at 6:02 PM, Sameera Jayasoma  wrote:

> !ENTRY org.eclipse.equinox.p2.director.app 4 0 2013-07-16 18:01:12.290
> !MESSAGE The installable unit
> org.wso2.carbon.deployment.synchronizer.git.feature.group/4.2.0.SNAPSHOT
> has not been found.
>
> Please fix.
>
> --
> Sameera Jayasoma,
> Architect,
>
> WSO2, Inc. (http://wso2.com)
> email: same...@wso2.com
> blog: http://sameera.adahas.org
> twitter: https://twitter.com/sameerajayasoma
> flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
>
> Lean . Enterprise . Middleware
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Piyum Fernando
Software Engineer

Mobile: +94 77 22 93 880
Home:  +94 31 22 75 715
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Decoupling webapp-mgt component and bam.webapp.statistic publisher

2013-07-16 Thread Geeth Munasinghe
Hi

For next AS release we have implemented a data-agent to publish web
applications statistics to BAM. In AS user can enable or disable statistics
publishing functionality for each web applications separately from using
either of following methods.


   1. Webapp developers can  add a  context-param called 'enable.statistics'
   to the web.xml in webapps
   2. In webapp-mgt console we have given a check box for user to enable or
   disable web app statistics for each web application.

User can user either one of them.

For the second scenario we maintain a hash map and registry resource in
bam.webapp.statistic.publisher component. When user click the check box in
webapp-mgt.ui to enable or disable statistic, bam.webapp.statistic
publisher component updates registry and hashmap. when a request comes to
tomcat valve implemented in bam.webapp.statistic publisher component, it
check in the hashmap to verify statistic publishing enabled or disabled. if
the value does not exist in hashmap, it reads from the registry and update
the hashmap.

To give statistics enable and disable  function from webapp-mgt ui for
webapps, we have to add  bam.webapp.statistic.publisher.stub as a
dependency to webapp-mgt.ui. This causes a problem when GREG product
building, because it has a dependency of webapp-mgt.ui and webapp-mgt.ui
has bam.webapp.statistic.publisher.stub dependency.

One way to resolve this issue is add bam.webapp.statistic.publisher.stub
to webapp-mgt.ui as a optional dependency and check in osgi level weather
that dependency exists.
WDYT?

*G. K. S. Munasinghe
*
*Software Engineer,*
*WSO2, Inc. http://wso2.com *
*lean.enterprise.middleware.*
*
*
email: ge...@wso2.com
phone:(+94) 777911226
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [Build Failure] [AS] Product profile-gen build fails

2013-07-16 Thread Sameera Jayasoma
!ENTRY org.eclipse.equinox.p2.director.app 4 0 2013-07-16 18:01:12.290
!MESSAGE The installable unit
org.wso2.carbon.deployment.synchronizer.git.feature.group/4.2.0.SNAPSHOT
has not been found.

Please fix.

-- 
Sameera Jayasoma,
Architect,

WSO2, Inc. (http://wso2.com)
email: same...@wso2.com
blog: http://sameera.adahas.org
twitter: https://twitter.com/sameerajayasoma
flickr: http://www.flickr.com/photos/sameera-jayasoma/collections

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


Re: [Dev] UI integration test failure in Greg in tests-ui

2013-07-16 Thread Randika Ratnayake
executed all the test cases ,
here are the test failiurs

SearchActivityTestCase- Due to search activity functionality issue
ApiTestCase - Due to API list doesn't display the added API
WsPolicyTestCase- Due to policies doesn't display in the policy list page
UriTestCase- added URI doesn't display in the URI list Page
WsdlTestCase - Added WSDL doesn't display in the WSDL LIST Page

Thanks
Randika.






On Tue, Jul 16, 2013 at 2:42 PM, Randika Ratnayake  wrote:

> hi all ,
> I m currently executing the selenium test cases for the governance
> registry the. found 2 bugs causing the test failurs please refer below jira
> for the further information of the issues.
>
>   REGISTRY-1674 
>
>1. REGISTRY-1675 
>
>
> Thanks
> Randika
>
>
>
>
>
> On Mon, Jul 8, 2013 at 10:14 AM, Randika Ratnayake wrote:
>
>> ill execute the Greg selenium tests  against the new release most of the
>> ui elements have changed ill inform once its fixed
>>
>> Regards
>> Randika
>>
>>
>> On Fri, Jul 5, 2013 at 11:08 AM, Krishantha Samaraweera <
>> krishan...@wso2.com> wrote:
>>
>>> Most probably those selenium locators have changed in this release.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>>
>>> On Fri, Jul 5, 2013 at 10:59 AM, Pulasthi Supun wrote:
>>>
 Hi QAA team

 There are several integration test failures in the UI automation tests
 in greg [1]. It seems that some xpaths and id's defined in the properties
 file are incorrect. can someone from the automaton team take a look at this
 and fix them. i have attached the surefire reports.

 Thanks,
 Pulasthi

 [1]
 http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/greg/modules/integration/registry/tests-ui/
 --
 --
 Pulasthi Supun
 Software Engineer; WSO2 Inc.; http://wso2.com,
 Email: pulas...@wso2.com
 Mobile: +94 (71) 9258281
 Blog : http://pulasthisupun.blogspot.com/
 Git hub profile: https://github.com/pulasthi

>>>
>>>
>>
>>
>> --
>> Randika Ratnayake,
>> Mobile : +94773-440677 
>>
>
>
>
> --
> Randika Ratnayake,
> Mobile : +94773-440677 
>



-- 
Randika Ratnayake,
Mobile : +94773-440677 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Compilation Failure

2013-07-16 Thread Lalaji Sureshika
Hi,

This is sorted out..It's due to a old twitter jar placed in my m2
repo.Thanks Dushan..

Thanks;


On Tue, Jul 16, 2013 at 3:53 AM, Dushan Abeyruwan  wrote:

> Hi
>Please take update in twitter connector and try to build it again.
> Cheers
> Dushan
>
>
> On Tue, Jul 16, 2013 at 4:05 PM, Lalaji Sureshika  wrote:
>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
>> (default-compile) on project
>> org.wso2.carbon.mediation.library.connectors.twitter: Compilation failure:
>> Compilation failure:
>> [ERROR]
>> /home/lalaji/trunk/platform/components/mediation/mediation-library/connectors/org.wso2.carbon.mediation.library.connectors.twitter/src/main/java/org/wso2/carbon/mediation/library/connectors/twitter/TwitterSearch.java:[85,41]
>> incompatible types
>> [ERROR] found   : java.util.List
>> [ERROR] required: java.util.List
>>
>> What am I missing..? I updated orbit,kernel and platform..
>>
>> Thanks;
>>
>> --
>> Lalaji Sureshika
>> WSO2, Inc.;  http://wso2.com/
>> email: lal...@wso2.com; cell: +94 71 608 6811
>> blog: http://lalajisureshika.blogspot.com
>>
>>
>>
>
>
> --
> Dushan Abeyruwan
> Associate Tech Lead
> *Integration Technologies Team*
> *WSO2 Inc. http://wso2.com/*
> *Mobile:(+94)714408632*
>



-- 
Lalaji Sureshika
WSO2, Inc.;  http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Need a release version of Jaggery for MDM

2013-07-16 Thread Dilshan Edirisuriya
Name was somewhat misleading. I will use this one. Thanks.


On Tue, Jul 16, 2013 at 4:40 PM, Nuwan Bandara  wrote:

> Hi Dilshan,
>
> Its not a snapshot. Its a released version based on the Jaggery master.
>
> Regards,
> /Nuwan
>
>
> On Tue, Jul 16, 2013 at 2:14 PM, Dilshan Edirisuriya wrote:
>
>> Hi,
>>
>> We need the latest release version of Jaggery for MDM. Right now the the
>> release version found in Nexus is 0.9.0.ALPHA2-wso2v5 which was added last
>> month. This does not have the latest changes we need. However when we use
>> the version 0.9.0-SNAPSHOT-07042013 added on July 4th all works well. Since
>> this is a snapshot version is it ok to use it or will you be able to add a
>> release version there? Please advice.
>>
>> Regards,
>>
>> Dilshan
>>
>
>
>
> --
> *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 763
> 9629
> *
> 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Need a release version of Jaggery for MDM

2013-07-16 Thread Nuwan Bandara
Hi Dilshan,

Its not a snapshot. Its a released version based on the Jaggery master.

Regards,
/Nuwan


On Tue, Jul 16, 2013 at 2:14 PM, Dilshan Edirisuriya wrote:

> Hi,
>
> We need the latest release version of Jaggery for MDM. Right now the the
> release version found in Nexus is 0.9.0.ALPHA2-wso2v5 which was added last
> month. This does not have the latest changes we need. However when we use
> the version 0.9.0-SNAPSHOT-07042013 added on July 4th all works well. Since
> this is a snapshot version is it ok to use it or will you be able to add a
> release version there? Please advice.
>
> Regards,
>
> Dilshan
>



-- 
*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 763 9629
*

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


Re: [Dev] Compilation Failure

2013-07-16 Thread Dushan Abeyruwan
Hi
   Please take update in twitter connector and try to build it again.
Cheers
Dushan


On Tue, Jul 16, 2013 at 4:05 PM, Lalaji Sureshika  wrote:

> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
> (default-compile) on project
> org.wso2.carbon.mediation.library.connectors.twitter: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/lalaji/trunk/platform/components/mediation/mediation-library/connectors/org.wso2.carbon.mediation.library.connectors.twitter/src/main/java/org/wso2/carbon/mediation/library/connectors/twitter/TwitterSearch.java:[85,41]
> incompatible types
> [ERROR] found   : java.util.List
> [ERROR] required: java.util.List
>
> What am I missing..? I updated orbit,kernel and platform..
>
> Thanks;
>
> --
> Lalaji Sureshika
> WSO2, Inc.;  http://wso2.com/
> email: lal...@wso2.com; cell: +94 71 608 6811
> blog: http://lalajisureshika.blogspot.com
>
>
>


-- 
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/*
*Mobile:(+94)714408632*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Compilation Failure

2013-07-16 Thread Lalaji Sureshika
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0:compile
(default-compile) on project
org.wso2.carbon.mediation.library.connectors.twitter: Compilation failure:
Compilation failure:
[ERROR]
/home/lalaji/trunk/platform/components/mediation/mediation-library/connectors/org.wso2.carbon.mediation.library.connectors.twitter/src/main/java/org/wso2/carbon/mediation/library/connectors/twitter/TwitterSearch.java:[85,41]
incompatible types
[ERROR] found   : java.util.List
[ERROR] required: java.util.List

What am I missing..? I updated orbit,kernel and platform..

Thanks;

-- 
Lalaji Sureshika
WSO2, Inc.;  http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] A better Java JSON library?

2013-07-16 Thread Shameera Rathnayaka
On Tue, Jul 16, 2013 at 3:20 PM, Asanka Dissanayake wrote:

> thanks shameera. requirement is I have use gitblit api. Passing  obejcts
> to the api is fine.
> I need to process the repsonse. it's like JSON to Java object mapping.
> I think Staxon is better than using Gson alone. right?
>

Staxon uses only the streaming support of Gson and Jackson libraries. That
means if you need to get more performance then you can change backend to
use Jackson. There are few other features[1] too. Therefore it is better to
use Staxon IMO.

Thanks,
Shameera.



>
> cheers!!
>
>
> On Tue, Jul 16, 2013 at 3:12 PM, Asanka Dissanayake wrote:
>
>> cool.i think gson will suit for the purpose. thanks
>>
>> cheers!!
>>
>>
>> On Tue, Jul 16, 2013 at 2:58 PM, Lasantha Fernando wrote:
>>
>>> Hi Asanka,
>>>
>>> If you need to only serialize/deserialize json, I think you might use
>>> google-gson (https://code.google.com/p/google-gson/). It has already
>>> being used in already existing components (e.g. data-bridge).
>>>
>>> If you need something like JsonPath for querying JSON, you can try
>>> json-path (https://code.google.com/p/json-path/). It is already bundled
>>> in
>>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/json-path/.
>>> (It is used in ESB I think in and will be used with the next CEP release as
>>> well)
>>>
>>> HTH,
>>>
>>> Lasantha
>>>
>>> On 16 July 2013 14:33, Asanka Dissanayake  wrote:
>>>
 Hi Devs,
 Is there any $subject, which is recommended to use in wso2. I need to
 use one to deal with gilblit api.

 cheers!!

 --

 *Asanka Dissanayake
 Software Engineer*
 *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
 *
 email: asan...@wso2.com ,   blog:
 cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
 71 8373821*

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


>>>
>>>
>>> --
>>> *Lasantha Fernando*
>>> Software Engineer - Data Technologies Team
>>> WSO2 Inc. http://wso2.com
>>>
>>> email: lasan...@wso2.com
>>> mobile: (+94) 71 5247551
>>>
>>
>>
>>
>> --
>>
>> *Asanka Dissanayake
>> Software Engineer*
>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>> *
>> email: asan...@wso2.com ,   blog:
>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>> 71 8373821*
>>
>
>
>
> --
>
> *Asanka Dissanayake
> Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
> *
> email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
> 8373821*
>



-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Naming convention of kernel patches pom

2013-07-16 Thread Janaka Ranabahu
I see that the name of the kernel patch pom is as follows

WSO2 Carbon Kernel Kernel Patch 0001
WSO2 Carbon Kernel Kernel Patch 0003

Is there any specific reason why we have added the version to the name and
why do we have 2 'Kernel' words? IMO the version should be excluded from
the name.

Thanks,
Janaka

-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


Re: [Dev] An essential integration test for every product

2013-07-16 Thread Krishantha Samaraweera
What is the best way to get unsatisfied SCs ? Is there any API to get the
list easily ?

Thanks,
Krishantha.

On Sat, Jul 13, 2013 at 8:20 AM, Krishantha Samaraweera  wrote:

> Will write a sample test for this
>
> Thanks,
> Krishnatha.
>
>
> On Sat, Jul 13, 2013 at 4:54 AM, Afkham Azeez  wrote:
>
>> One of the problems that you would come across at runtime would be due to
>> ServiceComponents being in the "Unsatisfied" state. The server startup
>> could be successful but the server is not in a correct running state
>> because of these unsatisfied SCs. I came across such a scenario in AS,
>> where webapp & tenant lazy loading did not work because of this issue.
>>
>> If we could startup the server with the OSGi console enabled, do an ls,
>> and grep for "Unsatified" during integration testing, we can catch these
>> situation easily. Otherwise, critical issues may show up after we release
>> or during production.
>>
>> Azeez
>>
>> --
>> *Afkham Azeez*
>> Director of Architecture; WSO2, Inc.; http://wso2.com
>> Member; Apache Software Foundation; http://www.apache.org/
>> * **
>> email: **az...@wso2.com* * cell: +94 77 3320919
>> blog: **http://blog.afkham.org* *
>> twitter: **http://twitter.com/afkham_azeez*
>> *
>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>> *
>> *
>> *Lean . Enterprise . Middleware*
>>
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] [Trunk] Test failures in Axis2

2013-07-16 Thread Janaka Ranabahu
Hi,

Please note im getting the following error when building on a clean repo.

janaka@janaka-T530:~/work/wso2/carbon/kernel/trunk$ svn info
Path: .
Working Copy Root Path: /home/janaka/work/wso2/carbon
URL: https://svn.wso2.org/repos/wso2/carbon/kernel/trunk
Repository Root: https://svn.wso2.org/repos/wso2
Repository UUID: a5903396-d722-0410-b921-86c7d4935375
Revision: 178368
Node Kind: directory
Schedule: normal
Last Changed Author: prab...@wso2.com
Last Changed Rev: 178328
Last Changed Date: 2013-07-16 08:29:25 +0530 (Tue, 16 Jul 2013)



[INFO] Building Apache Axis2 - Metadata 1.6.1-wso2v10
[INFO]

[INFO]
[INFO] --- maven-clean-plugin:2.2:clean (default-clean) @ axis2-metadata ---
[INFO] Deleting directory
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target
[INFO]
[INFO] --- incremental-build-plugin:1.3:incremental-build (default) @
axis2-metadata ---
[INFO] Verifying module descriptor ...
[INFO] Pom descriptor modification detected.
[INFO] Deleting
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @
axis2-metadata ---
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO]
[INFO] --- maven-dependency-plugin:2.0:copy (default) @ axis2-metadata ---
[INFO] Configured Artifact:
org.apache.geronimo.specs:geronimo-jaxws_2.2_spec:?:jar
[INFO] Copying geronimo-jaxws_2.2_spec-1.0.jar to
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/endorsed/geronimo-jaxws_2.2_spec.jar
[INFO]
[INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @
axis2-metadata ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @
axis2-metadata ---
[INFO] Compiling 190 source files to
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/classes
[INFO]
[INFO] --- maven-antrun-plugin:1.2:run (gen-ts) @ axis2-metadata ---
[INFO] Executing tasks
[mkdir] Created dir:
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/schema
[mkdir] Created dir:
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/schema/src
[mkdir] Created dir:
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/schema/classes
 [echo] Generating JAX-B classes from XSDs
 [echo] Generating java from ProxyDocLitWrapped.wsdl
[INFO] Executed tasks
[INFO]
[INFO] --- axis2-repo-maven-plugin:1.6.1-wso2v10:create-test-repository
(default) @ axis2-metadata ---
[INFO] Adding addressing-1.6.1-wso2v10.mar
[INFO] Copying axis2.xml
[INFO]
[INFO] --- maven-resources-plugin:2.4.2:testResources
(default-testResources) @ axis2-metadata ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/src/test/resources
[INFO] Copying 2 resources
[INFO]
[INFO] --- build-helper-maven-plugin:1.4:add-test-source (add-test-source)
@ axis2-metadata ---
[INFO] Test Source directory:
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/schema/src
added.
[INFO]
[INFO] --- maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @
axis2-metadata ---
[INFO] Compiling 67 source files to
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/test-classes
[INFO]
[INFO] --- maven-antrun-plugin:1.2:run (build-repo) @ axis2-metadata ---
[INFO] Executing tasks
 [copy] Copying 3 files to
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/test-classes
[INFO] Executed tasks
[INFO]
[INFO] --- maven-surefire-plugin:2.13:test (default-test) @ axis2-metadata
---
[INFO] Surefire report directory:
/home/janaka/work/wso2/carbon/kernel/trunk/dependencies/axis2/1.6.1-wso2v10/modules/metadata/target/surefire-reports

---
 T E S T S
---
Running org.apache.axis2.jaxws.utils.WSToolingUtilsTests
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec
Running org.apache.axis2.jaxws.description.ValidateServiceImplTests
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.401 sec
Running org.apache.axis2.jaxws.description.DocLit

Re: [Dev] A better Java JSON library?

2013-07-16 Thread Asanka Dissanayake
thanks shameera. requirement is I have use gitblit api. Passing  obejcts to
the api is fine.
I need to process the repsonse. it's like JSON to Java object mapping.
I think Staxon is better than using Gson alone. right?

cheers!!


On Tue, Jul 16, 2013 at 3:12 PM, Asanka Dissanayake wrote:

> cool.i think gson will suit for the purpose. thanks
>
> cheers!!
>
>
> On Tue, Jul 16, 2013 at 2:58 PM, Lasantha Fernando wrote:
>
>> Hi Asanka,
>>
>> If you need to only serialize/deserialize json, I think you might use
>> google-gson (https://code.google.com/p/google-gson/). It has already
>> being used in already existing components (e.g. data-bridge).
>>
>> If you need something like JsonPath for querying JSON, you can try
>> json-path (https://code.google.com/p/json-path/). It is already bundled
>> in
>> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/json-path/.
>> (It is used in ESB I think in and will be used with the next CEP release as
>> well)
>>
>> HTH,
>>
>> Lasantha
>>
>> On 16 July 2013 14:33, Asanka Dissanayake  wrote:
>>
>>> Hi Devs,
>>> Is there any $subject, which is recommended to use in wso2. I need to
>>> use one to deal with gilblit api.
>>>
>>> cheers!!
>>>
>>> --
>>>
>>> *Asanka Dissanayake
>>> Software Engineer*
>>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>>> *
>>> email: asan...@wso2.com ,   blog:
>>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>>> 71 8373821*
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Lasantha Fernando*
>> Software Engineer - Data Technologies Team
>> WSO2 Inc. http://wso2.com
>>
>> email: lasan...@wso2.com
>> mobile: (+94) 71 5247551
>>
>
>
>
> --
>
> *Asanka Dissanayake
> Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
> *
> email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
> 8373821*
>



-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] A better Java JSON library?

2013-07-16 Thread Asanka Dissanayake
cool.i think gson will suit for the purpose. thanks

cheers!!


On Tue, Jul 16, 2013 at 2:58 PM, Lasantha Fernando wrote:

> Hi Asanka,
>
> If you need to only serialize/deserialize json, I think you might use
> google-gson (https://code.google.com/p/google-gson/). It has already
> being used in already existing components (e.g. data-bridge).
>
> If you need something like JsonPath for querying JSON, you can try
> json-path (https://code.google.com/p/json-path/). It is already bundled
> in
> https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/json-path/.
> (It is used in ESB I think in and will be used with the next CEP release as
> well)
>
> HTH,
>
> Lasantha
>
> On 16 July 2013 14:33, Asanka Dissanayake  wrote:
>
>> Hi Devs,
>> Is there any $subject, which is recommended to use in wso2. I need to use
>> one to deal with gilblit api.
>>
>> cheers!!
>>
>> --
>>
>> *Asanka Dissanayake
>> Software Engineer*
>> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
>> *
>> email: asan...@wso2.com ,   blog:
>> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94
>> 71 8373821*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Lasantha Fernando*
> Software Engineer - Data Technologies Team
> WSO2 Inc. http://wso2.com
>
> email: lasan...@wso2.com
> mobile: (+94) 71 5247551
>



-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] A better Java JSON library?

2013-07-16 Thread Shameera Rathnayaka
Hi Asanka,

C
ould you explain the requirement bit, Because if you are searching a
streaming perpose I would like to suggest to go with Jackson[1] or Gson[2].
Jackson is faster than Gson but Gson error handling is far better than
Jackson.

If you are searching for JSON to Java object mapping then Staxon[3] or Gson
would be good libraries. If you go with Staxon you can configure it to use
Jackson or Gson underneath it.

Thanks,
Shameera.

[1] http://jackson.codehaus.org/
[2] http://code.google.com/p/google-gson/
[3] https://github.com/beckchr/staxon




On Tue, Jul 16, 2013 at 2:33 PM, Asanka Dissanayake wrote:

> Hi Devs,
> Is there any $subject, which is recommended to use in wso2. I need to use
> one to deal with gilblit api.
>
> cheers!!
>
> --
>
> *Asanka Dissanayake
> Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
> *
> email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
> 8373821*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Exception during tenant cleanup

2013-07-16 Thread Chanika Geeganage
Hi,

This was because of the latest changes for the new caching model. I have
attached the patch to [1].

[1] https://wso2.org/jira/browse/DS-740

Thanks


On Mon, Jul 15, 2013 at 12:48 PM, Kasun Gajasinghe  wrote:

> Hi Chanika,
>
> Please try this in a latest pack from trunk.
>
>
> On Mon, Jul 15, 2013 at 11:47 AM, Chanika Geeganage wrote:
>
>> Hi Azeez,
>>
>> I couldn't reproduce this error. I used DSS 3.0.1 and here are the steps
>> I followed.
>>
>> 1. Created a tenant.
>> 2. Sign in as the tenant admin.
>> 2. Added a data source
>> 3. Deployed a dataservice
>> 4. Sign out and wait for the tenant cleanup.
>>
>> Then tenant is cleaned up without any exceptions. Is there any other
>> steps to follow to reproduce the error?
>>
>> Thanks
>>
>>
>> On Mon, Jul 15, 2013 at 10:39 AM, Chanika Geeganage wrote:
>>
>>> I will check on this.
>>>
>>> Thanks
>>>
>>>
>>> On Sat, Jul 13, 2013 at 7:24 PM, Afkham Azeez  wrote:
>>>
 [2013-07-13 17:09:15,544]  INFO
 {org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils} -  Starting to
 clean tenant : azeez.org
 [2013-07-13 17:09:15,966]  INFO
 {org.wso2.carbon.webapp.mgt.WebApplication} -  Unloaded webapp:
 StandardEngine[Catalina].StandardHost[localhost].StandardContext[/t/
 azeez.org/webapps/Calendar]
 [2013-07-13 17:09:15,970] ERROR
 {org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver}
 -  Error in initializing data sources for tenant: 1 - Error in getting all
 data sources from repository: null
 org.wso2.carbon.ndatasource.common.DataSourceException: Error in
 getting all data sources from repository: null
 at
 org.wso2.carbon.ndatasource.core.DataSourceRepository.updateAllUserDataSource(DataSourceRepository.java:143)
  at
 org.wso2.carbon.ndatasource.core.DataSourceRepository.unregisterAllUserDataSources(DataSourceRepository.java:123)
 at
 org.wso2.carbon.ndatasource.core.DataSourceManager.unloadTenant(DataSourceManager.java:108)
  at
 org.wso2.carbon.ndatasource.core.DataSourceAxis2ConfigurationContextObserver.terminatingConfigurationContext(DataSourceAxis2ConfigurationContextObserver.java:49)
  at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:515)
 at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:477)
  at
 org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:429)
 at
 org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
  at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
 at
 java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
  at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
 at
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
  at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
  at java.lang.Thread.run(Thread.java:680)
 Caused by: java.lang.NullPointerException

 --
 *Afkham Azeez*
 Director of Architecture; WSO2, Inc.; http://wso2.com
 Member; Apache Software Foundation; http://www.apache.org/
 * **
 email: **az...@wso2.com* * cell: +94 77 3320919
 blog: **http://blog.afkham.org* *
 twitter: 
 **http://twitter.com/afkham_azeez*
 *
 linked-in: **http://lk.linkedin.com/in/afkhamazeez*
 *
 *
 *Lean . Enterprise . Middleware*

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


>>>
>>>
>>> --
>>> Best Regards..
>>>
>>> Chanika Geeganage
>>> Software Engineer
>>> WSO2, Inc.; http://wso2.com
>>>
>>> Mobile: +94773522586
>>>
>>
>>
>>
>> --
>> Best Regards..
>>
>> Chanika Geeganage
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Mobile: +94773522586
>>
>
>
>
> --
> *Kasun Gajasinghe*
> Software Engineer;
> Development Technologies Team, WSO2 Inc.; http://wso2.com
>
>
>  ,
> *email: **kasung AT spamfree wso2.com
>
>
> ** cell: **+94 (77) 678-0813*
> *linked-in: *http://lk.linkedin.com/in/gajasinghe
>
>
> *
> *
> *blog: **http://kasunbg.org* 
>
>
> *
> twitter: **http://twitter.com/kasunbg* 
>
>
> *
> *
>



-- 
Best Regards..

Chanika Geeganage
Softwa

Re: [Dev] Compilation error

2013-07-16 Thread Suresh Attanayaka
Hi,

Fixed in 178376. Sorry for the inconvenience.

Thanks,
-Suresh

On Tue, Jul 16, 2013 at 2:47 PM, Amila Suriarachchi  wrote:

>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project org.wso2.carbon.identity.mgt: Compilation
> failure: Compilation failure:
> [ERROR]
> /home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[25,39]
> cannot find symbol
> [ERROR] symbol  : class ChallengeQuestionIdsDTO
> [ERROR] location: package org.wso2.carbon.identity.mgt.dto
> [ERROR]
> /home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[278,8]
> cannot find symbol
> [ERROR] symbol  : class ChallengeQuestionIdsDTO
> [ERROR] location: class
> org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor
> [ERROR]
> /home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[281,2]
> cannot find symbol
> [ERROR] symbol  : class ChallengeQuestionIdsDTO
> [ERROR] location: class
> org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor
> [ERROR]
> /home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[281,36]
> cannot find symbol
> [ERROR] symbol  : class ChallengeQuestionIdsDTO
> [ERROR] location: class
> org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor
>
> thanks,
> Amila.
> --
> *Amila Suriarachchi*
>
> Software Architect
> WSO2 Inc. ; http://wso2.com
> lean . enterprise . middleware
>
> phone : +94 71 3082805
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Suresh Attanayake
Senior Software Engineer; WSO2 Inc. http://wso2.com/
Blog : http://sureshatt.blogspot.com/
Web : http://www.ssoarcade.com/
Facebook : https://www.facebook.com/IdentityWorld
Twitter : https://twitter.com/sureshatt
LinkedIn : http://lk.linkedin.com/in/sureshatt
Mobile : +94755012060
Mobile : +01-616-617-1172
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] A better Java JSON library?

2013-07-16 Thread Lasantha Fernando
Hi Asanka,

If you need to only serialize/deserialize json, I think you might use
google-gson (https://code.google.com/p/google-gson/). It has already being
used in already existing components (e.g. data-bridge).

If you need something like JsonPath for querying JSON, you can try
json-path (https://code.google.com/p/json-path/). It is already bundled in
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/dependencies/orbit/json-path/.
(It is used in ESB I think in and will be used with the next CEP release as
well)

HTH,

Lasantha

On 16 July 2013 14:33, Asanka Dissanayake  wrote:

> Hi Devs,
> Is there any $subject, which is recommended to use in wso2. I need to use
> one to deal with gilblit api.
>
> cheers!!
>
> --
>
> *Asanka Dissanayake
> Software Engineer*
> *WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
> *
> email: asan...@wso2.com ,   blog:
> cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
> 8373821*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Lasantha Fernando*
Software Engineer - Data Technologies Team
WSO2 Inc. http://wso2.com

email: lasan...@wso2.com
mobile: (+94) 71 5247551
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Registry Test failures in kernel

2013-07-16 Thread Shameera Rathnayaka
Hi Pulasthi/ Senaka,

I got this test failures when i ran the build in an EC2 instance, Yes i too
checked with local machine and there is no test failures. Seems there is
issue with EC2 side not with registry code, will sort it out.

Thanks,
Shameera.



On Tue, Jul 16, 2013 at 2:29 PM, Pulasthi Supun  wrote:

> Hi Shameera
>
> Are you running the test with the latest updates. i am not getting these
> test failures. can you please check again.
>
> Regards
> Pulasthi
>
>
> On Tue, Jul 16, 2013 at 12:22 PM, Shameera Rathnayaka 
> wrote:
>
>> Please note $Subject, Following is part of build error, I have attached
>> full build error with this. As we are on kernel 4.2.0 release process
>> please consider this as urgent.
>>
>> Running org.wso2.carbon.registry.core.test.jdbc.ResourcesTest
>> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.036 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.CustomQueryTest
>> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.032 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.TagsTest
>> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.033 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.TransactionsTest
>> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.037 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.PathsTest
>> Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.08 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.QueryTest
>> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.053 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.MoveTest
>> Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.051 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.CopyTest
>> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.046 sec
>> <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.VersionHandlingTest
>> Tests run: 10, Failures: 0, Errors: 10, Skipped: 0, Time elapsed: 0.056
>> sec <<< FAILURE!
>> Running org.wso2.carbon.registry.core.test.jdbc.SymlinkTest
>> log4j:WARN No appenders could be found for logger
>> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
>> log4j:WARN Please initialize the log4j system properly.
>> Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.656 sec
>> Running org.wso2.carbon.registry.core.test.jdbc.ChrootJDBCTest
>> log4j:WARN No appenders could be found for logger
>> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
>> log4j:WARN Please initialize the log4j system properly.
>> Tests run: 26, Failures: 0, Errors: 26, Skipped: 0, Time elapsed: 2.821
>> sec <<< FAILURE!
>>
>> T
>> hanks,
>> Shameera.
>>
>>
>> --
>> *Software Engineer - WSO2 Inc.*
>> *email: shameera AT wso2.com  , shameera AT 
>> apache.org
>> *
>> *phone:  +9471 922 1454*
>> *
>> *
>> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
>> *Twitter : *https://twitter.com/Shameera_R
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> --
> Pulasthi Supun
> Software Engineer; WSO2 Inc.; http://wso2.com,
> Email: pulas...@wso2.com
> Mobile: +94 (71) 9258281
> Blog : http://pulasthisupun.blogspot.com/
> Git hub profile: https://github.com/pulasthi
>



-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Compilation error

2013-07-16 Thread Amila Suriarachchi
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.identity.mgt: Compilation
failure: Compilation failure:
[ERROR]
/home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[25,39]
cannot find symbol
[ERROR] symbol  : class ChallengeQuestionIdsDTO
[ERROR] location: package org.wso2.carbon.identity.mgt.dto
[ERROR]
/home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[278,8]
cannot find symbol
[ERROR] symbol  : class ChallengeQuestionIdsDTO
[ERROR] location: class
org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor
[ERROR]
/home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[281,2]
cannot find symbol
[ERROR] symbol  : class ChallengeQuestionIdsDTO
[ERROR] location: class
org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor
[ERROR]
/home/amila/projects/trunk/platform/components/identity/org.wso2.carbon.identity.mgt/src/main/java/org/wso2/carbon/identity/mgt/ChallengeQuestionProcessor.java:[281,36]
cannot find symbol
[ERROR] symbol  : class ChallengeQuestionIdsDTO
[ERROR] location: class
org.wso2.carbon.identity.mgt.ChallengeQuestionProcessor

thanks,
Amila.
-- 
*Amila Suriarachchi*

Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 71 3082805
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Tenant domain is null during tenant login process

2013-07-16 Thread Pradeep Fernando
Hi,

I don't have clear idea, why it sends a logout message..
CC is null since it is not populated. (default value). No it can't be null.
TenantID can be -1, since we can figure out later using the tenant domain.

thanks,
--Pradeep


On Tue, Jul 16, 2013 at 1:31 PM, Miyuru Wanninayaka  wrote:

> Hi all,
>
> When I writing a handler to set tenant domain and ID in NIO message flow,
> I found that when user is logs in to a tenant, 3rd request which received
> during login process points to local://services/AuthenticationAdmin
>
> with following message
>
> http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing
> ">local://services/AuthenticationAdminurn:uuid:85d2f9fb-fd32-40a9-9387-3aa592f5ab14urn:logout
> *http://authentication.services.core.carbon.wso2.org"/>*
> 
>
> Also when I checked carbon context data holder, only tenant ID is there (
> 1 in my case) and all other fields are null ( even tenant domain!)
>
> I have 2 questions:
>
> *Is it valid to have a CC with tenant domain = null
> *Why are we calling logout during login
>
> --
> Miyuru Wanninayaka
> Technical Lead
> WSO2 Inc. : http://wso2.com
>
> Mobile : +94 77 209 9788
> Blog : http://miyurudw.blogspot.com
> Flickr : http://www.flickr.com/photos/miyuru_daminda




-- 
*Pradeep Fernando*
Associate Technical Lead;WSO2 Inc.; http://wso2.com

blog: http://pradeepfernando.blogspot.com
m: +94776603662
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Socket closed Exception

2013-07-16 Thread Dilshan Edirisuriya
Hi,

We time to time get this. Seems like it is coming from the http client
itself. Is there anything we can do to solve this?

Regards,

Dilshan


On Tue, Jul 16, 2013 at 12:31 PM, Chan  wrote:

> Hi all,
> I am getting a Socket closed Exception in certain situations. I have tried
> the UES latest release from github as well but it seems it also gives this
> error.
>
> [2013-07-16 12:29:17,971] ERROR
> {org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  Socket closed
> java.net.SocketException: Socket closed
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
>  at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:579)
>  at java.net.Socket.connect(Socket.java:528)
> at java.net.Socket.(Socket.java:425)
> at java.net.Socket.(Socket.java:280)
>  at
> org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)
> at
> org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)
>  at
> org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
> at
> org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
>  at
> org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
> at
> org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
>  at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
> at
> org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
>  at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:523)
> at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:517)
>  at
> org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:278)
> at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source)
>  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
>  at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
> at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
>  at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at
> org.jaggeryjs.rhino.mdm.controller.c2._c_anonymous_1(/mdm/controller/console.js:13)
>  at org.jaggeryjs.rhino.mdm.controller.c2.call(/mdm/controller/console.js)
> at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
>  at
> org.jaggeryjs.rhino.mdm.modules.c0._c_anonymous_13(/mdm/modules/absolute.js:181)
> at org.jaggeryjs.rhino.mdm.modules.c0.call(/mdm/modules/absolute.js)
>  at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
> at org.jaggeryjs.rhino.mdm.c0._c_script_0(/mdm//index.jag:194)
>  at org.jaggeryjs.rhino.mdm.c0.call(/mdm//index.jag)
> at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
>  at
> org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
> at org.jaggeryjs.rhino.mdm.c0.call(/mdm//index.jag)
>  at org.jaggeryjs.rhino.mdm.c0.exec(/mdm//index.jag)
> at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:577)
>  at
> org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:280)
> at
> org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:432)
>  at
> org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
>  at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
>  at
> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
> at
> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
>  at
> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
> at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
>  at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
>  at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
> at
> org.apach

Re: [Dev] UI integration test failure in Greg in tests-ui

2013-07-16 Thread Randika Ratnayake
hi all ,
I m currently executing the selenium test cases for the governance registry
the. found 2 bugs causing the test failurs please refer below jira for the
further information of the issues.

  REGISTRY-1674 

   1. REGISTRY-1675 


Thanks
Randika





On Mon, Jul 8, 2013 at 10:14 AM, Randika Ratnayake  wrote:

> ill execute the Greg selenium tests  against the new release most of the
> ui elements have changed ill inform once its fixed
>
> Regards
> Randika
>
>
> On Fri, Jul 5, 2013 at 11:08 AM, Krishantha Samaraweera <
> krishan...@wso2.com> wrote:
>
>> Most probably those selenium locators have changed in this release.
>>
>> Thanks,
>> Krishantha.
>>
>>
>> On Fri, Jul 5, 2013 at 10:59 AM, Pulasthi Supun wrote:
>>
>>> Hi QAA team
>>>
>>> There are several integration test failures in the UI automation tests
>>> in greg [1]. It seems that some xpaths and id's defined in the properties
>>> file are incorrect. can someone from the automaton team take a look at this
>>> and fix them. i have attached the surefire reports.
>>>
>>> Thanks,
>>> Pulasthi
>>>
>>> [1]
>>> http://svn.wso2.org/repos/wso2/carbon/platform/trunk/products/greg/modules/integration/registry/tests-ui/
>>> --
>>> --
>>> Pulasthi Supun
>>> Software Engineer; WSO2 Inc.; http://wso2.com,
>>> Email: pulas...@wso2.com
>>> Mobile: +94 (71) 9258281
>>> Blog : http://pulasthisupun.blogspot.com/
>>> Git hub profile: https://github.com/pulasthi
>>>
>>
>>
>
>
> --
> Randika Ratnayake,
> Mobile : +94773-440677 
>



-- 
Randika Ratnayake,
Mobile : +94773-440677 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] A better Java JSON library?

2013-07-16 Thread Asanka Dissanayake
Hi Devs,
Is there any $subject, which is recommended to use in wso2. I need to use
one to deal with gilblit api.

cheers!!

-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Registry Test failures in kernel

2013-07-16 Thread Pulasthi Supun
Hi Shameera

Are you running the test with the latest updates. i am not getting these
test failures. can you please check again.

Regards
Pulasthi


On Tue, Jul 16, 2013 at 12:22 PM, Shameera Rathnayaka wrote:

> Please note $Subject, Following is part of build error, I have attached
> full build error with this. As we are on kernel 4.2.0 release process
> please consider this as urgent.
>
> Running org.wso2.carbon.registry.core.test.jdbc.ResourcesTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.036 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.CustomQueryTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.032 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.TagsTest
> Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.033 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.TransactionsTest
> Tests run: 6, Failures: 0, Errors: 6, Skipped: 0, Time elapsed: 0.037 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.PathsTest
> Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.08 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.QueryTest
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.053 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.MoveTest
> Tests run: 7, Failures: 0, Errors: 7, Skipped: 0, Time elapsed: 0.051 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.CopyTest
> Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 0.046 sec
> <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.VersionHandlingTest
> Tests run: 10, Failures: 0, Errors: 10, Skipped: 0, Time elapsed: 0.056
> sec <<< FAILURE!
> Running org.wso2.carbon.registry.core.test.jdbc.SymlinkTest
> log4j:WARN No appenders could be found for logger
> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
> log4j:WARN Please initialize the log4j system properly.
> Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.656 sec
> Running org.wso2.carbon.registry.core.test.jdbc.ChrootJDBCTest
> log4j:WARN No appenders could be found for logger
> (org.wso2.carbon.context.internal.CarbonContextDataHolder).
> log4j:WARN Please initialize the log4j system properly.
> Tests run: 26, Failures: 0, Errors: 26, Skipped: 0, Time elapsed: 2.821
> sec <<< FAILURE!
>
> T
> hanks,
> Shameera.
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
--
Pulasthi Supun
Software Engineer; WSO2 Inc.; http://wso2.com,
Email: pulas...@wso2.com
Mobile: +94 (71) 9258281
Blog : http://pulasthisupun.blogspot.com/
Git hub profile: https://github.com/pulasthi
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Build Failed in 4.1.2 patch release

2013-07-16 Thread Asanka Dissanayake
Hi ,
I get following error when building patch release 4.1.2.


Installing org.wso2.carbon.stratos.deployment.feature.group 2.1.0.
Installing
org.wso2.carbon.identity.authenticator.saml2.sso.server.feature.group 4.1.2.
Installing
org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group 4.1.2.
Installation failed.
An error occurred while configuring the installed items
 session context was:(profile=WSO2CarbonProfile,
phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null
--> [R]org.wso2.carbon.stratos.common.server.feature.group 2.1.2,
action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).
 I/O Error while copying
/home/asanka/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xml
- see details.
Caused by:  java.io.IOException: Source:
/home/asanka/carbon/platform/4.1.0/products/apimgt/1.4.0/modules/p2-profile/product/target/wso2carbon-core-4.1.0/repository/components/features/org.wso2.carbon.stratos.common.server_2.1.2/conf/identity.xmldoes
not exists
Application failed, log file location:
/home/asanka/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1373963644296.log

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 22.372s
[INFO] Finished at: Tue Jul 16 14:04:15 IST 2013
[INFO] Final Memory: 12M/981M
[INFO]

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.2:p2-profile-gen
(4-p2-profile-generation) on project am-p2-profile: P2 publisher return
code was 13 -> [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]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
a
-- 

*Asanka Dissanayake
Software Engineer*
*WSO2 Inc. - lean . enterprise . middleware |  wso2.com*
*
email: asan...@wso2.com ,   blog:
cyberwaadiya.blogspot.com, asankastechtalks.wordpress.com  mobile: +94 71
8373821*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Janaka Ranabahu
On Tue, Jul 16, 2013 at 1:58 PM, Asanka Sanjeewa  wrote:

> Hi,
>
> On Tue, Jul 16, 2013 at 1:30 PM, Keheliya Gallaba wrote:
>
>> Hi,
>>
>> It will be good to have TOOLS-1626[1] also as a high priority item. There
>> have been few questions on StackOverflow[2][3] about this. We've been
>> suggesting them to go back to Dev Studio 3.0.0 version only for BPEL
>> development due to this.
>>
>> Thanks & Best Regards,
>> Keheliya
>>
>> [1] https://wso2.org/jira/browse/TOOLS-1626
>> [2]
>> http://stackoverflow.com/questions/17547806/wso2-developer-studio-edit-properties-of-an-assign-activity
>> [3]
>> http://stackoverflow.com/questions/17616862/wso2-business-process-bpel-error-in-gui-with-if-component
>>
>>  


> Developer Studio still uses forked version of Eclipse BPEL editor 0.5.0
> version which does not support with Eclipse Juno release. There are few
> more releases of Eclipse BPEL editor after 0.5.0 (latest is 1.0.3,
> according to [1]). Eclipse BPEL editor 0.8.0 version onwards supports with
> Eclipse Juno. I think if we can fork or use the latest stable version of
> BPEL editor will solve the most of the issues that we are facing with
> Developer Studio BPEL editor.
>
+1 for the idea. Do we know why we have forked the earlier version? Was it
due to some missing features? Please make sure that we do not loose any of
the existing functionality when we move to the newer version.

Thanks,
Janaka

>
> [1] http://download.eclipse.org/bpel/site/
>
> Thanks and Regards,
> AsankaS.
>
>
> *Asanka Sanjeewa*
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Janaka Ranabahu*
Member - Solutions Management Committee;
Senior Software Engineer; WSO2 Inc.; http://wso2.com*

E-mail: jan...@wso2.com
**M: **+94 718370861**

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


[Dev] Need a release version of Jaggery for MDM

2013-07-16 Thread Dilshan Edirisuriya
Hi,

We need the latest release version of Jaggery for MDM. Right now the the
release version found in Nexus is 0.9.0.ALPHA2-wso2v5 which was added last
month. This does not have the latest changes we need. However when we use
the version 0.9.0-SNAPSHOT-07042013 added on July 4th all works well. Since
this is a snapshot version is it ok to use it or will you be able to add a
release version there? Please advice.

Regards,

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


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Thilini Ishaka
On Tue, Jul 16, 2013 at 1:58 PM, Asanka Sanjeewa  wrote:

> Hi,
>
> On Tue, Jul 16, 2013 at 1:30 PM, Keheliya Gallaba wrote:
>
>> Hi,
>>
>> It will be good to have TOOLS-1626[1] also as a high priority item. There
>> have been few questions on StackOverflow[2][3] about this. We've been
>> suggesting them to go back to Dev Studio 3.0.0 version only for BPEL
>> development due to this.
>>
>> Thanks & Best Regards,
>> Keheliya
>>
>> [1] https://wso2.org/jira/browse/TOOLS-1626
>> [2]
>> http://stackoverflow.com/questions/17547806/wso2-developer-studio-edit-properties-of-an-assign-activity
>> [3]
>> http://stackoverflow.com/questions/17616862/wso2-business-process-bpel-error-in-gui-with-if-component
>>
>>  


> Developer Studio still uses forked version of Eclipse BPEL editor 0.5.0
> version which does not support with Eclipse Juno release. There are few
> more releases of Eclipse BPEL editor after 0.5.0 (latest is 1.0.3,
> according to [1]). Eclipse BPEL editor 0.8.0 version onwards supports with
> Eclipse Juno. I think if we can fork or use the latest stable version of
> BPEL editor will solve the most of the issues that we are facing with
> Developer Studio BPEL editor.
>

+1 This is a blocker at the moment. It's not practical to switch to an
older version only for this task.

>
> [1] http://download.eclipse.org/bpel/site/
>
> Thanks and Regards,
> AsankaS.
>
>
> *Asanka Sanjeewa*
> Senior Software Engineer
> Mobile: +94772532924
> WSO2 Inc. http://wso2.com/
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Thilini Ishaka
Senior Software Engineer**
WSO2 Inc. http://wso2.com*
*bolg: thiliniishaka.blogspot.com*
*linkedin: http://lk.linkedin.com/in/thiliniishaka*
*twitter: https://twitter.com/#!/ThiliniIsh*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] WSO2 Developer Studio 3.2.0 Released!

2013-07-16 Thread Asanka Sanjeewa
Hi,

On Tue, Jul 16, 2013 at 1:30 PM, Keheliya Gallaba  wrote:

> Hi,
>
> It will be good to have TOOLS-1626[1] also as a high priority item. There
> have been few questions on StackOverflow[2][3] about this. We've been
> suggesting them to go back to Dev Studio 3.0.0 version only for BPEL
> development due to this.
>
> Thanks & Best Regards,
> Keheliya
>
> [1] https://wso2.org/jira/browse/TOOLS-1626
> [2]
> http://stackoverflow.com/questions/17547806/wso2-developer-studio-edit-properties-of-an-assign-activity
> [3]
> http://stackoverflow.com/questions/17616862/wso2-business-process-bpel-error-in-gui-with-if-component
>
> 
>>>
>>>
Developer Studio still uses forked version of Eclipse BPEL editor 0.5.0
version which does not support with Eclipse Juno release. There are few
more releases of Eclipse BPEL editor after 0.5.0 (latest is 1.0.3,
according to [1]). Eclipse BPEL editor 0.8.0 version onwards supports with
Eclipse Juno. I think if we can fork or use the latest stable version of
BPEL editor will solve the most of the issues that we are facing with
Developer Studio BPEL editor.

[1] http://download.eclipse.org/bpel/site/

Thanks and Regards,
AsankaS.


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


[Dev] Updated Invitation: [Code Review] CMIS Specification Support @ Tue Jul 16, 2013 3pm - 4:30pm (pulas...@wso2.com)

2013-07-16 Thread Pulasthi Supun
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20130716T093000Z
DTEND:20130716T11Z
DTSTAMP:20130716T082351Z
ORGANIZER;CN=pulas...@wso2.com:mailto:pulas...@wso2.com
UID:inuie0en9ts8olhe0rp0n1l...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Ajith Vitharana;X-NUM-GUESTS=0:mailto:aji...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Eranda Sooriyabandara;X-NUM-GUESTS=0:mailto:era...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Shelan Perera;X-NUM-GUESTS=0:mailto:she...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TR
 UE;CN=LK #58 5th Floor - Meeting room;X-NUM-GUESTS=0:mailto:wso2.com_323831
 3439343838343...@resource.calendar.google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=Pulasthi Supun;X-NUM-GUESTS=0:mailto:pulas...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Lasith Chandrasekara;X-NUM-GUESTS=0:mailto:las...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Senaka Fernando;X-NUM-GUESTS=0:mailto:sen...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=dev@wso2.org;X-NUM-GUESTS=0:mailto:dev@wso2.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Vijitha Kumara;X-NUM-GUESTS=0:mailto:viji...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=Sriragu Arudsothy;X-NUM-GUESTS=0:mailto:srir...@wso2.com
CREATED:20130715T155150Z
DESCRIPTION:Crusible : http://wso2.org/crucible/cru/WCP081-2\n\nhttps://red
 mine.wso2.com/issues/485\nView your event at http://www.google.com/calendar
 /event?action=VIEW&eid=aW51aWUwZW45dHM4b2xoZTBycDBuMWxqYnMgZGV2QHdzbzIub3Jn
 &tok=MTcjcHVsYXN0aGlAd3NvMi5jb200NzllZWQ3NDVhY2U2ZjFkNWNkYjg2N2I1MGUwNTM1NT
 hjMDFjNTAz&ctz=Asia/Colombo&hl=en.
LAST-MODIFIED:20130716T082351Z
LOCATION:LK #58 5th Floor - Meeting room
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY: [Code Review] CMIS Specification Support
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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


[Dev] Tenant domain is null during tenant login process

2013-07-16 Thread Miyuru Wanninayaka
Hi all,

When I writing a handler to set tenant domain and ID in NIO message flow, I
found that when user is logs in to a tenant, 3rd request which received
during login process points to local://services/AuthenticationAdmin

with following message

http://www.w3.org/2003/05/soap-envelope";>http://www.w3.org/2005/08/addressing
">local://services/AuthenticationAdminurn:uuid:85d2f9fb-fd32-40a9-9387-3aa592f5ab14urn:logout
*http://authentication.services.core.carbon.wso2.org
"/>*

Also when I checked carbon context data holder, only tenant ID is there ( 1
in my case) and all other fields are null ( even tenant domain!)

I have 2 questions:

*Is it valid to have a CC with tenant domain = null
*Why are we calling logout during login

-- 
Miyuru Wanninayaka
Technical Lead
WSO2 Inc. : http://wso2.com

Mobile : +94 77 209 9788
Blog : http://miyurudw.blogspot.com
Flickr : http://www.flickr.com/photos/miyuru_daminda
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] -DapplyPatches option not working properly in trunk

2013-07-16 Thread Manoj Kumara
Hi,

I'll look in to this.

Thanks,
Manoj

Best Regards..


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

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


On Tue, Jul 16, 2013 at 12:39 PM, Shameera Rathnayaka wrote:

> H
> i Manoj,
>
> Seems patch application process doesn't working as it suppose to be, This
> may be side effect of your patch application optimization could you please
> re check this and confirm.
>
> Thanks,
> Shameera.
>
>
> On Mon, Jul 15, 2013 at 7:40 PM, Sanjeewa Malalgoda wrote:
>
>>
>>
>> On Mon, Jul 15, 2013 at 7:30 PM, Manoj Kumara  wrote:
>>
>>> Hi,
>>>
>>>
>>>
  In current trunk we do not need to specify -DapplyPatches as an
> argument. If any patches are exist it will automatically apply those
> patches.
>
 Yes i know  -DapplyPatches is there in server start-up script. But my
 concern was not picking up patches if they exists. Is that working for you?

>>>
>>>  Yes, This works fine for me.
>>>
>> You meant in trunk? what is the product? when you built it?
>>
>>>
>>>
>>>

> During run-time jars on the plugins folder are used. Nothing wrong
> with that.
>
 Yes that is default behavior only for jars which are not in patches.

>>>
>>>
>>> AFAIK during run-time all the jars in the plugins directory will be
>>> used. Non from the patches directories.
>>>
>> When you put -DApplyPatch jars in patches folder will copy to plugins and
>> executed in run-time. That is what not working for me. Hope you understand
>> what i said.
>>
>>
>>
>> --
>> *
>> *
>> *Sanjeewa Malalgoda*
>> WSO2 Inc.
>> Mobile : +94713068779
>>
>>  blog
>> :http://sanjeewamalalgoda.blogspot.com/
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Software Engineer - WSO2 Inc.*
> *email: shameera AT wso2.com  , shameera AT 
> apache.org
> *
> *phone:  +9471 922 1454*
> *
> *
> *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
> *Twitter : *https://twitter.com/Shameera_R
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] -DapplyPatches option not working properly in trunk

2013-07-16 Thread Shameera Rathnayaka
Hi Sanjeewa,

On Mon, Jul 15, 2013 at 7:19 PM, Sanjeewa Malalgoda wrote:

>
> Yes i know  -DapplyPatches is there in server start-up script.
>
-DapplyPatches is no longer use to activate patch application process.
Hence this is miss leading, please remove this from server startup script.

Thanks,
Shameera.



>  But my concern was not picking up patches if they exists. Is that working
> for you?
>
>>
>> During run-time jars on the plugins folder are used. Nothing wrong with
>> that.
>>
> Yes that is default behavior only for jars which are not in patches.
>
>>
>> Thanks,
>>
>> Best Regards..
>>
>>
>> Manoj Kumara
>> Software Engineer
>> WSO2, Inc.; http://wso2.com
>>
>> Twitter:  http://twitter.com/ManKuma
>> Mobile: +94713448188
>>
>>
>> On Mon, Jul 15, 2013 at 6:09 PM, Sanjeewa Malalgoda wrote:
>>
>>> Hi Team,
>>> Noticed $subject in trunk API manager pack (built today). I can see
>>> patch folder created but in run-time it will pick jars at plugins
>>> folder. Any idea?
>>>
>>> Thanks,
>>> Sanjeewa.
>>> --
>>> *
>>> *
>>> *Sanjeewa Malalgoda*
>>> WSO2 Inc.
>>> Mobile : +94713068779
>>>
>>>  blog
>>> :http://sanjeewamalalgoda.blogspot.com/
>>>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] -DapplyPatches option not working properly in trunk

2013-07-16 Thread Shameera Rathnayaka
H
i Manoj,

Seems patch application process doesn't working as it suppose to be, This
may be side effect of your patch application optimization could you please
re check this and confirm.

Thanks,
Shameera.


On Mon, Jul 15, 2013 at 7:40 PM, Sanjeewa Malalgoda wrote:

>
>
> On Mon, Jul 15, 2013 at 7:30 PM, Manoj Kumara  wrote:
>
>> Hi,
>>
>>
>>
>>>  In current trunk we do not need to specify -DapplyPatches as an
 argument. If any patches are exist it will automatically apply those
 patches.

>>> Yes i know  -DapplyPatches is there in server start-up script. But my
>>> concern was not picking up patches if they exists. Is that working for you?
>>>
>>
>>  Yes, This works fine for me.
>>
> You meant in trunk? what is the product? when you built it?
>
>>
>>
>>
>>>
 During run-time jars on the plugins folder are used. Nothing wrong with
 that.

>>> Yes that is default behavior only for jars which are not in patches.
>>>
>>
>>
>> AFAIK during run-time all the jars in the plugins directory will be used.
>> Non from the patches directories.
>>
> When you put -DApplyPatch jars in patches folder will copy to plugins and
> executed in run-time. That is what not working for me. Hope you understand
> what i said.
>
>
>
> --
> *
> *
> *Sanjeewa Malalgoda*
> WSO2 Inc.
> Mobile : +94713068779
>
>  blog
> :http://sanjeewamalalgoda.blogspot.com/
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Software Engineer - WSO2 Inc.*
*email: shameera AT wso2.com  , shameera AT
apache.org
*
*phone:  +9471 922 1454*
*
*
*Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561
*Twitter : *https://twitter.com/Shameera_R
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Socket closed Exception

2013-07-16 Thread Chan
Hi all,
I am getting a Socket closed Exception in certain situations. I have tried
the UES latest release from github as well but it seems it also gives this
error.

[2013-07-16 12:29:17,971] ERROR
{org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject} -  Socket closed
java.net.SocketException: Socket closed
at java.net.PlainSocketImpl.socketConnect(Native Method)
at
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at java.net.Socket.connect(Socket.java:528)
at java.net.Socket.(Socket.java:425)
at java.net.Socket.(Socket.java:280)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:80)
at
org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:122)
at
org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707)
at
org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1361)
at
org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387)
at
org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at
org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.executeRequest(XMLHttpRequestHostObject.java:523)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.send(XMLHttpRequestHostObject.java:517)
at
org.jaggeryjs.hostobjects.xhr.XMLHttpRequestHostObject.jsFunction_send(XMLHttpRequestHostObject.java:278)
at sun.reflect.GeneratedMethodAccessor120.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:126)
at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:386)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.mdm.controller.c2._c_anonymous_1(/mdm/controller/console.js:13)
at org.jaggeryjs.rhino.mdm.controller.c2.call(/mdm/controller/console.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at
org.jaggeryjs.rhino.mdm.modules.c0._c_anonymous_13(/mdm/modules/absolute.js:181)
at org.jaggeryjs.rhino.mdm.modules.c0.call(/mdm/modules/absolute.js)
at org.mozilla.javascript.optimizer.OptRuntime.call1(OptRuntime.java:32)
at org.jaggeryjs.rhino.mdm.c0._c_script_0(/mdm//index.jag:194)
at org.jaggeryjs.rhino.mdm.c0.call(/mdm//index.jag)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:394)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:3091)
at org.jaggeryjs.rhino.mdm.c0.call(/mdm//index.jag)
at org.jaggeryjs.rhino.mdm.c0.exec(/mdm//index.jag)
at
org.jaggeryjs.scriptengine.engine.RhinoEngine.execScript(RhinoEngine.java:577)
at org.jaggeryjs.scriptengine.engine.RhinoEngine.exec(RhinoEngine.java:280)
at
org.jaggeryjs.jaggery.core.manager.WebAppManager.execute(WebAppManager.java:432)
at org.jaggeryjs.jaggery.core.JaggeryServlet.doPost(JaggeryServlet.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:749)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:487)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:339)
at org.jaggeryjs.jaggery.core.JaggeryFilter.doFilter(JaggeryFilter.java:21)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
at
org.wso2.carbon.tomcat.ext.valves.CompositeValve.invoke(CompositeValve.java:177)
a