Re: [Dev] Error building carbon

[Thanuja Jayasinghe]

Hi Nipuni,

Using Maven version like 3.0.5 will solve your problem.

Thanks,
Thanuja


On Fri, Jul 18, 2014 at 12:01 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:

> Hi Nipuni,
>
> Build with a clean Maven repo using Maven3.
>
> Thanks !
>
>
> On Fri, Jul 18, 2014 at 11:51 AM, Harsha Kumara  wrote:
>
>> Hi Nipuni,
>> May be the maven version you using can be the issue here. What's your
>> maven version?
>> Thanks,
>> Harsha
>>
>>
>> On Fri, Jul 18, 2014 at 11:47 AM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> I am using java 6 and I have tried with a clean repo build. I got the
>>> following error stack trace.
>>>
>>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
>>> project wso2carbon-student-mgt-repository: P2 publisher return code was 13
>>> -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen
>>> (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2
>>> publisher return code was 13
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher
>>> return code was 13
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> ... 19 more
>>> Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher
>>> return code was 13
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
>>> ... 22 more
>>>
>>> Thanks,
>>> Nipuni
>>>
>>>
>>> On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando 
>>> wrote:
>>>
 Hi
 What is the java version you are using? Is it java 6 or java 7? If its
 7 try with java 6.

 Thanks & Regards
 Danushka Fernando
 Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729


 On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera 
 wrote:

> Hi,
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
> [7:30.905s]
> [INFO] WSO2 Carbon - Integration . SKIPPED
> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
> [INFO] WSO2 Carbon - Integration Core  SKIPPED
> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
> [INFO] WSO2 Carbon - UI styles ... SKIPPED
> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
> [INFO] WSO2 Carbon - Distribution  SKIPPED

Re: [Dev] Error building carbon

[Danushka Fernando]

Hi
Even in Maven 3 minor versions matters some times. There were some issues
with maven 3.1.x IIRC. If that's the case try with 3.0.5.

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Fri, Jul 18, 2014 at 12:01 PM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:

> Hi Nipuni,
>
> Build with a clean Maven repo using Maven3.
>
> Thanks !
>
>
> On Fri, Jul 18, 2014 at 11:51 AM, Harsha Kumara  wrote:
>
>> Hi Nipuni,
>> May be the maven version you using can be the issue here. What's your
>> maven version?
>> Thanks,
>> Harsha
>>
>>
>> On Fri, Jul 18, 2014 at 11:47 AM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> I am using java 6 and I have tried with a clean repo build. I got the
>>> following error stack trace.
>>>
>>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
>>> project wso2carbon-student-mgt-repository: P2 publisher return code was 13
>>> -> [Help 1]
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
>>> execute goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen
>>> (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2
>>> publisher return code was 13
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>> at
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>> at
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>> Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher
>>> return code was 13
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
>>> at
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>> at
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>> ... 19 more
>>> Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher
>>> return code was 13
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
>>> at
>>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
>>> ... 22 more
>>>
>>> Thanks,
>>> Nipuni
>>>
>>>
>>> On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando 
>>> wrote:
>>>
 Hi
 What is the java version you are using? Is it java 6 or java 7? If its
 7 try with java 6.

 Thanks & Regards
 Danushka Fernando
 Software Engineer
 WSO2 inc. http://wso2.com/
 Mobile : +94716332729


 On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera 
 wrote:

> Hi,
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
> [7:30.905s]
> [INFO] WSO2 Carbon - Integration . SKIPPED
> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
> [INFO] WSO2 Carbon - Integration Core  SKIPPED
> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
> [INFO] WSO2 Carbon - UI styles ... SKIPPED
> [INFO] WSO2 Carbon - Style Feature ... 

Re: [Dev] Error building carbon

[Manula Chathurika Thantriwatte]

Hi Nipuni,

Build with a clean Maven repo using Maven3.

Thanks !


On Fri, Jul 18, 2014 at 11:51 AM, Harsha Kumara  wrote:

> Hi Nipuni,
> May be the maven version you using can be the issue here. What's your
> maven version?
> Thanks,
> Harsha
>
>
> On Fri, Jul 18, 2014 at 11:47 AM, Nipuni Perera  wrote:
>
>> Hi,
>>
>> I am using java 6 and I have tried with a clean repo build. I got the
>> following error stack trace.
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
>> project wso2carbon-student-mgt-repository: P2 publisher return code was 13
>> -> [Help 1]
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen
>> (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2
>> publisher return code was 13
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>> at
>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>> at
>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>> Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher
>> return code was 13
>> at
>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210)
>> at
>> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
>> at
>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>> at
>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>> ... 19 more
>> Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher
>> return code was 13
>> at
>> org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
>> at
>> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
>> ... 22 more
>>
>> Thanks,
>> Nipuni
>>
>>
>> On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando 
>> wrote:
>>
>>> Hi
>>> What is the java version you are using? Is it java 6 or java 7? If its 7
>>> try with java 6.
>>>
>>> Thanks & Regards
>>> Danushka Fernando
>>> Software Engineer
>>> WSO2 inc. http://wso2.com/
>>> Mobile : +94716332729
>>>
>>>
>>> On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera  wrote:
>>>
 Hi,

 [INFO] Reactor Summary:
 [INFO]
 [INFO] WSO2 Carbon Core - Distribution ... FAILURE
 [7:30.905s]
 [INFO] WSO2 Carbon - Integration . SKIPPED
 [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
 [INFO] WSO2 Carbon - Integration Core  SKIPPED
 [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
 [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
 [INFO] WSO2 Carbon - Product Parent .. SKIPPED
 [INFO] WSO2 Carbon - UI styles ... SKIPPED
 [INFO] WSO2 Carbon - Style Feature ... SKIPPED
 [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
 [INFO] WSO2 Carbon - Distribution  SKIPPED
 [INFO] Distribution-Aggregate  SKIPPED
 [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 --

Re: [Dev] Error building carbon

[Harsha Kumara]

Hi Nipuni,
May be the maven version you using can be the issue here. What's your maven
version?
Thanks,
Harsha


On Fri, Jul 18, 2014 at 11:47 AM, Nipuni Perera  wrote:

> Hi,
>
> I am using java 6 and I have tried with a clean repo build. I got the
> following error stack trace.
>
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
> project wso2carbon-student-mgt-repository: P2 publisher return code was 13
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen
> (2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2
> publisher return code was 13
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher
> return code was 13
> at
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210)
> at
> org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher
> return code was 13
> at
> org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
> at
> org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
> ... 22 more
>
> Thanks,
> Nipuni
>
>
> On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando 
> wrote:
>
>> Hi
>> What is the java version you are using? Is it java 6 or java 7? If its 7
>> try with java 6.
>>
>> Thanks & Regards
>> Danushka Fernando
>> Software Engineer
>> WSO2 inc. http://wso2.com/
>> Mobile : +94716332729
>>
>>
>> On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
>>> [7:30.905s]
>>> [INFO] WSO2 Carbon - Integration . SKIPPED
>>> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
>>> [INFO] WSO2 Carbon - Integration Core  SKIPPED
>>> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
>>> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
>>> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
>>> [INFO] WSO2 Carbon - UI styles ... SKIPPED
>>> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
>>> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
>>> [INFO] WSO2 Carbon - Distribution  SKIPPED
>>> [INFO] Distribution-Aggregate  SKIPPED
>>> [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
>>> [INFO]
>>> 
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> 
>>> [INFO] Total time: 7:32.532s
>>> [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014
>>> [INFO] Final Memory: 33M/1217M
>>> [INFO]
>>> -

Re: [Dev] [Dev Studio] Adding mediators within a sequence doesn't get saved

[Viraj Rajaguru]

Hi Ishara,

Developer Studio does not allow you to put In/Out mediators inside any
arbitrary Sequence or any Proxy service. But if you create the main
sequence using DevS, it will contain In/Out mediators because we definitely
need In/Out mediators inside the main sequence.

This limitation was introduced because it is almost impossible to represent
the meaning of In/Out mediators inside a Sequence graphically. In/Out
mediators represent in path and out path and we may need to divide sequence
diagram into two parts to represent this forward and reverse message flow
if we allow In/Out mediators. After discussing with ESB team, we decided
not to support In/Out mediators for sequences except main sequence since
users have alternatives to accomplish this.
But I understand that there is a limitation in DevS according to the ESB
config specification.

You can use service chaining for your use case instead of In/Out mediators.

Thanks,
Viraj.


On Fri, Jul 18, 2014 at 9:57 AM, Ishara Premadasa  wrote:

> Hi,
>
> When i add the below config inside a sequence.xml file in Developer Studio
> 3.7.0, once the file is saved and open the source view back, all the
> configs are wiped out.
>
> http://ws.apache.org/ns/synapse"; name="TestSequence">
>
>   
>  
>   
>   
>  
> http://localhost:9764/jaxrs_starbucks_service/services/Starbucks_Outlet_Service/orders/
> ">
>  
>   
>
>
>   
>  
>   
>
> 
>
> However when use ESB UI editor to create this config it is supported there.
>
>
> ​
>
> May i please know how to create In,Out mediators from Dev studio, as i
> have several sequences which invokes external API endpoints at the  and
> need to get the response into .
>
> Thanks!
> Ishara
>
> --
> Ishara Premasada
> Software Engineer,
> WSO2 Inc. http://wso2.com/
>
>
> *Blog   :  http://isharapremadasa.blogspot.com/
> Twitter   :
> https://twitter.com/ishadil  Mobile   :
> +94 714445832 <%2B94%20714445832>*
>
>
>


-- 
Viraj Rajaguru
Software Engineer
WSO2 Inc. : http://wso2.com

Mobile: +94 77 3683068
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error building carbon

[Nipuni Perera]

Hi,

I am using java 6 and I have tried with a clean repo build. I got the
following error stack trace.

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen (2-p2-repo-generation) on
project wso2carbon-student-mgt-repository: P2 publisher return code was 13
-> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.wso2.maven:carbon-p2-plugin:1.5.3:p2-repo-gen
(2-p2-repo-generation) on project wso2carbon-student-mgt-repository: P2
publisher return code was 13
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: P2 publisher
return code was 13
at
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:210)
at
org.wso2.maven.p2.RepositoryGenMojo.execute(RepositoryGenMojo.java:191)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.plugin.MojoFailureException: P2 publisher
return code was 13
at
org.wso2.maven.p2.RepositoryGenMojo.generateRepository(RepositoryGenMojo.java:255)
at
org.wso2.maven.p2.RepositoryGenMojo.createRepo(RepositoryGenMojo.java:204)
... 22 more

Thanks,
Nipuni


On Fri, Jul 18, 2014 at 10:22 AM, Danushka Fernando 
wrote:

> Hi
> What is the java version you are using? Is it java 6 or java 7? If its 7
> try with java 6.
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
>
> On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera  wrote:
>
>> Hi,
>>
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
>> [7:30.905s]
>> [INFO] WSO2 Carbon - Integration . SKIPPED
>> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
>> [INFO] WSO2 Carbon - Integration Core  SKIPPED
>> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
>> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
>> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
>> [INFO] WSO2 Carbon - UI styles ... SKIPPED
>> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
>> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
>> [INFO] WSO2 Carbon - Distribution  SKIPPED
>> [INFO] Distribution-Aggregate  SKIPPED
>> [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
>> [INFO]
>> 
>> [INFO] BUILD FAILURE
>> [INFO]
>> 
>> [INFO] Total time: 7:32.532s
>> [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014
>> [INFO] Final Memory: 33M/1217M
>> [INFO]
>> 
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
>> (materialize-product) on project wso2carbon-core: Cannot generate P2
>> metadata: 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-ru

[Dev] using the tag in contextualizing the new option for dec_studio projects

[Awanthika Senarath]

Hi,

Im trying to contextualize the eclipse new project option in

 project (in projectExplorer) -> rightclick -> new -> wso2projects  (CEP
project/ proxy service etc.)

 to make it more meaningful.

I have been trying with the  tag inside the
  filtering by project nature
in plugin.xml with no success.

is there anyone who has previous experience in using this tag? OR any other
way of getting it done? I also tried with the property-tester in eclipse.

thanks and regards
-- 
Awanthika Senarath
Software Engineer, WSO2 Inc.
Mobile: +94717681791
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] What is the Role of an Identity Server on a single sign-on using OpenID

[Thanuja Jayasinghe]

Hi Dilan,

You can use Identity Server as an OpenID provider or relying party when It
comes to identity federation.

If you want to use IS as an OpenID provider, no configuration is needed in
IS side. So you can try the travelocity sample which can be checkout from
http://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/is/5.0.0/modules/samples/sso/

For federated identity, you have to register some other OpenID provider as
an identity provider in IS. Please go through Configuring OpenID section
at  http://docs.wso2.com/display/IS500/Adding+an+Identity+Provider. Feel
free to ask any question you come across.

Thanks,
Thanuja.


On Fri, Jul 18, 2014 at 6:02 AM, Dilan Udara Ariyaratne 
wrote:

> Hi everyone,
>
> I would like to inquire on what is the role of an Identity Server
> at the relying party's end with respect to authenticating users via OpenID.
>
> Appreciate if an elaboration can be given on how our own wso2 identity
> server
> works with OpenID...
>
> Thanks!
>
> *Dilan U. Ariyaratne*
> Software Engineer
> WSO2 Inc. 
> Mobile: +94775149066
> lean . enterprise . middleware
>



-- 
*Thanuja Lakmal*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94715979891
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error building carbon

[Danushka Fernando]

Hi
What is the java version you are using? Is it java 6 or java 7? If its 7
try with java 6.

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera  wrote:

> Hi,
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
> [7:30.905s]
> [INFO] WSO2 Carbon - Integration . SKIPPED
> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
> [INFO] WSO2 Carbon - Integration Core  SKIPPED
> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
> [INFO] WSO2 Carbon - UI styles ... SKIPPED
> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
> [INFO] WSO2 Carbon - Distribution  SKIPPED
> [INFO] Distribution-Aggregate  SKIPPED
> [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 7:32.532s
> [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014
> [INFO] Final Memory: 33M/1217M
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
> (materialize-product) on project wso2carbon-core: Cannot generate P2
> metadata: 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
>
> Thanks,
> Nipuni
>
>
> On Fri, Jul 18, 2014 at 9:47 AM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Hi,
>>
>> Can you put the full error log.
>>
>>
>> On Fri, Jul 18, 2014 at 9:44 AM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> I got following error when building carbon checked out from[1].
>>>
>>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
>>> (materialize-product) on project wso2carbon-core: Cannot generate P2
>>> metadata: P2 publisher return code was 13 -> [Help 1]
>>>
>>> [1] https://github.com/wso2-dev/carbon4-kernel
>>>
>>> Thanks,
>>> Nipuni
>>> --
>>> Nipuni Perera
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> Email: nip...@wso2.com
>>> Git hub profile: https://github.com/nipuni
>>> Mobile: +94 (71) 5626680
>>>  
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manu...@wso2.com / man...@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error building carbon

[Pulasthi Mahawithana]

Hi,

I was able to do a clean repo build of carbon from git yesterday. Since it
has not been changed for last 14 days, It may be due to one of your local
changes.

Can you include the log before "[INFO] Reactor Summary:" also?


On Fri, Jul 18, 2014 at 10:00 AM, Nipuni Perera  wrote:

> Hi,
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] WSO2 Carbon Core - Distribution ... FAILURE
> [7:30.905s]
> [INFO] WSO2 Carbon - Integration . SKIPPED
> [INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
> [INFO] WSO2 Carbon - Integration Core  SKIPPED
> [INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
> [INFO] WSO2 Carbon - Integration Tests ... SKIPPED
> [INFO] WSO2 Carbon - Product Parent .. SKIPPED
> [INFO] WSO2 Carbon - UI styles ... SKIPPED
> [INFO] WSO2 Carbon - Style Feature ... SKIPPED
> [INFO] WSO2 Carbon - Profile Generation .. SKIPPED
> [INFO] WSO2 Carbon - Distribution  SKIPPED
> [INFO] Distribution-Aggregate  SKIPPED
> [INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 7:32.532s
> [INFO] Finished at: Fri Jul 18 09:49:23 IST 2014
> [INFO] Final Memory: 33M/1217M
> [INFO]
> 
>
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
> (materialize-product) on project wso2carbon-core: Cannot generate P2
> metadata: 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
>
> Thanks,
> Nipuni
>
>
> On Fri, Jul 18, 2014 at 9:47 AM, Manula Chathurika Thantriwatte <
> manu...@wso2.com> wrote:
>
>> Hi,
>>
>> Can you put the full error log.
>>
>>
>> On Fri, Jul 18, 2014 at 9:44 AM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> I got following error when building carbon checked out from[1].
>>>
>>> [ERROR] Failed to execute goal
>>> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
>>> (materialize-product) on project wso2carbon-core: Cannot generate P2
>>> metadata: P2 publisher return code was 13 -> [Help 1]
>>>
>>> [1] https://github.com/wso2-dev/carbon4-kernel
>>>
>>> Thanks,
>>> Nipuni
>>> --
>>> Nipuni Perera
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> Email: nip...@wso2.com
>>> Git hub profile: https://github.com/nipuni
>>> Mobile: +94 (71) 5626680
>>>  
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manu...@wso2.com / man...@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pulasthi Mahawithana*
Software Engineer
WSO2 Inc., http://wso2.com/
Mobile: +94-71-5179022
Blog: http://blog.pulasthi.org
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error building carbon

[Nipuni Perera]

Hi,

[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 Carbon Core - Distribution ... FAILURE
[7:30.905s]
[INFO] WSO2 Carbon - Integration . SKIPPED
[INFO] WSO2 Carbon - Security Verification Service ... SKIPPED
[INFO] WSO2 Carbon - Integration Core  SKIPPED
[INFO] WSO2 Carbon - Integration Testing Framework ... SKIPPED
[INFO] WSO2 Carbon - Integration Tests ... SKIPPED
[INFO] WSO2 Carbon - Product Parent .. SKIPPED
[INFO] WSO2 Carbon - UI styles ... SKIPPED
[INFO] WSO2 Carbon - Style Feature ... SKIPPED
[INFO] WSO2 Carbon - Profile Generation .. SKIPPED
[INFO] WSO2 Carbon - Distribution  SKIPPED
[INFO] Distribution-Aggregate  SKIPPED
[INFO] WSO2 Carbon - Aggregate Pom ... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 7:32.532s
[INFO] Finished at: Fri Jul 18 09:49:23 IST 2014
[INFO] Final Memory: 33M/1217M
[INFO]

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
(materialize-product) on project wso2carbon-core: Cannot generate P2
metadata: 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

Thanks,
Nipuni


On Fri, Jul 18, 2014 at 9:47 AM, Manula Chathurika Thantriwatte <
manu...@wso2.com> wrote:

> Hi,
>
> Can you put the full error log.
>
>
> On Fri, Jul 18, 2014 at 9:44 AM, Nipuni Perera  wrote:
>
>> Hi,
>>
>> I got following error when building carbon checked out from[1].
>>
>> [ERROR] Failed to execute goal
>> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
>> (materialize-product) on project wso2carbon-core: Cannot generate P2
>> metadata: P2 publisher return code was 13 -> [Help 1]
>>
>> [1] https://github.com/wso2-dev/carbon4-kernel
>>
>> Thanks,
>> Nipuni
>> --
>> Nipuni Perera
>> Software Engineer; WSO2 Inc.; http://wso2.com
>> Email: nip...@wso2.com
>> Git hub profile: https://github.com/nipuni
>> Mobile: +94 (71) 5626680
>>  
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manu...@wso2.com / man...@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>


-- 
Nipuni Perera
Software Engineer; WSO2 Inc.; http://wso2.com
Email: nip...@wso2.com
Git hub profile: https://github.com/nipuni
Mobile: +94 (71) 5626680

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

[Dev] [Dev Studio] Adding mediators within a sequence doesn't get saved

[Ishara Premadasa]

Hi,

When i add the below config inside a sequence.xml file in Developer Studio
3.7.0, once the file is saved and open the source view back, all the
configs are wiped out.

http://ws.apache.org/ns/synapse"; name="TestSequence">
   
  
 
  
  
 
http://localhost:9764/jaxrs_starbucks_service/services/Starbucks_Outlet_Service/orders/
">
 
  
   
   
  
 
  
   


However when use ESB UI editor to create this config it is supported there.


​

May i please know how to create In,Out mediators from Dev studio, as i have
several sequences which invokes external API endpoints at the  and need
to get the response into .

Thanks!
Ishara

-- 
Ishara Premasada
Software Engineer,
WSO2 Inc. http://wso2.com/


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

Re: [Dev] Error building carbon

[Manula Chathurika Thantriwatte]

Hi,

Can you put the full error log.


On Fri, Jul 18, 2014 at 9:44 AM, Nipuni Perera  wrote:

> Hi,
>
> I got following error when building carbon checked out from[1].
>
> [ERROR] Failed to execute goal
> org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
> (materialize-product) on project wso2carbon-core: Cannot generate P2
> metadata: P2 publisher return code was 13 -> [Help 1]
>
> [1] https://github.com/wso2-dev/carbon4-kernel
>
> Thanks,
> Nipuni
> --
> Nipuni Perera
> Software Engineer; WSO2 Inc.; http://wso2.com
> Email: nip...@wso2.com
> Git hub profile: https://github.com/nipuni
> Mobile: +94 (71) 5626680
> 
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware

email : manu...@wso2.com / man...@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error building carbon

[Nipuni Perera]

Hi,

I got following error when building carbon checked out from[1].

[ERROR] Failed to execute goal
org.wso2.maven:carbon-p2-plugin:1.5.3:materialize-product
(materialize-product) on project wso2carbon-core: Cannot generate P2
metadata: P2 publisher return code was 13 -> [Help 1]

[1] https://github.com/wso2-dev/carbon4-kernel

Thanks,
Nipuni
-- 
Nipuni Perera
Software Engineer; WSO2 Inc.; http://wso2.com
Email: nip...@wso2.com
Git hub profile: https://github.com/nipuni
Mobile: +94 (71) 5626680

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

[Dev] Add NuwanW to automation project's white list

[Krishantha Samaraweera]

Hi Maheshika,

Please add NuwanW to white list of following projects.

1. carbon-platform-integration-utils
2. carbon-platform-integration
3. carbon-platform-automated-test-suite

Thanks,
Krishantha.

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

[Dev] Updating Jaggery "0.9.0.ALPHA4.wso2v6" into WSO2 repo

[Ayesha Dissanayaka]

Hi,

We have deployed the required changes into wso2 git repo.

Please find updated Jaggery "0.9.0.ALPHA4.wso2v6" in [01].
You can use this[01] now instead of earlier given forked-repo [02].

[01] https://github.com/wso2/jaggery/tree/0.9.0.ALPHA4.wso2v6
[02] https://github.com/ayshsandu/jaggery/tree/0.9.0.ALPHA4.wso2v6


Thank you!

-- 
*Ayesha Dissanayaka*
Software Engineer,
WSO2, Inc : http://wso2.com

20, Palmgrove Avenue, Colombo 3
E-Mail: aye...@wso2.com 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] What is the Role of an Identity Server on a single sign-on using OpenID

[Dilan Udara Ariyaratne]

Hi everyone,

I would like to inquire on what is the role of an Identity Server
at the relying party's end with respect to authenticating users via OpenID.

Appreciate if an elaboration can be given on how our own wso2 identity
server
works with OpenID...

Thanks!

*Dilan U. Ariyaratne*
Software Engineer
WSO2 Inc. 
Mobile: +94775149066
lean . enterprise . middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Pull Request - (TA-866) Intermediate TCP Client like tool to capture messages goes from ESB to backend and vice versa

[Krishantha Samaraweera]

Done..

Thanks,
Krishantha.


On Thu, Jul 17, 2014 at 8:56 PM, Amalka Subasinghe  wrote:

>
> Hi Krishantha,
>
> Please merge the pull request [1]
> [1] https://github.com/wso2-dev/carbon-platform-integration/pull/5
>
> Thanks
> Amalka
>
> --
>
> Amalka Subasinghe
>
> Senior Software Engineer
> WSO2 Inc.
> Mobile: +94 77 9401267
>



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

[Dev] Pull Request - (TA-866) Intermediate TCP Client like tool to capture messages goes from ESB to backend and vice versa

[Amalka Subasinghe]

Hi Krishantha,

Please merge the pull request [1]
[1] https://github.com/wso2-dev/carbon-platform-integration/pull/5

Thanks
Amalka

-- 

Amalka Subasinghe

Senior Software Engineer
WSO2 Inc.
Mobile: +94 77 9401267
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] BAM Daily Build - 17/07

[Ayash]

Thanks gokul :)


On Thu, Jul 17, 2014 at 6:49 PM, Gokul Balakrishnan  wrote:

> Please find the BAM pack built today at [1].
>
> The surefire reports for BAM can also be found in the same localtion.
>
> [1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/
>
> Thanks,
>
> --
> *Balakrishnan Gokulakrishnan*
> Software Engineer,
> WSO2, Inc. http://wso2.com
> Mob: +94 77 593 5789 | +1 650 272 9927
>



-- 
Ayashkantha Ramasinghe
Software Engineer WSO2, Inc.
email: ayashkan...@wso2.com ;
TP: +94 77 7 487 669
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] BAM Daily Build - 17/07

[Gokul Balakrishnan]

Please find the BAM pack built today at [1].

The surefire reports for BAM can also be found in the same localtion.

[1] https://svn.wso2.org/repos/wso2/people/gokul/bam/build/17-07/

Thanks,

-- 
*Balakrishnan Gokulakrishnan*
Software Engineer,
WSO2, Inc. http://wso2.com
Mob: +94 77 593 5789 | +1 650 272 9927
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Jaggery integration test module - Code coverage true Exception

[Dimuthu De Lanerolle]

Hi Krishantha,

I am getting the following error while trying to run Jaggery integration
tests after enabling code coverage feature.(true).
(Note that I have already updated filters.txt and instrumentation.txt file
with the latest entries for jaggery). However I am still getting this
exception. Seems like after instrumentation of jars only we are getting
this error. How can we fix this?

[2014-07-17 15:48:15,134]  INFO
{org.wso2.carbon.user.core.internal.UserStoreMgtDSComponent} -  Carbon
UserStoreMgtDSComponent activated successfully.

[2014-07-17 15:49:57,321]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
delayed due to the following unsatisfied items:
[2014-07-17 15:49:57,322]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
OSGiAxis2Service: org.jaggeryjs.jaggery.app.mgt-0.9.0.SNAPSHOT
[2014-07-17 15:50:57,321]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
delayed due to the following unsatisfied items:
[2014-07-17 15:50:57,321]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
OSGiAxis2Service: org.jaggeryjs.jaggery.app.mgt-0.9.0.SNAPSHOT
[2014-07-17 15:51:57,322]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
delayed due to the following unsatisfied items:
[2014-07-17 15:51:57,322]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
OSGiAxis2Service: org.jaggeryjs.jaggery.app.mgt-0.9.0.SNAPSHOT
[2014-07-17 15:52:57,321]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Carbon initialization is
delayed due to the following unsatisfied items:
[2014-07-17 15:52:57,321]  WARN
{org.wso2.carbon.core.init.CarbonServerManager} -  Waiting for required
OSGiAxis2Service: org.jaggeryjs.jaggery.app.mgt-0.9.0.SNAPSHOT
Fail to start carbon server
java.lang.RuntimeException: Port 9763 is not open
at
org.wso2.carbon.integration.common.utils.ClientConnectionUtil.waitForPort(ClientConnectionUtil.java:101)
at
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerManager.startServerUsingCarbonHome(CarbonServerManager.java:134)
at
org.wso2.carbon.integration.common.extensions.carbonserver.TestServerManager.startServer(TestServerManager.java:102)
at
org.wso2.carbon.integration.common.extensions.carbonserver.CarbonServerExtension.onExecutionStart(CarbonServerExtension.java:49)
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.wso2.carbon.automation.engine.extensions.TestNGExtensionExecutor.executeExtensible(TestNGExtensionExecutor.java:73)
at
org.wso2.carbon.automation.engine.testlisteners.TestExecutionListener.onExecutionStart(TestExecutionListener.java:47)
at org.testng.TestNG.runExecutionListeners(TestNG.java:1032)
at org.testng.TestNG.run(TestNG.java:983)
at
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:177)
at
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:92)
at
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:105)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74)Jaggery
integration test module - Code coverage true Exception

Regards
-- 
Dimuthu De Lanerolle
Software Engineer
WSO2 Inc.
lean . enterprise . middlewear.
http://wso2.com/
Tel. : +94 11 2145345  Fax : +94 11 2145300  email : dimut...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [G-Reg][integration-testing]Test status differ when ran alone and ran as packages

[Krishantha Samaraweera]

Every intermittent test failure has a reason which need bit of
patience figure what went wrong.  I'm petty much sure test classes executes
before the failure case causing this trouble. You need to isolate which
test class causing the failure when run in package.

Can you please check the following.

1. Check whether any other class use the same resources referred by failure
cases.
2. Check all resources are deleted correctly @AfterClass
3. Divide the test suite into two and include failure case to it and
execute (you need to include test classes to testng xml). Keep on dividing
test suite and try to find the exact test case casing the problem.


Thanks,
Krishantha.





On Thu, Jul 17, 2014 at 4:18 PM, Sameera Kannangara 
wrote:

> Hi all,
>
> I have following test cases which passes when ran alone, and fails when
> running as test packages.
>
> addWSDL(org.wso2.carbon.registry.jira.issues.test.Carbon11572TestCase):
> expected: but was:
>
> cleanup(org.wso2.carbon.registry.jira2.issues.test2.Registry633TestCase):
> Failed to perform delete operation
>
> Unlike previous similar case mentioned in the mail thread [1], these
> classes have "depends on" attributes added to @test annotations.
> repository used for testing is located at [2].
>
>
> Thank you,
> SameeraK.
>
> [1] [Dev][G-Reg][integration-testing] Interleaving test classes
> [2] https://github.com/sameerak/product-greg
>
>
> --
> Sameera Kannangara,
> Software Engineer,
> WSO2 Inc.
>



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

[Dev] [G-Reg][integration-testing]Test status differ when ran alone and ran as packages

[Sameera Kannangara]

Hi all,

I have following test cases which passes when ran alone, and fails when
running as test packages.

addWSDL(org.wso2.carbon.registry.jira.issues.test.Carbon11572TestCase):
expected: but was:
  cleanup(org.wso2.carbon.registry.jira2.issues.test2.Registry633TestCase):
Failed to perform delete operation

Unlike previous similar case mentioned in the mail thread [1], these
classes have "depends on" attributes added to @test annotations.
repository used for testing is located at [2].


Thank you,
SameeraK.

[1] [Dev][G-Reg][integration-testing] Interleaving test classes
[2] https://github.com/sameerak/product-greg


-- 
Sameera Kannangara,
Software Engineer,
WSO2 Inc.
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB] MediationTracerService is tightly coupled with MemoryAppender

[Gayashan Amarasinghe]

Hi all,

MediationTracerService [1] within the carbon-mediation repo is tightly
coupled with the MemoryAppender which is available in the carbon-kernel.
MediationTracerService is only reading the log. We believe this is not the
best way to achieve this. We can use a Logging Provider [2] available
within the carbon-utils to achieve this task.

WDYT?


​[1]
https://github.com/wso2-dev/carbon-mediation/blob/master/components/mediation-monitor/mediation-tracer/org.wso2.carbon.mediation.tracer/src/main/java/org/wso2/carbon/mediation/tracer/MediationTracerService.java
​

[2]
https://github.com/wso2-dev/carbon-utils/tree/master/components/logging/org.wso2.carbon.logging.service/src/main/java/org/wso2/carbon/logging/util

​Thanks.

/Gayashan​

-- 
*Gayashan Amarasinghe*
Software Engineer | Platform TG
WSO2, Inc. | http://wso2.com
lean. enterprise. middleware

Mobile : +94718314517
Blog : gayashan-a.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] dbscripts folder structure for BPS 3.5.0

[Nandika Jayawardana]

Looks good to me. Lets update with this stricture. Also we need to fix and
test the -Dsetup option.

Regards
Nandika


On Thu, Jul 17, 2014 at 2:44 PM, Hasitha Aravinda  wrote:

> Hi Team,
>
> We are going to use a separate database for activiti engine. So we will
> need to ship separate database scripts for activiti engine with BPS 3.5.0.
>
> In BPS 3.2.0 we have following structure.
>
> dbscripts
> ├── bps
> │  ├── derby.sql   <- BPEL and HT scripts .
> │  ├── 
> │
> ├── db2.sql  <- reg_um scripts
> ├── ...
>
> Proposed structure for BPS 3.5.0 as follows,
>
> dbscripts
> ├── bps
> │   ├── bpel  <- ODE and HT scripts .
> │   │   ├── create
> │   │   │  ├──  derby.sql
> │   │   │
> │   │   ├── truncate
> │   │   │   ├── (to be created)
> │   │   │
> │   │   ├── upgrade
> │   │├── 300_350
> │   │├── 310_350
> │   │
> │   ├── bpmn<- activiti related scripts.
> │  ├── create
> │  │  ├── activiti.db2.create.engine.sql
> │  │
> │  ├── drop
> │  │   ├── activiti.db2.drop.engine.sql
> │  │
> │  ├── upgrade
> │   ├── (empty since no upgrade scripts in initial
> version)
> │
> ├── db2.sql   <- reg_um scripts
> ├── ...
>
>
>
> Thanks
> Hasitha.
>
> --
> Hasitha Aravinda,
> Software Engineer,
> WSO2 Inc.
> Email: hasi...@wso2.com
> Mobile: +94 71 8 210 200
>
>


-- 
Nandika Jayawardana
Senior Technical Lead
WSO2 Inc ; http://wso2.com
lean.enterprise.middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Invitation: Code Review : APPMGR Enterprise Subscription @ Thu Jul 17, 2014 2pm - 2:30pm (Kasun Dissanayake)

[Kasun Dissanayake]

review notes:
 - Remove the class.forname() s for idp versions
 - Will be having a caching method to cache subscriptions so that we
can clean the cache when the admin revoke them.

Thanks and Regards




On Wed, Jul 16, 2014 at 2:01 PM, Rushmin Fernando  wrote:

> more details »
> 
> Code Review : APPMGR Enterprise Subscription
> *When*
> Thu Jul 17, 2014 2pm – 2:30pm Colombo
> *Where*
> LK 3rd Floor Meeting Room - Kernel (map
> )
> *Video call*
> https://plus.google.com/hangouts/_/wso2.com/code-review
> 
> *Calendar*
> Kasun Dissanayake
> *Who*
> •
> Rushmin Fernando - organizer
> •
> Jenananthan Yogendran
> •
> Thilini Shanika
> •
> Roshan Wijesena
> •
> Nuwan Dias
> •
> dev@wso2.org
> •
> Rajeeva Uthayasangar
> •
> Dinusha Senanayaka
> •
> Kasun Dissanayake
> •
> Sumedha Rubasinghe
> •
> Chamila Adhikarinayake
> •
> Ruwan Yatawara
>
> Going?   *Yes
> 
> - Maybe
> 
> - No
> *
> more options »
> 
>
> Invitation from Google Calendar 
>
> You are receiving this email at the account kas...@wso2.com because you
> are subscribed for invitations on calendar Kasun Dissanayake.
>
> To stop receiving these notifications, please log in to
> https://www.google.com/calendar/ and change your notification settings
> for this calendar.
>



-- 
Kasun Dissanayake
Software Engineer
WSO2 Inc.
Lean | Enterprise | Middleware
Tel - +94 77 086 2860
Skype - kasun.dissanayake4
LinkedIn - lk.linkedin.com/in/kasundis/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Carbon Component with Custom Exception Web Service

[Darshana Akalanka Pagoda Arachchi]

Hi,

I finally got it fixed. Thank you all for your support and specially
Gayashan for your time.


I changed two main things to get this working, yet still don't understand
what was the problem.

   1. Changed the service's exception package name from
   'com.wso2.axis2.exception' to 'com.wso2.orderproc.exception'.
   2. Removed the complete -ns2p argument from the wsdl2java command in the
   stub pom file.

Thanks.


On Thu, Jul 17, 2014 at 11:44 AM, Danushka Fernando 
wrote:

> You haven't specified the version in the pom for the artifact. This could
> be a reason for osgi cannot find the class.
>
>   Exported packages
> com.wso2.orderproc.service; version="*0.0.0*"[exported]
> com.wso2.axis2.orderproc.exception.xsd; version="*0.0.0*"[exported]
> com.wso2.orderproc.stub; version="*0.0.0*"[exported]
>
> Try adding *4.2.0* to the top level of the pom.
>
>
>
> Thanks & Regards
> Danushka Fernando
> Software Engineer
> WSO2 inc. http://wso2.com/
> Mobile : +94716332729
>
>
> On Thu, Jul 17, 2014 at 10:34 AM, Darshana Akalanka Pagoda Arachchi <
> darsha...@wso2.com> wrote:
>
>> Yes sure Gayashan. Here's the output from the commands.
>>
>>
>> osgi> ss com.wso2.orderproc.stub
>> "Framework is launched."
>>
>>
>> id State   Bundle
>> 16 ACTIVE  com.wso2.orderproc.stub_4.2.0
>> osgi> b 16
>> com.wso2.orderproc.stub_4.2.0 [16]
>>   Id=16, Status=ACTIVE  Data
>> Root=/home/akalanka/Programs/wso2carbon-4.2.0/repository/components/default/configuration/org.eclipse.osgi/bundles/16/data
>>   "No registered services."
>>   No services in use.
>>   Exported packages
>> com.wso2.orderproc.service; version="0.0.0"[exported]
>> com.wso2.axis2.orderproc.exception.xsd; version="0.0.0"[exported]
>> com.wso2.orderproc.stub; version="0.0.0"[exported]
>> *; version="0.0.0"
>>   No fragment bundles
>>   Named class space
>> com.wso2.orderproc.stub; bundle-version="4.2.0"[provided]
>>   No required bundles
>>
>>
>> osgi> diag 16
>> reference:file:../dropins/com.wso2.orderproc.stub-4.2.0.jar [16]
>>   No unresolved constraints.
>> osgi>
>>
>>
>>
>> On Thu, Jul 17, 2014 at 12:35 AM, Gayashan Amarasinghe > > wrote:
>>
>>> Hi Danushka,
>>>
>>> Can you also execute the following 2 commands in the osgi console and
>>> see the results?
>>>
>>> b 
>>> diag 
>>>
>>> Lets have a chat and figure this out tomorrow.
>>>
>>> /Gayashan
>>>
>>>
>>> On Wed, Jul 16, 2014 at 10:38 PM, Darshana Akalanka Pagoda Arachchi <
>>> darsha...@wso2.com> wrote:
>>>
 Hi Danushka,

 I checked the state as you mentioned and it gives me as it is active as
 well. Also I forgot to mention that the deployed components works fine
 unless I give it a wrong input to trigger the Custom Exception.

 osgi output

 osgi> ss com.wso2.orderproc.stub
 "Framework is launched."


 id State   Bundle
 16 ACTIVE  com.wso2.orderproc.stub_4.2.0



 On Wed, Jul 16, 2014 at 8:28 PM, Danushka Fernando 
 wrote:

> Hi
> Seems bundle is not loaded to the OSGi. So start the server with the
> option -DosgiConsole and when server is started in console press
> enter/return then it will promt the OSGi console which looks like follows.
>
> osgi>
>
> Then enter the command
>
> ss 
>
> This will show the status of the bundle in OSGi. Check [1] for the
> OSGi life cycle states.
>
> If it shown in the list and not in ACTIVE state that means some thing
> wrong with the bundle. You can figure it out using OSGi console.
>
> If it is not listed under as command that means you are doing
> something wrong in installing it. So for time being you can try dropping
> the jar to the repository/components/dropins folder.
>
> [1] http://en.m.wikipedia.org/wiki/OSGi#Life-cycle
> On Jul 16, 2014 6:11 PM, "Darshana Akalanka Pagoda Arachchi" <
> darsha...@wso2.com> wrote:
>
>> Hi Gayashan,
>>
>> I've attached the pom file of the stub bundle. The required class is
>> available in the jar file generated.
>>
>>
>> Thanks
>>
>> On Wed, Jul 16, 2014 at 6:00 PM, Gayashan Amarasinghe <
>> gayas...@wso2.com> wrote:
>>
>>> Hi Darshana,
>>>
>>> Have you properly exported the relevant package and imported the
>>> relevant packages within maven bundle plugin of each bundle? Seems like
>>> this is occurring because the required class is not available for the
>>> bundle's class path. If you can attach your pom files, would be easier 
>>> to
>>> find the issue.
>>>
>>> Thanks.
>>>
>>> /Gayashan
>>>
>>>
>>> On Wed, Jul 16, 2014 at 5:49 PM, Darshana Akalanka Pagoda Arachchi <
>>> darsha...@wso2.com> wrote:
>>>
 Hi,

 I am developing a carbon components which throws a custom Exception
 when necessary. The stub packaging also contains these custom 
 Exceptio

[Dev] dbscripts folder structure for BPS 3.5.0

[Hasitha Aravinda]

Hi Team,

We are going to use a separate database for activiti engine. So we will
need to ship separate database scripts for activiti engine with BPS 3.5.0.

In BPS 3.2.0 we have following structure.

dbscripts
├── bps
│  ├── derby.sql   <- BPEL and HT scripts .
│  ├── 
│
├── db2.sql  <- reg_um scripts
├── ...

Proposed structure for BPS 3.5.0 as follows,

dbscripts
├── bps
│   ├── bpel  <- ODE and HT scripts .
│   │   ├── create
│   │   │  ├──  derby.sql
│   │   │
│   │   ├── truncate
│   │   │   ├── (to be created)
│   │   │
│   │   ├── upgrade
│   │├── 300_350
│   │├── 310_350
│   │
│   ├── bpmn<- activiti related scripts.
│  ├── create
│  │  ├── activiti.db2.create.engine.sql
│  │
│  ├── drop
│  │   ├── activiti.db2.drop.engine.sql
│  │
│  ├── upgrade
│   ├── (empty since no upgrade scripts in initial
version)
│
├── db2.sql   <- reg_um scripts
├── ...



Thanks
Hasitha.

-- 
Hasitha Aravinda,
Software Engineer,
WSO2 Inc.
Email: hasi...@wso2.com
Mobile: +94 71 8 210 200
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Stuck Thread Detection valve works only if WARN logs are enabled

[Nipuni Perera]

Hi,

I will remove the if condition as in Azeez's solution, as there is no
performance gain having if condition in production environment.

Thanks,
Nipuni


On Thu, Jul 17, 2014 at 12:25 PM, Prasad Tissera  wrote:

> If you need to keep the if condition, something like following will do the
> job.
>
> if (log.isWarnEnabled()) {
> String msg = sm.getString(
> "stuckThreadDetectionValve.notifyStuckThreadDetected",
> monitoredThread.getThread().getName(), activeTime,
> monitoredThread.getStartTime(), numStuckThreads,
> monitoredThread.getRequestUri(), threshold);
> msg += ", tenantDomain=" + monitoredThread.getTenantDomain();
> // msg += "\n" + getStackTraceAsString(trace);
> Throwable th = new Throwable();
> th.setStackTrace(monitoredThread.getThread().getStackTrace());
> log.warn(msg, th);
>
> }
>
> monitoredThread.getThread().interrupt();
> monitoredThread.getThread().stop();  // TODO: Not a good practice, but we
> are using this as a last resort to kill rogue tenant threads
> activeThreads.remove(monitoredThread.getThread().getId());
>
> But as Azeez said, because at logging level always set at least to WARN
> that does not have any performance gain.
>
> Regards,
> Prasad.
>
>
> On Thu, Jul 17, 2014 at 12:09 PM, Afkham Azeez  wrote:
>
>>
>>
>>
>> On Thu, Jul 17, 2014 at 12:01 PM, Nipuni Perera  wrote:
>>
>>> Hi,
>>>
>>> Regarding the issue[1], handleStuckThread() method in class
>>> CarbonStuckThreadDetectionValve [2] interrupt threads only when warn logs
>>> are enabled.
>>>
>>
>> Generally. we set log level to INFO so this has been working fine. In
>> production, you will set the log level to at least WARN. However, it is
>> fine to remove that condition check.
>>
>>
>>> If the thread handling operations are handled outside the if block,
>>> stuck threads can be interrupted without user being informed. Is it
>>> preferred to kill threads without giving any warning?.
>>>
>>> [1] https://wso2.org/jira/browse/CARBON-14603
>>> [2]
>>> https://github.com/wso2-dev/carbon4-kernel/blob/master/core/org.wso2.carbon.tomcat.ext/src/main/java/org/wso2/carbon/tomcat/ext/valves/CarbonStuckThreadDetectionValve.java
>>>
>>> Thanks,
>>> Nipuni
>>>
>>> --
>>> Nipuni Perera
>>> Software Engineer; WSO2 Inc.; http://wso2.com
>>> Email: nip...@wso2.com
>>> Git hub profile: https://github.com/nipuni
>>> Mobile: +94 (71) 5626680
>>> 
>>>
>>>
>>
>>
>> --
>> *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 <%2B94%2077%203320919> 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
>>
>>
>
>
> --
> Prasad Tissera
> Software Engineer.
> Mobile : +94777223444
>



-- 
Nipuni Perera
Software Engineer; WSO2 Inc.; http://wso2.com
Email: nip...@wso2.com
Git hub profile: https://github.com/nipuni
Mobile: +94 (71) 5626680

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

[Dev] Apache CXF based reliable messaging samples/tutorials

[Sandamal Weerasinghe]

Hi,

I'm in the process of implementing reliable messaging for the WSO2 ESB
inbound endpoint which is implemented using Netty io. I've trying to find
good reference materials regarding $subject, but so far had little success.
Anyone has prior experience using Apache CXF? It would be great if someone
could point me towards some good reference material.

Thanks.

Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is there an API to retrieve the list of defined transports (receivers and senders) defined in Axis2 ?

[Isabelle Mauny]

Not an option Akila.. this must work OOTB :)
Will raise a requirement.

Isabelle.

-
*Isabelle Mauny*



On Thu, Jul 17, 2014 at 9:14 AM, Akila Ravihansa Perera 
wrote:

> Hi Isabelle,
>
> AFAIK, there is no SOAP API in Axis2 OOTB that you can use for what
> you need. But you can easily create a new Axis2 service that would
> expose an SOAP API to list available transports. You could achieve
> this by few lines of code.
>
> Thanks.
>
> On Thu, Jul 17, 2014 at 11:05 AM, Isabelle Mauny 
> wrote:
> > Hi Akila,
> >
> > Goal is to list available transports from 3rd party app (not running in
> > process with the ESB) - So we need an API (SOAP would work).
> >
> > Isabelle.
> >
> >
> > On Thu, Jul 17, 2014 at 4:01 AM, Akila Ravihansa Perera <
> raviha...@wso2.com>
> > wrote:
> >>
> >> Hi Isabelle,
> >>
> >> Do you mean an API exposed as a web service Or Java API?
> >>
> >> I presume you are referring to transports defined in axis2.xml when you
> >> say Axis2.
> >>
> >> Thanks.
> >>
> >> On 16 Jul 2014 14:44, "Isabelle Mauny"  wrote:
> >>>
> >>> $subject pls.
> >>>
> >>>
> -
> >>> Isabelle Mauny
> >>>
> >>>
> >>> ___
> >>> Dev mailing list
> >>> Dev@wso2.org
> >>> http://wso2.org/cgi-bin/mailman/listinfo/dev
> >>>
> >
>
>
>
> --
> Akila Ravihansa Perera
> Software Engineer
> WSO2 Inc.
> http://wso2.com
>
> Phone: +94 77 64 154 38
> Blog: http://ravihansa3000.blogspot.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Is there an API to retrieve the list of defined transports (receivers and senders) defined in Axis2 ?

[Akila Ravihansa Perera]

Hi Isabelle,

AFAIK, there is no SOAP API in Axis2 OOTB that you can use for what
you need. But you can easily create a new Axis2 service that would
expose an SOAP API to list available transports. You could achieve
this by few lines of code.

Thanks.

On Thu, Jul 17, 2014 at 11:05 AM, Isabelle Mauny  wrote:
> Hi Akila,
>
> Goal is to list available transports from 3rd party app (not running in
> process with the ESB) - So we need an API (SOAP would work).
>
> Isabelle.
>
>
> On Thu, Jul 17, 2014 at 4:01 AM, Akila Ravihansa Perera 
> wrote:
>>
>> Hi Isabelle,
>>
>> Do you mean an API exposed as a web service Or Java API?
>>
>> I presume you are referring to transports defined in axis2.xml when you
>> say Axis2.
>>
>> Thanks.
>>
>> On 16 Jul 2014 14:44, "Isabelle Mauny"  wrote:
>>>
>>> $subject pls.
>>>
>>> -
>>> Isabelle Mauny
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>



-- 
Akila Ravihansa Perera
Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +94 77 64 154 38
Blog: http://ravihansa3000.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev